Updated plugin not showing up - review your cache validation mechanisms

[binarykitchen]

Good evening,

The World Federation of Deaf contact page is broken:
https://wfdeaf.org/contact/

It is based on Ninja Forms and Videomail plugins which was running fine a few weeks ago.

Customers are complaining, so I've manually released a new version of the Videomail plugin. Once they have updated it, it might work for them 🤷

Here's the commit which made a difference:
binarykitchen/videomail-for-ninja-forms@284201d

Although, I think this isn't right and is just a temporary fix.
I do not want to rename the file each time I release.

Let's talk.

[szepeviktor]

Same URL + different content = enemy of caches.

[hi-hai]

@binarykitchen If the issue is about the cached pages, you can simply fire a purge page via our API to clear it.

[binarykitchen]

If the issue is about the cached pages, you can simply fire a purge page via our API to clear it.

Hmm, how can I do that from my own WordPress plugin? Are there any examples? Thanks @hi-hai

[binarykitchen]

Same URL + different content = enemy of caches.

No @szepeviktor, it's always a different URL, the version is amended at the end with the wp_register_script function.

    wp_register_script(
      'nf-videomail-client',
      NF_Videomail::$jsUrl . 'videomail-client/index.min.js',
      array(),
      NF_Videomail::VERSION
    );

Generates URLs like this .../wp-content/plugins/videomail-for-ninja-forms/target/js/main.min.js?ver=8.0.3
Having version numbers should bust cache, and hence I believe it could be a bug with your plugin?