-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with mediafinder generated links on October installed on subfolder after update to build 467 #5204
Comments
@fgschafer I've added a note to the config file about how to properly handle this: 5a5208b |
I second this. Any word on a permanent fix? |
@adrian-stein you'll need to follow @LukeTowers notes and adjust your configuration accordingly. |
@fgschafer @adrian-stein does it work if you set your app.url to correctly include the subfolder and leave the uploads and media URLs unchanged? |
Indeed the initial issue that motivated that comment in the documentation was that the thumbnail previews on the backend mediafinder widget were not working WITH the app_url set WITH the subfolder and link policy left on the default (detect). The subfolder was missing in the url of the image preview.
|
@fgschafer Thanks for clarifying, but I did not encounter that issue in the scenario you stated. The image preview appeared just fine for me. |
@bennothommo Thanks. The issue is for example here.
|
I have changed the 'linkPolicy' to be 'force' and left the media_path and uploads_path and app.url untouched and it works. |
I noticed that after updating to build 467, the mediafinder generated links don't work unless the link policy is set to "force" if October is installed in a subfolder. It would be nice to have proper support for relative links in this situation too.
The text was updated successfully, but these errors were encountered: