This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.

Strict Standards Error

  • Creator
  • #12026

    Just upgrade my version of php and am getting this error while using jumpstart:

    Strict Standards: Declaration of ThemeBlvd_Select_Menu_Walker::start_el() should be compatible with Walker_Nav_Menu::start_el(&$output, $item, $depth = 0, $args = Array, $id = 0) in /wp-content/themes/jumpstart/framework/includes/parts.php on line 459

    Any ideas?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Author
  • #12030
    Jason Bobich

    Sounds pretty minor, but I can look into it for the next update to keep things tighty for sure. What version of PHP did you update to?


    5.4.. looks like it’s something to do with 3.6

    Jason Bobich

    All right, this one is fixed for the next update. Thanks for pointing it out.

    If you’d like to fix, you just need to change line 438 in /framework/includes/parts.php from this:

    function start_el( &$output, $item, $depth, $args ) {

    To this:

    function start_el( &$output, $item, $depth = 0, $args = array(), $id = 0 ) {

    Yes one down but an average site with average plugins can have tons more.

    So how to disable anal strict check in 5.4 and 5.5:

    Check links and if useful paste that 1 line of code in a file placed in /wp-content/mu-plugins folder. If not I guess it kicks in too late.

    Plugin Name: Remove E_STRICT fra PHP 5.4, 5.5
    Plugin URI: http://
    Description: Remove E_STRICT from PHP 5.4, give problems with some wp- devs.
    Version: 1.0
    Author: Sad Face
    Author URI: http://
    error_reporting(E_ALL ^ E_STRICT);
    //error_reporting(E_ALL & ~E_STRICT & ~E_NOTICE);

    Problem which is a feature! is WordPress 3.6 vs. newer PHP, born here

    Strict are strict but commented out line also remove notices – more debatable and devs. should also be more willing to fix. But hmm, just one funky plugin can mess up wp-debug log so can be useful. Some will give dozens, 100s in a flash.

    Btw, not sure why but I remember changing line 1094 in helpers.php from

    $parts[$last]['text'] .= ' ('.themeblvd_get_local('page').' '.get_query_var('paged').')';


    if( isset ( $parts[$last]['text'] ) ) { $parts[$last]['text'] .= ' ('.themeblvd_get_local('page').' '.get_query_var('paged').')'; }

    Have strong feeling this is PHP 5.4/5.5 notice.

    I have abandoned newer than 5.3.x for now. Possible to pull off but too troublesome as of today.


    Did I say 100s, how about 141065 for 1 page load. Is true for this plugin, try it 🙂 26.2mb log file in 1 second. All spitting out this line

    [03-Oct-2013 22:48:48 Europe/London] PHP Strict Standards:  Only variables should be assigned by reference in /wp-content/plugins/bbpress-string-swap/includes/bbpsswap-frontend.php on line 341

    Make troubleshooting hopeless so away with strict check is my tactic. If no errors, warnings, notices, deprecated notices that will have to do.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.