[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. 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: That means that in first element, the "condition" and node "00" was written as folder- "mgnl:content" 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: We published the content by activating whole page with option "Publish incl. subpages". 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,
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. |