Posted by daveslc on June 9, 2010 at 5:53am
I have successfully installed and set up OpenPublish on shared hosting, but I am getting a few 'Internal Server Errors' that occur on administering the site. The site has no traffic at all (except me) yet.
I am wondering if OP is very server intensive, or if it's possible that the host is not providing much server resources per account.
thanks
Dave
Comments
You can check the status on
You can check the status on the status page.
There is a php memory limit which says how much Mb you have been assigned.
You can tweak that in your .htaccess
I have 90 mb assigned for
I have 90 mb assigned for php.
I don't see any setting in .htaccess.
Since I'm on shared hosting, I doubt if there's a way I can increase that, but let me know.
Are there any of the modules that are much more memory intensive than others that I might consider turning off? Are admin modules generally more intensive than user visits?
I get Internal Server Errors with no visitors, I am very worried about what will happen when the site goes live. My hosting provider says that it is usage of server ram that is causing the problem.
The errors have shown up when modifying blocks, and a couple of other admin modules.
OP is memory intensive - it
OP is memory intensive - it uses Panels, Views, Contexts among others but thats not really the problem. On shared hosting it may say you have 90mb available but in truth you don't and your processes will be killed if they appear to be taking up too much. Turning off some of the 'heavy' modules removes alot of the built in OP functionality. If this is ok for you is there a need for you to use OP at all?
I tried OP on 2 different shared solutions to no avail (one where it stated I had 512mb php memory limit!!) so ended up on a VPS with dedicated RAM and have had no problems since. I do think that some modules could have php memory issues that future releases might identify and solve but they are hard to track down it appears.
Thanks,
M
I have used OP on a shared
I have used OP on a shared host for some time without problem. The only provisos were I needed to bump my memory in the php.ini file to the max, plus edit the mysql and mysqli libraries.