Thread Starter
anonymized-17115093
(@anonymized-17115093)
Correction! The problem is from version 3.0.8. It’s not there until version 3.0.7!
Warning: call_user_func_array() expects parameter 1 to be a valid callback, class ‘Elementor\Frontend’ does not have a method ‘add_menu_in_admin_bar’ in (…)/public_html/wp-includes/class-wp-hook.php on line 287
-
This reply was modified 4 years, 2 months ago by anonymized-17115093.
Hi @7dotmarketing
Thanks for sharing your input.
In v3.0.8 we converted the print method of this element to be printed using JS.
It seems that a JS conflict somewhere in your install.
Start by deactivating all other add-ons and plugins other than Elementor Core & Elementor Pro (if installed) – then proceed to edit and see if the issue has been resolved. You may need to switch to the default theme to rule out your theme as the cause of the conflict.
If the issue is resolved by following the above action the proceed to reactivate each plugin 1 at a time and checking the editor till you find the one causing the conflict.
Please share your findings here and we’ll continue from there.
Thanks
Thread Starter
anonymized-17115093
(@anonymized-17115093)
The problem concerns a footer built with Elementor. If we change to a footer build with widgets, it is OK, but if we stay with the footer made with Footer Builder, an error appears – from version 3.8.
How did you build this footer? Using which plugin? This may be the cause for the compatibility issue.
Thread Starter
anonymized-17115093
(@anonymized-17115093)
JNews Theme 7.1.0
Elementor 3.8.1
We can opt out of all plugins and leave the footer only made 100% in Elementor and it’s the same. Of course, now this theme may not be compatible, but you’ve made such an express with your fixes that no one can keep up with it. Themes devs have found out from customers that you are racing for fixes with Maglev.
Elementor core doesn’t have the ability to design footers.
We want to locate the issue, if it’s in your theme – we will check what’s causing this issue.
If not – we will continue our debugging, but we need to know if switching a theme and deactivating all plugins resolves the issue.
Thanks