benstewart

Got it! I searched for that stupid shortcode and could not find it. Thanks.

Found it. I figured out that the offending script is automatically created whenever a person updates the “Theme Panel ? Scripts & Styles” tab. I just changed a JS setting on that page and it re-wrote the old file with a new one.

I has “Seedprod Coming Soon Pro” enabled when I installed the theme. The errors seems to have been caused by that plugin because there was HTML from the coming soon page in the JS file. So there is a conflict that should be resolved there.

Thanks!

As a customer I just finished helping another developer add a fix to a commercial plugin of theirs that they said they would not have time to implement in the foreseeable future.I agree that we can all pitch in — especially if we want things done on a specific timeframe.

However, I was not demanding a timeframe at all. I have a site that I just launched for a client. I need to either use this plugin (patched) or use an alternative. I would prefer to use this plugin (patched) and if the patch was about to be released then I could wait for it. However, the patch was going to take more time then I need to find another solution (which I did). Doesn’t matter to me either way. I don’t expect much since this is a free plugin.

With that said, I imagine that CrowdFavorite and Mailchimp have the development resources to maintain their plugins reasonably well.

@alex – Any idea when the update with the patch will be published?

This is still broken. The solution is SIMPLE. Google Charts API uses a different URL for HTTPS traffic but AddThis is trying to load the chart using the insecure URL over either protocol.

If I replace:

//chart.apis.google.com/chart?...

with:

//chart.googleapis.com/chart?...

then the images load properly. Please implement a fix.

And the WordPress HTTPS plugin won’t filter the URL because the protocol has been removed (I imagine in an effort to fix this very issue).

Thanks. First, on plugin update Sunny lost my Cloudflare credentials. Once I got those put back in I noticed that I still cannot disable email notifications. I don’t want a daily email… I want to disable email notifications for blacklisted IPs. Will this be possible?

Just to be safe I actually did:

if (!isset($p['cat']) || !is_array($p['cat'])) {
    $p['cat']=array();
}

It seems to have worked although I didn’t go back through and change all of my code yet.

I have not had an opportunity to try it yet. Busy.

Where am I replacing that code?

Sure. I did:
get_cat_icon('cat=118'); // FAILED!

Then I did:
get_cat_icon(); // SUCCESS!

What I used to have (that used to work properly) was:
echo get_cat_icon("max_icons=1&echo=0&link=0&small=false&cat=".$cat_id);

In that case, the $cat_id variable was being retrieved dynamically by a get_the_category() call and then later a get_the_terms() call instead. But, to eliminate variables (no pun intended) I removed all of the extra options from my get_cat_icon() call and hard-coded the category ID in there. It still didn’t work.

I just had to do the same thing again. After the automatic plugin update the settings page said “No banner found” but once I manually deactivated and reactivated the plugin it gave me the “This WP Bannerize release has a different Database Table struct. WP Bannerize has found an old Database Table. Do you want convert old struct for this release?” message.

I’m running WP 3.0.1 on CentOS Linux hosted by Webfaction with a private PHP 5.2.9 stack.

Ah… I had to manually deactivate and reactivate for the plugin to ask me if I wanted it to upgrade my database tables.

Found the “solution” …

The developers have commented out line 33 of wp-bannerize_widget.php with a note saying “Not used in this version” but it is actually NECESSARY in order pull in the standard WP widget arguments. Just uncomment that line and it should work properly again. The line of code that needs to be uncommented is:
extract($args);

I just hope a future update fixes this oversight instead of disabling the standard functionality again.

Can’t you just use this:

do_shortcode('[wpp]');