[MGNLFORM-220] When publishing content from authoring to public instance content is not copied into JCR Created: 13/Nov/13  Updated: 28/Jan/14  Resolved: 28/Jan/14

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 2.2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Maja Assignee: Jan Haderka
Resolution: Not an issue Votes: 0
Labels: maintenance, next
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

On authoring instance we created page with form(formSelection, formSubmit, formCondition) component. We also created conditionList with all the conditions for page navigation which worked properly on authoring instance. When publishing it to public instance, content from JCR (conditionList - all the conditions) was not copied to public instance. Therefore, we had to export the content from autor instance manually and import it to public instance.



 Comments   
Comment by Jan Haderka [ 27/Jan/14 ]

Hi Maja,

could you please provide version of Form module and Magnolia w/ which you had the issue? You can find version numbers if you go to Configuration and look under /modules/core and /modules/form.
Also, could you please confirm how you published the content? Did you do it by activating whole page from the pages app or from JCR Brower?
And last but not least - did you actually confirm that the condition list was not activated before importing it to public manually, or did you think it was not activated because of the status icon in JCR Browser for the condition list? (MAGNOLIA-5626).

Thanks for the info.

Comment by Maja [ 28/Jan/14 ]

Hello,

First of all thank you for your feedback, I think we already found out the cause of our problem.

Recently we changed some of our templates's structure, so we had inconsistance in JCR's data structure which then lead to the problem of publishing.

Let me give you more detailed description:
When looking at exported content of our condition list, we found out that there was a problem with structure:

That means that in first element, the "condition" and node "00" was written as folder- "mgnl:content"
but in second element we had the "condition" and node "00" written as node - "mgnl:contentNode"

The node with "mgnl:content" did not copy on public instance. So as I said before, the structure was not correct and that was probably the reason it didn't copy.

About the version of Magnolia:
core version is 5.2.1 and form version is 2.2.1.

We published the content by activating whole page with option "Publish incl. subpages".
The status of our page in pages app was activated, we did not have problem with bug MAGNOLIA-5626.

We will test publishing again making sure that data structure will be correct in JCR, and we will report if we find out about any problem with publishing again.

Thank you.

Comment by Jan Haderka [ 28/Jan/14 ]

Hi Maja,

The node with "mgnl:content" did not copy on public instance. So as I said before, the structure was not correct and that was probably the reason it didn't copy.

This is indeed the case. mgnl:content is a super type of mgnl:page and any node of this type will be considered by system to be a separate page/entity for activation purposes so this indeed explains why you could not activate it.

I'm glad to hear you were able to resolve the issue in the mean time. I'm closing this ticket, but please do not hesitate to reopen it or to create new one in case you reproduce the problem or run into another.

Generated at Mon Feb 12 05:38:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.