Details
-
Bug
-
Resolution: Done
-
Critical
-
WCM 5.0 SP2
-
None
-
Sp217448
Description
Tested on the imported online demo.
If I enter the verisoning sub-engine (page properties from the home page), it directly try to put a lock on the whole site (before even having selected the choice of restoration or the pages to restore). Such a check is very time consuming (cf JAMON performance in screesnhot for a small site of 40 pages -to be tested on a large site of 10'000 pages).
So could we only acquire locks when displaying the AJAX sitemap and only for the selected pages (and perhaps the sub-page. I do not know how the versioning module works and if the non-selected sub-pages could be destroed or modified by a parent page modifications). But most of the time we do not need to lock the full site as we will only restore one section (e.g. the home page and one section below the home, but not all sections).
I also entered another JIRA in order to try to AJAX such locks as this also cause some display problem in the workflow sitemap (very slow).
TestRail: Results
Attachments
Issue Links
- is duplicated by
-
JAHIA-1956 Sp2: certain fields (page field, big text field;...) are not locked in read-only mode when a user (or the workflow) put a lock on the container
- Closed
-
JAHIA-1980 Performance: AJAX Move Sitemap: AJAX the LockRegistry.isAcquireable method as it is very slow
- Closed