Menu problems on upgrade

I think if you plan to keep upgrading the theme in the future, you are better off keeping all custom CSS in the child them rather than via theme options, to avoid the potential of an override with a future update.

That’s what has happened here: the recoding in order to support new formatting options apparently has abandoned some of the earlier options. The same thing happened with the upgrade to 3.5, only in that case it was a significant rewrite of the CSS for the bootstrap slider — see https://www.ads-software.com/support/topic/problem-with-boostrap-slider-caption-after-theme-upgrade

That’s what is holding me back on upgrading on my live site. I am thinking that I need to move any customizations I have made via the back end into the child style.css …or else I will just be facing the same problem again in 6 months or whenever the authors decide to go to 3.7.

Hi Abigailm

I went through the same upgrade issues in 3.5 ??

I wanted to keep theme CSS as small as possible, but I think you are right. I do not upgrade Live either!

Thanks

David

I agree with you in theory about keeping the style.css file lean, but it really is only a few lines of code and trivial in comparison to the load time of all of the other styles and javascript that tend to be loaded with any feature-rich theme. Once you have the styles set up, you can minify them.

Same problem here: gilitadas.com

What should I update in the child theme? I’m not clear about that.

You can first try to make corrections to Theme Options.

To avoid the change to white text on hover, go to:

Appearance > Theme Options > Styling > Menu and look for the “Menu hover font color”

Well, I had to revert to the parent theme to solve the mesh. The find box icon is still lower than it should be. If I activate the child theme everything goes wrong: menu with mobile format even on a desktop, slider text aligned to the left…

So the question is: what should I add to the child theme other than functions.php and style.css?

I also have big problems with the evolve theme update. Now I have to put back my backup again (third time) because updating of the theme is gone bad again. Clearing cache and all is not the solution. I already did that but no luck.

Check https://www.eckkies.nl to see the problem.

breitlingwings – I found that the problems I had with the mobile menu was due to a custom header.php with my child theme. In my case, I had added only one small customization (a translation bar immediately below the social media links). I found that the solution was to delete the child header.php, and to add my modification instead to a child template with this path and file name:
/templates/header_v1.php

I was successful in getting all formatting issues resolved.

I also had the issue with the search box icon, but for me that was because the upgrade change the font size on the menu. So that problem was resolved simply by changing the appropriate font size specification in my style sheet.

Hi there,

I updated the site

https://stimmprofis-institut.de/

today. All went fine but the update of evolve theme reverted to the default configuration. I saved the evolve theme options before upgrade and applied them afterwards. So as i am a free user i recogniced that there have been some changes of free accessible features from 3.5 to 3.6. Is this right?

I haven’t been able to restore my configuration and have to stay with Version 3.5.

Are there any known issues with the free usage of this theme in 3.6?
Have some features been moved to the PRO-version?

Cheers,
Alex

I put back my backup and restored my website https://www.eckkies.nl again to version Evolve 3.5 and leave it this way. Although I use a free version I hope that there will be a better update available.

Hi Fredius

I faced the same dilema and eventually I chose to move forward with v3.6. The problems fell into three cathegories:

1.- Evolve settings different, not migrated or missing (mainly style related).
2.- Evolve settings not working (Eg. general link style settings do not seem to work)
3.- Child theme customizations that did not work (rework required)

On my opinon problem #1 will most probably not be solved by future versions (last december upgrade had similar problems). So it seems that versions divergence increases with versions and that future upgrades could require more work. To me, upgrading smoothly step by step is a better solution so I benefit from improvements and possible security risks.

I will explain you the steps I finally followed for the upgrade, just in case they can be useful for you:

.- Setup an staging environment (either local or hosted)
.- Activate evolve theme and deactivate all the plugins not strictly necessary. Check that desktop menu is not a mobile menu
.- Activate Child theme after having included only the following
1.- Fonts
2.- Translations
3.- Style.css loading only the custom fonts
4.- Functions.php limited to load translations and fonts

.- Check that the child theme works more or less, and start adjusting style.css. This is the part that took most of the time. There is a part of discovery of settings location, discovery of incidences, copying old style.css contents, and sometimes adding new classes to fix some rendering problems.
.- Finally, I reworked on the PHP customizations. For example, my CPT use modified index.php/archive.php files. Header was also slightly adjusted (header of v3.5 is not compatible with v3.6)
.- Reactivate all remaining plugins.
.- Save Redux Settings in staging environment, upgrade Evolve in prod environment, and the Load Redux Settings into prod environment.
.- Review settings with stage URLs and fix them in prod. (Eg. RSS Feed https://localhost/env/feed.rss was renamed https://mysite/feed.rss). This can be done visually or importing settings into Excel

And thats all…

Cheers

David

Alex, I could be mistaken, but I don’t think that anything that was free before requires premium. I think the problem is that some features were rewritten in a way that impacts display. In particular, the upgraded version allows a choice of different header styles. In the free version there are 2 styles to choose from, with more styles available in premium. The previous version only had one style. But in order to give the choice, the templates were rewritten, with an accompanying change in configuration options.

I did the same as David (zulok) — I was frustrated but decided it was best to implement the upgrade, but deferred the task until a time when I could take things slowly and carefully, one step at a time. In the meantime I set my styles for my child theme in a staging site. I didn’t move to the production site until I had solved all of the display issues first in the staging site.

Hi @denzel,
Sorry for my very late response, but I didn’t have any time sooner to go ‘make a mess of my live website’ ??
But now I did have some time and it didn’t become a mess because the plugin you suggested really worked. Thanks for your tip!

@mvdweer You are welcome!