Maybe an update failed? Can you just delete the plugin and reinstall it? You won’t lose anything
Reinstalling didn’t help unfortunately. Could it be conflicting with the Oxygen builder plugin? Just a thought. Everything had been working just fine before the recent updates (including Oxygen).
What sort of errors do you see? Do you know how to check the browser console for errors too?
Can you add new blocks or is it essentially not even loading at all?
Can you link to the plugin? I’ll install it and see.
https://mysite.com/wp-content/themes/oxygen-is-not-a-theme/home/hostuser/mysite.com/www/wp-content/plugins/code-block-pro/build/index.css?ver=1.13.0
net::ERR_ABORTED 404 (Not Found)
It seems as the plugin doesn’t load when the post is being edited, but the styles applied to the previously added code blocks work even in the editor (it’s just transparent a bit). There’s no option to make a new CBP block or edit the existing ones. The only option is above each existing block offering to either Install Code Block Pro or Keep as HTML.
So, I restored my baked up site version prior to WordPress 6.5.3 update and the plugin works fine. Once WordPress update is installed I end up with the same problem.
Hey, sorry for the late reply. The url you shared indicates a server misconfiguration of some sort. If you notice the URL segment that mentions /home/hostuser, that’s sugesting that something is set up wrong within WordPress (not specifically in the plugin). When you did the restore, did that error still show up?
Do you have other plugins too? Could you try to rule things out by deactivating them and seeing if the block loads?
Sorry I bothered you with this issue and thanks for your time and efforts to solve the problem. The plugin works just fine. Oxygen Builder plugin was causing this.
That’s no problem at all. Hope they resolve this issue. Others have actually reported the same thing recently. Have you contacted them? If they seem delayed in finding a solution let me know and I’ll see if I can help debug further.
Yes, I spoke to them. It’ll be fixed with the next Oxygen update they said but there’s also a release candidate plugin version (4.8.3 RC 1) with this bug solved and it’s available for download on their website. As they explained they had received reports before so they included the solution in that RC but it’s only available for users with login and password.
