rxbracho

Important Update: Network Solutions has changed their environment in such a way that the work-around is no longer needed. Standard .htaccess files work coming out of the admin interface. Unfortunately, this means (for some of us) that we must undo our fixes. Fortunately, however, it also means that it will work for everyone else.

Rafael Bracho

Sorry but I went through the entire blog and there was nothing new there. I honestly cannot figure out why it doesn’t work, given that so many people have no problem using the /index.php/ work around.

Does anyone know where is the code that does the parsing? I’ll take it from there.

Rafael Bracho

Macmanx: This is my situation.

The domain /brachiza.fambracho.org points to the directory /htdocs/wordpress in my shared host. I have not edited any wordpress files, other than insert die() statements to see if particular code branches were being executed — those statements are all gone. That’s how I found out that the code I thought was doing the parsing is not being executed. So, it’s a virgin wordpress release I got about four days ago.

I had an .htaccess from when I was under the impression that Network Solutions-My-Ass indeed enabled mod_rewrite. I just deleted it (following forceagainstsomething’s suggestion) but got the same problem. An error page simply saying: ‘No input file specified’ — this has to be an error within PHP and not part of WordPress, right?

My feeling is that whatever code is supposed to parse the permalink (which in my tests is /brachiza.fambracho.org/index.php/2005/07/24/hello-world/) is not being executed at all! Does anyone know WHERE is that code? Is there a way to put some sort of debugging statements — I’ve never worked with PHP before, I’m sorry, though I’ve worked with enough languages that I can guess what’s going on.

I don’t have anything in the categories section of permalinks (one thing at a time, I guess).

The no-permalinks case works, i.e., /brachiza.fambracho.org/index.php?p=1 will return the first (and only so far) posting. But if I use /index.php/%post_id% as the permalinks structure, /brachiza.fambracho.org/index.php/1 does NOT work — as expected, I suppose.

If anyone tries those URLs, you’ll see that the blog is in Spanish. I have only touched the theme files to do that. I can put back the ‘default’ theme if you’d like, and you’ll see that the errors are identical.

Thanks again to all.

Rafael Bracho

Thanks but that doesn’t help me right now. The hosting entity is Network Solutions — I was happy with them until now. If I follow some threads correctly, you (Kafkaesqui) had a similar problem. I can see that the permalinks are being substituted correctly (e.g. /brachiza.fambracho.org/index.php/2005/07/24/hello-world/) but it seems that the extra characters are not being parsed or maybe even given to the right script! I tried “/index.php?p=%post_id%” and of course it worked, but “/index.php/%post_id%” did not. Do I have to add some parsing code somewhere? Thanks again!

I just tried the solution above and it didn’t work for me. I have Apache but mod_rewrite is not enabled by my hosting place due to security concerns. I get the ‘No input file specified’ whenever I use the permalink structure with /index.php/ as a prefix. Even the php.ini didn’t help. Things work fine if I don’t enable permalinks, so I know that WP is working. Does anyone have a clue? Thanks in advance!