Our workaround is to create a copy of the image using the "Extended
Image Editing Options" in the Asset Manager, and where it asks
"Replace original file/Create new file" choose the latter.
However we uncovered a bug in the version of CMS we were using at the
time (7.5.1.xx). Strange things happe
Are they in the database or in the filesystem?
I guess filesystem.
If so, the filename is the unique identifier.
Change the filename local and then change it to the same in the
database IO_THB in THB1
That should do it.
Do a backup before, do some testing!
If you developed some nice scripts doing
I would be very interested in seeing responses to this myself - we are
in the midst of renaming a couple thousand files in Asset Manager as well.
The process that we are currently using consists of a copy of the Assets
directory, and providing users responsible for renaming access to this
copy
I have become inured to the bizarre nature of Asset manager but here
is a new one.
Because we are going to a flat folder structure with no sub-folders,
we've instituted a naming convention. Users want to re-name their
assets.
It appears that there is no way to re-name a file in Asset manager.
That
