Postname permalinks cause Page Not Found after auto update to 3.8.1

  • After the auto update to 3.8.1, when I publish a new post and click on View Post or Preview (or manually typing url), it shows me a Page Not Found error.

    My permalink settings is set to “Post name”. The problem does not exist if I change the setting to “Default” or any of the other choices like “Numeric”. But I need my permalinks to be based on post names. Other than the update to 3.8.1, no other changes were made to my site before this Page Not Found error starting happening.

    Here are the things that I have tried without success:
    1) I reinstalled 3.8.1 from the dashboard.
    2) I changed themes including one time to Twenty Fourteen.
    2) I disabled all plugins.
    3) I renamed the plugins folder (to test if a deactivated plugin may be the culprit).
    4) I checked the .htaccess file and made sure it includes this code:

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

    5) I changed the permission of .htaccess to 444, 644, and just about all the combinations available.
    6) I tried viewing the post when logged in vs. not logged in.

    Is there anything else I can try?

    Has anyone found a solution to this problem?

Viewing 12 replies - 31 through 42 (of 42 total)

  • I think I had the permalink problem because I had edited the pretty link when I was initially adding my pages. For example, I’d change ‘this-is-a-new-page’ to ‘new-page’. When I turned on permalinks, the link would not work. However, if I left the link alone when adding the page, the permalinks worked. Don’t know if this helps.

    New installation of WordPress 3.8.1 on localserver and when going through the settings and updating – fine.

    Final update made, to Permalinks, custom permalink, result being:

    Forbidden

    You don’t have permission to access /wordpress/wp-admin/options-permalink.php on this server.

    End of!!

    @ladypenelope: If you require assistance then, as per the Forum Welcome, please post your own topic.

    This topic is a month old.

    Apologies, @esmi, I will post topic anew.

    Instead of creating topic anew, much rather report as to having solved the issue experienced with setting custom permalinks!

    Resolved by editing and adding scripts to my Apache Server.

    @ladypenelope : can you tell me what script you adding to ur apache server, i get this problem too…

    Hello unholyknightz,

    <Directory />
                Options FollowSymLinks
                AllowOverride All
        </Directory>
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride All
                Order allow,deny
                allow from all
        </Directory>

    Change AllowOverride from None (default) to All

    Kind regards,

    Penny

    navjeetc

    (@navjeetc)

    Thanks LadyPenelope. I had the same issue and this fixed my problem.

    fixrunner

    (@fixrunner)

    Thanks Lady, it worde for us as well.

    @ladypenelope – can you please elaborate on how you added this script to your Apache server?

    Is it something that can be added to an htaccess file?

    Currently same issue I am facing with my site on daily coupons. All posts once made to edit and republished, they are changing their urls. Guide please.

    I’ve been having this issue for the last few days, no idea why it suddenly started.

    Finally seemed to have fixed it temporarily by:
    – going to the Plugins page, selecting all plugins, and Deactivate (by bulk action). Note you must choose ALL plugins, don’t try to deactivate them individually
    – browse to site, refresh a few pages (they will still all give an error)
    – go back to Plugins, select all plugins, Activate (by Bulk Action)
    – visit site again, all pages working again

    However, if I go the Permalinks setting, and click Save again (without changing the setting – it is still set as /%postname%/) the issue returns (ie page errors).

    So, make sure you set the permalinks setting first, then go through and to the process above.

    Hope this helps.

Viewing 12 replies - 31 through 42 (of 42 total)
  • The topic ‘Postname permalinks cause Page Not Found after auto update to 3.8.1’ is closed to new replies.