Just allow envato.com regular login to permit redirect to different websites. With somekind of a response.
Not quite that simple. There’s a client side handshake and token exchange, which is then verified server side.
There’s plenty of Open Source RoR OAuth Provider / Server options on GitHub
There are, but it’s not just a case of just running
gem install some_awesome_oauth_thing. There’s a bunch of integration with existing internal systems that needs to be customised to get it all working.
Plus every time I’ve had to do any oauth coding (even with 3rd party libraries), I’ve needed one of these pretty quick…
Well done devauthopers.
Sounded like it was a fun hack-week project. Mine was just boring backend stuff
After waiting 5 days for an initial soft rejection, I made the requested changes and my item got approved
And if eadz ever gets his other hack-week pet project across the line, you can buy his track using bitcoin (don’t hold your breath on that one…)
Though, some sort of testing regarding search results is happening, because on codecanyon this is what can be seen in the source code of the page with any search results:<meta content="original" name="WT.new_sorting_method_test" /> <meta content="100" name="WT.sales_boost_test" /> <meta content="control" name="WT.qs_branch" />http://awesomescreenshot.com/0ea2vkf52f
So: what we see now in the search results is from some temporary branch, displayed with the purpose to see how this affects the sales??
We had one in there for:
<meta content="true" name="WT.item_title_uses_blink_tags_test" />
but it didn’t convert very well, so we disabled that pretty quick