[JIRA] Created: (HREPTWO-3358) Document templates should be valid after upgrade
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
[JIRA] Created: (HREPTWO-3358) Document templates should be valid after upgrade
by JIRA (Berry van Halderen)
::
Rate this Message:
Document templates should be valid after upgrade
------------------------------------------------ Key: HREPTWO-3358 URL: http://issues.onehippo.com/browse/HREPTWO-3358 Project: Hippo Repository 2 Issue Type: Improvement Affects Versions: r2.09.02 Reporter: Frank van Lankvelt Assignee: Frank van Lankvelt After an upgrade from 2.06.xx to 2.09, new instances of upgraded document types can be invalid. In particular, Xinha fields can cause validation messages to appear for non-mandatory fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.onehippo.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ HippoRepos-dev mailing list HippoRepos-dev@... http://lists.hippo.nl/mailman/listinfo/hipporepos-dev |
|
|
[JIRA] Updated: (HREPTWO-3358) Document templates should be valid after upgrade
by JIRA (Berry van Halderen)
::
Rate this Message:
[ http://issues.onehippo.com/browse/HREPTWO-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Westen updated HREPTWO-3358: ------------------------------------ Fix Version/s: r2.09.04 Should be fixed for 2.09.04. Problem does not hold for 2.10 since we rewrite required validation logic. > Document templates should be valid after upgrade > ------------------------------------------------ > > Key: HREPTWO-3358 > URL: http://issues.onehippo.com/browse/HREPTWO-3358 > Project: Hippo Repository 2 > Issue Type: Improvement > Affects Versions: r2.09.02 > Reporter: Frank van Lankvelt > Assignee: Frank van Lankvelt > Fix For: r2.09.04 > > > After an upgrade from 2.06.xx to 2.09, new instances of upgraded document types can be invalid. > In particular, Xinha fields can cause validation messages to appear for non-mandatory fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.onehippo.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ HippoRepos-dev mailing list HippoRepos-dev@... http://lists.hippo.nl/mailman/listinfo/hipporepos-dev |
|
|
[JIRA] Updated: (HREPTWO-3358) Document templates should be valid after upgrade
by JIRA (Berry van Halderen)
::
Rate this Message:
[ http://issues.onehippo.com/browse/HREPTWO-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rita Bijlsma updated HREPTWO-3358: ---------------------------------- Attachment: OK_Release7_2.xml KO_Release7_2.xml I also had the problem that I could not save a new document because of complains about missing mandatory fields, while there where no mandatory fields missing. I made the document again and clicked done a lot in between work (i.e. between copy-pasting text in it). At the third section the problem occurred. I deleted that section and everything was fine again. Then I recreated it and it was still fine. The same thing happened with a test file. Later, I added a section in the console by copying a section node from another document. Then in the CMS, I tried to add a title to the document. Then the problem reoccurred. I added the version of the document that was OK and the later version (a draft) that went knock out (KO). The OK file contains exactly the same content as I had added before and that then gave the problem. The only difference was that I added most of it without clicking 'done' in between and that I did not delete a 'bad' section in between. > Document templates should be valid after upgrade > ------------------------------------------------ > > Key: HREPTWO-3358 > URL: http://issues.onehippo.com/browse/HREPTWO-3358 > Project: Hippo Repository 2 > Issue Type: Improvement > Affects Versions: r2.09.02 > Reporter: Frank van Lankvelt > Assignee: Frank van Lankvelt > Fix For: r2.09.04 > > Attachments: KO_Release7_2.xml, OK_Release7_2.xml > > > After an upgrade from 2.06.xx to 2.09, new instances of upgraded document types can be invalid. > In particular, Xinha fields can cause validation messages to appear for non-mandatory fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.onehippo.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ HippoRepos-dev mailing list HippoRepos-dev@... http://lists.hippo.nl/mailman/listinfo/hipporepos-dev |
|
|
[JIRA] Commented: (HREPTWO-3358) Document templates should be valid after upgrade
by JIRA (Berry van Halderen)
::
Rate this Message:
[ http://issues.onehippo.com/browse/HREPTWO-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=73452#action_73452 ] Rita Bijlsma commented on HREPTWO-3358: --------------------------------------- I seem to have found a workaround: I add a point (.) in all empty Xinha fields. Then I can save. Then I remove all points and I can save again. The cause seems to be that Xinha fields have a required content child. However, as I described above, I also got to a state where I can save by removing the bad section (a child node), saving and recreating it. I only filled the title then, so the Xinha fields in it actually where empty. Still it worked OK. Bart seems to have worked around this bug by adding <br/> tags in all empty Xinha fields. They would not have to be removed. However, when I tried that solution, I got an errormessage that a node could not be deleted because it had been changed internally. From the CMS the document could not be saved, nor closed. The draft did not contain the change I had made before. I then deleted the draft in the console, while I was still logged in the CMS. It was still there in the CMS and I logout and in. It was still there. Then I found two 'live' variants in the console instead of a live and a draft. I deleted the second live and now things where normal again. Then I did my edit again and used the workaround described above. > Document templates should be valid after upgrade > ------------------------------------------------ > > Key: HREPTWO-3358 > URL: http://issues.onehippo.com/browse/HREPTWO-3358 > Project: Hippo Repository 2 > Issue Type: Improvement > Affects Versions: r2.09.02 > Reporter: Frank van Lankvelt > Assignee: Frank van Lankvelt > Fix For: r2.09.04 > > Attachments: KO_Release7_2.xml, OK_Release7_2.xml > > > After an upgrade from 2.06.xx to 2.09, new instances of upgraded document types can be invalid. > In particular, Xinha fields can cause validation messages to appear for non-mandatory fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.onehippo.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ HippoRepos-dev mailing list HippoRepos-dev@... http://lists.hippo.nl/mailman/listinfo/hipporepos-dev |
|
|
[JIRA] Commented: (HREPTWO-3358) Document templates should be valid after upgrade
by JIRA (Berry van Halderen)
::
Rate this Message:
[ http://issues.onehippo.com/browse/HREPTWO-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=73573#action_73573 ] Rita Bijlsma commented on HREPTWO-3358: --------------------------------------- Forget about finding two 'live' variants. That is normal. It is the state summary. The variants were published and draft. In one instance, the workaround with the point now gave me the same problems as with the <br/>. It was related to problems with a facetselect and I made another issue for that, which I linked to this one. > Document templates should be valid after upgrade > ------------------------------------------------ > > Key: HREPTWO-3358 > URL: http://issues.onehippo.com/browse/HREPTWO-3358 > Project: Hippo Repository 2 > Issue Type: Improvement > Affects Versions: r2.09.02 > Reporter: Frank van Lankvelt > Assignee: Frank van Lankvelt > Fix For: r2.09.04 > > Attachments: KO_Release7_2.xml, OK_Release7_2.xml > > > After an upgrade from 2.06.xx to 2.09, new instances of upgraded document types can be invalid. > In particular, Xinha fields can cause validation messages to appear for non-mandatory fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.onehippo.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ HippoRepos-dev mailing list HippoRepos-dev@... http://lists.hippo.nl/mailman/listinfo/hipporepos-dev |
|
|
[JIRA] Resolved: (HREPTWO-3358) Document templates should be valid after upgrade
by JIRA (Berry van Halderen)
::
Rate this Message:
[ http://issues.onehippo.com/browse/HREPTWO-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank van Lankvelt resolved HREPTWO-3358. ----------------------------------------- Resolution: Fixed Issue has been fixed in a different way; the validation no longer applies in this case. > Document templates should be valid after upgrade > ------------------------------------------------ > > Key: HREPTWO-3358 > URL: http://issues.onehippo.com/browse/HREPTWO-3358 > Project: Hippo Repository 2 > Issue Type: Improvement > Affects Versions: r2.09.02 > Reporter: Frank van Lankvelt > Assignee: Frank van Lankvelt > Fix For: r2.09.04 > > Attachments: KO_Release7_2.xml, OK_Release7_2.xml > > > After an upgrade from 2.06.xx to 2.09, new instances of upgraded document types can be invalid. > In particular, Xinha fields can cause validation messages to appear for non-mandatory fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.onehippo.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ HippoRepos-dev mailing list HippoRepos-dev@... http://lists.hippo.nl/mailman/listinfo/hipporepos-dev |
| Free embeddable forum powered by Nabble | Forum Help |
