If this happens, you need to have a little chat with your host. If it exists, try renaming it to php.ini.bak and retry loading your site. asked 2 years ago viewed 755 times active 2 years ago Blog Stack Overflow Podcast #91 - Can You Stump Nick Craver? Richard Please Log in or Create an account to join the conversation. navigate to this website
Monday, 14 January 2013 07:54 CST IThypercube AKEEBABACKUP, ADMINTOOLS I can confirm that the migration of the backup was from Linux to Linux. If you don't have a file named .htaccess create a new one. Also do the same thing in your site's administrator directory. Edit the configuration.php file in the root of your site and modify it so that the line starting with var $live_site looks like this: public $live_site = "http://www.mysite.com"; or (if you
You should have modified memory_limit in php.ini to 32MB-64MB depending on your requirements. –Alex Sep 14 '10 at 14:52 I don't care if it's good or bad, I care Edit the .htaccess file in your site's root. First, let's see if it is a .htaccess issue. After removing the back-end .htaccess and loging in to your restored site's back-end you can always go back to Components, Admin Tools, Administrator Password Protection and set the password afresh.
The Joomla! Please don't write to us claiming that changing the .htaccess bears no result. When is it okay to exceed the absolute maximum rating on a part? and wait...
works. We know! Make an ASCII bat fly around an ASCII moon Why was the identity of the Half-Blood Prince important to the story? Add the following to the end of the file: php_flag display_errors On php_value error_reporting 32767 and retry loading the problem page.
Such problems are easy to spot because you have put this code in the .htaccess file and you should know about what it does. Thank you for your fast and professional support! If you are using apc, memcache, memcached and so on it is possible that these are not supported by your new host. Thank in advance.
This is mandatory, every time you move your site to a different host, domain name, subdomain or directory. additional hints Reply time: Depending on the complexity of your support issue it's usually between a few minutes and 24 hours. Oh yes, I did not yet get access to the Apache Error log, maybe that would have helped... Copyright ©2006-2016 Akeeba Ltd.
Please check if you need to do any changes to .htaccess file things to work correctly. useful reference Regards, .htaccess joomla1.5 internal-server-error share|improve this question asked May 28 '12 at 6:42 rajiv.inext 813 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted In When we expect longer delays we will notify you when you file a ticket or reply. Joomla 1.5.26 -> site was running until this morning.
Professional name different from legal name How to say you go first in German Word for destroying someone's heart physically Keyboard shortcut to search for text in MS Outlook 2007 Nest Why did my electrician put metal plates wherever the stud is drilled through? Thanks, I will ask them for the apache error log files. –AndyZ Jul 24 '14 at 13:36 Also check the contents of the articles updated recently (check directly in my review here Yes Have I read the documentation before posting (which pages?)?
Copyright ©2006-2016 Akeeba Ltd. The only times I have seen such an error has been when installing one of the latest versions of Traffic on an older installation of Joomla 2.5 as you can see Extensions Directory work.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count). I'm pretty sure that the Apache error logs will reveal something. How do I identify which bitlocker protector is active? If unsure about the error log location, please consult your host.
I solved the problem now by uploading a new Joomla archive and then I reuploaded all customized files. Forgot your password? RewriteBase in .htaccess Another thing you should look into is the RewriteBase line. http://colvertgroup.com/internal-server/internal-server-error-500-joomla-1-7.php Your problem is most likely 2.2 (point #2, subpoint #2).
Try visiting the problem page again. When we expect longer delays we will notify you when you file a ticket or reply. Try commenting them out (putting a hash in front of the line) to see if it helps.