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 you rename an asset indirectly in the Git repo from an all lowercase to all uppercase, Studio doesn't correctly ingest the change and removes the original asset but doesn't add the new asset.
CI: 4959
Steps to reproduce
Steps:
Create a site based in Editorial
Update the Project Policy to not transform all filenames to lowercase
Upload an image in all lowercase under /static-asset/images (e.g. mountains.jpg).
Using the CLI, rename the image to all uppercase (e.g. mv mountains.jpg to MOUNTAINS.jpg)
Commit the change
If you go to the sidebar, you'll see that the image dissapeared from the sidebar.
Relevant log output
No response
Screenshots and/or videos
No response
The text was updated successfully, but these errors were encountered:
A rename is read from git as a CREATE and a DELETE in a different path. So Studio creates an item in MOUNTAINS and deletes the one in mountains.
Problem is that by default, MariaDB is case-insensitive. So both (upper case and lower case) version of the name are the same path for the database.
The opposite (upper case to lower case) seems to work because of getting the operations in reverse order (delete then create).
One possible solution would be to process all deletes first.
Duplicates
Latest version
Describe the issue
If you rename an asset indirectly in the Git repo from an all lowercase to all uppercase, Studio doesn't correctly ingest the change and removes the original asset but doesn't add the new asset.
CI: 4959
Steps to reproduce
Steps:
/static-asset/images
(e.g.mountains.jpg
).mv mountains.jpg to MOUNTAINS.jpg
)If you go to the sidebar, you'll see that the image dissapeared from the sidebar.
Relevant log output
No response
Screenshots and/or videos
No response
The text was updated successfully, but these errors were encountered: