Oh I just noticed this part in the Debug Tweet Data panel:
“1Notice: Undefined index: Accept-Encoding in \/home\/kebo\/home\/api-twitter\/public_html\/request\/index.php on line 129
Hi dossolini,
Sorry you are having problems, thank you for providing the error from the debug data. I will look into this and see if I can work out why it might have stopped working suddenly. The error from the API is certainly a red flag.
Hi dossolini,
I have found and fixed one bug thanks to your report, but will need to see whether or not that resolves your problem. The error message you had showed an issue in how I was checking for GZIP support. If the ‘Accept-Encoding’ header was not set at all, it would assume GZIP was supported. This would result in the site being unable to decode/understand the response from my API.
I have just released a hotfix to the API servers to address this and will be monitoring them closely to ensure there are no other issues with my code change.
It might be that this resolves your problems, but either way I would love to hear back and if needed I will continue debugging!
Hi Peter,
Thanks for looking into this for me!
I just checked the Debug Tweet Data panel but I’m still getting the same error:
“1Notice: Undefined index: Accept-Encoding in \/home\/kebo\/home\/api-twitter\/public_html\/request\/index.php on line 129
The page where I’m using the widget is here:
http://www1.earningthroughlearning.com/exam-prep-for-the-chrp/
Hi dossolini,
If you save the settings on the plugins settings page, does that change anything? Once there is odd data stuck in the Tweet Data, like the error message, it will not be able to update correctly. Saving the settings also flushes the content of the Tweet Data so may help get it working.
If that does not help I will continue looking into it. Thank you for your responses and for helping me to debug the issue.
Hi dossolini,
I just found a second instance of the problem I mentioned above in the API, I hadn’t actually fixed the right one. Now both are fixed and there are no more occurrences in the code. That’s what I get for late night hotfixes.
If you click ‘Save Changes’ on the plugins settings page, it should work now if this was the problem.
Hi Peter,
Thanks for continuing to look at this issue.
I tried “Save Changes” a few times but the error is still there on the Debug Tweet Data panel. So no tweets are loading yet.
Hi dossolini,
Sorry you are still having issues. This is strange as I am quite certain the API is not responding with that error anymore (it is not visible in the logs). Which means that the Transient used to store the Tweet data is probably not getting flushed when saving changes.
Would you mind de-activating and deleting the plugin, then re-installing? This *should* flush the contents and get it to refresh properly. If the error message is still present, is it exactly the same as before?
I will have another look through the code to make sure I really have fixed the issue I identified.
Perfect, that did it!!
Thank you very much Peter!
Hi dossolini,
I am really pleased it works for you now and I am very grateful for you making the time to go through your problems with me. I am sure many more people have suffered from the same issue and not come forward, so this will help others in the future too.
No problem! It helped me to help you! and everyone else too 🙂
