4.1 Upgrade & 404 errors

  • mikej855

    (@mikej855)


    11 years, 3 months ago

    Hi

    I’ve updated wordpress from 3.9.3 to 4.1.1. I’ve also updated the download manager plug-in from 2.6.4 to 2.7.88.

    I’m getting a 404 error when I try and access the content created under the download manger plug-in. My Permalinks is set to “Post Name”.

    I’ve updated my .htaccess file to have the following:
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    in the folders:
    wwwroot\wp-content\uploads\download-manager-files\.htaccess
    wwwroot\wp-content\plugins\download-manager\files\.htaccess

    If I switch the Permalinks to default, I can view the content. I need to keep Premalinks at Post Name.

    Can anyone suggest any solution? I’ve also switched to default and purged the cache but that hasn’t worked.

    Regards

    Michael.

Viewing 8 replies - 1 through 8 (of 8 total)
  • barnez

    (@pidengmor)

    11 years, 3 months ago

    Try taking a backup of the .htaccess file in your root, deleting it and then using Settings –> Permalinks –> %postname% to regenerate the .htaccess file.

    Thread Starter mikej855

    (@mikej855)

    11 years, 3 months ago

    Hi Barnez

    I didn’t have a .htaccess file in the root folder. I’m currently hosting in Azure. I have a wwwsite folder and inside this I have the 3 wordpress folders.

    I have already dropped a .htaccess file into the wwwsite folder, with the following content:
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    Still seeing the same issue. Changed the permalinks to default, purged the cache and changed permalinks back to normal. I’ve also added custom and tag into the Custom and Tag base optional fields.

    Regards

    Michael.

    Thread Starter mikej855

    (@mikej855)

    11 years, 3 months ago

    I should also highlight that I’m hosting the wordpress site on Azure.

    Regards

    Michael.

    barnez

    (@pidengmor)

    11 years, 3 months ago

    That would be the reason why then as Azure does not recognise an .htaccess file. Have a look at this post:

    http://stackoverflow.com/questions/17871717/how-do-you-configure-windows-azure-for-url-rewrite-using-wordpress

    Thread Starter mikej855

    (@mikej855)

    11 years, 3 months ago

    Hi Barnez

    I’ve gone through the link. I’ve already got the web.config file in place (and it matches for the rules section, but uses a different name for the rule).

    Unfortunately, I’m after inheriting the site so don’t have the background information. I had gone with the automatic upgrade approach when I upgraded on Friday.

    Regards

    Michael.

    barnez

    (@pidengmor)

    11 years, 3 months ago

    I see. there is also this walk through but it seems to contain pretty much the same information. Are there any Azure/Wordpress specific forums you could post to?

    Thread Starter mikej855

    (@mikej855)

    11 years, 3 months ago

    This is frustrating. I’m considering revert the upgrade as the site can’t be showing 404 errors.

    Regards

    Michael.

    barnez

    (@pidengmor)

    11 years, 3 months ago

    Hi Michael.

    That could be a temporary solution, and I hear your frustrations. The problem with running older versions of WordPress is of course the security aspect. What is often suggested is to set up a test site which mirror’s the production site, but allows you to explore and resolve issues such as this without affecting your live site and its traffic/SEO.

    Regards,
    Barnez

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘4.1 Upgrade & 404 errors’ is closed to new replies.