Support Forum

Simple:Press 6 Theme Topics

Unexpected Actions Menu Behavior with Reboot on Mobile

Page: 1 2 3 4

Unexpected Actions Menu Behavior with Reboot on Mobile

Yellow Swordfish

Glinton, England

SP Master

Offline

May 3, 2016 - 5:26 pm

It might depend a little on at which point it is enqueued but the first thing to try would be to wrap that enqueue line of code in this:

if ( sp_is_forumpage() == false ) {
.... do the enqueue here
}

I assume you will try this on your sandbox system first so it should be safe. It just depends whether SP has had a chance to initialise the info it needs at the point of the enqueue. If not and the above errors then there are other ways we can investigate...

YELLOW

SWORDFISH

jim

Here and Now

Member

Pro Subscribers

Offline

May 3, 2016 - 6:05 pm

Yellow Swordfish said
...the first thing to try would be to wrap that enqueue line of code in this:
if ( sp_is_forumpage() == false ) {
.... do the enqueue here
}

Thanks for that, I actually went the dequeue route. I added the following to the theme functions:

/* *** Dequeue modernizr on Forums. *** */
function woomod_dequeue() {
   if ( is_page( 'forums' ) ) {
   wp_dequeue_script( 'modernizr' );
   }
}
add_action( 'wp_print_scripts', 'woomod_dequeue', 100 );
/* *** END Dequeue modernizr *** */

Any concerns with this?

So far, it seems to do the trick on our dev site. Modernizr loads on other pages but not on forums/ or PM inbox, Profile, etc. And, the toolset slides up within view, as it should!

It's a Band-Aid, but I guess those are sometimes required when not everybody plays nice together in the sandbox...just need to ensure nothing else has imploded with this theme hack before updating our live site, and putting this topic to rest.

Simple:Press powers the Tripawds Discussion Forums.

It's better to hop on three legs than to limp on four.

The Tripawds Blogs Community is made possible by The Tripawds Foundation.

Yellow Swordfish

Glinton, England

SP Master

Offline

May 3, 2016 - 6:43 pm

Sure the method you have used is fine.

I would really like to know the reason for this. Modernizr itself is not the cause. It is either a combination of Modernizr and something else or somewhere in the scripts where a Modernizr function is being used. But that is a bit like looking for a needle in a haystack if you don't know the code.

As the guys said - you could probably get away without it although there may be the odd user still using IE6!

YELLOW

SWORDFISH

jim

Here and Now

Member

Pro Subscribers

Offline