Publication fails when an Asset Publisher references a category from another Site

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.10 EE GA1, 6.2.X EE
• Fix Version/s: 6.2.X EE
• Component/s: Staging
• Labels:
  • ee-6.2.x-only
  • ee-ts
  • liferay-fixpack-portal-131-6210
• Branch Version/s:
  6.2.x
• Backported to Branch:
  Committed
• Story Points: 1
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal-ee/pull/15354

Steps to reproduce:

1. Setup two different 6.2 Liferay portals
2. On the first portal, create a Site (e.g. "Test Site")
3. Add a vocabulary and a category to this Site
4. On "Test Site", enable Remote Staging targeting a Site on the second portal
5. Publish your category to Live
6. Go to configuration of the default Site
7. Enable Remote Staging targeting a Site on the second portal
8. Go to the public page in Staging mode
9. Add an Asset Publisher to the page
10. Configure the Asset Publisher :

• Select the "Test Site" site
• Unselect the default site
• Filter with the following parameters:
  Contains Any of the following Categories
• Select the category from "Test Site"
  11. Save the configuration of the Asset Publisher
  12. Try to publish to Live

Result:

    An unexpected error occurred with the publication process. Please check your portal and publising configuration.
there-are-missing-references-that-could-not-be-found-in-the-live-environment
Category : News (Referenced by a Portlet: Asset Publisher)

This will be a unique fix for 6.2, since the feature introduced by LPS-48299 can't be backported.