Updating last publish date creates incorrect portlet preferences

• Type: Bug
• Status: Closed
• Resolution: No Longer Reproducible
• Affects Version/s: 6.2.X EE, 7.0.0 M3
• Fix Version/s: 7.0.0 Alpha 4
• Component/s: Portal Services, Portal Services > Configuration Management, Portal Services > Configuration Management > Portlets, Staging
• Labels: None
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/21157

1. Start up portal and turn on local staging for the default site
2. After the initial publication is complete, query the Portletpreferences table from the database

Result: There will be a few portlet preferences that have ownertype as 3 (layout) but have 0 as plid. These type of preferences should not exist. This is causing issues e.g. when executing 2 staging publications for separate sites in parallel, because both of them would want to read/write these preferences.

The cause of the issue is that even though the affected portlet preferences are queried as strict portlet preferences (which means they should not be created in the database if they are not found), the process of updating the last publish date calls their store() procedure later, which adds them to the database with incorrect parameters after all.