- December 22, 2021 at 7:23 pm
After activating Adminify, we have seen that anonymous visitors to our websites get a 500 error on the front end. This has happened at times on multiple sites we’ve tried.
Now that you’ve added Adminify UI as a module we can toggle on/off, I was able to narrow down the cause to that module.
Current example (see attached):
I want Adminify UI because it provides a white label effect via its main logo. However we can’t use if it conflicts with the well-established theme and plugins we’re using:
EWWW Image Optimizer
Easy Updates Manager Premium
Rank Math SEO
I can get you a login account.
Also: I’m within the 14 day refund period so I’d like this issue noted in case a refund becomes necessary.
Attachments:You must be logged in to view attached files.
Philip LevineCustomerI am an end user like yourself – Can you by chance enable debug mode on WordPress so it will show the 500 error as to point to what / where the issue is.
- December 23, 2021 at 2:51 pm
While I’m not using Kadence I’m using pretty much all the rest of those plugins and haven’t seen this isuse
- December 27, 2021 at 5:33 am
OK, the login info has been sent for this site:
- February 16, 2022 at 5:19 pm
Pls log in and go to the WP Adminify settings to replicate the issue.
When ‘Adminify UI’ is enabled, the front end of the website throws the following 500 error:
“There has been a critical error on this website.”
Note that we bought the software 30 days ago, and reported the problem within the 14 day refund window. At this point I would simply prefer a refund, but I understand that you apparently don’t have a “no questions asked” refund policy and don’t like to give refunds without gaining access to people’s websites, presumably to disable their themes and plugins.
I’ll wait for your response and see what actions you take.
- May 26, 2022 at 6:11 pm
Extremely sorry for the inconvenience you’ve faced.
We didn’t ignore anyone, we’re focusing regular and stable updates.
I thought your problem was fixed.
Somehow I missed your email with Login Credentials.
I’m checking your issue personally, please allow me max 48hrs for investigating the problem.
On the meantime, please let me know more informations about “500 error” on backend or frontend.
- May 27, 2022 at 6:52 am
- May 27, 2022 at 4:02 pm
Thanks, yes, that’s correct. However, the point is that I would like to enable the Adminify UI since that is the main reason I bought the product.
This minor wedding website was chosen for support because it is not a commercial client. At the time in January it was important not to break it, but the wedding is now over and it is OK to disable the theme and plugins and test things.
I’ll try troubleshooting it too.
- May 27, 2022 at 4:24 pm
After doing just a couple of plugin updates, this seems to be resolved!
When I logged into the test site just now, I enabled the Admin UI module and got the 500 error.
Then I noticed that the Adminify plugin needed an update. (Also there were some updates available for some Kadence plugins.)
I ran the updates, and now the 500 error is gone on this site!
I then went to another site that had also had the 500 error before, and it is working with the updated Adminify plugin now.
So I have to conclude that something in the Adminify plugin update has solved the 500 error. That is good news!
It seems that I am good to go now. Thanks for getting back to me and seeing the error. Even if we don’t know what caused it or what the original conflict was, at least you are now aware it existed with a previous version of Adminify but is now gone.
The ticket can be closed. Thanks.
- This reply was modified 4 weeks ago by line49.design.
- May 27, 2022 at 4:28 pm
Thanks a lot for the update.
Actually, we never got issues like “500 error” for WP Adminify.
I know it’s very serious issue.
Again, extremely sorry for the delayed response.
We’re coming with lots of bugs fixes. It will be more stable and feature rich.
Please remove the user you’ve created for us.
Have a great day.