file does not exist 500.shtml and 404.shtml in joomla internal server error - apache

today i encountered a very weird problem on joomla that is file does not exist 500.shtml and 400.shtml. In my every web page no matter what i am trying to open it is showing me the same error over and over again which turned off my website. I also google out for it and found some suggestions that are turn off your sef in config file of joomla or change your htaccess by putting a # in front of option and close the htaccess file but still it does not helped me. Any help would be appreciated the most.

In general the first step when dealing with this sort of error would be to turn on error reporting by putting the following at the beginning of your index.php:
ini_set('display_errors','On');
error_reporting(E_ALL);
Doing so might give you some php-specific error message with which I will find it easier to trouble shoot the problem.
This would Display the real error , I had a same trouble, and I found that a new template/plugin/module were creating the problem .So I uninstalled/disabled it .And it was working again.
Cheeers

Related

White screen and missing file warning, prestashop or apache?

Sometimes and sporadically, when I navigate on my back office I receive a white screen and warning of "missing file".
I do not know if it's apache or prestashop problem. I have searched everywhere, without success.
Any ideas?
Missing file prestashop or apache:
It shall be an Apache problem :
- I assume index.php really exists. It's the root of Prestashop after all.
- Routes are created by their controller name.
- I assume you have also in your installation controllers/admin/AdminDashboardController.php
So regenerating Apache configuration in the SEO & URLs menu should do the job :).
strangle problem, but may be it is php problem , please try to fix it following link :
https://www.inmotionhosting.com/support/prestashop-16/blank-screen
this problem may be due to your (files & folders) permissions. i already had this problem

smarty migration website doesn't work. Error 500

I've got to transfer a website from an hoster to another (MelbourneIT).
So I've done as usual with my favorite FileZilla, just copy the html website (without DB) to the other url.
So this one work for the first page ( http://www.lmhceramics.com/) because it's an html one but all my other pages doesn't work!
I've check the folders of my website and I found that this one worked with "Smarty" who is apparently a third party application.
I tried for 5 hours different things as : create an .htaccess to launch index.php instead of index.html, change the configuration on my site_globals.php but it didn't work. It looks like only the first page : index.html is loading.
I can give the access to the ftp if anyone could help it will be sweet as it's one website of my company!
Thanks guys.
Cheers
Initially I tested whether PHP was working, then when I was sure I looked at the error log. The overriding issue was a required library not being found because of a broken path, and PHP's display_errors setting was disabled so it resulted in a white screen.
The site main pages now function.
In site_globals.php, there were two paths that begun with a forward slash. This results in the code looking in the root directory of the server for a particular folder of files (the Smarty library, and the Smarty templates), which likely worked on the old server but not on the new shared hosting environment. New code italicised:
define( "SMARTYPATH", _$_SERVER['DOCUMENT_ROOT'] ._ "/deldridge_smarty/" );
define( "TEMPLATEPATH", _$_SERVER['DOCUMENT_ROOT'] ._ '/smarty/' );
Once that was fixed the code library and templates could be loaded and the rest of the configuration file continued to load. It then dies on:
$db_interface = new DBInterface;
$db_interface->connect( '172.20.254.1' , 'ampnet', 'cable05' );
This is an attempt to connect to a database. I haven't investigated what the database was for yet (that'd require looking through the PHP files in depth) but I'm assuming it was the login system or some such. Almost all of the pages in the site function with those two lines commented out, which I've done for now so that the majority of the content is available again. There's another reference to database connection details further down but they were already commented out.
One other area of particular interest is this:
// different dir structure on secure domain, make ammends
// ensure trailing slash if directory present
define( "SECURE_DIR", 'buildersbollards/' );
if ( $_SERVER['DOCUMENT_ROOT'] == '/home/deldridge/secure.4mation.com.au' )
{
$site_path = '/' . SECURE_DIR;
}
Hop that helps!
It's difficult to know with so little information. Enable error reporting in php or just look at the php error log in your server. One probable cause for the error 500 may be that some key folders don't have CHMOD permission to write; In smarty, for example, templates_c must be writable

Acute 404 errors from Pelican blog on localhost

After a few generations of my pelican site, suddenly after changing the theme once my localhost has tries to find all files non-relatively.
WARNING:root:Unable to find file /jonocodes.com/theme/css/main.css/index.html or variations.
I believe it should be looking for my file in /localhost/theme/css/main.css/index.html.
Where is this getting generated? I have not edited my publishconf.py and my page template is the default.
Is there any good reason why it suddenly started messing up after working for a while?
So the issue I was having, and I still can't explain why it happened all of a sudden, was that I had added the field 'SITEURL' to my pyconfig. This made everything relative to the SITEURL and so it did this on local host and of course didn't work.

This web page has a redirect loop

Alright so I tried forcing either www. or allowing without the www. . It wasn't working so I took it all out of the .htaccess file and re-uploaded. Now when I try to view the website I get the error message of:
This web page has a redirect loop
How long does this take to refresh and not display this error message anymore? I tried clearing my cookies and flushing my DNS. It's still there.
Thank you!
Maybe have a look at this previous question's answers: How long does it take for .htaccess changes to take effect?
Changes to .htaccess should take effect immediately. It might help to re-check the obvious things (that the file on the server is indeed the correct .htaccess, etc)
Apache's help page on the matter: http://httpd.apache.org/docs/2.2/configuring.html#htaccess

Updating Files on Apache

I'm having trouble with my Apache Web Server. I have a folder (htdocs\images) where I have a number of images already in place. I can browse them and see them on my web server (and access them via HTML). I added a new image in there today, and went to browse to it, and it can't be found. I double and triple checked the path and everything. I even restarted Apache and that didn't seem to help.
I'm really confused as to what's going on here. Anybody have any suggestions?
Thank you.
Edit I just turned on the ability for the images directory to be listed, browsed to it (http://127.0.0.1/images/) and I was able to see all the previous images that were in the folder, but not the new one.
Turn directory indexes on for htdocs\images, remove (or move out of the way) any index.* files, and point your browser at http://yoursite/images/
That should give you a full listing of files in that directory. If the file you're looking for isn't there, then Apache is looking at a different directory than you think it is. You'll have to search your httpd.conf for clues -- DocumentRoot, Alias, AliasMatch, Redirect, RedirectMatch, RewriteRule -- there are probably dozens of apache directives that could be causing the web server to get its documents from somewhere other than where you think it's looking.
make sure the caSE and spelling are 100% correct.
There is not magic in programming (some may disagree:), so look for silly errors. Wrong server? Case of your letters? Wrong extension?
There's a chance it could be due to the cookies stored on your device. I would delete all cookies to the website you're working on before you refresh again