David Artiss

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/

Very odd. That all looks like fine, so I have no idea why it’s not working. A clean install of the plugin onto my own test site and I experience no such issues.

If you go to Tools -> Code Search, does that work? That has different permissions than the settings page.

Hi Lyn,

I can’t recreate this behaviour at all. Can you answer some questions, as this may help me narrow this down…

1. Are you an admin on the site?
2. Which version of the plugin are you using?
3. Where are you trying to access the settings screen? Settings -> Code Embed?
4. Can you provide me with the URL that is in your browser when you try to go into the settings and the error appears?

This plugin has now been adopted by a new developer.

This plugin has now been adopted.

Thank you to all the users of this plugin over the years – I hope Joe, as the new developer, gives this plugin the love that it needs.

Ah, brilliant. Yes, SSL was another thing that would have affected this, so I’m glad you found it.

Hi Florian,

Reinstalling shouldn’t make a difference. Indeed, nothing should have changed for it to stop working.

Has the site domain or structure changed at all? WordPress or PHP version?

If you head to Settings -> Discussion, are the settings for the plugin correct? The description on that screen should include which domain it’s looking for.

Okay, noticed a response to this under another support topic (the topic title didn’t give it away to me).

Needless, my point about better descriptive errors still stands.

You’re very welcome.

Do you want to try now – it’s working for me now?

Thanks for letting me know, Dani.

This is an issue I’ve seen before and is to do with the directory’s caching – it’s somehow cached and empty release. All the files are present, but this caching is serving up the wrong results. It’s not to do with me, though, and I’ve reported it to the plugin team, who should get it fixed.

I’ll report back here once that’s been done.

Thanks Oscar. I’ll keep you informed of any progress.

Meantime, you can drop Spanish translations any time – and always appreciated!

Hi Oscar,

Yes, it’s my intention to add custom post types. No timeline for this, yet, but it is my next big update for this.

Can you point me to the plugin you’re using so, when I do add this, I can use this specifically to check it works?