-
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 M4
-
Component/s: Calendar, Calendar > Upgrade
-
Labels:None
-
Fix Priority:3
-
Git Pull Request:
ISSUE
After upgrade, the portal starts up with NoSuchUserException when deleting the site for a calendar portlet.
STEPS TO REPRODUCE
1) Start up the Liferay 6.1 GA2 vanilla bundle.
2) Create new user "user1@liferay.com"
3) Assign the admin privileges to the new user and logout test user.
4) Login with user1@liferay.com
5) Create a sample site named "Test Site"
6) Create two pages home and Calendar in this site
7) Add the calendar portlet on Calendar page
8) Add an new event to calendar portlet.
9) Logout user1.
10) Login with omni user test@liferay.com
11) Deactivate and then delete the user1@liferay.com
12) Access the Calendar portlet in "Test Site"
13) Add an new event to this Calendar
15) Shutdown Liferay 6.1 GA2 server.
16) Extract clean Liferay bundle 6.2 SP7 EE.
17) Configure the portal-ext.properties for upgrade.
18) Add the database configuration in the portal-ext.properties file by pointing to the same database which is used in the Liferay 6.1 GA2
18) Add the following property in portal-ext.properties file.
passwords.encryption.algorithm.legacy=SHA
18) Start the server
19) Login with the omni user(admin user).
20) Go to the Test Site site's public page where the calender is added.
Actual result:
The server starts up with NoSuchUserException.
Expected result:
No Exception is thrown when the server starts up.