After this the upgrade summary takes some time and I get the following errors (proj_new_projects is our custom module, error_reporting is on - if off would result in a blank page):
[i]Notice: Undefined index: proj_new_projects in /usr/local/apache2/virtualhosts/suitecrm/include/SubPanel/SubPanelDefinitions.php on line 495
Notice: Undefined index: in /usr/local/apache2/virtualhosts/suitecrm/include/SubPanel/SubPanelDefinitions.php on line 499
Warning: include_once(/usr/local/apache2/virtualhosts/suitecrm): failed to open stream: Permission denied in
/usr/local/apache2/virtualhosts/suitecrm/include/SubPanel/SubPanelDefinitions.php on line 499
Warning: include_once(): Failed opening ‘’ for inclusion
(include_path=’/usr/local/apache2/virtualhosts/suitecrm:/usr/local/apache2/virtualhosts/suitecrm/include/…:.:/usr/local/lib/php’) in
/usr/local/apache2/virtualhosts/suitecrm/include/SubPanel/SubPanelDefinitions.php on line 499
Fatal error: Class name must be a valid object or a string in /usr/local/apache2/virtualhosts/suitecrm/include/SubPanel/SubPanelDefinitions.php on line 500[/i]
Our custom module isn’t available, but if I refresh this page with the errors, I get the ‘upgrade is complete’ confirmation and our module is available.
Have you tried performing a Quick Repair & Rebuild in Admin -> Repair? It’s unusual that you are experiencing permissions issues after setting the correct permissions.
With regard to the permissions problem, I noticed that the script was trying to include the sugar directory rather than a file. I presume because the module ‘proj_new_project’ was undefined at that point it didn’t append the file name to the path. I guess you would get some sort of error if you tried to include a directory instead of a file, not sure if it would be a permission error though.
When I refreshed the page, at that point the module had been defined and the installation worked.
I restored sugar to it’s former state (files and db). set the permissions again. Ran a repair and rebuild (which completed successfully), then proceeded to upgrade and the same errors popped up.