Divi Theme front end error
-
Fuse is conflicting with the front end editor on the Divi Theme, hiding the front end menu on /?et_fb=1&PageSpeed=off. So, to exit the editor you have to manually go back to the URL. I have confirmed with Divi that this plugin is causing the error, but not sure how to fix it.
The page I need help with: [log in to see the link]
-
Hi there,
Is it possible for you to share a screenshot of how it’s showing on your end?
Hi Dani
Yes, here are some links (one is a video screen capture):
https://drive.google.com/file/d/10afnZTRnRik77ER0-wbJ9JBeMM5iezHm/view?usp=sharing
https://drive.google.com/file/d/1aeBeJPJ4374iq04Lqy7D3fZmed38WS-d/view?usp=sharing
https://drive.google.com/file/d/1ua7PWEYNB6Tq58LQd-8Lx4q3zYn058FS/view?usp=sharingYes, here are some links (one is a video screen capture):
https://drive.google.com/file/d/10afnZTRnRik77ER0-wbJ9JBeMM5iezHm/view?usp=sharing
https://drive.google.com/file/d/1aeBeJPJ4374iq04Lqy7D3fZmed38WS-d/view?usp=sharing
https://drive.google.com/file/d/1ua7PWEYNB6Tq58LQd-8Lx4q3zYn058FS/view?usp=sharingFollowing since I am having the same problem & would like to keep using Fuse on my DIVI websites 🙂
@daniyalahmedk I’ve deleted your offer to login to your user’s site. While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their
phpinfo();output. - Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves.
You’ve been placed on “modwatch” until we’re convinced such postings have stopped. Your account has *not* been banned, we just want to check things for a while before they’re public. If you wish to take issue with this, contact moderators via the #forums channel on slack (https://make.wordpress.org/slack)
Oh, sorry about that, I totally forget that, I will take care of that in the future.
Thanks for letting me know!
Hi – this error has been reported a few times and has been supposed to be fixed many times since.:
From the fuse_social_Sidebar.php file in the root of the Plugin folder
What you have to do to fix this is to change:
add_action( ‘wp_footer’, ‘fuse_social_sidebar’, 100 );
to
add_action( ‘wp_footer’, ‘fuse_social_sidebar’, 1000 );PLEASE fix this for the next version… Thanks 🙂
Thank you so much Andymackk, I was never able to reproduce this issue on my end, so it took me that while to make that fix available.
I will try to make that available in the next release.
The topic ‘Divi Theme front end error’ is closed to new replies.