v2.5.2 – getting 404 error on .js load

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Daan van den Bergh

    (@daanvandenbergh)

    1 month, 2 weeks ago

    Hi!

    That’s correct. Yesterday we realized that this could’ve used some UX-related polishing on our end.

    This last update migrated everyone to the new, v2 JS library. This requires the Plugins API to be present, which means that you need to upgrade your CE instance if you haven’t already, and connect the plugin using the API token (on the plugin’s Settings page):

    In the next release we’ll add a clear admin notice, explaining to CE users that the API token is now required.

    Thread Starter jamesshallcross

    (@jamesshallcross)

    1 month, 2 weeks ago

    Hi Daan,

    All sorted, on one site I had to manually remove the plausible related entries in wp_options – as it would not do anything when i pressed Connect to configure the newly set up token.

    I see v2.5.3 is out already with the note to CE users.

    Thanks 🙂

    Plugin Contributor Daan van den Bergh

    (@daanvandenbergh)

    1 month, 2 weeks ago

    Oh, that’s interesting. Did you see errors when clicking the Connect button?

    Thread Starter jamesshallcross

    (@jamesshallcross)

    1 month, 2 weeks ago

    no errors visible on the page, or in Console…

    but i can’t replicate that issue though as all our sites are updated now.

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

You must be logged in to reply to this topic.