Plugin Author
Ajay
(@ajay)
That looks like an issue to me. Are you able to check for any console errors?
One way to check is to open up the developer tools in Firefox or Chrome and see what is called under the XHR subtab.
Does this issue recur constantly, is it specific posts or just saved posts as you said?
Well, now it is not happening! It’s been happening for at least the last few days and now it’s working fine! I will let you know if it starts up again (and if it does, I’ll see what it’s called under the XHR subtab). Thank you for making one of the best plugins!
Plugin Author
Ajay
(@ajay)
I have to say I am very happy to hear that.
Thank you again for your kind words.
OK this problem is back today! Where exactly do I need to look in Chrome’s Developer Tools to get the info you asked for (under the XHR subtab)? I assume I should be editing the page within WordPress and then open the developer tools — but what do I look for from there?
Plugin Author
Ajay
(@ajay)
Keep the edit screen open. Open developer tools (F12 usually) > Network tab > Fetch/XHR.
I suggest clearing the network log first (circle with /)
When you start typing the name of the post in the manual posts box, you’ll see an entry for admin-ajay come through. If you click it and go to the “Payload” or “Request” tab, you can see an action called “crp_get_posts_action”. This means you are looking at the correct request.
Check for any errors or review what is returned in the “Response” tab. This should have a list of post id and titles.
Separately, are you using the block editor or the classic editor?
Hmm, it seems to work fine in Chrome. I’m only having this problem in Safari. When I try to use developer tools in Safari and follow the instructions above, nothing happens once I’m in the Network tab.
Plugin Author
Ajay
(@ajay)
This is really weird. I tested it on Safari and it works for me, so wondering if it is specific to your safari.
Is this on Mac or ipad? And, do you have any extensions installed in Safari that could be blocking requests?
Last thing to try is to do a clear cache in the browser and see if that works.