Hello Stacey,
Welcome to SuiteCRM Community. It could be an issue of file permission. Do verify file permission are correct or not. Here is general documentation for the same.
If still doesn’t work do check your Apache and PHP error log for the reason.
Thank you so much for pointing me in the right direction. I have changed the permissions as needed for the daemon user (default for the vm instance); however, the issue remains. The apache error log file is giving the following errors when I click on the option to rename modules:
PHP Warning: Undefined array key “moduleList” in /bitnami/suitecrm/cache/smarty/templates_c/%%F60^F609237E%%_headerModuleList.tpl.php on line 28PHP
PHP Warning: Undefined array key “Administration” in /bitnami/suitecrm/cache/smarty/templates_c/%%F60^F609237E%%_headerModuleList.tpl.php on line 72PHP
PHP Warning: Undefined array key “Administration” in /bitnami/suitecrm/cache/smarty/templates_c/%%F60^F609237E%%_headerModuleList.tpl.php on line 215PHP
PHP Warning: Undefined array key “LBL_SEARCH_BUTTON” in /bitnami/suitecrm/cache/smarty/templates_c/%%F60^F609237E%%_headerModuleList.tpl.php on line 662PHP
Yes, thank you very much. I have already run the above commands and the permissions are all correct in/for the suitecrm directory.
Is there anything else that might possibly be causing the issue? Are there any other special permission settings that should be in place on any other files/folders? Attached is a snippet in case they it is helpful:
Thank you for the information. No, the daemon user does not appear to have been assigned to the Apache user group. That has just been updated, and the server/services have been rebooted. Please see screenshot for review:
However, I am still receiving the same error messages in the apache log file, and the same blank screen loads after selecting the option to change module names (or make other changes).
Just to test, I changed the permissions to the suitecrm directory to the www-data user and group, with daemon still assigned to that group. However, the same errors exist.
You did it right. That was next thing i’d do.
What happens if you delete the .htaccess file? You can rebuild it from the Admin page > Repair > Rebuild .htaccess File
What happens if you empty the cache folder? Not the folder itself, just what it’s inside.
public static function buildImageButtons($buttons, $horizontal=true)
this should solve the FATAL error in your log, and hopefully won’t break anything else. I have no idea if it will affect your original issue, but it’s worth a try.
Thank you so much for the very helpful information. That worked to get me past the first blank screen, and I was able to access the page which allows for those modules to be renamed. However, I then started receiving another Fatal error after saving the changes. This new error was similar and said the following:
PHP Fatal error: Uncaught Error: Non-static method DropDownHelper::saveDropDown() cannot be called statically in /bitnami/suitecrm/modules/Studio/wizards/RenameModules.php…
Using the same (very helpful) solution you provided for the first one, I was able to make the same change for this method by locating which config file it was in, and then adding “static” to that line of code. In case someone else comes across the same issue, I used grep to locate that config file as follows:
grep -i -r “public function saveDropDown” /bitnami/suitecrm/
Then I updated “public function saveDropDown…” to “public static function saveDropDown…”
I don’t see any other Fatal errors at the moment, so I hope it stays that way. I really appreciate your assistance with this. That was incredibly helpful.
well… I noticed something very important to keep in mind:
in version 7.10.32, this works fine!
in version 7.10.36, it’s broken!
in version 7.11.20, this works fine too!
So what I did was:
copy the file modules\Studio\DropDowns\DropDownHelper.php
from version 7.11 to version 7.10.36
and this fixed the problem
