No need to self promote yourself for this reason..
I have done this in my latest theme 2 weeks agohttp://wordpress.org/extend/plugins/oauth-twitter-feed-for-developers/
Hi Ruben, I’m not self promoting, this is an update to a thread that has been going on for a while in relation to dealing with the Twitter API 1.1 and the curl and base_encode errors I was getting via Theme Check. All I was doing is posting a link so the other subscribers of the thread were able to have a quick look at the widget/integration working, I’ve already posted the link for the resource of the API class which is available on github.
I’d remove the link, but it won’t let me edit now. Sorry this caused you any offence as this was not my intention and well done for adding in a Twitter oAuth API on your latest theme.
Feel free to flag my comment if you want it removed.
We’ve just had approval on our first oAuth 1.1 Twitter API theme…http://themeforest.net/item/literary-a-wp-blog-theme-for-all-types-of-author/full_screen_preview/4713129
You can see it in action on the sidebar here: http://www.meanthemes.com/theme/literary/blog-layout-3/
So that’s good news
I have got a response back from the review team – sounds like they are very busy so there was a bit of a delay…
“Hey Chris, thanks for your email and I am very sorry for the delay in responding. We are experiencing a high volume of inquiries and we are doing our utmost to respond as soon as possible.
No worries, those are a few harmless warnings. base64_encode() is sometimes used by some bad people to inject nasty code into themes and that’s why Theme-Check warns about it.
Give it a go, put in the ‘Message for the Reviewer’ section a small note about this ticket. “
So, it looks like we’re going to be ok, we’re working on a new theme at the moment so will submit that with the twitter oAuth for review at the same time, will keep you updated on here.
hugw saidLooks like they gave a little more time. New date is June 11, 2013.
The Twitter REST API v1 will officially retire on Tuesday, May 7, 2013. https://dev.twitter.com/blog/api-v1-retirement-final-dates
Fantastic, I had an inkling that date would be put back, that’s good news as well as hopefully we can get an answer from themeforest on the above theme check warnings.
As soon as I’ve had a response to the support ticket I’ll update here.
meanthemes saidIf you meant the forum button ‘request staff reply’, then I guess that’s what KingDog just did
KingDog saidI’ve requested a staff reply but will raise a ticket too, thanks for the advice
You may need to open up a Support ticket for this one so they can forward it to the Review department
Thanks I hadn’t spotted the staff ribbon when I replied. Still not had a response from support though, wondering if a review team member could comment on here for everyone to see?
I think sometimes an authors inability to contact buyers results in a situation like this, we can’t pre-warn, we can’t inform and educate & the result is that many themes and templates are about to break, whether integrating a new solution or retiring the old, I’m sure most people are about the feel the burden..
This is my worry too, even though we are aiming to have an alternative, we’re still inevitably going to get an influx of “my twitters broken” or “my theme is broken” type support and more support explaining that each user will have to go to dev.twitter.com, login to twitter, authorise their own app and then create authentication tokens and then copy all those weird encrypted keys back into the theme options.
An official word from Themeforest on code compliance based on above will be great for me as we can then educate our customers about the changes to the Twitter API and quickly deal with support requests by making it clear what is going on and how to deal with it.
It would also be super-fantastic if Envato were able to globally announce (maybe in the header bar above the toolbar where Microlancer currently is) about the changes to the Twitter API and how it will have a far reaching effect on a lot of the items sold on their marketplace.
Hi, I figured this was the best place to ask this. We’ve got a working prototype for Twitter oAuth API v1.1 integration based on a custom widget utilising this source:http://github.com/j7mbo/twitter-api-php
It’s all working brilliantly, however – when running theme check we are presented with these warnings.
WARNING: Found base64_encode in the file framework/twitter-api.php. base64_encode() is not allowed. Line 151: $oauth_signature = base64_encode(hash_hmac(‘sha1’, $base_info, $composite_key, true)); WARNING: curl_init was found in the file framework/twitter-api.php possible file operations.Line 198: $feed = curl_init(); WARNING: curl_exec was found in the file framework/twitter-api.php possible file operations.Line 200: $json = curl_exec($feed);
Basically, I’d like an official response on this as I don’t think we can avoid using those techniques to get what we need from the Twitter API. The code is not encrypted and they are valid PHP functions, obviously there is no malicious code either.
Will we be able to release a Twitter API v1.1 oAuth enabled theme whilst these warnings remain?
Thanks in advance