• Resolved czytam

    (@czytam)


    Last night I decided I wanted to replace Feedburner Feed Replacement plugin with the offical Feedburner Feedsmith, but something went wrong. I think while cleaning .htaccess file I accidentally removed a line too much and my permalinks stopped working.

    I quickly copied the correct .htacceess file (less the old feedburner feed replacement lines), but it still doesn’t work and now instead of nice and clear permalinks (/%year%/%monthnum%/%postname%/) like I used to have, I’m stuck with /index.php/%year%/%monthnum%/%postname%/

    Worse, even if I completely clear .htaccess and try to start from scratch, my WordPress doesn’t overwrite it. Apache and mod_rewrite shouldn’t be a problem, cause (1) I had a working version of permalinks only yesterday and (2) I have another WordPress install on this server and it works with permalinks (though I didn’t replace old feedburner plugin with Feedsmith).

    Anyone can save me?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Feedburner Feedsmith does not appear to write to the .htaccess file, so you shouldn’t need anything more than the standard WordPress .htaccess, which is provided to you on the permalinks page in the admin. It usually looks like this:

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    When you say the permalinks don’t work, what exactly doesn’t work? What is the error?

    Thread Starter czytam

    (@czytam)

    I mean the ‘cute’ version of permalinks – all I could do was to set up the ‘/index.php/ version and all my internal and incoming links got broken.

    The standard WordPress .htaccess didn’t work – it was the first thing I did while trying to restore the things they used to be.

    Finally, I’ve come up to a lame solution, but it works. I changed the /wp-includes/vars.php file and instead of this:

    $is_apache = ((strpos($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) !== false) || (strpos($_SERVER[‘SERVER_SOFTWARE’], ‘LiteSpeed’) !== false)) ? true : false;

    I have:

    $is_apache = ((strpos($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) !== true) || (strpos($_SERVER[‘SERVER_SOFTWARE’], ‘LiteSpeed’) !== false)) ? true : false;

    but now every time I update WordPress I’ll have to remember that vars.php needs to be modified again.

    It looks like my server didn’t realise it’s got mod_rewrite on.

    all my internal and incoming links got broken

    What do you mean by “broken”? What do they look like?

    Thread Starter czytam

    (@czytam)

    filosofo, it’s all fine now.

    By broken I meant that internal and incoming links had the ‘cute’ form without index.php. When my permalinks got broken I could only have the /index.php/%year%/%monthnum%/ etc. version.

    Actually, I’m greatly interested in WordPress development and bug-quashing, so if someone has to modify core files to get permalinks to work, not everything is fine.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[htaccess] Permalinks not working after plugin replacement’ is closed to new replies.