tonyquicktech

@fibrojedi I did some testing and your solution does indeed resolve the nonce error in the inspector. It appears however that the css is still broken, for example, on the post creation page – headers and other text are nearly or completely invisible as they are light grey or white, and the background is also white. I’m guessing there is a file that’s not being loaded somehow. Haven’t had time to investigate further yet though. Cheers

@atakanau it seems the dev has disappeared unfortunately – even their personal site is offline. (I wonder if that has something to do with this issue maybe). Given the access level of this plugin I was assuming a security check would be necessary (and of course it is according to WP guidelines), but… I suppose if you have enough other security measures in place it should be manageable. As it currently stands the check is doing naught anyways.

@fibrojedi wouldn’t commenting out the nonce open the site up to security risks like CSRF? While it does solve the problem, I don’t think the risk is worth it. I currently have the same issue, so looking into a safer fix for this.

@omarelhawary many thanks! All the best.

Hi Omar,

I think I found a solution – that was to make the pages private, then give subscribers access to view the pages. I don’t know if this is the best way, but it does seem to work. I guess the only thing I’m worried about would be the constant generation of 404 pages and if that will have any effect on the server.

Anyways, I think it would be a really good idea to add this basic tidbit to the documentation, as it might not be obvious to people (as in my case, apparently), that you have to privately publish and give access to the necessary roles on the edit screen of each page, after allowing view access in settings.

Cheers