CvtfRadio Posted January 5, 2014 Posted January 5, 2014 Hi all. The hosting company's server threw an error (sat. evening gmt uk time) immediately after that our website could not show any pages, although the admin pages are showing up correctly - I am able to navigate within the admin page. Originally we had a problem with re-activating the shipping module (needed for shipping delivery rate charges). I was editing 2 files regarding the shipping rates. I reverted the 2 files back to their original states - to see whether this might enable the display of the pages correctly - to no avail. :( I do not know how to fix this problem, the client is about to contact the hosting company - we need to be able to prove 'we' have not done anything wrong from our side, or that we have tried to fix the problem before contacting them. I read in this forum/board, that 1 of the most likely causes could be either a problem with the .htaccess or the http.conf. does anyone here have any ideas - link upon requests, as its not my website - I am just developing the website. Any help would be much appreciated daLegsman thx in adv.
CvtfRadio Posted January 5, 2014 Author Posted January 5, 2014 Managed to find and fix the problem, it was 2 renamed files, seems the system see and reads any .php file in this directory (modules/ ). So renaming the 2 .php files to .txt cleared the error_log file and now the site is showing the pages correctly. So it was a user error - Every .php file is read in this (modules/) directory. thx all, check and recheck and re - recheck again. daLegsman <- Slap wrist ;)
MrPhil Posted January 5, 2014 Posted January 5, 2014 modules/ is supposed to have a number (more than 2) of .php files. Are you sure the problem isn't something stupid like giving them "world writable" permissions (xx6 or xx7 permissions)? If the host just turned on security software to catch world writable files or directories, that could explain the problem. Were those 500 (Internal Server) errors? It's kind of hard for us to guess what happened if you gave no details.
burt Posted January 5, 2014 Posted January 5, 2014 The modules are dynamic so let's say you are need to add some code to paypal_standard.php, and you make a backup prior to amending it called paypal_standard_backup.php. Now you make your changes and you've ended up with an extra .php called paypal_standard_backup.php which will have no language file == Danger, Will Robinson! Get into the habit of making backup files without a .php ending, eg: paypal_standard.php.bak or paypal_standard.phpBLAH
MrPhil Posted January 6, 2014 Posted January 6, 2014 Get into the habit of making backup files without a .php ending, eg: paypal_standard.php.bak or paypal_standard.phpBLAH Note, though, that someone may be using .htaccess (or just default server behavior) to block others from viewing .php files (say, configure.php files with passwords). Changing the extension to something other than .php can expose the file to being read by others. This can be a problem if there is proprietary code or sensitive information (e.g., passwords) in the file. Be careful! An extension like .php~ would still need an explicit rule in .htaccess to block it from being readable. Who is going to invoke paypal_standard_backup.php? I'm not sure what problem you're preventing here.
burt Posted January 6, 2014 Posted January 6, 2014 Try making a new .php file in any module directory (without it's accompanying language file)...and accessing admin to turn it on. That's a problem. And the problem is created by not naming backups appropriately.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.