-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.X EE, 7.0.0 Alpha 1
-
Fix Version/s: 6.2.4 CE GA5, 6.2.X EE, 7.0.0 Alpha 2
-
Component/s: Staging, Staging > Export/Import
-
Labels:
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Story Points:9
-
Fix Priority:3
-
Git Pull Request:
Steps to reproduce with JournalFolder
- Create a new site
- Create a JournalFolder into webcontent, called "Test"
- Create a JournalArticle into previous created "Test" JournalFolder
- Export site to a LAR file
- Delete JournalFolder "Test" and empty the recycle bin
- Create another JournalFolder into webcontent, called "Test"
- Import LAR file to site with old JournalFolder called "Test"
- Wrong behavior: During document import, "Test" JournalFolder cannot imported as other folder with name "Test" already exists and a duplicate exception is thrown. LAR is not imported
- Expected behavior: During document import, due of name collision with existing JournalFolder "Test", new JournalFolder "Test" is renamed into "Test (2)". LAR is successfully imported
- Wrong behavior: During document import, "Test" JournalFolder cannot imported as other folder with name "Test" already exists and a duplicate exception is thrown. LAR is not imported
- is a dependency of
-
LPS-54233 Renaming of JournalFolder and creation of a new one with Staging causes com.liferay.portlet.journal.DuplicateFolderNameException during publish to Live. This issue is also reproduced during some LAR imports
- Closed
- relates
-
LPE-14389 Exception is thrown when you import a LAR with a new JournalFolder with a name that collides with other JournalFolder
-
- Closed
-
- Testing discovered
-
LPS-59041 org.hibernate.exception.ConstraintViolationException error is thrown when importing a LAR file when duplicated names exists in recycle bin
- Closed