brianfreytag

This is ridiculous. .live was removed in jquery 1.9. It’s been considered deprecated since 2013, replaced with .on. I can’t believe anything is still using it.

Additionally, this is causing issues with other plugins.

I had to disable this plugin to be able to navigate the menus in Elementor.

You claim that this has been tested up to 5.5… no, it wasn’t.

@lizkarkoski

Sorry, I completely forgot it. Here’s the latest that came this morning:

[91093560/success]

I’m having the same issue with graceoverwhelms.me.

Would you please remove it for me?

Same issue here.

SSH2 credentials.

@karenalenore – One thing you should check is if you’re using any kind of caching plugins. If you’re doing disk or opcache caching of pages/posts and didn’t clear the cache after removing the plugin, the whole thing or remnants of the widget will remain in place until they expire or you delete them.

@annoyingmouse – I can’t really comment on anything beyond what was said in my post. I only posted it to keep my name clean – not to speculate on the outcome.

I have every confidence in Otto and his team to get this issue resolved the way it has to be resolved.

I just want to make it clear that I have not been the maintainer of Social Media Widget since January of 2013 (version 2.9.7).

This post is to disassociate myself with this issue. I want the record to reflect that this issue arose months after I passed off the widget and have not had SVN access since signing over the widget in January. As the original creator of Social Media Widget and beginning its legacy, I want to remain clean of this in the case I decide to release a new WordPress plugin.

I had a discussion with the current maintainer whom I transferred the rights over to – It seems that one of the freelancers that he hired to do some updates decided to go rogue or his password was cracked, though you will have to hear it from him for the full story.

— Update – Changed the version I last pushed in the first paragraph

I just want to make it clear that I have not been the maintainer of Social Media Widget since January of 2013 (version 2.9.7).

This post is to disassociate myself with this issue. I want the record to reflect that this issue arose months after I passed off the widget and have not had SVN access since signing over the widget in January. As the original creator of Social Media Widget and beginning its legacy, I want to remain clean of this in the case I decide to release a new WordPress plugin.

I had a discussion with the current maintainer whom I transferred the rights over to – It seems that one of the freelancers that he hired to do some updates decided to go rogue or his password was cracked, though you will have to hear it from him for the full story.

— Update – Changed the version I last pushed in the first paragraph

Note that I resolved my issue by changing line 21 of sites.php to:

$vl_sites["Bible.com"] = array("singleVerseUrl"=>"https://www.bible.com/bible/111/[book].[chapter].[verse]", "verseRangeUrl"=>"https://www.bible.com/bible/111/[book].[chapter].[verse]-[endverse]", "chapterRangeUrl"=>"https://www.bible.com/bible/111/[book].[chapter].[verse]", "bookFind"=>array(),"bookReplace"=>array());

And then added the following lines after line 44 of verselinks.php:

45 if(get_option('vl_preferred_website') == "Bible.com") {
46       $bookName = substr(str_replace("_","",$bookName),0,3);
47 }

Now Bible.com is working correctly for me.

Note that you don’t have an option to choose Bible version and since the NIV is my version of choice, I manually hard-coded 111 into the URL in sites.php. Note also that Bible.com does not allow searches that span chapters since each chapter is displayed individually.

— Edit – Changed line 46 of verselinks.php because you automatically add “_” to spaces, so 1 Corinthians, 1 Peter, etc, was incorrect.

— Edit 2 – I didn’t notice you already had YouVersion, but now with the merge of YouVersion and Bible.com, YouVersion uses the same query string as Bible.com so that one is also incorrect.

I appreciate everything you did for the widget, Ken. You definitely increased interest and brought it to prominence. Unfortunately, one of the side effects were way more requests than I had the capacity to take care of by myself. Most of the 600,000+ d/l plugins out there are run by a team of developers. It was getting way too big and way too popular for me to keep up-to-date by myself, so when Blink Web Effects came to me and agreed to keep the widget F/OSS, I knew this group would be able to keep up the legacy.

Thanks for everything, Ken.

To demonstrate this, if you don’t use tools like Firebug, or Chrome Developer tools or anything like that:

In the white space to the right of the Facebook icon, double click. You’ll see that it highlights “Search Store.” This shows that something is overlapping.

But I can tell what your problem is going to be.

Under your Search Store div, you have a div “art-center-wrapper” that has the following styles:

div.art-center-wrapper {
position: relative;
float: right;
right: 50%;
}

What this div is doing is covering up over half of the “Follow Us!” widget, which would make any other icons unclickable. You’re going to have to rethink how this div functions so that it doesn’t overlap the div to the left.

Can you please re-active the e-mail icon so I can take a look?

You can just use CSS to resize the 32px icons to 24px quite easily.

This plugin is quite large and cannot handle another complete set of icons, unfortunately.

There are already people who have cheap hosting and cannot install this plugin via the admin panel because their hosting doesn’t allow PHP to complete the entire task of downloading, unzipping or installing this plugin, so this is not something I will be looking in to.

You can just use CSS to resize the 32px icons to 24px quite easily.

This plugin is quite large and cannot handle another complete set of icons, unfortunately.

There are already people who have cheap hosting and cannot install this plugin via the admin panel because their hosting doesn’t allow PHP to complete the entire task of downloading, unzipping or installing this plugin, so this is not something I will be looking in to.