FATAL ERROR suddenly appearing

  • Resolved kneadle

    (@kneadle)


    9 years, 11 months ago

    I think with the WP 3.9.1 upgrade an incompatibility was introduced. I’m running the latest Twenty Eleven theme.

    This is the error message: Fatal error: Cannot use object of type WP_Error as array in /home/etc. …line 535.

    Upon inspecting line 535, I noticed it was trying to get file size of uploaded podcast, so I overrode that value in the newest post. The post would load properly, but then the RSS file was corrupt, which defeats the purpose.

    Any help?

    Thanks,
    David

    https://wordpress.org/plugins/seriously-simple-podcasting/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter kneadle

    (@kneadle)

    9 years, 11 months ago

    To clarify, everything wrote perfectly on May 9, 2014, and then, whammo! Fatal Error, first thing today, May 14.

    Plugin Contributor Hugh Lashbrooke

    (@hlashbrooke)

    9 years, 11 months ago

    Thanks for reporting this – I’m going to look into this today and if the error is what you say it is then it should be a relatively quick fix.

    Thread Starter kneadle

    (@kneadle)

    9 years, 11 months ago

    It seems to be posting better, now, but the RSS feed is still broken.

    My site is http://nachmu.com/podcast

    Right now it’s in its pristine condition, without the new podcast, so the RSS is working fine. Would you like me to “break” it by trying to post a new podcast?

    Thread Starter kneadle

    (@kneadle)

    9 years, 11 months ago

    BTW: thank you. Plugin author can be thankless, I’m sure. I appreciate your attention, and it’s a great plug-in.

    Thread Starter kneadle

    (@kneadle)

    9 years, 11 months ago

    Seems to have magically resolved itself. I’m guessing something was going on in MySQL or the PHP management otherwise.

    Thanks for the attention!

    Plugin Contributor Hugh Lashbrooke

    (@hlashbrooke)

    9 years, 11 months ago

    Thanks for reporting back.

    I did some tests and was unable to reproduce the error, so it sounds like it was a server-specific issue on your side.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘FATAL ERROR suddenly appearing’ is closed to new replies.

Tags