[WEswift]

I have reverted back to 2.70 so we don’t get a blank page. But could you explain what happened? Looks like the wp-config.php file was changed. That shouldn’t happen. Please inform.

[WEswift]

Hello,

I have also updated from 2.70 to 2.75 and we are coming up with a blank page: http://mcknightplace.com/

It says the reply above was private. Help?

[WEswift]

Ed – all true. Thanks again. These themes do rock my socks.

[WEswift]

My selector does target a direct child of the .left-sidebar. That importantly also includes a class that contains “col-” and that doesn’t also have a class that includes “sidebar”. What’s the issue with this logic? It’s working on this page: http://clients.werremeyer.com/frontenacEngineering/markets-served/education/

I see a potential issue if a third column is added, but if it’s not the main content column it may also be a class=sidebar or at least an aside element. In which case I could specify div – but I didn’t want to do that in case other html5 elements might be used in the future to define that element. I’m not sure a three column configuration is possible with this sidebar method at this time.

[WEswift]

Ed – Thanks for input. I think the ultimate fix would be to add a main content column specific class or id. In the interim, I think my prior submitted css is a bit more future proof. Given that column widths can ideally be anything.

[WEswift]

Rui – thanks for the response. I think the provided fix makes certain assumptions that might break in the future. The element .col-sm-8 should probably be specified as a direct child of .has-left-sidebar so that subsequent generations of the same class are not also affected. Additionally, it assumes the widths assigned to the content area and the sidebar are 8 and 4 respectively. With those above considerations, ideally we would use:

.inner-page-wrap.has-left-sidebar > [class*=”col-“]:not(.sidebar)
{
float: right;
}

I think assigning the main content column a class would greatly simplify the selector.

[WEswift]

This reply has been marked as private.

[WEswift]

I’m having the same problem. I think Dante needs to float the main content to the right whenever the parent container has the class “has-left-sidebar”. It’s currently floating the main content column and the sidebar left. Since the content column comes first in the code, the sidebar appears on the right. Here’s an example page:

http://clients.werremeyer.com/frontenacEngineering/markets-served/education/

I can fix this in the custom css code, but a theme level fix is more appropriate in this case. Thanks!

[WEswift]

Ah. The submenu links, in this particular case, are actually on-page anchor links for the current page.

For example, the parent is:
http://clients.werremeyer.com/wgsd/thematic-goals/

And the submenu Culture of Innovation link is:
http://clients.werremeyer.com/wgsd/thematic-goals/#culture-of-innovation

As a test, I replaced the links from the first two submenu links with a #. Those links now appear as intended because their parent element li’s aren’t being given the class “current-menu-item”.

Since this is a highly unique use case, I suspect the theme is not setup to test for an on-page anchor link and differentiate it from the base page link itself. The appropriateness of the “current-menu-item” designation depends on one’s definition of what the “current-menu-item” should be – specifically how granular it should be. I suspect it will be up to me to solve this particular styling challenge with custom css afterall.

Thanks again for your help.

[WEswift]

As mentioned, I could correct this issue with custom css. However, I think the fix is best implemented in the theme itself. The Appearance > Customize feature settings for dropdown hover style (text and background color) seems to be getting misapplied to the default active dropdown links. Please see the attached screenshot for clarification.

Thoughts?

Attachments:

You must be logged in to view attached files.

[WEswift]

Kyle – Thanks for looking into this. It turns out I misunderstood the issue. All is well. Thanks again! -Paul

[WEswift]

This reply has been marked as private.

[WEswift]

Kyle – I didn’t want to modify any core Dante files and break compatibility with theme upgrades. I was able to achieve what I wanted with the following (specifically targeting .menu-item-has-children did the trick):

#mobile-menu ul li a:hover, #mobile-menu ul li a:focus, #mobile-menu ul li:hover > a, #mobile-menu ul li:focus > a, #mobile-menu ul li.menu-item-has-children:focus > a, #mobile-menu ul li.menu-item-has-children:hover > a { color: #CA1014 !important; }

Thanks for the assist.

[WEswift]

I’m already using that style declaration in custom css. It’s not being applied in the scenario mentioned.

#mobile-menu ul li a { color: #252525; }

[WEswift]

Kyle – the forced login has been turned off temporarily to simplify testing. Keep me posted. Thanks! -Paul