Sona
(@support-web-dorado)
@spearwarrior,
Thank you for providing feedback. Actually this can be a super simple conflict between two plugins- FAQ and your page builder or FAQ and your theme. In both cases the conflict makes the back end not reachable and you need to remove one of the plugins to get the site back. But if yo actually contact us at support[at]web-dorado.com we will be happy to help you out. We will find the causes of the conflict and modifying the code get it back to working.
In any case this is not a plugin bug, it is just a common case which happens a lot in WordPress system.
Thank you for your offer to help but I am so disappointed when every plugin developer begins by responding with issues regarding their plugin with “you have a simple conflict and have to disable your plugins one at a time to find the offending one”. The truth is I’ve only installed 8 VERY common ones like Backup Buddy, Akismet, WordFence, etc. and they all play nice. When I installed yours the site broke. When I uninstalled yours the site was fine. You (and every other developer) can blame another one or more plugins but when 8 work and yours doesn’t, which one do you think I’m uninstalling…AND…when all my other ones are premier, well-respected and ubiquitous which one would appear to you as not-ready-for-primetime?
I also run a MH Theme and paid for it. It is not a freebie from some unknown developer and has never been tweaked. To say you will make something work and expect me to give you my site to change code on the theme and other plugins or even your own plugin only tells me again it wasn’t fully tested and is an ongoing beta. This is particularly true when I see you have two of the same king of plugins in the wordpress.org repository and update them at different times.
Here’s an idea for every plugin developer. Google the 300 most purchased themes, 100 most downloaded plugins and show test results that it works with all of them. That would at least be a help in believing some time was spent by a developer in testing a plugin before releasing it. Saying “we can make it work, just call” really means very little to someone trying to launch sites quickly and who wants to sleep at night when other plugins update. If I had that kind of time with every plugin I use I’ll just write them myself…which is becoming more and more a possibility from what I’m experiencing. I’ve already made two of them for another site.
Again, thanks for your reply but “It is what it is.”
Sona
(@support-web-dorado)
@spearwarrior,
You can actually track the error, if you go to wp-config file and here enable wp-debug. This will display the error. Send it to us.
As for the plugins, those are completely different plugins and have different structure and options. Thus we update the plugins separately whenever a new feature is accessible. And it is a common strategy. And your review is misleading since the error was coming from only one of the plugins.
The plugins are being tested with a unit test which is the most typical practice of testing the plugins. Thank you.
