Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-124827

Link to Page mappings of fragments point to staging on live

    Details

      Description

      Reproduction steps

      1. Setup Liferay portal
      2. Set up Staging→Local Live
      3. Create a structure TestStructure
      4. Add a Link to Page field→Save
      5. Create a template TestTemplate
      6. For the Structure, select TestStructure
      7. Click on the Link to Page in the list
      8. Delete the HTML part, only the code should remain, e.g.
        ${LinkToPagefoa9.getFriendlyUrl()}
      9. Create a page destination→Publish
      10. Create a new web content using TestStructure, with the title TestWebContent
      11. Select destination as Link to Page→Publish
      12. On the Home page, add a Banner→click on the Go Somewhere button
      13. Under Selection click on 03-link
      14. Link: From Content Field
      15. Content: with the + sign, select TestWebContent
      16. Field: TestTemplate
      17. Click on Publish
      18. Check that clicking on the Go Somewhere button redirects to the destination page (it should)
      19. Click on Publish to Live
      20. Go to the Live version
      21. Click on the Go Somewhere button on the Home page

      Expected Behavior
      We are redirected to the Live destination page.

      Actual Behavior
      We are redirected to the Staging destination page.

      Additional Information

      • I only received the errors on the branch.
      • The 7.3.x code in FragmentEntryLinkExportImportContentProcessor.replaceImportContentReferences(..) tries to replace the references in a JSON content like this:
        "link":{
        	"defaultValue":"\n\t\tGo Somewhere\n\t",
        	"en_US":"Go Somewhere Test",
        	"config":{
        		"classPK":"39254","className":"com.liferay.journal.model.JournalArticle",
        		"classNameId":"20131","fieldId":"ddmTemplate_39191"
        	}
        }
        

      Since the actual "className" key is inside "config", it won't be found and won't be replaced.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              yang.cao Yang Cao
              Reporter:
              vendel.toreki Vendel Töreki
              Participants of an Issue:
              Recent user:
              Clarissa Velazquez
              Engineering Assignee:
              Vendel Töreki
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                14 weeks, 2 days ago

                  Packages

                  Version Package
                  7.2.10 DXP FP12
                  7.2.X
                  7.3.X
                  7.3.10 DXP FP1
                  7.3.10.1 DXP SP1
                  7.3.6 CE GA7
                  Master