MrMiyamoto

I’m suffering from the same hack but that code, or a base_64 encrypted version of it is *nowhere in any of my files*.

Ended up being that the error only shows up before you enable your first code block, so it’s not as big of a deal as I thought. Thanks for looking into it.

I had the problem with IE9 as well. I ended up having to edit the plugin file so that these were the top lines in /mystickymenu/js/mystickymenu.js:

//disable at small screen sizes
var myfixed_disable_small = parseInt(mysticky_name.mysticky_disable_at_width_string);
var mybodyWidth = parseInt(document.body.clientWidth);

//detect IE9
function isIE () {
  var myNav = navigator.userAgent.toLowerCase();
  return (myNav.indexOf('msie') != -1) ? parseInt(myNav.split('msie')[1]) : false;
}

if (mybodyWidth >= myfixed_disable_small && isIE() == false) {

and then edit the main mystickymenu.php on line 472 so that it loads the regular .js instead of .min.js

Turns out there were browser cache issues preventing website visitors who had previously visited my page from seeing the addthis buttons.

I’m using a heavily modified Kubrick theme from back in the day, and the website is https://gameusagi.com.

This code appears:
<div class="addthis_toolbox addthis_default_style" addthis:url='https://gameusagi.com/2012/06/quantum-conundrum-impressions/' addthis:title='Quantum Conundrum Impressions' ><a class="addthis_button_facebook"></a><a class="addthis_button_twitter"></a><a class="addthis_button_n4g"></a><a class="addthis_button_stumbleupon"></a><a class="addthis_button_reddit"></a><a class="addthis_button_preferred_1"></a><a class="addthis_button_compact">

But nothing is rendered. I tried disabling all of my other plugins to see if it was an incompatibility, but even by itself addThis 2.4.1 will not display.

The display problem persists in 2.4.1, but Build Your Own has indeed returned.

WP Search seems to be incompatible with custom menus. It slows down my general post saving/publishing time too. I’ve had to stop using this plugin because of these issues.

Thanks for the help. I ended up just disabling the “Cancel reply” button in WP-Touch. I need Spectacu.la on the mobile devices instead of the default WP-Touch comments because I’ve fully integrated Cubepoints including my own custom badge system with Spectacu.la and don’t want to have to do it all over again with WP-Touch’s comment system. Otherwise, I’m sure your suggestion would be the better option.

While you’re here, there’s still a small bug with my implementation. When you reply directly to a previous comment in WPTouch the “Cancel reply” button shows right on top of the “Post Comment” button.

Here’s what it looks like: https://gameusagi.com/hotlink/wptouch-bug.png

Is there a way to stop this overlap and perhaps have the Cancel Reply button styled in the same way as the Post Comment button?

Thanks.

Okay, I figured it out. For anyone with the same problem, just add:

style="position: relative;"

Into both of the the divs that say class=”comment-buttons” in the includes/functions.php file in Spectacu.la

: D