WordPress.org

Ready to get started?Download WordPress

Forums

WP to Twitter
[resolved] WP-Twitter require_once error (6 posts)

  1. baszer
    Member
    Posted 1 year ago #

    Hello,

    I really like your plugin, but since a couple of days I have got this error every time I publish a post.

    Warning: require_once(/public/sites/www.manneninderuimte.nl/wp-admin) [function.require-once]: failed to open stream: No such file or directory in /public/sites/www.manneninderuimte.nl/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 599
    
    Fatal error: require_once() [function.require]: Failed opening required '' (include_path='.:/usr/share/php:/usr/share/pear') in /public/sites/www.manneninderuimte.nl/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 599

    I have no idea how to fix it. Can somebody please give me the solution?

    http://wordpress.org/extend/plugins/wp-to-twitter/

  2. Joe Dolson
    Member
    Plugin Author

    Posted 1 year ago #

    What version of WP to Twitter are you using? This is an odd error message, because it implies that WP to Twitter is requiring a resource on line 599...and the current version of WP to Twitter does not do this.

  3. baszer
    Member
    Posted 1 year ago #

    thank you for your anser, I am using Version 2.5.0
    and version 3.4.2 of WP.

  4. Joe Dolson
    Member
    Plugin Author

    Posted 1 year ago #

    Well, I have to be honest - I have no idea what this is. There are a number of problems: first, the error seems to be triggered by line 599 of wp-to-twitter.php -- but that's a blank line. There's nothing there.

    Can you tell me a bit more? What shortener are you using? Have you customized your set up in any way - either WordPress core or WP to Twitter?

  5. baszer
    Member
    Posted 1 year ago #

    weird indeed, but I got it working now. Deleted the old files and installed it again.

    And it worked, thanks for your time.

  6. Joe Dolson
    Member
    Plugin Author

    Posted 1 year ago #

    Perhaps it was just a corrupted download causing wacky problems. Glad it was resolved!

    Best,
    Joe

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic