-
Posts
-
We’re using a child theme for Enfold; after updating WordPress to 4.9.5, the visual editor stopped working. We updated Enfold to 4.2.6 and the visual editor worked, but the nav got wonky – it would not display at browser width before scrolling (though it did upon scrolling), and the mobile menu is gone regardless of scrolling.
We’ve researched this behavior, and it appears to be in a line of other concerns about recent updates. One observation was to update the hosting’s php to 7.0; we’ve done that, but it’s still not resolved.
We temporarily made the parent theme active, and got the error relating to line 6 in the header.php file, no site to be seen…so we reverted to the child theme – still no mobile nav, but at least the site is visible! =O
We’ll make you a temporary admin in order to suss this out; we just need a user email. For the record, we have very consciously only made updates to the child theme’s content, creating any files there that needed to override the underlying theme…and the admin settings tools for Enfold don’t appear to have changed, but the behavior persists.
Please help! Thank you.
Hi SSCM,
You have the outdated versions of the files in your child theme, in this case it is header.php, you need to update it with a fresh copy and the footer.php.
The Advanced Layout Builder loaded fine.
If you need further assistance please let us know.
Best regards,
VictoriaPer your instructions, I went (via FTP and code editor) to update the child’s header.php and footer.php files. When I pulled up the parent theme’s files, their dates were from December of 2014 and March of 2015, which told me that (at least some of) the theme update didn’t work. ??? When we recently updated the theme to 4.2.6 (or attempted to, rather), it was via the admin, NOT manually, so I don’t know what went hooey. =(
I’ve gone to ThemeForest and downloaded what is ostensibly the latest version, and the files absolutely have newer dates (header.php is dated 3-6-18; footer.php is dated 1-30-18) and they were definitely different from what are supposed to be the newest theme files in the parent folder. This is disconcerting on several levels (did the theme actually update when we told it to? If it did, why were the files still dated 2014-2015? If it didn’t, why didn’t it – and why did it then break the nav?), but I went ahead and replaced the footer.php file wholesale for both the parent and child themes, and took all of the code from the latest header.php file and applied it to the parent’s header file, while selectively applying it to the child’s header file, retaining the custom css references that were created since the site’s inception.
It didn’t fix anything, which has made me think that the theme update was – at the very least – incomplete. So: I manually updated the theme, using the files downloaded today, and…nada. The mobile nav is still MIA.
Please advise what else may be wrong!
Hi SSCM,
When you update the theme, it’s the original parent theme that gets updated, the files in your child theme are not updated, it is for the users to be able to keep their customizations, but if you have copies of the parent theme files in your child theme it is up to you to keep them updated.
Best regards,
VictoriaHi,
Thank you for the info.
You have to update the header.php file and the footer.php file in the child theme. Why did you duplicate the entire css folder in the child theme? Use the updated versions of the stylesheets from 4.2.6.
Best regards,
IsmaelI don’t mean to sound snarky, but if you had looked you would have seen that the footer.php files are identical between the child and parent themes (I cleaned up some spacing to show that – extra space was the only alteration); and truly the only difference with the child’s header.php file is the addition of the following:
<title><?php if(function_exists(‘avia_set_title_tag’)) { echo avia_set_title_tag(); } ?></title>
<link rel=”stylesheet” href=”/wp-content/themes/enfold-child/css/custom.css” type=”text/css” media=”all” />
<link rel=”stylesheet” href=”/wp-content/themes/enfold-child/js/custom.js” type=”text/css” media=”all” />Is there a plausible reason that the above is causing the mobile nav to disappear? Btw, I looked in the theme options area of the Admin but didn’t see any ‘add to your header/footer here’ areas, so this was the option for adding that stuff.
Please actually look at the header & footer files to confirm what’s amiss (since those seem to be what you folks keep mentioning). Also, please actually look at the css now – you will only see the custom.css file in the css folder….
Please advise as to what’s causing the mobile nav to disappear. Thx –
Hi,
The header.php file of your child theme differs a lot from the latest version. Please check it again.
This is the latest header.php file: https://pastebin.com/RMZ8HEMe
Another version (4.3) of the theme is available. You may need to update those files again including the footer.php file.
Best regards,
IsmaelI can scarcely begin to tell you how frustrating this has been….
Per your above message from this morning, I accessed the latest header.php file and applied it to the child theme’s header.php file…nothing. I then went to update the theme via the Admin panel from 4.2.6 to 4.3, and got this error (see private):
I then temporarily reverted the parent theme to 4.2.6, went to ThemeForest & downloaded 4.3 from there, and replaced the files via FTP – the site now no longer has the error message and doesn’t seem to have suffered anything new. I then opened the child header.php & footer.php files & updated them per the 4.3 files.
And still, the mobile nav is not there.
?????????
What more should I be doing?!?
So, I’m seeing weird inconsistencies between what’s displaying via FTP and what’s displaying via the Admin. Around 4/19, I consolidated into the custom.css (retaining the custom-previous-build.css file) and then ditched all of the redundant child css files via FTP, and via my FTP client and text editor (Cyberduck and Sublime Text) – even after rebooting so as to ‘clear the decks’ (as it were) – I still see only the custom-previous-build.css, and custom.css files in the child’s css folder, with none of the others. Yet when I look in the Admin, it’s showing files that no longer exist… =(
Moreover, when I look at the custom.css file in the Admin, it does not jibe with what I saved via FTP….
Please advise. Thanks!
Hi,
The mobile menu is not visible because its background is the same as the header background. We had to add this code in the Quick CSS field.
#top .header_color.av_header_transparency .avia-menu-fx, .av_header_transparency div .av-hamburger-inner, .av_header_transparency div .av-hamburger-inner::before, .av_header_transparency div .av-hamburger-inner::after { background: #808080; }We also disabled the “VaultPress” plugin temporarily.
Best regards,
Ismael
- You must be logged in to reply to this topic.