Bug #51786
closed
Exception for non-migrated images, even so mount-point exists (6.1.3 -> 6.1.4)
Added by Simon Schick over 10 years ago.
Updated over 5 years ago.
Category:
File Abstraction Layer (FAL)
Description
I can't see the images anymore, that the user added to a record.
In this example I use tt_news (don't say it's old and shouldn't be used).
Even if I create a mount-point for the folder /uploads/pics/, it doesn't help.
As long as this isn't fixed, many, relying on extensions that haven't integrated their upload to FAL already, can't update.
Files
The tests here are as be-admin but do as well apply to restricted be-users.
- Category changed from 1394 to File Abstraction Layer (FAL)
- Status changed from New to Accepted
- Target version changed from 6.2.0 to next-patchlevel
Does work for admin be-users, but not for restricted be-users. Doesn't matter if the mount is browsable or not.
I can't even access the mounted folder in the Filelist module ... so .. can be that the reason for this not-working moved anywhere else ;)
Tested it on 6.1.4 and 6.1.5-DEV. Was not able to test it on master due to some extensions relying on some old code.
Simon, the fix was merged just some minutes ago to the 6.0 and 6.1 branches. If you would be so kind to retest with current "6.1-DEV" then (do a "git pull" before!) it would be great.
Plans are to release new patchlevel releases of 6.0 and 6.1 tomorrow.
- Status changed from Accepted to Resolved
Thanks for your feedback, Simon. This is now backported to 6.0 and 6.1 and solves some "inconsistencies". Will be part of the next patch level releases of 6.0 and 6.1. So this one is resolved too. :)
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
