jaydoe96

One thing that I’ve noticed is that when a user with admin privileges publish or modifies a post, then that post is queried and posted. But when a user with Editor privileges publish a post (most of our entries are posted by Editors, not admins) then they are stuck like the ones that appear in the previous posts.

The only difference is that admins can see the nextscripts settings metabox in the editor, but those metaboxes are hidden for the editors. I selected the Editor role in the setting: ” Who can see auto-posting options on the “New Post” and “Edit Post” pages and make autoposts? “, so these metaboxes are not hidden for them, and now the posts are queried and posted.

Why is this happening? Before, those metaboxes were hidden for them, and the posts where auto posted with no problems.

• This reply was modified 4 years, 2 months ago by jaydoe96. Reason: add more info

Just did. Picked a “faulty shared post” and ran it through that tool. The fetched URL and canonial URL match, but in the history of the canonical URL appears that at first, the canonical URL was the one with the post id and then changed to the pretty URL one. The og:url meta tag field contains the correct URL (the pretty URL).

Well, I placed some prints inside that method that gets the URL (nxs_getURL), and actually it retrieved the correct URLs, it never obtained an URL using the post id.

This was tested on our production site, when some posts were being automatically posted on facebook with the error, but the links are not the problem. So the problem is not nxs_getURL, that means that the problem is being caused where in other place of the plugin, or not by the plugin at all.

In which file/line of the plugin are the URLs that are going to be used for facebook gotten?

I was checking the code this morning but I had a hard time finding the exact place. Maybe there’s something that change between in Yoast that affects NextScripts. I would like to help checking that.

Let’s say that the cause is not Nextscript but Yoast, at least knowing where the URL is being gotten will allow me to run some custom code, so if I get an URL like https://www.site.com/?p=XYZ, I could discard it, or use some workaround to get the proper pretty URL.

• This reply was modified 4 years, 3 months ago by jaydoe96.

I messaged Yoast and asked for this issue. I told them this problem of “yoast taking too long to setup the meta tags” and they say that’s not happening, that once you save/publish the post, yoast immediately saves the meta tags.

Mind sharing the list of plugins that you’re using on your blog? Maybe we have some plugins in common that are causing the problem. Since there isn’t much information about this issue on the internet, it could be worth trying to figure this out.

Thanks for your response @krstarica . Which version of Yoast are you currently using?

Any updates on this issue? Did you manage to solve it? I’m experiencing the same behavior. @krstarica