• Resolved itsmir

    (@itsmir)


    Upgrading from v1.9.9 to v2.0.2 caused the following fatal error:

    Fatal error: Cannot redeclare theme_favicon() (previously declared in /home/wereldwi/public_html/functions.php:31) in /home/wereldwi/public_html/wp-content/themes/wwnew2/functions.php on line 67

    I’ve downgraded to 1.9.9 and all is good once again but would really like to upgrade to v2, so if you have any advice I’d be very grateful.

    Currently running WP 3.9.2

    https://ww.wp.xz.cn/plugins/special-recent-posts/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Luca Grandicelli

    (@lgrandicelli)

    Hello. As you can see, that error does not concern any plugin’s file. Instead, it’s something related to your theme.
    I understand that this happen when you try to activate the last version, but there is nothing in the code of the SRP plugin which handles the theme_favicon function the error is reporting about.

    Thread Starter itsmir

    (@itsmir)

    Thanks for your quick reply, much appreciated.

    I had suspected it was theme related, however as only the SRP plugin kills the site thought I’d ask here. The theme was generated using Artisteer and I have no clue what needs to change in the theme files so it looks like I’ll be staying on v1.9.9 – boooh!

    Thanks for your time.

    Plugin Author Luca Grandicelli

    (@lgrandicelli)

    Ok bu what’s the name of your theme? Can i download it somewhere?

    Thread Starter itsmir

    (@itsmir)

    I’ve zipped the live theme and put it on another server – you can download it here: http://itsmir.nl/temp/wwnew2.zip

    Domain for the theme is wereldwinkelkapelle.nl

    Plugin Author Luca Grandicelli

    (@lgrandicelli)

    thank you.

    Thread Starter itsmir

    (@itsmir)

    Just thought I’d leave a note to let you know I’ve solved this issue with a clean install of WP with no changes to plugins or theme. No idea what caused it but happy that it’s sorted.

    Thanks for your help.

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

The topic ‘Fatal error upgrading to 2.0.2’ is closed to new replies.