Plugin could not be activated because it triggered a fatal error

  • Resolved cGt2099

    (@cgt2099)


    11 years, 6 months ago

    Update fubar’ed my site. Manually deleted and reinstalled.

    Reinstall results with this message:

    Plugin could not be activated because it triggered a fatal error

    Warning: require_once(/nfs/c02/h05/mnt/15224/domains/cgt2099.com/html/blog/wp-content/plugins/feedwordpress/externals/myphp/myphp.class.php) [function.require-once]: failed to open stream: No such file or directory in /wp-content/plugins/feedwordpress/feedwordpress.php on line 105

    Fatal error: require_once() [function.require]: Failed opening required ‘/nfs/c02/h05/mnt/15224/domains/cgt2099.com/html/blog/wp-content/plugins/feedwordpress/externals/myphp/myphp.class.php’ (include_path=’.:/usr/local/php-5.3.15/share/pear’) in /wp-content/plugins/feedwordpress/feedwordpress.php on line 105

    HALP!

    https://www.ads-software.com/extend/plugins/feedwordpress/

Viewing 10 replies - 31 through 40 (of 40 total)
  • Thread Starter cGt2099

    (@cgt2099)

    OP here

    Thank you radgeek for a speedy update. I tested the new release and it’s fixed the problem. Cheers to you for all your work, it’s very much appreciated; and I hope and believe the rest of the posters in this thread will echo or at least feel these sentiments.

    Thanks!

    Thanks for the speedy update. However, my install still only gives the illusion of updates.

    Update complete. 0 new posts were syndicated and 0 existing posts were updated
    Last checked 1 min ago · Next 6:16pm 10 items
    Scheduled to be checked for updates every 60 minutes
    This update schedule was requested by the feed provider using a standard <sy:updateFrequency> element.

    So, if there were 10 items, why didn’t pull them?

    I have another feed that has 750 items, and it pulls none of them either.

    Yet another feed with 50 items, and it doesn’t pull them either.

    Plugin Author C. Johnson

    (@radgeek)

    @miamitom,

    I’m sorry to hear you’re having that problem. It sounds like it is a separate issue from the one being discussed in this thread, and one that I’d need to do some troubleshooting with you to resolve.

    Could you send me an e-mail via the contact page at feedwordpress.radgeek.com with the version of WordPress you’re using, the version of PHP (if you don’t know it, you can find that out by going to Syndication > Diagnostics), the URLs of the feeds you’re having this problem with, and let me know whether the same thing happens with all the feeds, or only with some? I’ll see if I can replicate the problem on a test box, and if not, can follow up to see if I can find out where the problem is coming in on your end.

    Thanks,
    -C

    Thanks will do.

    Running Feedwordpress diagnostics consumed more memory for mysql than my webhosting company would allow, and I have to wait now for them to unblock my database for wordpress before I can continue.

    Thanks for the fix!

    Too bad that some people take this to complain in general.

    @sinitita – It’s not about complaining. This is a support forum. I’m doing exactly what this forum is for. You want to give kudos and warm fuzzies – great, but this is a support forum and I’m doing my best to give the developer as much info as I can to help fix the problem.

    Updated with no problems now. Thanks radgeek!

    WPChina

    (@wordpresschina)

    Yes I have seen the “This update schedule was requested by the feed provider using a standard <sy:updateFrequency> element.” problem on a number of FWP installs hosted on different/separate boxes and it’s not pulling any data. This thread was started 3 months ago and I searched and couldn’t find if there is a fix yet for this. Is it a fix I’m missing?

    yes latest update (3 months ago) fixed this for me.

Viewing 10 replies - 31 through 40 (of 40 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error’ is closed to new replies.