Open Dvalin21 opened 2 weeks ago
@Dvalin21 Do you know which previous version worked? Nothing has significantly changed around this area of code if I remember correctly
Also I don't think we can support an installation script not owned in this org. Feel free to try the installation script in repo instead
Also I don't think we can support an installation script not owned in this org. Feel free to try the installation script in repo instead
So the last time I was messing with crm, I believe it was 5.6 and 5.7.
Also I don't think we can support an installation script not owned in this org. Feel free to try the installation script in repo instead
Oh I know and no worries. The script just walks through the installation process as if doing it manually. So Im pretty sure I would get the same if I used the script or not.
Description
A clear and concise description of what the reported bug is:
Steps To Reproduce
Steps to reproduce the behavior: Initial Install install script https://raw.githubusercontent.com/Dvalin21/churchcrm_script/main/setup_churchcrm.sh
⚠️ If you cannot do this for some reason, please document the steps to reproduce below.
Expected behavior
On the previous version of Churchcrm, when installing, I never got this error install. I did notice also that Config.php.example shows permission for 755 instead of 644. I can go past the integrity check and it creates the Config.php with 644 permissions. However I was not able to get Churchcrm to start. (This is possible its because of this or because I'm also getting the modrewite x on the integrity check)
Debugging Steps
ℹ️ If you need help debugging, please refer to the wiki for guidance: https://github.com/ChurchCRM/CRM/wiki/Logging-and-Diagnostics.
What has been done to debug the issue so far? When I saw that integrity check showed that Config.php was not writable, I went to /var/www/churchcrm/Include to verify what was there. It only showed Config.php.example but with permission 755 and not 644. I tried to press forward ignoring the issue. When I did, I verified the location again and it showed Config.php set at permissions 644
Have you looked at the browser's developer tools to see if an error is thrown / network request failed? No
Are there any associated error logs on the backend that get emitted when you attempt to do this action?
Desktop (please complete the following information):