Enfold header menu problems after updating to latest Enfold theme

Hey Enis,
Thank you for the images, First please explain how you updated, via ftp?
If so, please note that overwriting the theme files will cause errors because old files will be left behind. You would need to delete the enfold parent theme folder and then upload the new enfold folder.

If this is not the case then:
I see in your child theme you have a copy of avia.js which would be from v4.0.7 and could conflict with the newer version. When you took the screenshot above was the child theme activate?
Typically the only reason to add a file to the child theme is because there are customizations made to it, what changes were made to yours?

Did you restore your site with a backup? If so, please try exporting your theme settings at Enfold Theme Options > Import/Export > Export Theme Settings File
and then install the new version of the enfold parent theme, and import your theme settings.
Then please check that the Enfold Theme Options > Performance > Disable Template Builder Elements > Always load all elements is set, and Enfold Theme Options > Performance > JS & CSS file merging and compression is disabled, then check your site.
This should look like your child theme without activating it.

Doing this will ensure the custom files in your child theme are not causing the error.
Let us know if you still have the error, and restore your site so you won’t lose visitors.

If you still have this issue, please check your webhost to see if you have the one click staging site option, this is a option in most cPanels to create a staging clone of your site so we can test on it and you site will stay up and running. You can always ask your webhost to help you with setting this up if you want.
Here are some screenshots of what it would look like:

Best regards,
Mike

Hi,
Thank you for creating the staging site, I activated the Enfold v4.4.1 theme and it seems to be working correctly now, Please clear your browser cache and check.

The only difference now is that the old child theme “avia.js” and the child theme custom “slideshow_fullscreen.php” is not loaded
these may have been the conflict because we have made many changes to Enfold and these files since your version.
Perhaps the changes to these files was to fix small bugs from a long time ago, and are no longer needed.
Please compare this site to your live site for anything different, and let us know.

Best regards,
Mike

Hi,
I recommend using a child theme, and after we sort out your issue we will modify the child theme for you to use.
Right now the goal with the staging site to determine the cause of the black error at the top of your page, which I believe is due to your child theme having a old copy of “avia.js” loading.

Once you have a chance to text your staging site working with just the parent theme, that is the latest enfold, I will recommend removing the “avia.js” and the custom ‘slideshow_fullscreen.php’ from your child theme and activating it for you to test for errors and verify it is running correctly.

The you will be able to do the same for your live site with confidence.

Best regards,
Mike

Hi,
It is great news that you found out that it was the avis.js causing the issue.
I can try to compare your modified avis.js with the v4.0.7 version to determine what you were trying to do back then.
Once we know that, you will be able decide if you want the add the modifications to the current version.
Please upload the modified file via Dropbox or Google Drive so I can compare, I have a copy of v4.0.7 to work with.

In your last post you indicated that your live site has the error, even though you removed to custom files. I have checked and don’t see the error, so I assume you have corrected the issue, or the server cache has been cleared?

Best regards,
Mike

Hi,
I tried to recreate the issue on my localhost and found the issue was with the function that called the child theme avia.js file, replacing yours:

function wp_change_aviajs() {
   wp_dequeue_script( 'avia-default' );
   wp_enqueue_script( 'avia-default-child', get_stylesheet_directory_uri().'/js/avia.js', array('jquery'), 2, true );
}
add_action( 'wp_print_scripts', 'wp_change_aviajs', 100 );

with this:

function add_my_script() {
  wp_enqueue_script( 'my-custom-script', get_stylesheet_directory_uri() . '/js/avia.js', array('jquery'), '1.0.1', true );
}
add_action( 'wp_enqueue_scripts', 'add_my_script', 10);

removed the error no matter which version of avia.js was used, on your live site and my localhost.
So right now on your live site the child theme is active with the newer avia.js and there is no error.
I recommend using the new avia.js because a lot has changed in it since v4.0.7. When I compared yours to the standard v4.0.7 a lot of functions were missing, but none were added, I believe that you might have been using an even older version.

Best regards,
Mike

Hi,
This is correct. We will leave this thread open for now so you can test. Please let us know once you are fully satisfied and we can close the thread.

Best regards,
Mike

Hi,
It tells the theme to use your child theme avia.js file.
Note, in my haste, I posted the incomplete code here, I have since corrected.
The error in the old script was ‘wp_print_scripts’ which should have been ‘wp_enqueue_scripts’
But as you are using the same avia.js as the parent theme, and I assume have no planned changes for it, I would recommend removing this all together so any improvements to it with upcoming updates will take effect.
If in the future you wish to customize avia.js, then this is how you would do it.

Best regards,
Mike

Hi BlueSolution,

Please open a new thread and include WordPress admin login details in private, so that we can have a closer look at your site.

Best regards,
Rikard