Home › Forums › Weaver Xtreme Theme › problem with menu color
- This topic has 75 replies, 4 voices, and was last updated 3 years, 3 months ago by
beethoven.
-
AuthorPosts
-
June 2, 2023 at 13:34 UTC - Views: 75 #72964
beethoven
Participantnothing else is missing, only Additional CSS
June 2, 2023 at 16:19 UTC - Views: 68 #72965scrambler
ModeratorLe mystère s’épaissi ….
Try pasting the rule below in the Header BG CSS+ box and post back so I can see if it shows up
.menu-primary .wvrx-menu >li >a {color: red}
June 2, 2023 at 16:51 UTC - Views: 62 #72966beethoven
ParticipantThe pasting is done
June 2, 2023 at 17:00 UTC - Views: 62 #72967beethoven
Participantwhen I inspect the menu items, I can change the color with this line : wrapper a {color: #1D23CF;} Est-ce normal ?
June 3, 2023 at 00:37 UTC - Views: 59 #72968scrambler
ModeratorOK, so the Custom CSS rule placed in the Header BG CSS+ box is not there, so the CSS+ boxes are also broken.
When you inspect the site, you can put all the CSS we mentioned and it works. Right now because the menu CSS is missing, the link color comes from the theme wrapper link color, so a wrapper link rule does work.
@weaver, in summary here is what is going on his site.- Menu CSS rule for the menu item color are missing
- in the developer tools, clicking on the Index link next to some of the CSS rule goes to an empty file
- In the customizer the WordPress Custom CSS item is missing
- Added Custom CSS in the CSS+ box does not show up in the site
June 3, 2023 at 07:39 UTC - Views: 53 #72975This reply has been marked as private.June 3, 2023 at 16:26 UTC - Views: 50 #72979Weaver
KeymasterI am back to my dev site. The fact that it works in the Customizer is what I would have expected.
I’m pretty sure I understand the issue, but have not been able to test it. I should have an idea withing a few hours now.
June 3, 2023 at 19:37 UTC - Views: 43 #72980June 3, 2023 at 21:46 UTC - Views: 54 #72986Weaver
KeymasterOK – all fixed, but I had to play with some setting and the CSS you may have added from previous suggestions.
There were some errors in your CSS also – like one place you’d misspelled line-heigh: which has been fixed.
I’m still not sure where the bug came from. I think it may have gotten started with a Weaver Xtreme 6.2.0 which likely converted the ‘>’ in CSS to ‘>’ due to incorrect and overly aggressive filtering of text output. This meant your custom CSS rules with
.menu-primary .wvrx-menu >li >a {color:#FEEFEF;}
got changed to
.menu-primary .wvrx-menu >li >a {color:#FEEFEF;}
when saved to the settings.So your site has been updated to Weaver Xtreme 6.2.1.4.1 (will be 6.2.1.5 when officially released) that fixes the bad text output filtering.
But … the broken previous settings in your Custom CSS rules did not get auto updated, so I corrected the other settings on your site’s settings. I’m not 100% sure the menu colors ended up as you had intended. They are now #FFEFEF for the menu colors, yellow for the current page, red on yellow for hover. (These can be changed/fixed on Customizer > Menus > Primary Menu Bar > Primary Menu Colors.) I thought the menu bar background itself was too light for the white menu items to be easily readable so I made it a bit darker gray. And I’m not sure the yellow for current page is great.
One note – most of the CSS+ / Custom CSS rules do not use selector values (e.g. .wvrx-menu) – just the style rules in {}s. So when you added selectors to the specific spots, it ended up with a double set of slectors, which of course failed to work as one might expect. On the other hand, the global CSS rules do use selector values. And for some reason your site does not show the Additional CSS – WP Setting option. I don’t know why – my best theory is that your site uses French and Weaver’s customizer rules may be English based. But in fact, it is much better to use Weaver’s global rules as they are then saved in the settings files.
But thank you so much for your patience. It was a bit of a challenge to fix, but I think you should be all set.
Interesting site – especially if I use Chrome to look. Chrome (unlike Firefox) auto-translates to English, and the translations seem decent.
June 3, 2023 at 22:39 UTC - Views: 36 #72987scrambler
ModeratorMay be some caching issue, but I am not seeing any changes right now.
The standard Theme menu CSS for menu item color is still missing. and other issues still there too.
June 3, 2023 at 22:57 UTC - Views: 30 #72988beethoven
Participant@weaver many thanks for your help but @scrambler is right, the issue is still there when the site is seen as user (not logged in)
Another thing : I created two more sites with weaver xtreme : vitaliteyoga.fr and teplitz-theatre.net and both in french and there is the option Additional CSS in the customizer in both of them. So ???
La suite à demain
June 3, 2023 at 23:01 UTC - Views: 28 #72989scrambler
Moderator@weaver, the key issue here is not custom CSS but some theme standard CSSS that is missing.
When you set a color for the primary menu items in the weaver settings, that normally creates a theme rule
.menu-primary .wvrx-menu >li >a {color: color}
But although he has set a color in the theme menu options, that rule is nowhere to be found on his public site (not logged in) and as a result, the menu items color is set by the wrapper link rule (that is present).
So there is a group of Theme CSS rules that does not make it to the public site when not logged in.
June 4, 2023 at 01:20 UTC - Views: 25 #72991This reply has been marked as private.June 4, 2023 at 07:31 UTC - Views: 17 #72992This reply has been marked as private.June 4, 2023 at 10:00 UTC - Views: 14 #72993beethoven
ParticipantDid you see that the issue is only on the menu, not on the submenus ?
June 4, 2023 at 17:38 UTC - Views: 6 #72994scrambler
ModeratorWhen you install Word fence, it should take you through the configuration, then it should do a scan that will report if it finds anything strange.
Have you already tried deactivating ALL non weaver plugins?
And your site is on maintenance right now
-
AuthorPosts
- You must be logged in to reply to this topic.

