kennethfeldman

[kennethfeldman]

Thank you! That was certainly it.

I edited the parent theme file — which I’ll let get overwritten with the next update.

Thank you!

[kennethfeldman]

Sweet!

So I’ll just go edit template_redirect myself for now.

[kennethfeldman]

Sure.

I have set up a fresh JS install, with only the TB plugins, and get the same issue.

http://www.kilopapafoxtrot.com/dct/

Sample Page should redirect to Another Page, but gets error.

See redirect-source page using redirect template:

https://postimg.org/image/4e1mxe3f5/

[kennethfeldman]

Thanks Jason,

I see how that all works in general.

But it seems to be putting a new class (category nice name) into the body, and all article divs on the entire page.

However what I’m looking for is to only add a class of current_page_item to only the mini-post-list item (or article in the list) of the current page that is being displayed.

This way, the mini post list in the sidebar can be styled to indicate which is the currently viewed post.

Any way to do that?

[kennethfeldman]

Hey Travis, see this previous post:

http://support.themeblvd.com/forums/topic/top-banner-disappeared/

[kennethfeldman]

Ahhh! Thank you.

[kennethfeldman]

Awesome! Excited to see the next update!

Thanks as always.

[kennethfeldman]

Ugh — False alarm #2.

I think I see what was happening.

I now see that the sticky menu is a full second output/copy of the main menu.

And so if there are too many links to fit in one row within the top level of the main menu, then the sticky menu would also have too many links, and would also wrap to a second line — thus protruding down from behind the top of the screen (where it’s probably trying to hide, just out of view).

So maybe my whole initial issue (above) was caused because the Custom Mobile Menu Function was forcing its new custom menu to replace the main menu (by design) — but was in fact also replacing the sticky menu up above the top of the screen.

(Here’s the rub): I had attempted to expand that side mobile menu by adding a few “quick links” to the beginning (now, top) of that (already quite full) main menu — reasoning that the new links would fit since it now is supposed to appear vertically in the side slide out menu.

But since the Custom Mobile Menu Function effectively replaces the main menu, it also added those links to both the original and sticky menus. THE PROBLEM then came when the page was viewed on iPads with enough width — where the CSS triggered the regular horizontal nav menus to display — but they were still getting the new Mobile Menu. And so they both (the regular and sticky) now had too many links in them to fit horizontally, so they both wrapped to a second line, and as such the sticky menu now became too tall to fit fully hidden up behind the top of the viewport.

Ultimately, it looks like the if>wp_is_mobile method is not robust enough to detect wide-screen (or, side-oriented) mobile devices that could otherwise display the regular menu.

IN THE END — I was able to achieve my “additional quick links” effect in the mobile slide out menu via CSS — however had to the hide the new links from both the main and sticky menu output.

Whew!!!

See it working correctly now in action here: http://www.greenhedges.org/

• This reply was modified 6 years, 10 months ago by kennethfeldman.

[kennethfeldman]

NEVER MIND on Q:1.

I fixed what I needed via CSS.

But Q:2 still seems happen — though not for me any more.

Thanks,

[kennethfeldman]

Hi Jason,

Thanks for this — it works a charm in iPhone and iPad (regular).

But in iPad Pro (the larger size version) it breaks the menus — (in ~two ways):

1) The mobile menu is correctly delivered to the iPad Pro (since it represents itself a mobile device), but the new mobile menu now displays horizontally in place of the regular main menu, across the screen.

(I suspect that the iPad Pro is too wide in pixels to trigger the switch from desktop to mobile-on-the-side) menu. Indeed if I swipe in the split-screen view on the iPadPro, the side-mobile menu gets triggered.)

By itself, this is not a huge problem. But I have added a few more (quick) links to the (beginning of) my mobile menu, and so now the apparent main menu wraps to a second horizontal line in the iPad Pro.

2) By itself, while this is all a bit unsightly, it triggers a second issue with the theme — one that happens on any device even without the your Mobile Menu Function in place:

If the main menu wraps to a second line (because too many links to fit horizontally in one line), then the sticky menu is triggered and partly protrudes down from the top of the screen — as if it thinks the page has been scrolled down.

While this could have something to do with my CSS or other mods, it doesn’t feel like it does.

SO here are my two questions:

ONE: Regarding the Mobile Menu Function: Is there a way to filter out the iPad Pro from receiving the new Mobile Menu?

TWO: Is the too-many-links-in-the-main-nav-bar a bug in the theme?

Take a look here: http://www.greenhedges.org/

You can see for yourself by using Safari Browser on a desktop, by switching to USER AGENT: Safari iOS: iPad.

Jump Start 2.0.4 with Theme Blvd Framework 2.5.2

• This reply was modified 6 years, 11 months ago by kennethfeldman.
• This reply was modified 6 years, 11 months ago by kennethfeldman.

[kennethfeldman]

Adding to this topic:

As admin, I WANT the DELETE buttons.

But I don’t want other user levels to have them.

So I’ve added a function which adds a user-level-class to the body tag of the admin pages.

Then using CSS, I can “turn off” the DELETE links for EDITORS, while leaving them in place for me, the ADMIN.

/**
 * Add class to admin <body>
 */
function my_admin_body_class( $class ) {

    if ( is_user_logged_in() ) {
        $user = new WP_User( get_current_user_id() );
        $class .= ' ' . array_shift( $user->roles );
    }

    return $class;
}
add_filter('admin_body_class', 'my_admin_body_class');

Then the CSS:

body.editor #optionsframework a.delete-element,
body.editor #optionsframework a.delete-section,
body.editor #builder_blvd #optionsframework a.delete-block {
display: none;
}

[kennethfeldman]

Great! All I needed was the admin body.

Thanks!

[kennethfeldman]

Ahhh, never mind — kind of…

I had recently added the following bit to my functions.php — in an attempt to get a unique body class for all admin pages of a certain user level.

This is an extension of the attempt to HIDE the DELETE buttons in the Builder, discussed recently.

My idea was to simply hide them in the builder from non-admin users — and my plan was to add a unique class to the body for each user level with which I could target the DELETE links with CSS.

I found the following on the ‘net somewhere, and unfortunately, this is what is breaking the TB Shortcodes pop up.

I know this is off-topic — but do you have a way for me to add a unique user-level-class to the body of admin pages?

(e.g. body class=”editor” body class=”administrator” etc.)

if ( is_user_logged_in() ) {
    add_filter('body_class','add_role_to_body');
    add_filter('admin_body_class','add_role_to_body');
}
function add_role_to_body($classes) {
    $current_user = new WP_User(get_current_user_id());
    $user_role = array_shift($current_user->roles);
    if (is_admin()) {
        $classes .= 'role-'. $user_role;
    } else {
        $classes[] = 'role-'. $user_role;
    }
    return $classes;
}

• This reply was modified 6 years, 11 months ago by kennethfeldman. Reason: typo

[kennethfeldman]

Great! I’ll do that too (priority 25).

NOTE: I just found another (red text) DELETE link. (And I suppose there are more in elements that I just haven’t used yet…)

This one’s in a TABS element inside of a COLUMNS element.

It’s: #builder_blvd #optionsframework a.delete-block

This one needs the #builder_blvd ID in front of the #optionsframework in order to override another display:block style coming from elsewhere.

So together now (so far) it’s:

#optionsframework a.delete-element,
#optionsframework a.delete-section,
#builder_blvd #optionsframework a.delete-block {
display: none;
}

[kennethfeldman]

Now I feel a little better about clients rooting around in the template builder area.

Thanks Jason and askwpgirl!

[Author]

Replies