[MAGNOLIA-6754] resource subnode not reflecting published changes Created: 02/Aug/16  Updated: 05/Feb/18  Resolved: 24/Aug/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.7, 5.4.8
Fix Version/s: 5.4.9

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Attachments: PNG File final-state.png     XML File magnolia_nodetypes.xml    
Issue Links:
relation
is related to MGNLACTIVATION-175 multiple publishing leaves page in "m... Closed
is related to PUBLISHING-34 multiple publishing leaves page in "m... Closed
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:
Sprint: Kromeriz 58
Story Points: 3

 Description   

To reproduce this issue:

  1. Edit /mtk/dialogs/components/image.yaml to be
    form:
      tabs:
        - name: tabImage
          fields:
            - name: image
              class: info.magnolia.ui.form.field.definition.BasicUploadFieldDefinition
              allowedMimeTypePattern: image.*
              label: Image
              binaryNodeName: image
              required: true
    actions:
      commit:
        class: info.magnolia.ui.admincentral.dialog.action.SaveDialogActionDefinition
      cancel:
        class: info.magnolia.ui.admincentral.dialog.action.CancelDialogActionDefinition
    
  2. Edit /mtk/templates/components/image.ftl
    [#assign rendition = imgfn.getImageVariationLinkFromBinary(content.image, "original")]
    <div><image src="${rendition}" /></div>
    
  3. Create a new page called imaging and assign it the basic template.
  4. Create a new image component with image A.
  5. Publish the imaging page. (v1.0)
  6. Edit the image component with image B.
  7. Publish the imaging page. (v1.1)
  8. Approve page v1.0 with image A and verify it on public.
  9. Approve page v1.1 with image B and see image A remains.

The final state of the page looked like this in the JCR Browser:

Here we can see all the states are incorrect.

I did verify the versions of each page looked good. It appears the issue is with the resources subnode of the component. It does get published upon first activation but on subsequent activation from the Pages app there is no change in the image. You must go to the JCR browser app and publish the resource node directly from there. Even after doing that the node still reflects the red state of un-activated.



 Comments   
Comment by Richard Gange [ 24/Aug/16 ]

To work around this issue:

  1. Shut down magnolia.
  2. Download magnolia_nodetypes.xml attached to this ticket.
  3. Move the new node types file into this folder /WEB-INF/config/repo-conf/nodetypes
  4. Edit the file /WEB-INF/config/default/repositories.xml an un-comment the customNodeTypes setting.
    <param name="customNodeTypes" value="WEB-INF/config/repo-conf/nodetypes/magnolia_nodetypes.xml" />
    
  5. Delete the file MAGNOLIA_HOME/repositories/magnolia/repository/nodetypes/custom_nodetypes.xml
  6. Startup magnolia
Comment by Richard Gange [ 24/Aug/16 ]

If you use db file system for your repo then your custom_nodetypes.xml will be inside the db.

Comment by Evzen Fochr [ 25/Aug/16 ]

Page stay in modified state see MGNLACTIVATION-135

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