Title: Strict Standards warnings
Last modified: August 21, 2016

---

# Strict Standards warnings

 *  Resolved [davemac](https://wordpress.org/support/users/davemac/)
 * (@davemac)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/strict-standards-warnings/)
 * With debug turned on and using PHP 5.4 I am getting a strict standards warning:
 * Strict Standards: Declaration of lctwidget_Taxonomy_Dropdown_Walker::start_el()
   should be compatible with Walker::start_el(&$output, $object, $depth = 0, $args
   = Array, $current_object_id = 0) in wp-content/plugins/list-custom-taxonomy-widget/
   list-custom-taxonomy-widget.php on line 300
 * [http://wordpress.org/plugins/list-custom-taxonomy-widget/](http://wordpress.org/plugins/list-custom-taxonomy-widget/)

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [Nick Halsey](https://wordpress.org/support/users/celloexpressions/)
 * (@celloexpressions)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/strict-standards-warnings/#post-4019545)
 * Thanks, there was another post about this but it seems to have been deleted due
   to a forum hiccup. I’ll fix it in the next update.
 *  Plugin Author [Nick Halsey](https://wordpress.org/support/users/celloexpressions/)
 * (@celloexpressions)
 * [12 years, 8 months ago](https://wordpress.org/support/topic/strict-standards-warnings/#post-4019546)
 * (also, this is just a warning that was added in 3.6)
 *  Thread Starter [davemac](https://wordpress.org/support/users/davemac/)
 * (@davemac)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/strict-standards-warnings/#post-4019577)
 * Just bumping that I am still receiving these Strict Standards Warnings in latest
   version, thanks.
 *  Plugin Author [Nick Halsey](https://wordpress.org/support/users/celloexpressions/)
 * (@celloexpressions)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/strict-standards-warnings/#post-4019579)
 * Thanks for the bump, I forgot about the current status of this plugin and haven’t
   pushed any updates since this issue came up. [I fixed this issue about 5 months ago in the dev version](https://plugins.trac.wordpress.org/changeset/783423/list-custom-taxonomy-widget)
   but had been having a lot of long-term problems with the dropdown display type
   linking to terms correctly. I’ll schedule this plugin for a big cleanup effort
   and try to push the update, including this fix, in the next few weeks.
 *  Thread Starter [davemac](https://wordpress.org/support/users/davemac/)
 * (@davemac)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/strict-standards-warnings/#post-4019580)
 * Really appreciate that, thanks Nick
 *  [Pixelatic](https://wordpress.org/support/users/davidhealy/)
 * (@davidhealy)
 * [12 years ago](https://wordpress.org/support/topic/strict-standards-warnings/#post-4019585)
 * Any word on a fix for this? I am seeing this same error under WordPress 3.9 using
   version 3.3 of the List Custom Taxonomy Widget plugin and with debug enabled.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Strict Standards warnings’ is closed to new replies.

 * ![](https://ps.w.org/list-custom-taxonomy-widget/assets/icon.svg?rev=1225454)
 * [List Custom Taxonomy Widget](https://wordpress.org/plugins/list-custom-taxonomy-widget/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/list-custom-taxonomy-widget/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/list-custom-taxonomy-widget/)
 * [Active Topics](https://wordpress.org/support/plugin/list-custom-taxonomy-widget/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/list-custom-taxonomy-widget/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/list-custom-taxonomy-widget/reviews/)

## Tags

 * [strict standards](https://wordpress.org/support/topic-tag/strict-standards/)

 * 6 replies
 * 3 participants
 * Last reply from: [Pixelatic](https://wordpress.org/support/users/davidhealy/)
 * Last activity: [12 years ago](https://wordpress.org/support/topic/strict-standards-warnings/#post-4019585)
 * Status: resolved