WordPress.org

Ready to get started?Download WordPress

Forums

Latest twitter sidebar widget
[resolved] fopen, fwrite, fclose errors? (5 posts)

  1. Clicknathan
    Member
    Posted 1 year ago #

    I'm getting all of these errors when using the plugin:

    Warning: fopen(/usr/www/users/website/devsite/wp-content/plugins/latest-twitter-sidebar-widget/website.json) [function.fopen]: failed to open stream: Permission denied in/usr/www/users/website/devsite/wp-content/plugins/latest-twitter-sidebar-widget/latest_twitter_widget.phpon line 252
    
    Warning: fwrite() expects parameter 1 to be resource, boolean given in/usr/www/users/website/devsite/wp-content/plugins/latest-twitter-sidebar-widget/latest_twitter_widget.phpon line 253
    
    Warning: fclose() expects parameter 1 to be resource, boolean given in/usr/www/users/website/devsite/wp-content/plugins/latest-twitter-sidebar-widget/latest_twitter_widget.phpon line 254

    The plugin still works, in that it shows everything off at the bottom, but those errors appear above it all. Any ideas?

    http://wordpress.org/extend/plugins/latest-twitter-sidebar-widget/

  2. Corey Salzano
    Member
    Plugin Author

    Posted 1 year ago #

    The clue in those warnings is Permission denied in/usr/www/users/website/devsite/wp-content/plugins/latest-twitter-sidebar-widget/latest_twitter_widget.phpon line 252

    The script does not have sufficient permissions on the server to read a file in the same directory. I do not expect the plugin to work reliably if it cannot save a local copy of the twitter data.

    You could try this fix that worked for some other users: http://wordpress.org/support/topic/plugin-latest-twitter-sidebar-widget-only-json-showing?replies=3

  3. Clicknathan
    Member
    Posted 1 year ago #

    Yeah my permissions were set to 755 (as you stated in the other thread). I had to change them to 777 in order to get it to work, which I don't believe is all that desirable...what would you recommend?

    Love the plugin otherwise, though, working wonderfully. :)

  4. Corey Salzano
    Member
    Plugin Author

    Posted 1 year ago #

    I am torn about this. I have ran this plugin on a couple different shared hosting servers (HostGator, 1&1), and I have not had to change any permissions for it to operate. I agree that it sucks to have 777 permissions out there just to get some tweets on your sidebar.

    I would like to rewrite the whole plugin to store the data in an option instead of a file on disk, but I can't justify putting a lot of time into developing for twitter anymore because they treat developers very poorly. (Surprise! That API you were using is gone, now!)

  5. Clicknathan
    Member
    Posted 1 year ago #

    Yeah, I definitely feel you on Twitter's attitude toward developers. That's the whole reason I was using this plugin, as a quick fix since my old custom development died after they decided to change everything up so they can keep their data in their precious wall.

    Thanks anyway, Corey!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.