WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: Twitter Blog] Fatal error upon activation (6 posts)

  1. Erlend Sogge Heggen
    Member
    Posted 4 years ago #

    I keep receiving this fatal error upon activating your plug-in:

    Fatal error: Call to undefined function curl_init() in /var/www/blog/wp-content/plugins/twitter-blog/twitter-blog.php on line 338

    It puts my entire admin panel out of action. As soon as I removed twitter-blog.php by FTP the error was resolved. I recently had Twitter Tools plus Twitter Tools: Bit.ly (separate author) installed but deactivated and deleted before installing your plug-in.
    Wickett Twitter Widget is still installed.

    http://wordpress.org/extend/plugins/twitter-blog/

  2. saluyot
    Member
    Posted 4 years ago #

    i have the same problem with twitter-blog. i'm using wordpress 2.8.4. i cannot do anything in my wp dashboard because of this Fatal error: Call to undefined function curl_init() in /var/www/blog/wp-content/plugins/twitter-blog/twitter-blog.php on line 338

    what's wrong?

    please reply. thanks!

  3. saluyot
    Member
    Posted 4 years ago #

    wonder why.

  4. saluyot
    Member
    Posted 4 years ago #

    have just deleted the offending twitter-blog.php through ftp. will not use anything from the plugin writer/programmer (Chris Mielke) ever again because of buggy plugin like this one and especially without support here or anything of the kind to inform us users what to do. i'll never recommend it to friends using wp either else they will blame me later.

  5. Milkdog7
    Member
    Posted 4 years ago #

    WordPress doesn't notify me when something is posted here. I try to check it frequently, but had a death in the family over the weekend. Contacting me via email is the best way.

    As for the problem... Twitter Blog requires the CURL library to run. I have an open ticket for WordPress to see if I can cancel the activation if a user does not have it, but I've heard no response yet.

    I'll try to add a check to notify users what the problem is so this error doesn't cause a "fatal error".

    Sorry for the slow response, but I hope you understand.

  6. Milkdog7
    Member
    Posted 4 years ago #

    Sorry, I just discovered I can subscribe to an RSS feed for these. I have done so, but I also hope that 24 hrs is a suitable turn-around time for addressing problem with a free plugin that I make no money off of.

Topic Closed

This topic has been closed to new replies.

About this Topic