Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Global structure and templates are able to be deleted despite community/organization using the global structure and template

Description

Replicated in 6.0.10, 6.0.11, 6.0.12, 6.0.x (Rev. 97203) and Trunk (Rev. 97203)

Steps to Reproduce:
1. sign in as test@liferay.com
2. Navigate to Control Panel
3. Set the scope to "Global"
4. Create a structure and template in the "Global" scope
5. Navigate to the guest community scope "liferay.com"
6. Create a web content article using the Global structure and template
7. Navigate back to the Global structure and template and delete them
8. User will be able to delete the structure and template

If a customer attempts to upgrade, will have a No JournalStructure exception which will stop the upgrade.
9. Shut down the server
10. Enable the portal-ext.properties property: "verify.frequency=-1"
11. Restart the server and there will be an unexpected startup error

NOTE: "verify.frequency=-1" works if global structure and template aren't deleted and a community web content uses the structure and template

If disabling the "verify.frequency=-1" property:
12. The server will start up with no exceptions
13. Add another structure and template in the "Global" scope
14. Add a web content article in the "Global" scope
15. When trying to delete the structure and template, user will be unable to
16. Follow steps 13-15 for community scope, will be unable to delete structures and templates

Activity

Show:

Matthew Kong January 16, 2012 at 4:31 PM

Please ignore my previous comment.

Matthew Kong January 12, 2012 at 3:56 PM

The fix for 6.0.x has been implemented differently so it does not require database changes. However, it does not cover all the cases. The limitation to the 6.0.x fix occurs when all of these conditions are met:
1. Site structure is created and it's parent is a global structure
2. No articles and templates are using this global structure
3. User tries to delete the global structure

Pani Gui January 11, 2012 at 6:06 PM

PASSED Manual Testing following steps in description.

Fixed on:
Tomcat 6.0 + MySQL 5. 6.0.x GIT ID: 5f04a61fdd0f764c466a055fd4a373bde26089c3.

The global structure and template are unable to be deleted if they are referenced by a web content.

Pani Gui January 10, 2012 at 1:03 AM
Edited

PASSED Manual Testing following steps in description.

Reproduced on:
Tomcat 6.0 + MySQL 5. 6.0.12 EE.
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 345193895dfe4cab689db540c7238881877845f5.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 65450046dcbb21c793742e9d0cdc0942d7b6f5a1.

The global structure and template can be deleted even though they are referenced by a web content in a community or organization.

Fixed on:
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 538c5571b34ff4fba8579db4fb562a1580779d51.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: b0200b1f1ea5d788d825afa9b3bd9a4a26f79915.

The global structure and template are unable to be deleted if they are referenced by a web content.

Michael Saechang January 9, 2012 at 11:19 AM

Committed on:
6.1.x GIT ID: 55de52b32605deada15d9a93e5066e574886904e.
6.2.x GIT ID: cc0cc11d3b55efe4ae537a58bc3f88c663bd96d8.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Branch Version/s

6.1.x
6.0.x

Backported to Branch

Committed

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created January 4, 2012 at 10:41 AM
Updated June 24, 2023 at 3:46 PM
Resolved March 12, 2012 at 1:39 PM