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!

• This reply was modified 6 years, 7 months ago by SSCM.

I 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 –

• This reply was modified 6 years, 7 months ago by SSCM.

Per 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!