Support » Plugins and Hacks » [Plugin: Bbpress Latest Discussion] Do not upgrade

[Plugin: Bbpress Latest Discussion] Do not upgrade

Viewing 9 replies - 1 through 9 (of 9 total)
  • For me, the latest 1.7 update conflicts with the WP-Cumulus plugin. I get an error saying wp_cumulus_widget() has already been declared. The odd thing is this plugin doesn’t even have a function called wp_cumulus_widget().

    Not sure what’s going on but reverting back to 1.6.4 works okay.

    I’m running WordPress MU 2.8.6, BuddyPress 1.1.3, and bbPress 1.0.2.

    If only I had seen this before… !

    Upon automatic upgrade, got a fatal error on the entire site. Took a while to realize it was this plugin, after renaming the plugins folder, activating one by one, etc.

    For me, it created fatal conflicts with Ad Buttons, and MyBlogLog Readers Roll. Same error as ph23man:
    adbuttons_widget() has already been declared

    I will revert back, as it was working fine before with no conflicts.

    Ok… my bad… i did this unintentionally… 🙁 Anyway the problem come from double call of “widget_init”. Due to my lazyness and copy paste code from wordpress default widget… that what happen…

    Anyway fix has been sent… you can get it from auto update (1.7.1) or download it from development version.


    Sorry for all the inconvenience i have cause…

    Ok… 1 thing bug me… this plugin not conflict with with akismet and any plugin that use the new 2.9 widget class. But on certain plugin like Ad Buttons it conflict… Still cant found the reason WHY!

    @ph23man & buddha trance

    I dont think this is Bbpress Latest Discussion problem since both of the plugin (Ad Buttons & WP Cumulus) break with WP-Polls also. It seem both the plugin not playing nice with wordpress new widget class.

    P/S: i cant reply with my other wordpress account since i dont know why wordpress ban me from posting

    @shirane – first of all, thank you for a very helpful plugin! It’s nice to have the forum discussions on the sidebar.

    The thing is that the previous version of your plugin, had no conflict with the other ones. Wonder why… I reverted back to a 1.5 version (could not find 1.6.4 again) and all is well.

    I will look into the Ad Buttons conflict with WP-Polls (which I am not using), to see if a fix is suggested. Oddly, I also had sudden problems with MyBlogLog Readers Roll too. And only reverting to an older version of bbPress Latest Discussions brought things back to normal. However, it’s always nice to have the latest release…

    I’m giving you a quick hack on how to resolve the error. Open up the conflict plugin (Not Bbpress Latest Discussion) and find “widget_init”. Replace that into “init”. Example:

    add_action('widgets_init', 'widget_init_adbuttons_widget');

    Change into

    add_action('init', 'widget_init_adbuttons_widget');

    Akismet plugin by default not use the “widget_init” (That why there is no conflict with them and they use old widget function) and they been develop by wordpress developer.

    @shirane – Thank you, that worked!

    I have also upgraded to your latest 1.7.2, which mentioned a new conversion engine to avoid encoding problems. At this point, is the hack you suggested needed on upgrade releases of Ad Buttons, or is the conflict resolved?

    Thank you again!

    For the mean time the hack is the only way… I have test both plugin from Viper007Bond and Lesterchan (Both ppl also a very active in wordpress community), and both have conflict with Ad Buttons also. I still cant figure out why the Ad Buttons widget got declare twice but by putting if (function_exists()) code inside the widget function to check if the function has been call or not work perfectly.

    FYI i change akismet plugin widget call into widgets_init and it work just fine. I don’t know why Ad Buttons and WP Cumulus have this problem and i think it not just gonna be this 2 plugin. Maybe it will effect many plugin.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Plugin: Bbpress Latest Discussion] Do not upgrade’ is closed to new replies.