mlepisto

Thanks for the help!

That does fix the “provider not detected” and is now showing provider detected.

Just in case it’s relevant, I don’t have that function at line 2911. I have it at 3022.
Here’s what I have at 2911. Plugin version is 4.7.10

        $all_posts = get_posts($args);

        foreach ($all_posts as $post) {

            $permalink = get_permalink($post);

            if ( $permalink !== false && !in_array( $permalink, $urls ) && strlen($permalink) > 0 ) {
                $urls[] = $permalink;
            }

        }

• This reply was modified 6 months, 3 weeks ago by mlepisto.

I’m not quite sure they are working. If I edit a page or post on the test site, it appears the SpinupWP page cache isn’t cleared. I can use the SpinupWP helper plugin to clear the cache and then it will show the edits, but the setting in CF Super Page Cache being set to clear the cache when something is changed doesn’t seem to be triggering the SpinupWP cache purge.

If you would like access to the test site on SpinupWP I am happy to share that with you. I can send you a message through your website contact for to connect.

Tried with a new install which has default WP theme and just these 2 plugins. Still behaves the same way.

I also removed the SpinupWP helper plugin and added it back. No difference.

Could it possibly have something to do with the order of how the plugin is checking whether that function exists – ex: the CF cache plugin registers first so the spinup functions don’t get detected? Forgive me, I’m not a dev so perhaps that’s a stupid question….

yes, very odd. I’ll set up a site with nothing but these 2 plugins and see how that works just in case there is a conflict with something else. Probably will take me a little while to get to but I will report back what I find.

I added to theme footer.php and it reports they do exist:
spinupwp_purge_site function exists
spinupwp_purge_url function exists

Odd. I have about 30 sites on SpinupWP (different themes, sets of plugins, etc) that all have this same “provider not detected” issue.

Is there something else I can do or provide to help troubleshoot?

Hi,

It sure appears those functions exist. However, there is a 3dr function as well in SpinupWP’s functions.php. Could that possibly be causing a conflict of any kind?

Thanks!

Here’s the content of their functions.php

if ( ! function_exists( 'spinupwp_purge_site' ) ) {
    /**
     * Purge the entire SpinupWP page cache.
     *
     * @return bool
     */
    function spinupwp_purge_site() {
        return spinupwp()->cache->purge_page_cache();
    }
}

if ( ! function_exists( 'spinupwp_purge_post' ) ) {
    /**
     * Purge a single post from the SpinupWP page cache.
     *
     * @param \WP_Post $post
     * @return bool
     */
    function spinupwp_purge_post( $post ) {
        return spinupwp()->cache->purge_post( $post );
    }
}

if ( ! function_exists( 'spinupwp_purge_url' ) ) {
    /**
     * Purge a single URL from the SpinupWP page cache.
     *
     * @param string $url
     * @return bool
     */
    function spinupwp_purge_url( $url ) {
        return spinupwp()->cache->purge_url( $url );
    }
}

Thank you, Paul.

Thanks @isaumya for pointing me in the right direction. Much appreciated!

Ah, I spoke too soon. This is really odd – now on both sites which have auto updated WP core to 6.0.2 (no other changes have been made to either site) the error appears as an alert and in console, but has changed to the following:

backend.js?ver=1.5.3:310
SyntaxError: Unexpected token ‘<‘, “<h1>Error “… is not valid JSON
swcfpc_purge_whole_cache @ backend.js?ver=1.5.3:310
await in swcfpc_purge_whole_cache (async)
(anonymous) @ backend.js?ver=1.5.3:805

Hi,

Sorry for the delay. I haven’t been able to troubleshoot this in detail, but ran into an interesting scenario today that appears to have resolved it – sort of.

I used duplicator to re-create the site on a different domain so I could try to troubleshoot. Once I was done with this (which is basically an identical copy, including the plugin and theme versions) the error has gone away. But it persists on the site I initially started this thread for.

So basically just a follow up to let you know I haven’t forgotten to try and look into this more, but unfortunately my attempt to do so on a dev site is not reproducing the error.

I will update if/when I find out something more.

Here’s what comes up in the console upon dismissing the alert. There’s nothing else in there that seems relevant: https://ibb.co/wM6yzLL

I will need a bit of time, but I am planning to replicate the site on a dev instance so I can try to isolate this further without potentially affecting visitors. I’ll follow up with anything I find if I can isolate a conflict.

Thanks!

Understood. I’ll send a message from the pro site to discuss further.