I’ve had EE running just fine using WebHost4Life, but I cannot get EE to work the same on AN Hosting. My problem is that I cannot use the .Htaccess 2-liner from the wiki:

RewriteEngine on
RewriteCond $1 !^(galleries|images|eecore|themes|favicon\.ico|robots\.txt|index\.php) [NC]
RewriteRule ^(.*)$ /index.php/$1 [L]

It comes back: No input file specified. Which you have a page on that too, but it’s talking about subdomains and my install is in the root of public_html.

Yes, I’ve followed the instructions on the page with details on migrating to a different server. :)

Any ideas? AN Hosting is trying to help, but they’re saying, “server configuration doesn’t allow to use this method of redirection.”, which could be true, but i don’t think he understands what i’m really trying to do.

I’m going to shift this one over to ‘How to’ as the full removal of index.php isn’t officially supported.  That’s because some server setups don’t allow it- which might be the case here.

But let’s see- if you try to access by manually putting the index.php in your url, does it still work?  It’s just the htaccess failing?

actually if i type in a full “url” like, http://ebohling.com/index.php/wine/list, (or any other valid url) it will still only display the homepage (with rewrite engine off in .htaccess). so i’m not sure what is going on.

additional info: PHP is running in a CGI process. I have completed the extra steps as outlined on wiki page (under troubleshooting). still no worky worky though.

with rewrite engine off, this url should display an archive (thumbnails) of photo of the day: http://ebohling.com/index.php/bryce/archive/. but instead it goes to the homepage.

ideas?

The new server is no fun- it sounds like you’ll need to force query strings and most likely change the $qtype in index.php- see this kblog entry- that look like what’s up?  And- remove the htaccess for now.  Let’s get this working stock first.

ok, now we got stock working after following not only the link you provided but also this one: http://expressionengine.com/wiki/Workaround_for_Forced_Query_Strings/. which i guess overrides the link you sent since the ouput is turned off and qtype is switched back to 0.

so stock works, .htaccess still no worky. getting there…now what?

i’m sure you have a lot of catching up to do robin, but if you get a chance i’d love to hear any further thoughts you had on this.

current status: web site works fine if i add “index.php” to the url, but not if i remove it.

thx,
—bb—

Heh- this one is just hard because the default approach has always worked for me.  So- I’ve never had to dink with it and have no real way to test. 

But- to be clear- it’s working now with $qtype set to the default 0 and force query string turned on?  Correct?

totally understand…i am pushing hard on the AN Hosting support folks to resolve this since they have the best knowledge of their server configuration. yes, the $qtype is set to ZERO and the $path_info is now set to (in index.php):

$path_info = (isset($_SERVER[‘ORIG_PATH_INFO’])) ? $_SERVER[‘ORIG_PATH_INFO’] : @getenv(‘ORIG_PATH_INFO’);

anytime i do anything with .htaccess though (turn on rewrite) i start getting the “no input file specified” error.

while i wait for AN Hosting support to answer, i thought i would temporarily go back to using the index.php in the url, but it looks like that’s going to require a lot of template re-work…even after i changed the homepage (in admin section) from being blank to being index.php. am i missing a step?

currently my links look something like this:

href=”{url_title_path=”{my_template_group}/entry”}”

or

href=”/bryce/archive/”

what should i be using to be able to quickly and easily (hopefully via just a change to the homepage entry in the admin section) change the links from using or not using index.php?

Any {path=”} will pick it up, as should {url_title_path}- they use the cp settings.  I tend to stay away from relative urls and use path instead, but I don’t see why they wouldn’t work if they already were.  About the only place I’d expect trouble would be hard coded full urls in the templates/entries and variables that use the settings in ‘Admin- Weblog Admin- Weblog Management’- path settings.  That url_title_path should be ok for sure- maybe try clearing all caches?

that’s the ticket: {path=}. well, i absolutely cannot stand the index.php in a URL as it provides absolutely no use to the viewer, but until i someone from AN Hosting tells me how to use .htaccess on their servers i guess i have no choice. thanks for all your help robin!

according to AN Hosting support, I need rewrite rules (.htaccess) for PHP on CGI servers.

The redirect rules you tried to use won’t work on PHP as CGI servers. It means
you need to contact your software developers (EE support) to have them assist
you with the updated rules that would allow you to replace URLs. Also I
mentioned the pluggins “search/replace” in case they were written for
CGI servers too.

any suggestions how to change the rewrite rules in .htaccess for PHP/CGI servers?

Not sure this is the issue or not, but maybe try adding a ? after index.php in the .htaccess file.  This solved my issues with my host:

shoot, i was really hoping that would work, but it didn’t. drats! anyone know rewrite rules for cgi servers (see hosting support note below)?

The redirect rules you tried to use won’t work on PHP as CGI servers. It means you need to contact your EE support to have them assist you with the updated rules that would allow you to replace URLs.

i’ve spent hours trying to figure out how to write the rewrite rules when PHP is run as CGI, but cannot seem to find anything. anyone? anyone?

no one? so what’s my next step…quit using hosting service or quit using EE? obviously i don’t want to do either, but i absolutely cannot stand having “index.php” in a URL…serves zero purpose to anyone (except EE).

Try this:

It’s what I’m using on my host, and I’m pretty sure they run PHP as CGI

No Kyle that did not work unfortunately. It does look like your ISP has both PHP as CGI and web module, so maybe you are not on a PHP/CGI server…or you’re just luck…and/or I’m just unlucky.