Find Answers and Get Support › Forums › Gwangi – PRO Multi-Purpose Membership, Social Network & BuddyPress Community Theme › Theme Customizer › Additional CSS › Critical error when going to profile
- This topic has 16 replies, 3 voices, and was last updated 1 year, 1 month ago by Jason.
My best guess is that your issue might probably be caused by some conflicting third party plugin as we don’t encounter this issue with our demos.
First of all, could you please deactivate all plugins that have not been installed with your theme during its setup and all existing custom PHP code snippets? It might help us getting a clue of which plugin is causing this issue. After deactivating the third party plugins, could you confirm me that the issue is still persisting please?
Please also make sure that you have the latest theme version and that all recommended plugins are up-to-date. This problem may be caused by a missing update or a conflicting version. Finally, you could also consider clearing all activated caching system as well as your browser cache before investigating any further. If you want to read more on what browser cache is and how to clear it, here is an article that might help you: How to Clear Internet Cache in Every Major Browser.
We’re waiting for your feedback.
Thank you.March 31, 2022 at 13:03 #39632
i did everyhting what you wrote.. still the same mistake… even if i deactive all the plugins, then I only get a critical error message, without seeing anyhting. After deactivating Grimlock the crictical error message was gone but the design was completly destroyed.
Could you please check. I want to finish the my webiste and it is more faster you check the website than I go an try to fix…April 1, 2022 at 08:36 #39649
Thank you for your feedback.
To help us getting clues and find a solution to this issue, please activate logging on your website, just turn WP_DEBUG to true, by pasting the following code lines in your wp-config.php file, just before the line that says ‘That’s all, stop editing! Happy blogging.’:
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 );
More on this in the following topic: Debugging in WordPress.
Please come back to us once this is done.
Thank you.April 1, 2022 at 09:35 #39653
Hey, still the same problem.
There is no change – since 8 days I am waiting now for a solution. What and when did you check?April 5, 2022 at 09:30 #39685
We checked the profile yesterday and all was working fine. Anyway, we check again and we’ve met an error again.
However this time, thanks to the code snippet that you’ve recently added to your
wp-config.phpfile, we should be able to read the error. Could you share the content of your
debug.logfile with us please? You can post the content of this file as plain text in your next reply and mark it as private to keep this between us.
After having reviewed your next reply, we’ll be able to tell you if the issue is caused by our product, a third party plugin or any type misconfiguration on your server.
If we’re not able to help, we’ll recommend you to transfer the error logs to the plugin author or to your server hosting support.
Thank you.April 5, 2022 at 10:07 #39691
I’ve investigated the issue on your website and I’ve found that the error comes from some custom code in your the function.php file of your child theme (Gwangi Child).
Since this issue is related with the use of custom code, and not directly related with our theme or plugins, unfortunately this falls out of the scope of the support we can provide.
If you are unable to fix the custom code causing the error, my advice would be to try activating the Gwangi theme instead of the Gwangi Child theme to remove this error.
Best regardsApril 6, 2022 at 10:19 #39716
all the custom codes which I put inside are normally from you.. so, in my different tickets I opend, you gave it to me or which code you mean? I mean if you know which custom code is making the error, why not telling me, which one.. and as I told you…I didnt put any code inside beside of that, what you gave me.April 6, 2022 at 19:13 #39730
I’m afraid we can’t tell from our side. To know precisely which code is causing this, I suggest you to remove temporarily the code snippet, one by one, from your child theme to check if this issue still appearing or not.
Don’t hesitate to share the solution with us, we’re really curious to know which one is causing this.
We’re waiting for your feedback.
Best,April 7, 2022 at 10:01 #39739
It’s important to remember that we share snippet generously. At this point, we’re not even sure which custom code is responsible.
I took a look at your topics and cannot find a snippet I might have send you that could be responsible. As I told you, we need you to delete temporarily the custom code from your child theme to make sure one of these lines is responsible. If deleting the custom code solve your issue, then, you need to add the line one by one to check which one is related to this issue. If the responsible line come from us, be sure we’ll do our best to help you. We do not ask you to resolve this, we ask you to make some tests to find which PHP line is responsible.
We thank you for your understanding.
Regards,April 8, 2022 at 10:33 #39756
If this can help, the error message says that the “is_site_admin()” function does not exist on line 77 of /wp-content/themes/gwangi-child/functions.php file. I think you should try deleting the code snippet surrounding that line to see if it fixes the issue.
I hope this is helpful.
Best regards,April 11, 2022 at 10:16 #39790
This topic has been inactive for a while now so we will be closing it to keep the forum tidy. Don't hesitate to create a new topic if you still need help and we'll be glad to help you!
The Themosaurus team.
The topic ‘Critical error when going to profile’ is closed to new replies.