Details
-
Bug
-
Resolution: Done
-
Major
-
WCM 5.0 SP3
-
None
-
SP3 18639
Description
I did a small site with two lang. I validated once my empty home page. Then I created a few other pages. Certain are translated, others not. Usually, when opening the worklfow engine, I can only select pages without any "blocking errors" (= pages whose title is transalted). I validated again my whole site.
Finally I restored the whole site at first validation (only my home page) and re-restored my whole site at the second validation time.
When I now open a workflow engine, I could perfectly select pages in all languages even if the title does not exist (and the warning is still present) in a given language. I do not know what we are testing in order to test if we need to display the radio button or not.. but something looks like incoherent with the "blocking errors" displayed in the Info column. So the check should nto be the same....
Of course this is impossible to validate such pages, which will always stay to red...
TestRail: Results
Attachments
Activity
Damien Saulnier
added a comment - 504 r20104
Same problem with pages created with a title in only one language, then moved
Damien Saulnier
added a comment - 504 r20104
Same problem with pages created with a title in only one language, then moved Problem: the problem encountered when resoring pages which are existing not in all languages. In this case an entry is created in the jahia_languages_states for page and language, where the page does not exist yet. Thus there is an inconstisency between jahia_languages_states and jahia_pages_data table.
Resolution: check once again if the object exists in the language, specified for jahia_languages_states
Actually, this is a general issue, with the inconsisency between the jahia_pages_data and jahia_languages_states.
I think, entries in the jahia_languages_states are updated not always correctly.
I was able to achieve the same inconsistency in another way (do not remember now, which one, but not using version restore)
There is a line in the org.jahia.services.workflow.WorkflowEventListener.myObjectChanged(WorkflowEvent):
if (mode != WorkflowService.INACTIVE)
{ service.storeLanguageState((ContentObjectKey) mainObject.getObjectKey(),languageCode,EntryLoadRequest.STAGING_WORKFLOW_STATE, mainObject.getSiteID()); }which update those entries not always correctly, i.e. it sometimes creates a language entry, which actually is not present. In such way the language state entry is present in the jahia_languages_states table, but there is no entry in the jahia_pages_data for this language.
I had to rollback the changes because of the side-effect JAHIA-2464
Resolution: do not store entry in the jahia_languages_states if the content object does not exist in the specified language
This is another problem, related to the move operation.
I have reported it as a separate issue (
JAHIA-2752) as it is not related to the data inconsistency between jahia_languages_states and jahia_pages_data tables. The entries are really created in the jahia_pages_data table after move.Should be some side-effect introduced after SP3.