Details

    • Branch Version/s:
      6.0.x
    • Backported to Branch:
      Committed
    • Liferay Contributor's Agreement:
      Accept
    • Similar Issues:
      Show 4 results 

      Description

      The case:

      The power user has a personal public page that uses global Structures/Templates to publish web contents.
      If i export this public pages and import the .lar in other power users, it duplicates the Structures/Templates in the user cummunity and doesn't uses the globals ones.
      This makes some bugs on the visualizations.

      P.S. I have the 6.0.5 but i have updated the lar dirs from thrunk, but the problem

        Issue Links

          Activity

          Hide
          Jelmer Kuperus added a comment -

          I've attached a patch that resolves the issue.

          This is how it works :

          When you do an import of a lar that contains templates / structures / articles that where global on the system where you did the export on.

          Then the importer will check if the same global entities can be found as a global resource on the system you do the import on AND if these entities have have not been changed

          if this is the case the existing global resource will be used. Otherwise the article / template / structure will be duplicated in the user's group

          This way you ensure that an export can still be imported on systems that do not have the global resources

          Show
          Jelmer Kuperus added a comment - I've attached a patch that resolves the issue. This is how it works : When you do an import of a lar that contains templates / structures / articles that where global on the system where you did the export on. Then the importer will check if the same global entities can be found as a global resource on the system you do the import on AND if these entities have have not been changed if this is the case the existing global resource will be used. Otherwise the article / template / structure will be duplicated in the user's group This way you ensure that an export can still be imported on systems that do not have the global resources
          Hide
          Jelmer Kuperus added a comment -

          Filippo, can you please verify the attached plugins patch?
          If this resolves the problem, please click the "Accept Contribution" link.

          Show
          Jelmer Kuperus added a comment - Filippo, can you please verify the attached plugins patch? If this resolves the problem, please click the "Accept Contribution" link.
          Hide
          Raymond Auge added a comment -

          Hey all,

          Thanks a lot for the contribution! We really appreciate it.

          However we decided to alter slightly the behavior. We will retain that to import/export content in the global scope that we use the portlet export mechanism of the portlets directly.

          e.g. Export global web content by going to the web content portlet in the global scope and exporting the portlet LAR, import into target system. Do this step before importing any group LARs which reference global web content.

          Otherwise we will behave pretty much just as you described:

          • look for an article first in the target group
          • if there is none (which there should not be) check the global scope
          • if there is one, use it, make sure the references are handled appropriately and don't import the one in the LAR
          • if there is no matching in the global scope, import the one in the LAR into the target group, make sure the references are handled appropriately
          Show
          Raymond Auge added a comment - Hey all, Thanks a lot for the contribution! We really appreciate it. However we decided to alter slightly the behavior. We will retain that to import/export content in the global scope that we use the portlet export mechanism of the portlets directly. e.g. Export global web content by going to the web content portlet in the global scope and exporting the portlet LAR, import into target system. Do this step before importing any group LARs which reference global web content. Otherwise we will behave pretty much just as you described: look for an article first in the target group if there is none (which there should not be) check the global scope if there is one, use it, make sure the references are handled appropriately and don't import the one in the LAR if there is no matching in the global scope, import the one in the LAR into the target group, make sure the references are handled appropriately
          Hide
          Justin Choi added a comment - - edited

          Tested in the following environments:
          1. Tomcat 6 + MySQL 5. IE8. 6.0.x. Revision 79079.
          2. Tomcat 6 + MySQL 5. IE8. 6.1.x. Revision 78885.

          Steps to reproduce.
          1. Select Global in the left drop down menu.
          2. Add a structure, template, and a web content entry in the Global section.
          3. Create another Power User.
          4. Go to My Public Pages and add a page and the Web Content Display portlet.
          5. Add another Web Content entry.
          6. Export this page as a LAR.
          7. Sign in as the newly created Power User and import this page.
          8. Once the page is imported, go to the Setup tab in the portlet's Configuration window. In the My Places menu, make sure that the entries under the global, My Sites, and Liferay communities are not mixed.

          The purpose of this test is to ensure that when a user creates web content using global structures and templates then exports as a LAR, the global structure and template are not duplicated in the user community when imported by another Power User. The global structure and template should remain distinct from the user community.

          Results: When signed in as the new user, I found the articles created in the different sites/communities remain distinct, that is, an article created with global structure and template is listed under the "global" menu and not anywhere else under the "My Places" search field in the configuration window. The previous error reported above does not exist any more in either 6.0.x or 6.1.x.

          Passed Manual Testing

          Show
          Justin Choi added a comment - - edited Tested in the following environments: 1. Tomcat 6 + MySQL 5. IE8. 6.0.x. Revision 79079. 2. Tomcat 6 + MySQL 5. IE8. 6.1.x. Revision 78885. Steps to reproduce. 1. Select Global in the left drop down menu. 2. Add a structure, template, and a web content entry in the Global section. 3. Create another Power User. 4. Go to My Public Pages and add a page and the Web Content Display portlet. 5. Add another Web Content entry. 6. Export this page as a LAR. 7. Sign in as the newly created Power User and import this page. 8. Once the page is imported, go to the Setup tab in the portlet's Configuration window. In the My Places menu, make sure that the entries under the global, My Sites, and Liferay communities are not mixed. The purpose of this test is to ensure that when a user creates web content using global structures and templates then exports as a LAR, the global structure and template are not duplicated in the user community when imported by another Power User. The global structure and template should remain distinct from the user community. Results: When signed in as the new user, I found the articles created in the different sites/communities remain distinct, that is, an article created with global structure and template is listed under the "global" menu and not anywhere else under the "My Places" search field in the configuration window. The previous error reported above does not exist any more in either 6.0.x or 6.1.x. Passed Manual Testing
          Hide
          Justin Choi added a comment - - edited

          Tested in the following environments:
          1. Tomcat 6 + MySQL 5. IE8. 6.0.x. Revision 79079.
          2. Tomcat 6 + MySQL 5. IE8. 6.1.x. Revision 78885.

          Passed manual testing.

          Show
          Justin Choi added a comment - - edited Tested in the following environments: 1. Tomcat 6 + MySQL 5. IE8. 6.0.x. Revision 79079. 2. Tomcat 6 + MySQL 5. IE8. 6.1.x. Revision 78885. Passed manual testing.

            People

            • Votes:
              8 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                4 years, 10 weeks, 3 days ago

                Development

                  Structure Helper Panel