Issue Updating from WordPress Version 4.1 to 4.1.1

  • Let me start by saying that I am working on a site that was recently hacked however I have used Sucuri Security to remove all added files and restore files that had been modified.

    I also deleted plugin folders from wp-content/plugins and re-installed new versions to ensure no hidden nasties. Either way Sucuri’s checks are coming back all clear as I had removed all added files and recovered all modified files.

    After doing this my WordPress Dashboard is stating that I am on Version 4.1 and to update to 4.1.1. I follow the link to “Please update now”. Then I click on the Blue “Update Now” button to do a one click install. And all seems to go through fine, however the next screen shows: Welcome to WordPress 4.1

    If I now go to Dashboard Updates it states: “You have the latest version of WordPress” however at the bottom of the screen in the lower right hand side it states my version is Version 4.1 – Obviously conflicting info and the update has not gone through 100%.

    Also when I go to Sucuri Security plugin I am told there are 28 core integrity files issues. When I expand this list the following files are listed:

    Modified ~23.01K wp-admin/js/common.js
    Modified ~62.21K wp-admin/js/customize-controls.js
    Modified ~12.24K wp-admin/js/common.min.js
    Modified ~26.68K wp-admin/js/customize-controls.min.js
    Modified ~4.08K wp-admin/async-upload.php
    Modified ~27.44K wp-admin/update-core.php
    Modified ~47.07K wp-admin/includes/update-core.php
    Modified ~7.05K wp-admin/includes/taxonomy.php
    Modified ~77.04K wp-admin/includes/ajax-actions.php
    Modified ~23.54K wp-admin/user-edit.php
    Modified ~11.18K wp-admin/about.php
    Modified ~11.00K wp-includes/js/media-audiovideo.min.js
    Modified ~19.99K wp-includes/js/media-audiovideo.js
    Modified ~20.16K wp-includes/js/media-grid.js
    Modified ~15.63K
    wp-includes/js/tinymce/plugins/wpeditimage/plugin.min.js
    Modified ~33.14K wp-includes/js/tinymce/plugins/wpeditimage/plugin.js
    Modified ~133.03K wp-includes/js/tinymce/wp-tinymce.js.gz
    Modified ~10.95K wp-includes/js/media-grid.min.js
    Modified ~102.07K wp-includes/general-template.php
    Modified ~34.18K wp-includes/class-wp-customize-manager.php
    Modified ~100.98K wp-includes/link-template.php
    Modified ~33.12K wp-includes/date.php
    Modified ~47.31K wp-includes/script-loader.php
    Modified ~619.00B wp-includes/version.php
    Modified ~14.86K wp-includes/class-wp-customize-setting.php
    Modified ~31.53K wp-includes/class-wp-customize-control.php
    Modified ~142.01K wp-includes/taxonomy.php
    Modified ~23.17K wp-includes/update.php

    My next step is to select all and hit “Restore files content” as I want to ensure that there are no integrity issues with my core files.

    When this is completed everything looks fine until I click to view a new screen, such as going to the dashboard. Then what do you know? It states I need to upgrade to Version 4.1.1 – again is it saying that I am still on version 4.1

    I have been stuck in this loop for hours now. Also I have tried manually updating through FTP by following the manual steps on this page: https://codex.www.ads-software.com/Updating_WordPress
    However the same issue arises.

    Hoping someone has a straight answer for me as it is doing my head in.
    The site is ahcln.com.au

    Thanks in advance – Cheers.

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

  • Yes, Sucuri plugin will show these alerts since these files are modified for 4.1.1 update.
    When you click “Restore files content” you change them to their previous version (prior the update). That cause WordPress request you to update again to 4.1.1.

    Update again your site and DO NOT restore files marked as modified by Sucuri Plugin.

    Thread Starter Greg Davids

    (@pressedwords)

    Yes I thought this too.

    If I do not restore the files to original content then I can still see the installed version in the lower right hand corner of WordPress stating Version 4.1

    So I restored the files to original content, I then disabled Sucuri plugin. Then went ahead with the WordPress update and the same thing happened. The install finished with the screen saying that the updated version was 4.1 and so on.

    I also have another site which housed the same scenario however this one was able to update from 4.1 to 4.1.1 with the update going through successfully. So what is the deal?

    Where are they hosted?

    Thread Starter Greg Davids

    (@pressedwords)

    Sure. Both sites were hosted with GoDaddy. I also copied this site using Duplicator plugin to VentraIP in Australia and same thing. Tired to update to 4.1.1 however cannot successfully update and stays on 4.1

    This is weird. Would you mind to give us your site URL?

    Thread Starter Greg Davids

    (@pressedwords)

    It was in the original post above. Here it is again: ahcln.com.au

    Sorry for that! Do you use any caching plugin?

    Thread Starter Greg Davids

    (@pressedwords)

    No no caching plugin at the moment. I only have this in the .htaccess file:

    # BEGIN Expire headers
    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresDefault “access plus 5 seconds”
    ExpiresByType image/x-icon “access plus 2500000 seconds”
    ExpiresByType image/jpeg “access plus 2500000 seconds”
    ExpiresByType image/png “access plus 2500000 seconds”
    ExpiresByType image/gif “access plus 2500000 seconds”
    ExpiresByType application/x-shockwave-flash “access plus 2500000 seconds”
    ExpiresByType text/css “access plus 600000 seconds”
    ExpiresByType text/javascript “access plus 200000 seconds”
    ExpiresByType application/javascript “access plus 200000 seconds”
    ExpiresByType application/x-javascript “access plus 200000 seconds”
    ExpiresByType text/html “access plus 600 seconds”
    ExpiresByType application/xhtml+xml “access plus 600 seconds”
    </IfModule>
    # END Expire headers

    # BEGIN Cache-Control Headers
    <IfModule mod_headers.c>
    <filesMatch “\.(ico|jpe?g|png|gif|swf)$”>
    Header set Cache-Control “public”
    </filesMatch>
    <filesMatch “\.(css)$”>
    Header set Cache-Control “public”
    </filesMatch>
    <filesMatch “\.(js)$”>
    Header set Cache-Control “private”
    </filesMatch>
    <filesMatch “\.(x?html?|php)$”>
    Header set Cache-Control “private, must-revalidate”
    </filesMatch>
    </IfModule>
    # END Cache-Control Headers

    However I have taken this out of the .htaccess file when trying the update and the issue remains.

    Only 5 plugins I have on the site are:
    1. All in One SEO Pack
    2. All in one WP Security
    3. Duplicator
    4. Revolution Slider
    5. Sucuri Security – Auditing, Malware Scanner and Hardening

    Also I have deactivated both plugins 2 and 5 while tying to perform the upgrade as I thought they may be causing an issue… But still same issue.

    I am feeling like I just need to wait for the next WordPress update release.

    Can you help me to review your file permissions please?
    https://codex.www.ads-software.com/Changing_File_Permissions

    This may cause that the new files doesn’t get overridden.

    Thread Starter Greg Davids

    (@pressedwords)

    All files seem to be 644 and all folders 755.

    Is this ok?

    Yes, that’s correct!
    I have never seen this issue before so it is very weird.

    Do you have a staging site?

    Have you tried deactivating ALL plugins and switching to a default theme?

    Thread Starter Greg Davids

    (@pressedwords)

    Thanks WPyogi. Found the culprit – Tisson Theme!

    After following your steps I can update to 4.1.1 however once I reactivate the Tisson theme it changes WordPress back to 4.1.

    I am using the latest version of this theme so guess I will have to bring it up with the theme developers.

    Mmmm, yeah, they should be keeping that theme updated and compatible :)!

    Thread Starter Greg Davids

    (@pressedwords)

    Yes totally did not expect that.

    Thanks for your help guys!

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Issue Updating from WordPress Version 4.1 to 4.1.1’ is closed to new replies.