Hey @jeffscroggs ,
Sorry you are having trouble with this. Have you tried to save a post in the admin side editor to see if results save that way when scanned?
If you are familiar with how the network tab in dev tools works you could look at the request and there is likely to be a more descriptive reason behind the save fail on there that would be good to know if you can get that.
- On this site are you using any page builders or a frontend builder like Visual Composor?
- Does this fail only on the homepage, the blog page or on all pages of the site?
A save error like this one is usually caused by a permission issue on the post you are trying to save issues for, are you a full admin on the site with permissions to edit every page or is your user account more limited?
Okay, here’s what we’re running into. I saw the error message the first few times I did it, but now it is working for me. However, it’s my admin that is in charge of using it that can’t get any of the re-scans to work. He is a full admin with the same permissions and whitelisted on everything I’m whitelisted on. I can’t find any differences between our permissions on anything. However, here is the logs that he is getting showing a 403 error with the scripts:
https://jumpshare.com/share/WN7r0tWgtOs7OpgnAd1w
Any thoughts on the cause?
Hey @jeffscroggs
A while ago we did tighten up the issue saving permissions having them gated on the fact that the user can actually edit the post they are saving onto. This would be fairly easy to check if you have the other admin visit post editor for whatever post is ID 13 (I see that’s the one listed in the screenshort as 403).
If they can edit and save that post from the admin side editor then there must be something wrong with the permissions gating on the scan saving and I can try to dig in there and find out what the cause is.
I can confirm that my admin has full permission to edit on that post and all others on the site. So I’d definitely appreciate your thoughts on how to troubleshoot.
