Forum Replies Created
March 8, 2019 at 9:18 am #50484
I gave up on Ubermenu — trying to upgrade it from v2 to v3.? was a nightmare because I had so much custom css in it — not just colors, etc, but margins to align the mega menu submenus, directions of submenus in relation to the main vertical menu, all kinds of things. Plus, I couldn’t really separate the Ubermenu css from custom Graphene css that I had done, which was considerable.
So, I gave up. I upgraded to Graphene Plus and switched the menu to WP Mega Menu, which for the most part works great — have to do some tweaking still, but I’ve only had one problem where I had to contact the developer, and he gave me a very quick css workaround for that.March 4, 2019 at 9:44 am #50472
Just updated to Graphene 2.6 and the error is still there. Yes, only when Ubermenu is activated.March 4, 2019 at 9:28 am #50470
Sorry, I should have include the WP version number. It’s v5.1. I just downloaded Graphene 2.6 but haven’t yet installed it.March 4, 2019 at 5:22 am #50463
A followup on this: I tried changing the menu assigned to the Ubermenu integration from the main menu to another one (actually I tried several). The same warning message appeared in the same place, only with fewer warning message instances. The menu that I chose as the Ubermenu showed up at the bottom of the warnings, exactly as the main menu in my previous post. So there is a definite connection. But why would the warnings appear as well as the functioning menu?
As an experiment I changed my EasyPhp from php 5.6.30 to php 7.13 and ran into an error message that came up immediately when I tried to load the site — I couldn’t get around it. I’m not sure if it’s actually related to the warnings in my original post, but it sounds similar so I thought it might be worth something:
Too few arguments to function graphene_nav_menu_css_class(), 2 passed in D:\EasyPHP-Devserver-17\eds-www\lsl\wp-includes\class-wp-hook.php on line 286 and exactly 3 expected
As soon as I switched back to php 5.6.30 the site would load again but with the original warning messages in the right column.
Your solution worked great and it gave me further ideas. In Joomla you can assign a css class to any page simply by naming it in the page properties, so I wondered if there was a way to do that in WP. If there was, it would mean that I could assign a css class to the pages where I wanted the two column layout and use the default where I wanted a one column layout.
So– I found a WP plugin called “custom-css-stylesheet-for-posts-or-pages” (here:
http://wordpress.org/extend/plugins/custom-css-stylesheet-for-posts-or-pages/) that was supposed to allow me to use custom css on individual pages. I set up the custom-css folder and copied the default style.css into it (renaming the css file of course), and I added your two-column css code to that css file. Except that I changed your
.page-id-XXX .child-pageto just
.page .child-pageso that it wasn’t page id specific.
Now I can open a page in the editor, assign the custom css to that individual page, and get the two column layout whenever I want it. And if I decide to change back to a one column layout, all I have to do is switch the page css back to the default style.css, Works great, and it saves all kinds of messing around dealing with individual page ID’s in the css file (and considering that the site I’m working on has over 80,.000 words of text and I don’t know how many articles, some of which are standalone and some of which are sub-articles under a main section description, dealing with individual page IDs wasn’t something I wanted to do)
Thanks again for your help…