Hi
Thanks for this. I’ve checked the current version while running in WP_DEBUG mode and I don’t get any errors reported. I’ve looked at the three references you’ve provided and as far as I can see the indexes are defined correctly and there’s no error message either in the admin or on the front end.
Also, I’ve looked at where the restricted message displays on the front end and that seems to be working correctly. I’ve tried deleting all the content from the message and again that works fine.
Have you tried disabling the Query Monitor plugin?
If you need help troubleshooting, maybe it’s easier to do it via email – info[at]catapultthemes.com?
Gareth
Thread Starter
KTS915
(@kts915)
Thanks. This was what I needed to know. Evidently, my own installation of your plugin had become corrupted. Reinstalling did not help. But after clearing out the database (4 entries in the Options table) and reinstalling, it’s back to how it should be. Weird!
Thanks again!
Okay – glad you got it sorted.
Let me know if you need anything else.
Thread Starter
KTS915
(@kts915)
Hmm, evidently not so fast! The problem has recurred after I edited the content in one of the messages.
Hmm… Have you tried disabling all other plugins and switching to a standard theme to test?
Could you get in touch via email? I’d like to take a look at the site if possible.
Thread Starter
KTS915
(@kts915)
1. Yes, I have tried that. It made no difference, except that (with WP DEBUG on) the first error message appeared on the front-end only, while the other two messages appeared on the plugin’s settings page.
2. Sorry, but this is all on localhost, so there’s nothing I can show you.
Okay, I don’t really know what to suggest. I’ve got a localhost installation of this plugin with Twenty Sixteen and WP_DEBUG enabled and I don’t get any error messages on the front or back end.
I’m wondering if your site is corrupted somehow. Are you able to try on a completely new installation?
Sorry not to be more help but without being able to replicate the problem it’s difficult.
Thread Starter
KTS915
(@kts915)
I understand. I’ll try a new, clean installation and see what I find.