Uber Menu stopped displaying today

Hey!
So today Uber Menu stopped displaying on the site. It is our main nav through the site. A random issue that is happening at the same time is any page that I set the “above masthead” to have a rev slider assigned (through the backend of the page in Ethos not front end through PRO) those sliders are not showing.

Note that Rev sliders are all over the site and those pages are all showing the sliders. But none of them have a uber menu assigned to them. (they are more like built out sales pages and do not need navigation)

The Uber menu is the main menu and is displayed on 90% of the site, but is not showing now.

So I first unassigned those for conflict. I cannot get them to show. (nor the uber menu on those pages)

I deactivated each plugin and nothing. I have a beta site that mirrors the main site and it is not having the issue. This is a huge site. I will put links and info in the private section here.

Help :grimacing: I have put up an alert that tells members (almost 50,000) to use the quick links in the footer until we fix this issue. I am at a loss.

Thank you so much! Noelle

Hi Noelle,

Beta and live have different structure when I checked.

On live, revslider was added via CONTENT using REVSLIDER classic element.

On beta, revslider was added using Masthead

Also, based on comparison, entire head part is missing on live. That is wehere the menu is. It might be because of customization on the child theme. Please try to switch from child theme the main theme. Check if the issue is fixed. If yes, please check customization you have. See this:

I had said that on the live site that I had added the Rev Slider via PRO as well right now as a fix for that part. I only did that on the live. It is still added in the back end (masthead) as well, did you not see it??

The issue is that the site is missing the entire head area period. I have not made any changes to my child theme and this just started happening mid day yesterday. I had already seen through dev tools before posting— where did it all go???

I made a video to give clarity. I am putting the link to the video in the secure thread as I’d like it private to you. Thank you! Noelle

Please see the video link :slightly_smiling_face:

Hello @Noellemena,

I have logged in both in your staging and live site. I can see that the header is completely gone in the live site. I have compared both the settings and I only noticed that the live site has the base.php in your child theme. Can you temporarily disable this file? And also, maybe there is a corrupt or missing file. Can you also please re install the Pro theme?

Kindly let us know how it goes.

Hey @RueNel
I’ve never had to reinstall the theme. This is such a huge site. I use a child theme but have no code in it. Do I delete the child theme and activate the PRO only?? Then reupload the child theme and activate??

I just want to be sure I do it right. I’d like to do it on the beta site first.

How do I temp disable that other file base php??

This all just like ‘happened’. I’m wanting to handle it where it doesn’t come back and bite me later on an update or something.

Thank you so much. Noelle

Hello @Noellemena,

You can log in to your FTP and browse to the child theme’s folder. You rename the base.php file to something else and it will get disabled from working in the child theme. You may also switch to the parent theme so you can test if the child theme is the one causing the issue. The last thing we can do is to reinstall Pro theme.

When reinstalling the Pro theme, you will have to put your site in under construction mode and then log in to your FTP and reinstall the theme manually. The fastest would be to go to your themes wp-content/themes/ folder and create pro-new folder. This is where you upload the Pro theme files. Once you are done uploading, you can simply rename the current pro folder into pro-old and then renamed the pro-new into just pro.

Hope this makes sense and it may help resolve the issue.

Ok @RueNel so I am going to have my hosting guy bring the beta site to be exactly like the main site. Then I will be able to do all of this on the beta site to troubleshoot.

I had an idea that I will try on the beta site too after it is mirrored. I made a quick video, can you please watch and let me know?

It is in the secure note.
Thank you so much! :hugs:
Noelle

Hey @Noellemena,

Thanks for updating in!

1.) When you set a custom header as your global header, the assign custom header will only replace the header of all the pages that is using the default header. Those pages that have their own assigned custom header will still be using that custom header. On that specific pages if there is a assigned header, it will override the global header assignment and not the other way around.

2.) The missing 404 *.js.map files are the source maps. You may ignore those errors as it is just the missing source maps that Safari will always look for. It appears when you open your browser developer tools and the source map is there to help with debugging. It can be turned off in some browser’s developer tools but I guess, not possible in Safari browser. It will always display in Safari’s developer tool’s console.

You’ll need the source map if you’ll debug a site, but you can’t do that on our theme and builder. Should be done by developers only, plus they tend to be permanent in its current version and shouldn’t be customized.

Best Regards.

@RueNel

Thank you for assisting me. There is no Global Header set through PRO on the site. When I built the site we did not have all that we do now in PRO and I used Uber Menu for the main navigation.

I did this temp on the beta and all went well.

I am waiting for the beta to be mirrored so it has the same issues as the main and I will do it there first again.

Did you have thoughts though on me doing this work around verses the steps you sent earlier? Like to you think based on what you see, that there could be a deeper issue and I should dig deeper?

It is just so weird that this happened all of a sudden.

Thank you!
Noelle

Hello Noelle,

I have compared your staging and your live site. I clearly see the difference in the child theme. The live site has some modified template in the child theme while in the staging there is none. That is why, it is best that we can test the parent theme and if the issue still persist then we really have to re install Pro theme to make sure that there are no corrupted or missing files. This corrupt or missing files usually happens during the previous updates not overwriting the old files or some old files still exist along with the new updates.

Kindly let us know how it goes.

@RueNel when you said you compared them, do you mean the functions php and style through the editor?? I do have additions in the Functions on both live and beta.

I’m thinking you mean differences in a deeper way into the core of the theme files. Yes?

How do you see those files?? Without access to hosting. I do not do the hosting in the site as it is so big I felt better having them have a separate person.

Thank you so much for all the insight! Noelle

Hello Noelle,

You have given us access to both the staging and live site. I can simply go to Appearance > Theme Editor, select the Pro Child theme and find out the different files present in your child theme.

Hope this explains it briefly.

Thank you so much @RueNel
I did not know because I have never seen these files:

… framework- views-- header-base.php- header2.php before.

So I did not know if there was somewhere else you were seeing that. It is not on the Beta site which was a direct mirror from late October.

Now that I have seen the added customization, are you saying that could just be from an odd update issue??

Or does that code look like it it means something and someone added it??? As that is very concerning. Does the code make sense to you as to what it is doing?

I am on the only person who works on the site except for the SEO team and I did not add that. Just trying to make sense of this all.

Thank you so much! :slightly_smiling_face:
Here is an image of that code to for quick glance.

Hello Noelle,

This is your live site’s Pro child theme. During the updates the child theme will not be overwritten. The updates will only happen in the parent theme. Someone must have added these files. If you are not the one who add it and since this files were not present in your staging site, just delete it. Log in to your FTP, browse to your Pro child theme’s folder and remove it. This might be causing the issue which is why I suggested to switch to the parent theme.

Regards.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.