Can’t enable 404 error, outbound links, file downloads anymore

We are currently having the same Issue. It seams to be a Bug regarding the Disabling of the revenue Switch. This adds a field from the Type “hook” to the checkbox array. This brakes the is_list check wich results in this Problem.

This changes the value of enhances_… from [“…”, “…”] to ‘on’. I will rase an Issue in Github. For now Maybe my information helps you to fix the Issue Temporaly. Adding the enabled values inside the array would do for now for example.

“https://github.com/plausible/wordpress/issues/202”

Thanks for reporting @dominic1dl the report at Github looks promising, I hope we can see a quick fix

Hi guys,

Thanks for notifying me of this bug. I just pushed a fix for this, so it’ll be included in the next release!

I am not fully sure if it’s actually solved. I made a comment about my test result on Github

https://github.com/plausible/wordpress/issues/202#issuecomment-2085431104

Is it please possible to get some further information on this case? Most of the details are handled on a technical level in the Github ticket.

I can’t use the plugin anymore, and have it disabled already for at least a week, as the latest provided beta version had nasty side effects, i.e. I could not use the wp-admin / backend anymore as I always got redirected to the Plausible URL within WordPress, as described in more detail on Github

I wish to be able to use it again, but because I was willing to try the beta, I am now locked in a state in between (at least to my knowledge)

Thanks

Hi Markus,

At the moment, I think the best thing for you to do is revert to 2.0.7, which can be downloaded at the bottom of this page.

Simply install it as you would usually, and WordPress will ask you to replace the currently installed package with the package you uploaded. Simply confirm and you’ve been rolled back to 2.0.7, while we’re working out the kinks in the beta of 2.1.0.

OK, will do that.

I hope it’s not messing up with other things. As the ride was a bit bumpy in the last 1 to 2 weeks, and I run from one problem to the next, I am a bit worried to just use the previous plugin version again. Many things happened in between, including that migration script of yours and many more things.

It makes it a bit difficult to rely that it’ll just work again (except for the initial issue reported)

I don’t really like that I see 3 versions installed now, but I will just get rid of the others. I have seen this in the past with some other plugins as well (although not very often)

https://cln.sh/9mp3KtW5

Oops! The API token you used is invalid. Please click here to generate a new token.

It’s becoming really difficult, also now as I downgraded to 2.0.7 – it’s just all a bit messed up now

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

sorry for the trouble @markussss

we don’t have support for the API token for self-hosting in the current latest release of our plugin unfortunately. we hope to introduce that in the next major release (there’s an early beta out there for it on GitHub here)

so if you’re self-hosting and using plugin version 2.0.7 or 2.0.8, then you would need to manually enable the self-hosting part in our plugin settings without using the API token

I hope this helps, thanks!

Unfortunately, I regret that I updated the Plausible version on the server to v2.1.0-rc.0 because I think this version suddenly required the API token. I waited many many weeks till I update, and still it seems it was way too soon

The question is, how to handle it now to stay on the server version 2.1.0 and still use the Plausible WordPress plugin. Weeks passed, I can’t go back to the version prior to 2.1.0

I am really, really not sure if I understand everything correct here, as those things are quite new to me. But it feels like people should definitely not at all update the self-hosted Plausible server to 2.1.0, unless the plugin version is actually compatible with it.

The mentioned early beta brings new issues (wp-admin becomes unusable as it’s always redirecting to the Plausible plugin URL within WordPress), at least that’s what I saw on my client’s site. But I can’t risk to mess with another site, hence I am not sure if this is only happening on my site or in general to all

so if you’re self-hosting and using plugin version 2.0.7 or 2.0.8, then you would need to manually enable the self-hosting part in our plugin settings without using the API token

Can you point me to the right direction on how to do that? I think without the API token Plausible is not working anymore!?

I am sorry, but I am in a completely confused state right now, and hope you can further clarify it.

I won’t have much time in the next days, but try to get to it again on the weekend

our plugin version 2.0.7 or 2.0.8 should work all fine without needing the API token even if you’re on CE v2.1.0-rc.0. here’s how it works:

1. in our WordPress plugin settings, you need to click on Self-Hosted tab in the top menu bar
2. enter the domain name where you installed your CE instance and click on the save button

that’s it. no API required. our next major plugin release will require an API token even for self hosters

OK, then I should not have spent all those hours on the API token then it seems.

I tested 2.0.7, and all possible beta versions of 2.0.8 and each broucht up new and different issues, not only related to API token generation and validation

Is the plugin necessary? I think I remember I could just add the script/code to a code snippet manager. Or will the Plausible plugin be mandatory, due to the latest developments with API tokens?

Overall, I am not able to risk any other site, so all the issues I reporte could be site-related as well, but I must admit I doub it.

I think I can only try to figure out which of the solutions makes the least problems, now that I know that I can ignore the API token thing

Our plugin is completely optional. It makes it more convenient and simpler to integrate Plausible into your site but you can use whatever other method you prefer as well.

Do you know @plausible if we can somehow get closer to finish this up, as I for almost a month struggle with the plugin as described in very detail in the Github issue

Every beta version solves something, and brings completely new other problems at the same time so far, and I tried my best so far to test and document / report it

Hope you can understand that I am trying hard to get it fixed to then finally set and forget about it