WordPress.org

Ready to get started?Download WordPress

Forums

Juiz Last Tweet Widget
[resolved] Warning: Latest update breaks lots of areas on website (11 posts)

  1. thewpguy
    Member
    Posted 1 year ago #

    I have updated 2 websites using this plugin with dramatic effects to both. So have had to roll back urgently to the previous version.

    1st website:
    Using Headway themes all of the content on the blog page disappeared.
    Get message in sidebar saying to update OAuth settings or something like that.

    2nd Website
    Slider froze and slider navigation buttons disappeared.
    Updated OAuth settings and did not resolve issue.

    http://wordpress.org/extend/plugins/juiz-last-tweet-widget/

  2. TheChicSpy
    Member
    Posted 1 year ago #

    Hello thewpguy,

    How did you roll back. Do you have the old file?

  3. thewpguy
    Member
    Posted 1 year ago #

    Hi,
    I had vaultpress backup running so restores are hands free and don't need the old files.

    I do have 1.1.4 if you need it.

    Below is neat trick someone told me once where you can find previous version of plugins if you follow the format in the link.

    http://plugins.svn.wordpress.org/juiz-last-tweet-widget/tags/1.1.4/

  4. EDJ
    Member
    Posted 1 year ago #

    Thanks thewpguy! Used your URL to rollback to the previous version and everything works fine now.

    The widget had stopped displaying tweets and the avatar but the grey box and twitter bird icon were displaying.

  5. thewpguy
    Member
    Posted 1 year ago #

    You're very welcome EDJ,
    I know that feeling when things return to normal and the world finds its balance again.

    It can really take a lot of things out for some reason the new code is conflicting all over the place.

    Another tip is if its on a client site and the client might accidentally update it and break things again then you can do this until it gets sorted out with future updates.

    Left side of admin area -> Plugins
    -> Go to the plugin and click on 'Edit' under the plugin Title
    -> Change the version number to 1001.1.4 (its near the top about line 6)
    -> click on 'Update file'

    That way its easy to see you have dialled up the version number and its easy to work out what it should be.
    More importantly it won't keep prompting to update as its a much larger number than the actual current version.

  6. robmeerwijk
    Member
    Posted 1 year ago #

    Yeah right, page source code stops right after de juiz div. No wonder you get into problems then :-)

    I have removed the plugin and all is well now!

  7. delatitude
    Member
    Posted 1 year ago #

    Hi.

    For those of the folks who are facing this same issue, they can do the following as I have done untill the plugin gets an update.

    1. create a new folder named "inc" inside "juiz-last-tweet-widget" (this folder can be found in "Plugins").

    2. Download two files OAuth.php & twitteroauth.php from the following link to the newly created folder "inc".
    https://github.com/abraham/twitteroauth/tree/master/twitteroauth

    3. Update OAuth settings that you get from the twitter application from your account.

    And that's it. It works !

  8. Geoffrey
    Member
    Plugin Author

    Posted 1 year ago #

    Yeah sorry for this missing folder.
    Seems to be an error coming from my SVN Tool (SmartSVN considers the folder as committed =_=)
    The 1.2.1 fixes this issue.

    Again, sorry.
    Thank you.
    Feedback are welcome :)

  9. Geoffrey
    Member
    Plugin Author

    Posted 1 year ago #

    thewpguy : never do that, if old version of a plugin has a security issue, your plugin will never be updated...
    You're crazy! :p

  10. Nessdufrat
    Member
    Posted 1 year ago #

    Thanks for the very quick reaction! I noticed the plugin not working yesterday, thought it was an issue with Twitter, and thanks to your new update, everything's working great again :)

  11. thewpguy
    Member
    Posted 1 year ago #

    Thank you Geoffrey and delatitude,

    Great solution to the issue, I will give it another go soon.

    Agreed It can be a dangerous option to increase the version number if there are security updates after doing so.

    It should only be used in emergencies which is what I call it when a plugin takes down all content of a home page if updated. In this case I am purely waiting for a stable version to return they I change the version number back to what it was.

    I really appreciate the work you have put into this plugin Geoffrey and I hope I speak for the others in this conversation. Your response time was amazing and really appreciated.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.