When Asset Publisher is configured to filter based on Content Structures, these selections are lost when the site is published to remote

Description

Currently when the Asset Publisher portlet has a configured filter to WebContents structure this setup lost during the publishing when remote staging.

Activity

Show:

Michael Hashimoto July 23, 2012 at 3:18 PM
Edited

PASSED Manual Testing using the following steps:

  1. Setup 2 Servers. One Sending Server and one Recieving Server.

    • The Receiving Server must have the following portal-ext.properties:

  2. Startup both Servers.



  3. Recieving Server - Log in as the test@liferay.com

  4. Recieving Server - Navigate to "Control Panel -> Sites"

  5. Recieving Server - Add a Site

    • Recieving Server - Click Add

    • Recieving Server - Click Blank Site from the drop down menu

    • Recieving Server - Fill in the Name (Required) field

    • Recieving Server - Click Save

  6. Recieving Server - Copy the Site ID



  7. Sending Server - Log in as the test@liferay.com

  8. Sending Server - Navigate to "Control Panel -> Sites"

  9. Sending Server - Add a Site

    • Sending Server - Click Add

    • Sending Server - Click Blank Site from the drop down menu

    • Sending Server - Fill in the Name (Required) field

    • Sending Server - Click Save

  10. Sending Server - Activate Remote Staging to be pointing to the Recieving Server

    • Sending Server - Navigate to "Control Panel -> Site Settings -> Staging" in the Scope of the Sending Site

    • Sending Server - Fill in the Remote Host/IP field with the IP of the Recieving Server

    • Sending Server - Fill in the Port with 8080

    • Sending Server - Fill in the Remote Site ID with the value copied from Step 6

    • Sending Server - Check off the box Enabled On Public Pages

    • Sending Server - Click Save

  11. Sending Server - Add a Page to the Site

    • Sending Server - Navigate to "Control Panel -> Site Pages" in the Scope of the Sending Site

    • Sending Server - Click Add Page

    • Sending Server - Fill in the Name (Required) field

    • Sending Server - Click Add Page

  12. Sending Server - Click View Pages

  13. Sending Server - Add a "Web Content Display" portlet

    • Sending Server - Click Add

    • Sending Server - Click Web Content Display

  14. Sending Server - Add an "Asest Publish" portlet

    • Sending Server - Click Add

    • Sending Server - Click Asset Publisher

  15. Sending Server - Navigate to "Control Panel -> Web Content" in the Scope of the Sending Site

  16. Sending Server - Add a Structure

    • Sending Server - Click Manage

    • Sending Server - Click Structures from the drop down menu

    • Sending Server - Click Add Structure

    • Sending Server - Fill in the Name (Required) field

    • Sending Server - Click Add Row

    • Sending Server - Type text-field in the new row field

    • Sending Server - Select Text in the new row drop down

    • Sending Server - Click Save

    • Sending Server - Close the Structures pop-up window

  17. Sending Server - Add a Template associated with the newly created Structure

    • Sending Server - Click Manage

    • Sending Server - Click Templates from the drop down menu

    • Sending Server - Click Add Template

    • Sending Server - Fill in the Name (Required Field)

    • Sending Server - Click Select in the "Structure" section

    • Sending Server - Click on the newly created "Structure" in the pop-up

    • Sending Server - Click Launch Editor

    • Sending Server - Type the following into the Text Field in the pop-up:

    • Sending Server - Click Update

    • Sending Server - Click Save

    • Sending Server - Close the Templates pop-up window

  18. Sending Server - Add a Web Content associated with the newly created Structure

    • Sending Server - Refresh the Page

    • Sending Server - Click Add

    • Sending Server - Click the newly created "Structure" in the drop down

    • Sending Server - Fill in the Title (Required) field

    • Sending Server - Fill in the text-field field

    • Sending Server - Click Publish

  19. Sending Server - Navigate to the Sending Site's pages

  20. Sending Server - Select the newly created Web Content in the "Web Content Display" portlet

    • Sending Server - Click the Select Web Content icon

    • Sending Server - Click on the newly created Web Content in the pop-up

    • Sending Server - Click Save

  21. Sending Server - Configure the "Asset Publisher" to Filter for only the Web Content associated with the Structure created earlier

    • Sending Server - Click the Options icon

    • Sending Server - Click Configuration from the drop down

    • Sending Server - Select Web Content from the Asset Type section

    • Sending Server - Select the newly created "Structure" in the Web Content Subtype section

    • Sending Server - Click Save

    • Sending Server - Close the Asset Publisher - Configuration pop-up

  22. Sending Server - Click Mark as Ready for Publication

  23. Sending Server - Publish the Page to the Recieving Server

    • Sending Server - Click the arrow next to the Staging tab at the top

    • Sending Server - Click Publish to Remote Live Now

    • Sending Server - Click Publish in the pop-up

    • Sending Server - Click OK in the pop-up window

  24. Sending Server - Click Go to Remove Live



  25. Recieving Server - Notice that the Results of Asset Publisher are not displaying

  26. Recieving Server - Click the Options icon

  27. Recieving Server - Notice that the "Structure" is NOT selected in the Web Content Subtype section

Reproduced on:

Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 6451bff1433317bdec7182d4457b36a3cdcc0d60.

The Filter for a particular structure is NO longer selected in the Asset Publisher Portlet after being exported to a Remote Server.

Fixed on:

Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 09229fa9e7962bbce654d9b64d34bda4cc48d79d.

Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: c499af26e8051a0f5b975588dbb0641edf83d0d6.

The Filter for a particular structure is STILL selected in the Asset Publisher Portlet after being exported to a Remote Server.

Michael Saechang June 19, 2012 at 10:38 AM
Edited

Committed on:
Portal 6.2.x GIT ID: abae10ad2e421868e4e238b9693a783b414091ce.

Fixed

Details

Assignee

Reporter

Labels

Branch Version/s

6.1.x

Backported to Branch

Committed

Fix Priority

4

Git Pull Request

Story Points

Components

Affects versions

Priority

Zendesk Support

Created June 4, 2012 at 12:18 AM
Updated June 24, 2023 at 3:57 PM
Resolved October 3, 2012 at 3:41 PM
Loading...