Error on running Setup Wizard
Site staff
I just installed a new site.
However, on running the setup wizard, I get an error after the last step
Code
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 528384 bytes) in /home/nettersp/holidaysng/sources/tempcode_compiler.php on line 163
Critical error – bailing out
This is an error that has been elevated to critical error status because it occurred during the primary error mechanism reporting system itself (possibly due to it occurring within the standard output framework). It may be masking a secondary error that occurred before this, but was never output - if so, it is likely strongly related to this one, thus fixing this will fix the other.
Allowed memory size of 134217728 bytes exhausted (tried to allocate 528384 bytes) [sources/tempcode_compiler.php at 163]
Details here are intended only for the website/system-administrator, not for regular website users.
» If you are a regular website user, please let the website staff deal with this problem.
Depending on the error, and only if the website installation finished, you may need to edit the installation options (the _config.php file).
ocProducts maintains full documentation for all procedures and tools (including disaster recovery). These may be found on the Composr website. If you are unable to easily solve this problem, we may be contacted from our website and can help resolve it for you.
Composr is a CMS for building websites, developed by ocProducts.
Am using the version from github and I guess this is the reason for the error, just don't know what to do next.
Site director
We'll resolve, however you shouldn't use direct from github. It has absolutely every non-bundled addon we have installed, including ones that will make your site very insecure. The issue here is likely that the amount that is installed is causing too much memory usage for your particular hosting environment.
It's vital for end-users to use a proper distributed package from our download page.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Site staff
However I tried to run delete_alien_files.php following the instructions on the download page and the script had to be ran via command line. Could it be possible to remove this restriction just in case one without command line access could use, maybe in a test environment.
Site director
enelson said
I would try the package from the download page then.
However I tried to run delete_alien_files.php following the instructions on the download page and the script had to be ran via command line. Could it be possible to remove this restriction just in case one without command line access could use, maybe in a test environment.
From “Post #2,023”, 25th March 2017, 12:47 am
Sorry it's truly developers-only, and I would expect developers to have SSH access to any servers they use. The restriction is important because of security - I'm imagining someone accidentally including the script in a live site, then a hacker tricking an admin to go to it and then many of their addons vanishing. We could make some kind of login form for it, but then we'd be bloating up the code.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
1 guest and 0 members have just viewed this.
