Dynamic Widgets 1.5.6

I’m pleased to announce that the next update of Dynamic Widgets has just become avaialble. Version 1.5.5 1.5.6 has the following features added, bugs fixed and changes:

  • Added WordPress filter ‘dynwid_urlprefix’ in case Dynamic Widgets detects the URL wrong.
  • Added WordPress filter ‘dynwid_taxonomies’ to be able to remove taxonomies from the admin view.
  • Added WordPress filter ‘dynwid_admin_modules’ to be able to remove modules from the admin view by request of Rick Anderson from Build Your Own Business Website who made a financial contribution to make this possible.
  • Added Toggle all sections button for visually impaired users.
  • Bugfix for Notice: Trying to get property of non-object in post-template.php on line 1275.
  • Bugfix for not using a full PHP opening tag in dynwid_admin_overview.php.
  • Bugfix for exception rules in single post types sometimes not followed.
  • Bugfix for Warning: Declaration of DW_CustomPost::registerOption() should be compatible with DWModule::registerOption($dwoption)
  • Bugfix for WPML category fails to follow the rules with the help and financial support by Advancis.
  • Changed the taxonomy terms tree to use ‘lazy loading’ by request of Rick Anderson from Build Your Own Business Website who made a financial contribution to make this possible.
  • Moved minimum PHP version up to 5.2.7 because of a PHP bug in lower versions not exposing all class properties while in the right scope. Thanks Sébastien for finding out!

UPDATE: The people who downloaded 1.5.5, please install 1.5.6. Due to a wrong copy command the wrong files were included in the 1.5.5 release.

 

23 Comments to “Dynamic Widgets 1.5.6”

  • Hallo,

    wanneer ik bij wordpress 3.7.1 theme responsive van CyberChimps.com de plugin Dynamic widgets actieveren wil krijg ik de melding: Oops! Something went horribly wrong. Please reinstall Dynamic Widgets.

    Ik heb dit gedaan, maar krijg steeds dezelfde melding. Is er een oplossing?

    Groet en dank

    Thorsten

    • Ja, er is een oplossing. Lees de FAQ.

      • I want to build a multisite wordpress site. As I can read this plugin is not working on it. Is this correct?

        • It is working, but only when you activate it on a single site base. No network activation.

        • Hello Jacco,

          it is working perfect!

          Thank you!

          Verry usefull plugin 🙂 I’ll make a donation soon.

          Regards

          Thorsten

  • Hi there I used version 1.5.4 no problem if install version 1.5.6. got error using wp 3.7.1

    Fatal error: Call to undefined function add_submenu_page() in /var/www/virtual/labomar.com/vhosts/www/htdocs/_sito-nuovo/it/wp-content/plugins/dynamic-widgets/dynamic-widgets.php on line 633

    But not with all my websites.

    • Your host is not meeting the requirements (anymore). Since version 1.5.6 the minimal PHP version is 5.2.7 (see also the post). The error you get is actually a bug which got fixed in version 1.5.6.1.

  • After each save i get a notice code. Everything seems to be working with the widgets but do’t know what this code is about.

    `Notice: Undefined index: page_act in /var/www/vhosts/aether.gr/httpdocs/wp-content/plugins/dynamic-widgets/classes/dwmodule_class.php on line 293 Notice: Undefined index: page_act in /var/www/vhosts/aether.gr/httpdocs/wp-content/plugins/dynamic-widgets/classes/dwmodule_class.php on line 295 Notice: Undefined index: page_act in /var/www/vhosts/aether.gr/httpdocs/wp-content/plugins/dynamic-widgets/classes/dwmodule_class.php on line 298 Notice: Undefined index: page_childs_act in /var/www/vhosts/aether.gr/httpdocs/wp-content/plugins/dynamic-widgets/classes/dwmodule_class.php on line 301 Notice: Undefined index: page_childs_act in /var/www/vhosts/aether.gr/httpdocs/wp-content/plugins/dynamic-widgets/classes/dwmodule_class.php on line 304 Notice: wpdb::escape is deprecated since version 3.6! Use wpdb::prepare() or esc_sql() instead. in /var/www/vhosts/aether.gr/httpdocs/wp-includes/functions.php on line 2900 Notice: wpdb::escape is deprecated since version 3.6! Use wpdb::prepare() or esc_sql() instead. in /var/www/vhosts/aether.gr/httpdocs/wp-includes/functions.php on line 2900 Notice: wpdb::escape is deprecated since version 3.6! Use wpdb::prepare() or esc_sql() instead. in /var/www/vhosts/aether.gr/httpdocs/wp-includes/functions.php on line 2900 Notice: wpdb::escape is deprecated since version 3.6! `

    • Thanks! A couple of those notices I already had. Notices are never fatal. It’s a warning basically. I advise by the way not to show notices in a production environment.

  • Hello,
    Thanks for this wonderful plugin !!
    I run wordpress last version and several extension every thing updated and every thing works fine but when edit a dynamic widget i get this :

    Strict Standards: Declaration of DW_Author::mkGUI() should be compatible with DWModule::mkGUI($type, $title, $question, $info, $except = false, $list = false, $name = NULL) in /Applications/MAMP/htdocs/…/wp-content/plugins/dynamic-widgets/mods/author_module.php on line 9

    Strict Standards: Declaration of DW_Category::GUIComplex() should be compatible with DWModule::GUIComplex($except, $list, $extra = NULL, $name = NULL) in /Applications/MAMP/htdocs/…/wp-content/plugins/dynamic-widgets/mods/category_module.php on line 9

    Strict Standards: Declaration of DW_Page_Walker::start_lvl() should be compatible with Walker::start_lvl(&$output, $depth = 0, $args = Array) in /Applications/MAMP/htdocs/…/wp-content/plugins/dynamic-widgets/mods/pages_module.php on line 139

    Strict Standards: Declaration of DW_Page_Walker::end_lvl() should be compatible with Walker::end_lvl(&$output, $depth = 0, $args = Array) in /Applications/MAMP/htdocs/…/wp-content/plugins/dynamic-widgets/mods/pages_module.php on line 139

    Strict Standards: Declaration of DW_Page_Walker::start_el() should be compatible with Walker::start_el(&$output, $object, $depth = 0, $args = Array, $current_object_id = 0) in /Applications/MAMP/htdocs/…/wp-content/plugins/dynamic-widgets/mods/pages_module.php on line 139

    Strict Standards: Declaration of DW_Page_Walker::end_el() should be compatible with Walker::end_el(&$output, $object, $depth = 0, $args = Array) in /Applications/MAMP/htdocs/…/wp-content/plugins/dynamic-widgets/mods/pages_module.php on line 139

    • Yeah, WordPress changed a lot in the last few updates there. Hard to catch up, but I’ll get there. Luckily it are all just strict warnings. Nothing serious. WordPress and DW will function normally. In production environments all notices should be turned off anyway.

  • Yes lots of new stuff !! including the automatic update would you also get this feature ?? thanks for your work

    • Please correct me if I’m wrong. As far as I know auto-update of plugins needs to be enabled site-wide by adding a filter.

  • Hi, does it plugin works with shortcodes? Is it possible to use this plugin to insert widgets (i.e. banners) inside posts?

    • I’m sorry, no… that’s not the way it works. It only works from a dynamic sidebar. Of course uou could define an extra sidebar in the single posts template and then use DW to control the banner in a widget.

  • Hi,
    I set the optinon „not in error page” but the widget sitll apear on error page. What to do?
    Thank you

    • Please try the OLD method.

  • In a nutshell the widget no longer seems to recognise my Page sidebar settings, tried Old version and checked wp_head is being called but despite ensuring widgets are dynamic and selecting which pages to NOT show a particular sidebar setting, and Saving that setting, the change never takes place and the widget remains displaying on all pages?

    I can get the widget to display on a static Front page when a post, I can display widget on Pages when set to All pages (but it remains on display in the Pages I exclude).

    My site uses the Atahualpa theme

    • The good news is that such kind of things do not happen suddenly. Something must have been changed that causes the problem. The bad news is that you have to find out what has been changed. One thing you can try anyway is doing a deactivate > reactivate cycle. Especially when you upgraded DW manually.

  • Apologies, please notify me of any followup comments via email, many thanks.

  • Losing faith that I will be able to get this plugin to work again, I have created a Dump if any use to you in helping me understand why it does not work with my theme, Atahualpa?

    • Have you tried the deactivate > reactivate cycle?

      • Hi, Thank you for the reply, yes even tried uninstalling and re-installing, tried different Themes too, in the end I have installed another plugin that does the same thing and it works fine, sorry about that as would have been great to pin down problem I was experiencing with DW as I like the user interface.

        Keep up the good work

        Amanda