Hi,
You're right, publication locks are not copied during the migration
process. There is no option to restore all locks in jahia 4.1 , but
we can help you writing a simple script that recreates them. On each
file, you can call JahiaWebdavBaseService.getInstance ().findUsages
(file.getPath (), jParams, true), and the just call file.lockFile
(true) if some usages are found. This can be quite long on 8Gb of
files, but this should recreate all locks on published files.
Thomas
Le 21 juil. 06 à 10:53, Fabrice Marchon a écrit :
Hi!
I am trying to upgrade from jahia version 4.0.7_01 to 4.1.1_01
using the
official patch. I have to migrate 8 Go of files for our production
server,
so that I try to be carefull as much as possible.
The patch has been applied successfully after some modifications of
the
original Slide 1 tables structure into our jahia database (running
on MySQL
4.0.27). In fact, there were some integrity problems that I have
corrected.
Full of motivation, I try the new Jahia 4.1, but when I use the Jahia
filemanager, I see that all locks on webdav files that are
published on
pages are gone, so that I (and all other users) can delete all
files without
any protection! I test the case of uploading some new files and the
latter
are locked after I have published them on a page.
So my question is how to restore the lost locks or how to create
them again
with the new slide 2 ?
It seems that the offical Jahia 4.1 patch simply drops the
jahia_slide_lock
table from the previous Slide 1.
Waiting for some help...
Regards,
Fabrice Marchon
