Hi ro72,
Looking into this now, ill let you know as soon as I have a better idea of what is going on.
Hi ro72,
That error is triggered when Twitter returns a specific error message stating there was a problem with giving us permission. Either through not clicking accept or another Twitter error.
I am now tracking those particular errors for a short period, would you mind trying the process again? If I can capture one I will see exactly what problem Twitter is having.
Just to confirm, when you click on the Connect to Twitter button now it takes you to the Twitter Accept/Decline page, but then you get stuck on an error message and/or blank white page?
Thread Starter
ro72
(@ro72)
Thanks for your quick reply. I just tried it again. I clicked connect in the plugin page, then clicked accept in twitter, see a screen with a “please wait while we redirect you to the application” message, then the white screen and no redirect. When I navigate back to the plugin page, it is still unconnected.
I have been trying to reproduce this behavior myself, but unfortunately I have had no luck.
I haven’t yet picked up any errors, as you just get a white page now that is expected. The blank white page would sugges that there was no error AND the response did not match any of the recongised formats, in this case services.
This could potentially be caused by Twitter responding in a format which is unexpected. I have checked the responses and that does not appear to be the case, and I have not found any relevant news of such on the Twitter Dev site either.
Would you be able to remove the Kebo apps permission from your Twitter account, log out of Twitter and then try to connect once more. I have put an extra check in which may display a message instead of the blank white page. Please let me know what happens.
Perhaps, trying it with a different web browser may work too (Internet Explorer, Firefox, Safari, Google Chrome, etc). As some specific privacy settings could potentially cause problems.
Thread Starter
ro72
(@ro72)
I tried removing the permissions from Twitter previously and reconnecting with the same experience. Originally I was using Firefox, just re-tried with Chrome and got the following message “Oops! This link appears to be broken.” Here is the displayed url link structure (identifying info replaced with generic terms)
http://URL.com/wp-admin/options-general.php?page=kebo-twitter&service=TwitterRead&token=USERID-TOKEN&secret=SECRET&account=USERNAME&userid=USERID&account_link=http%3A%2F%2Ftwitter.com%2FUSERNAME
Okay, this is progress. It would appear then that we are not generating the correct address to send you back to. Is there anything obviously wrong with the address?
Thread Starter
ro72
(@ro72)
The URL and twitter user ID info are all correct as far as I could tell, I don’t see any obvious structure errors (not an expert on that though).
Thank you for being so quick to respond and helping me to debug this. It is users like you who help us to improve the plugin for the future.
The Chrome error message should indicate that it could not find a website at that address, which would suggest something was very wrong with the structure. Would you be able to email me a copy of the URL (without anything removed) to mail@peterbooker.com please? If I can work out how the URL structure is wrong, I am sure I can fix this.
Thank you so much for the email. I have amended the script to not return the URL with the ‘http://’ aspect, which should mean you can use the normal method of connecting now. Let me know how it goes.
I am still unsure why this problem is occuring on your site, so would appreciate a plugin list.
I think from this experience, I will be taking a much closer look at how I transmit the relevant info in the URL. Perhaps finding a way to make it a POST request would avoid these potential problems.
Hi Rosie,
From all the troubleshooting we did last night I have just pushed out an update to version 0.5.8, which *should* prevent the Tweet data being corrupted by the special characters used to display symbols on Twitter.
Let me know how it goes and thanks again for all your assistance in troubleshooting these problems.
Just heard from the OP that the problem was resolved by the latest update. Ill mark this as resolved and if you have any more problems just let me know.
