Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: (unknown)
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Admin Tools version: (unknown)

Description of my issue:

Hi Although everything appears to be working fine, there is a requirement to set the php version for the hosting account. The hoster has provide the following to be activated via .htaccess:

PHP 5.3:

Action php /cgi-php53gd/php



AddHandler php53gd .php





PHP 5.4:

Action php /cgi-php54gd/php



AddHandler php54gd .php

When I have just one of those in a simple .htaccess file, it works fine for either php version.
However, when I copy say the php 5.3 Version into the .htaccessmaker as "own htaccess rules at the beginning of file" and activate that, I get a 500 error and a white screen, both front and backend. It goes away when I delete the generated htaccess file and restore the simple 2 line version. I have checked the generated file and the rules were correctly included.

Any ideas how to overcome this problem?

Regards
David

David,

I am a little confused about exactly what you put in the "own htaccess rules" box. What exactly did you put in the box?

I copied the same rules as provided by the hosting company:

Action php /cgi-php54gd/php

AddHandler php54gd .php

Nothing more or less.
Hope that clears it up.

Regards
David

The examples that I found showed the Action and AddHandler lines in reverse order. Is that the order that your host gave them to you?

When you add the command to the "include at top" box and generate the .htaccess file, make sure you do not have two AddHandler lines in the resulting .htaccess file.

I'm not sure I follow you.

I've attached the current generated file for you to look at. Perhaps you can spot where the issue lies.

Regards
David

OK, the coffee is kicking in now. :-)

It is not the AddHandler/Action lines that are the problem. You have already proven that they are fine because they work in an .htaccess file all by themselves. It is something else in the .htaccess file that Admin Tools is creating that causes the 500.

I can't see anything that looks wrong, but I still believe that .htaccess files are black magic. Not all commands work on all servers. You need to do a little trial and error searching, just comment out a line or group of lines and test your site to see if the 500 is still there. Any line that begins with the # character is a comment and is not processed by your server.

Very strange!
I've commented out each section and then tried it - no single section seems to be the problem.
Hmmm.

Even weirder:

• I commented out everything except the 2 lines calling up the php version - error

• I commented out everything including the 2 lines calling up the php version - error

I uploaded the file with just the 2 lines calling up the php version and it worked!

So the only thing I can think of is that there is some kind of coding issue in the file-format.

David, are you actually getting a 500 error or just a white page? I can think of another possiblitiy, but it would give you a 403 or a white page, it shouldn't give a 500.

Hi again - I appreciate the effort you putting in. Thanks.

I'm getting a 500 error - see attached image.

I'm out of ideas, I'll ask Nicholas to take a look. He may be done for today, he took a red eye from Boston last night.

OK - there isn't a huge hurry - the client is due to provide comments on the appearance of the site, but not until the weekend.
Thanks for your input - I appreciate it.
Regards
David

Hi Nicholas

Thanks. I've been in touch with the hoster and the problem has been solved:

The line that caused the problem is

Options All -Indexes

This is now commented out and the site works.

maybe this will help someone else.

Regards and thanky to you and Dale for all the effort.

David

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.