Greg Davids

No I have not. Been over 3 hours now and still nothing in CleanTalk dashboard showing for this site. Not sure if you can somehow check on my account to see if it is stuck somewhere?

Normally with paid subscriptions the plugin will keep working but you don’t get the new updates and cannot use the Priority support.

You continue to pay for the latest version through the updates and priority support..

So you could just pay for one year and then use the plugin forever but it will be stuck at the version when you stopped paying for the yearly fee.

@renanbernei – Thanks

The problem is that Free Version’s latest Version is 2.13. No updates pending.

So it sounds like the issue was fixed in their Paid version but not the Free version.

Maybe you can ask them when they will fix their free version too?

@renanbernei – What other topic thread did you see this comment? It does not really make sense to me.

I have checked my settings and they are as follows:
– Optimize Prebuild Only: Enabled
– Optimize in Background: Disabled

But, homepage not in warmup table is still happening.

Also I agree, why would I pay for Pro when the free version has this bug..

It is sad as apart from this downfall, I find it the best for speed performance. But if the Homepage is not optimized then what is the point?

Yes totally did not expect that.

Thanks for your help guys!

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.

All files seem to be 644 and all folders 755.

Is this ok?

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.

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

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

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?