coleh

@pixelsandthings It has been a while since I resolved it, but it was an error I found in the Chrome debug console with CSS. It was giving an error in the console that once I resolved, the Javascript resolved correctly in the block editor. Unfortunately, I can’t remember remember the exact issue but can confirm the the action still works to load a script in the block editor to run javascript.

If you need help debugging, feel free to reply and i’ll give give you some contact details.

I was able to find the issue. It appears the action still does work contrary to what i’ve seen posted saying it was removed.

I think it would have been better to have allowed all user roles by default with the new setting added.

I have this plugin on 170 sites and it will not be fun to have to go through and manually add permissions for every site.

• This reply was modified 3 years, 1 month ago by coleh.

I have tried the steps you outlined above and I am still seeing the first post as the URL in the og:url property. Everything else looks fine such as the Title, IMG etc.

I think one of the most recent updates caused an issue with the og:url output.

I went ahead and removed the WAF restriction so you should be able to see the site once it updates.

I also verified in our theme that we are not filtering the og:url on the homepage in any way using the provided plugin filters.

For some reason, when I deactivated the theme and installed a different theme the issue went away. When reactivating the theme the 1 plugin update no longer appears. There is some libraries included within the theme but I don’t think they should show a plugin update if one is available within the theme?

It doesn’t say which plugin needs updating. I am seeing the issue on localhost along with the actual live production server. I have deleted all plugins and the 1 plugin update still shows. I also have cleared any caching plugin that was being used and it doesn’t solve the issue. Weird thing is that it’s showing across both localhost and on the server.

Interesting piece to add to this. The post gets generated but when trying to debug the response it comes back with a 500 Internal Server Error on the POST request response. Any idea why this would be as the post is getting created? Is this related to the protected meta in any way? When I use Postman I get no issues with being able to update the protected meta.