We’ve recently updated to 2.5.3 (20120911) from 2.5.2 and noticed a problem and I just wanted put this out there to see if this could have been the update, or something else.
Basically, we have a required image field in an entry that was originally published by a Super Admin user. Previously, when other users from a different group have updated this entry, there’s been no problem, however, since the update last week, the client has reported a problem when editing the entry.
When they went to update it, it was getting thrown back because the required image field was empty. When I logged in as a Super Admin, I could see the image in the entry, but it wasn’t showing on the site. Logging in as a regular I could see that the image field was empty. The regular user didn’t have access to the specific upload directory specified for the image (which would explain why the field was empty).
What looks to be happening here is that when the entry was previously updated, EE didn’t care about whether the existing file could have been uploaded by the current user or not. Perhaps now its saying that I’ll show this entry on the front end, but not the image because the user who last updated the entry doesn’t have permission to access that file directory.
Is this likely/possible?
Andrew