SOLVED Template manager fails
-
-
- mecsys
- Sr. Rocketeer
- Posts: 192
- Thanks: 0
-
I have been working on a new install of joomla with Rocket Theme templates:
blockydogs.com/cms30bd/
Tried installing Praxis Bundle but when i tried to go into Template Manager i got a 500 Internal Server error
researched that error in the forum and saw a wide variety of possibilities.
I've installed Joomla and Rockettheme on more than a dozen accounts on the same hosting server, so don't think that's it.
since this is a new install, i uninstalled joomla and started over. have done that about 5 times so far.
With most recent attempts, i thought i'd try a different template, and installed Ricochet bundle.
for that i could get into Template Manager but is wasn't the fully functional RocktTheme manager.
had encoutnered this a couple of times in the past and the advise was reinstall Gantry, which i've done on two separate installs.
with the same result.
thinking it might be cache, i went into Globabl Config and turned Cache off, which i'd do anyway to tweak and test a new template.
after doing that, i get the 500 Internal Server error again.
i'm out of things to try.
admin access provided in secure area
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
You need to look in the apache error log and tell us the error message associated with the server500.
Regards, Mark. - Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
-
-
- mecsys
- Sr. Rocketeer
- Posts: 192
- Thanks: 0
-
I'd checked those but forgot to mention. Doesn't say very much (if these are the logs you mean)
[Fri Apr 10 09:10:42 2015] [error] [client 72.196.153.6] File does not exist: /home/blocky/public_html/500.shtml, referer: blockydogs.com/cms30bd/administrator/index.php
URL at the time of error: blockydogs.com/cms30bd/administrator/ind...option=com_templates
if there is another log you meant, let me know and i will check it
thanks
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
give me the last few lines of the apache error log. That error is just about the fact that your server doesn't have a default server500 page... we need to know the original error.
Regards, Mark. - Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
-
-
- mecsys
- Sr. Rocketeer
- Posts: 192
- Thanks: 0
-
The original error message had dropped off the log, so i had recreated it, and that's all the error log said.
not sure the error log i am looking at is the same as the Apache error log you are aksing for.
i am looking at the error log in Control Panel. I am checking with my hosting company to see if there is another one to check on.
Out of curiosity, i unparked one of this clients domains, and created a new hosting account, installed Joomla and the Praxis template bundle, and no problem.
this client is one of my oldest clients, and their account was moved from a previous host. had a couple of others that fell into that group,but didn't have a problem there.
i would like to get this working on the current site, since she has 11 years of history with the main domain and don't want to lose that for the SE ranking. if it would be helpful to compare settings on both, i have provided access to the new install as well.
thanks for all your help
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
Ok thanks. Yes, I think you were looking at the joomla logs rather than the apache error log.
Regards, Mark. - Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
-
-
- mecsys
- Sr. Rocketeer
- Posts: 192
- Thanks: 0
-
Couldn't get the logs from the original problems, but these are from today, when the error is regenerated
[Mon Apr 13 12:02:09 2015] [error] [client 72.196.153.6] Premature end of script headers: index.php, referer: blockydogs.com/cms30bd/administrator/ind...staller&view=install
[Mon Apr 13 12:02:22 2015] [error] [client 72.196.153.6] Premature end of script headers: index.php, referer: blockydogs.com/cms30bd/administrator/ind...staller&view=install
[Mon Apr 13 12:02:34 2015] [error] [client 72.196.153.6] Premature end of script headers: index.php, referer: blockydogs.com/cms30bd/administrator/ind...staller&view=install
[Mon Apr 13 12:04:19 2015] [error] [client 72.196.153.6] Premature end of script headers: index.php, referer: blockydogs.com/cms30bd/administrator/ind...staller&view=install
[Mon Apr 13 12:08:13 2015] [error] [client 72.196.153.6] Premature end of script headers: index.php, referer: blockydogs.com/cms30bd/administrator/index.php
Thanks,
Mary
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
Ok I know what that is - and it's related to your hosting environment:
This error occurs when the server is expecting a complete set of HTTP Headers but doesn’t get them.
This can be caused by several things:
1. Upgrading/downgrading PHP can leave unneeded options in httpd.conf.
2. RLimitCPU and RLimitMEM directives in httpd.conf can also be responsible for this error if a script was killed due to a resource limit.
3. A configuration problem in suEXEC, mod_perl, or some another third party module will often interfere with the execution of scripts.
4. If suphp’s log reaches 2GB in size you may see the error as well. See what the log contains and either gzip or null it. Restart apache and then deal with the issues that were found in the log. The suphp log is located at: /usr/local/apache/logs/suphp_log
5. The script’s permissions may also cause this error. CGI scripts can only access resources allowed for the User and Group specified in the httpd.conf. In this case, the error may simply be pointing out that an unauthorized user is attempting to access a script.
Regards, Mark. - Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
-
-
- mecsys
- Sr. Rocketeer
- Posts: 192
- Thanks: 0
-
that's a whole lot of stuff i know nothing about, but i will take this to my hosting company and i'm sure they can determine what our problem is.
Will let you know what they determine.
thanks
-
Time to create page: 0.063 seconds