thinkwired

Exactly, It should have never allowed the upgrade to begin with. If the requirement is 7.2 then you need to ensure the server is running 7.2 before proceeding to upgrade. Why would you allow the upgrade when the environment doesn’t meet the minimum requirements?

The result is a fatal error. The only way out of it was to delete the plugin folder from the directory.

This is on version 6.1.1 btw. Hope this helps.

I have the same issue.

1. The notes say php 7.0 is required but, throws a php 7.2 error after upgrading.
2. The plugin should not allow you to update if you meet have the minimum requirement.

I did this right before I posted.

Thank you for confirming my suspicion.

I’m going to mark this as resolved and reopen if it continues.

Thanks!

@vmarko

Again, just a heads up — this is happening on multiple websites on multiple different servers producing the same issue. It should also be noted that they were not all setup by me. This is a number of different clients.

My guess is that there are a number of installations in the wild with this same issue and they just don’t know it. They just click the button and assume it works.

Thank you for clearing this up. I’ve seen this asked a number of times now, I don’t think its clear to everyone.

So, a cached page will remain cached until either;

1. Someone manually clears the cache.
2. A page/post is updated.

I deleted the plugin and all the underlying files on the site where it wasn’t working. I then reinstalled the plugin, set it up, and now the http2 push works — I can verify the push htaccess file is now in place.

There must be a glitch in the config somewhere. Some setting that breaks this. Hopefully you can spot something in the diff.

Here is the diff; https://www.diffchecker.com/kI1Fr8RX

The one on the right works, the one on the left does not.

I don’t see anything that jumps out at me.

Hi @vmarko

I just wanted to let you know that I stumbled upon another website with this same issue. It is hosted on a completely different server AND there are other sites on this server that do NOT have the same issue. This is a really strange bug. I wish you could recreate it!

I am now comparing the sites which use the same server and looking for differences in their configurations.

Hi @vmarko

As expected, that .htaccess file does not exist on this particular website. I don’t see any obvious issues with file permissions. All of the folders look good (755).

I’m not sure why the rule being checked is not resulting an .htaccess file being created in this folder. Do you have any ideas?

Should I just created it manually? Will it be deleted when the cache is cleared?

Thank you again for your time. You have been very helpful.

Hi @vmarko

I am not running multisite.

Yes, HTTP/2 push is enabled for both JS and CSS.

Now you have me wondering if the HTTP/2 push rules are making it into the .htaccess to begin with. What exactly should I be looking for? What rule is w3 total cache supposed to write for HTTP/2 push?

Thank you.

HI @vmarko

I did not add any urls to the Cache alias hostnames list. I have no idea why that option was enabled, I assumed it was a default setting for some reason.

I just disabled it and cleared the cache. As far as I can see, the problem still remains.

Anything else I can do to help, please let me know!

@vmarko

Is there a way for me to send you the exported .json settings? Email? Slack? I could also send the compatibility test results if that helps?

If you don’t need all that info, my setup is pretty basic.

Minfiy is enabled and set to auto mode. Method = combine & minify.

The only options checked for Page Cache are “Cache posts page, Cache SSL (HTTPS) requests, Don’t cache pages for logged in users, and Cache alias hostnames”

Thank you.

• This reply was modified 3 years, 8 months ago by thinkwired.

Done. Settings changed, cache flushed.

Is there anything I can do to help diagnose on my end?

Thank you @vmarko for looking into this. It is appreciated.

• This reply was modified 3 years, 8 months ago by thinkwired.

Yes, I am happy to help.

The url is https://www.cooleydickinson.org/

When I disable page cache, the push does work as expected.