You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a ? character is added to Advanced -> Folder Name, it will cause errors to be thrown when uploading images. The images appear after removing the ? from the folder name. It is possible that other characters cause issues as well.
Steps to Reproduce:
Create a modular with a folder name containing a ? along with other alpha-numeric characters.
Save the page and attempt to upload images.
An error appears: move_uploaded_file([path to file *without* a ?]/image.jpg): failed to open stream: No such file or directory
Remove ? from Folder Name
Images upload smoothly.
The text was updated successfully, but these errors were encountered:
The problem is ? is a special character. We should disallow changing a folder name (or creating a new one) to contain ? in the first place, as it's going to be interpreted by the browser unless urlencoded. The problem seems linked to the fact you can first save as yourfolder? but then saving a second time, without any other change, the folder is back to yourfolder.
Obviously someone could set the folder name to include a ? but in this case everything was done through the admin panel. It seemed to me that it shouldn't let any invalid characters be saved.
Or, as a possible alternative, what about automatically swapping any unacceptable characters out for - to make it URL friendly. I'm thinking of something like this:
Overview
If a
?
character is added toAdvanced -> Folder Name
, it will cause errors to be thrown when uploading images. The images appear after removing the?
from the folder name. It is possible that other characters cause issues as well.Steps to Reproduce:
?
along with other alpha-numeric characters.move_uploaded_file([path to file *without* a ?]/image.jpg): failed to open stream: No such file or directory
?
fromFolder Name
The text was updated successfully, but these errors were encountered: