Type: Regression Bug
Affects Version/s: 7.0.X, Master
Steps to reproduce:
- Start a vanilla installation (System A) and create a new site (site A)
- Clone the database of a vanilla installation
- Set this database in a second vanilla installation (System B)
- Enable remote staging between site A of both Systems
Expected: Staging could be enabled
Can't enable remote staging between 2 sites, "Your request failed to complete.
Unable to activate remote staging on site with ID XXXX. The remote live site must be different from the stage site."
This is produced by logic introduced in
LPS-63724 that tries to prevent enable staging using the same site but breaks the use case of the cloned databases. Anyway, we could understand the original bug as a wrong use of the product since in the documentation (see https://dev.liferay.com/es/discover/portal/-/knowledge_base/7-0/enabling-staging) we could see the following information:
The remote (live) Liferay server and the local (staging) Liferay server should be completely separate systems. They should not, for example, share the same database.
Since two systems with cloned databases are not using the same database and are completely separate systems, we are breaking this behaviour.
Our suggestion is to rollback
LPS-63724 logic and modify the documentation to make this case even clearer.