David Artiss

It should be live now!

No, it’s automatic. Every day it runs. HOWEVER, this is only to remove transients that have genuinely expired. I suspect your issue is that they’ve not actually expired but something is just generating a lot of transient content.

I’m going to push out a new version of the plugin, within the next few minutes, that you should be able to install and use. From Tools -> Transient Cleaner there’s an option to remove ALL transients, which is what I believe you need.

Hi Yolanda,

I’m sorry you felt the need to leave a 1 star review rather than ask about this in the support forum. If you can find the time to do so, you might find some existing advice over how to restore your footnotes and, if that doesn’t work, I’ll be happy to provide further help

Yeah, so, after 5.8.9 the transient cleaning is built into WordPress, so my plugin shouldn’t be needed.

I am actually working on a version that will work for all releases and will allow you to see if it has worked and, if not, perform a manual run yourself – but that’s not ready for use yet.

Was it a specific Woo plugin that generated this message, as I’m curious about the source?

My plugin doesn’t look at Woo version. Do you mean the WordPress version?

Thanks for confirming.

As per the announcement, the code has been rolled back to how it was a few months back. If you’re making use of recent changes, that may be the issue. Please check the plugin instructions to see if you’re implementing the footnotes according to that.

Did you update to version 3? This is not compatible with PHP 8.2, if that could be the issue here.

I’m going to close this thread up now as people are trying to share links to code and having their posts pulled. Rather than get anyone banned, I think it’s best to just end the conversation. Thanks everyone.

Huh. Yeah, the way it should work is that, unless you specify an extension, it will go through the main options to try and find it. What happens if you don’t supply it? What if you do it in lower case?

This site isn’t live yet (something I’m working on), but here’s this plugin in use, along with screenshots… https://wpartiss.mystagingwebsite.com/plugins/current/code-embed/

Personally, and don’t tell anyone I told you, but I’m using the Footnotes block that’s now built into the editor. It may not do what you need but, I suspect, for most people it will be enough.

Hi Stephen,

I apologise that it’s causing issues. Of course, any features added to the plugin over the last few months have been lost if you’ve updated to version 3. It doesn’t help now, but for future, I’d highly recommend turning off automatic plugin updates for anything that’s so critical – that way you can review changes before implementing them.

Unfortunately, I don’t have access to the previous code to offer you a solution – it was either this or leave the plugin abandoned and, potentially, highly insecure.

Maybe another user, who has the previous release has a copy to share?

The plugin was adopted. Then wasn’t. Read more about what happened here. It’s now open for adoption again.

Hi! The plugin was closed before I had a chance to answer.

I hope this post answers your questions about what happened.

Cheers Joe. I’m actively using this plugin again, so expect some more feedback (I’ll use the Github repo as much as possible).

Well, it sounds like you can access that screen, which is all I wanted to know.

So, the difference is that the settings page requires you to have manage_options permissions rather than edit_posts. But I can’t see any reason why this may be happening, certainly not a plugin code issue.

This article may help you diagnose this further: https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-sorry-you-are-not-allowed-to-access-this-page-error-in-wordpress/