Table of Contents
Troubleshooting widget integrations
01. April 2025
Table of Contents
Problem
"App not registered" and kitten when opening /fotoweb/widgets/selection!
Cause
You are trying to use the widget in the legacy way (without any URL parameters (no access token)) when it is not enabled.
Remedy
Problem
"App not registered" and kitten when opening the FotoWeb OAuth URL (/fotoweb/oauth2/authorize/...)
Cause
Your application is not registered, or you are using the wrong redirect URL in the authorization request.
Remedy
Register your app using the correct redirect URI and use that redirect URI in the request:
Application registration using OAuth_2.0
Tip
If your app is registered with only one redirect URI, then you don't need to explicitly specify it in the authorization request. Not specifying it eliminates the problem of using the wrong one.
Tip 2
The redirect URL must be exactly as registered: Same path, same protocol (HTTPS vs. HTTP. I hope you are using HTTPS...). Query string parameters and fragments are not allowed.
Problem
The FotoWeb OAuth URL (/fotoweb/oauth2/authorize/...) requires a client ID. What is the client ID?
Cause
Your application is not registered, so there is no client ID, yet.
Remedy
Register your app, and you get a client ID:
Application registration using OAuth2.0.
Problem
My integration broke when I updated to FR12
Cause
Your integration is using the widget in the legacy way when it is not enabled.
Remedy
Either enable "Legacy selection widget" in the site settings, or update your integration to use the new (more secure) way: Using embeddable widgets
Problem
My integration still works after FR12 (with legacy enabled), but it looks ugly / I don't like it
Cause
We had to change the user experience to make it work with OAuth.
Remedy
Update your integration to use the new way. It will give you more freedom to determine the user experience for user authorization. See Using embeddable widgets. We are happy to help you migrate!
Problem
Instead of the selection widget, I only see a blank white box.
Cause 1
You are embedding the selection widget in an iFrame in an app that uses HTTPS, but FotoWeb does not use HTTPS.
Remedy 1
Configure FotoWeb to use HTTPS and open the selection widget using a HTTPS URL.
Cause 2
You are opening the FotoWeb OAuth URL (/fotoweb/oauth2/authorize/...) in an iFrame.
Remedy 2
You can only open the FotoWeb OAuth URL in a top-level browser window or tab. Either open it in the current window, or in a new browser tab or window and use local storage to get hold of the access token. See the iFrames section in Using the widgets.
Problem
Instead of the selection widget, I see a white box with a Log in to FotoWeb button.
Cause
You are trying to use the widget in the legacy way (without any URL parameters (no access token)).
Remedy
For information on how to use the widget, see Using embeddable widgets.
Alternative remedy
If you intend to use the legacy way, then this is the way it works. The user has to log in by clicking the button. If you don't like this, you can use the new way.