Support » Plugin: All In One Favicon » error after upgrading to latest

  • Resolved Mitch

    (@n2rga)


    got an error after upgrading to latest version via auto update

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 101

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 102

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 103

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 104

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 109

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 110

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 111

    Warning: _() expects exactly 1 parameter, 2 given in /home/xxxxxx/public_html/wp-content/plugins/all-in-one-favicon/all-in-one-favicon.php on line 112

    http://wordpress.org/extend/plugins/all-in-one-favicon/

Viewing 12 replies - 1 through 12 (of 12 total)
  • I have the same error messages on mine, as well – –
    I’m running WordPress 3.5

    And all errors disappear with the deactivation of All-in-one Favicon –

    Yes, but then you don’t have any, you know, Favicons.

    I’m sure when the author see’s this if he/she sees this it will be fixed until then I shut it off

    I am having the exact same issue with my clients website.

    That is just crazy, guys! Me two, I was going to hell for a minute. But I had one more problem: my language (Bulgarian) suffered greatly… Deactivated it and all went correct. Can this be from some functions in Better WP Security?

    Yes. me too. I am on the same boat as everyone here. this sucks. update means improvement not crash and errors and problems..

    same problem – seemed to break something in the back-end.

    everything appears to be OK client-side so think it’s fine to leave active (if you can put up with the error messages)

    Any chance of a new update?

    I just update my all in one fav icon plugin too and had the same warnings, but its a simple fix and just a little mistake in the coding of that file.

    Simply head to the file in the warning and change the following lines of code from:

    'frontendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
            'frontendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
            'frontendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
            'frontendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
          );
    
          //mapping of favicon types to translatable Strings
          $this->aioFaviconBackendMap = array(
            'backendICO' => _('ICO',AIOFAVICON_TEXTDOMAIN),
            'backendGIF' => _('GIF',AIOFAVICON_TEXTDOMAIN),
            'backendPNG' => _('PNG',AIOFAVICON_TEXTDOMAIN),
            'backendApple' => _('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

    Change to:

    'frontendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
            'frontendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
            'frontendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
            'frontendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)
          );
    
          //mapping of favicon types to translatable Strings
          $this->aioFaviconBackendMap = array(
            'backendICO' => __('ICO',AIOFAVICON_TEXTDOMAIN),
            'backendGIF' => __('GIF',AIOFAVICON_TEXTDOMAIN),
            'backendPNG' => __('PNG',AIOFAVICON_TEXTDOMAIN),
            'backendApple' => __('Apple Touch Icon',AIOFAVICON_TEXTDOMAIN)

    All that I have done is added an extra _ to each line (changing each _ to _e would also work, but I thought adding another _ looked easier to the eye when checking over the code in the future), which fixes the problem and will stop displaying the warnings 🙂

    Plugin Contributor techotronic

    (@techotronic)

    Hi,

    I just released 4.2.1 where this is fixed.
    Weird, I didn’t have any errormessages on my WordPress installation…

    Cheers,
    Arne

    very strange – my problem just disappeared after I re-saved the main plugin php file – I made no changes whatsoever though!

    Nice All Fixed was done fast Thank You

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘error after upgrading to latest’ is closed to new replies.