The Control Panel Server admin portlets don't work after start-up because the admin/view.jsp is being overriden

• Type: Bug
• Status: Closed
• Resolution: No Longer Reproducible
• Affects Version/s: 6.1.20 EE GA2
• Fix Version/s: 6.2.0 CE M4
• Component/s: Legacy, Legacy > Control Panel menu
• Labels:
  • community-verifier
  • problem
• Environment: LINUX CentOS release 6.3 (Final); Postgres 9.1

I have a multi-site instance. I wanted to disable User pages for all sites. I found the following property settings on the forums and applied them to portal-ext.properties:

#

1. Disabling user private and public pages
   #

layout.user.private.layouts.enabled=false
layout.user.private.layouts.modifiable=false
layout.user.private.layouts.auto.create=false

layout.user.public.layouts.enabled=false
layout.user.public.layouts.modifiable=false
layout.user.public.layouts.auto.create=false

After restarting, the User pages were disabled as expected, but the admin/view.jsp file was overridden with the attached version of the file. I tried reverting the changes to the portal-ext.properties to no effect. I resorted to replacing the overridden view.jsp with the correct one after start-up.

Further investigation identified that the overwriting happens as soon as the database comes up during the start-up routine.

Although I failed to reproduce this problem on a clone of the environment made before this issue manifested itself, I'm hoping for some guidance on where this database trigger might be found so I can fix the problem as opposed to re-installing.