Commodore C64 in 1985 with 5.25’’ floppy disk drive. Elite and The Pirates! were the games to spend days and days playing. There is no game today to come even close to the excitement of playing those old ones.
From what I remember cookie contains username, so changing username will be a problem.
As for the purchase of your own products, if the user clicks your link, creates and account and purchases, you will get affiliate commission. But, if he clicks your link, and he already has an account on Envato, than you will not get affiliate commission. Only when user registers through your link, and makes a purchase you will get the commission.
Hey community! I just talked to the devs, and things with the API should be returning back to normal. Sorry once more for the inconveniences.
Will it require use of user agent or not? That is what is important, because it would require massive updates to change the existing API related code to do it. Can we get some detailed information on this subject and what to expect and will there be any change to the way API is accessed?
I’m using the CloudWork-Verifi plugin on my support forum, i have not received any complaint yet about registrations not working, i’ve also had a really quick look inside the code of the plugin but i haven’t noticed any file_get_contents or curl calls, is anyone using this plugin too and having any problems with it?
This plugin uses internal WordPress functions to get remote content, so it is still using CURL, but these functions already put user_agent in all calls so it is OK.
All calls seams to require user_agent set, here is the main thread with one solution:http://codecanyon.net/forums/thread/envato-api-is-not-working-for-me-anymore/114284?page=3#1003830
I created patch for my plugins and made it available though support forum. But, we need official clarification on this including the information if this is permanent change, and what type of user agent is acceptable. Only than we can roll out updates to plugins with permanent fix.
Well, I hope this was just a mistake or a problem on their end and they will work on it. I do not think they made such a major change without notifying developers. For now, I will use the suggested hack to calm down some angry customers
I hope this is the case too, but some of my CodeCanyon plugins have Envato API as a core functionality, and for all who purchased, websites are crushing all day because of this. And as we have already used to, no one from Envato staff has anything to say about something I and many others consider a major issue. If the user agent is required from now on, OK, it is not the problem it is easy to change, but we need to know what to do and how to update plugins.
But it was working fine until yesterday. Isn’t there a solution from Envato rather than hacking the code to make it work?
This is very bad move Envato did, they made changes to API without announcing it anywhere, without any warning that it will happen, and ALL apps anywhere using API have stopped working because of it. This is very, very unprofessional. I expect great many users will start blaming developers for apps they purchased to have stopped working. Nice one Envato!
I have confirmed that user agent is required, by running CURL requests with and without user agent, and if there is no user agent, all requests timeout.
API is down for at least 9 hours now, since that is the last time I got update from it. None of the websites using API or apps on different devices can’t connect to API servers.
2 weeks ago I have purchase Lenovo Yoga 2 Pro and it has 13.3 display with resolution of 3200×1800 – http://shop.lenovo.com/us/en/laptops/ideapad/yoga/yoga-2-pro/ with 128GB SSD, 8GB RAM and new Core i5 CPU, under 7 seconds for cold boot.
It uses higher resolution than MacBook with Retina display. It has Windows 8.1, and I was surprised to see that almost all applications can deal with HiDPI screen. Problem for me was that Java applications can’t and I use NetBeans for development. Right now, there are many applications that will not support such displays properly and will display too small to read. Also, there are some inconsistencies between browsers, and IE11 displays things 20% larger than Chrome or Firefox.
These very high resolution screens will be more common in the next year, and hopefully all software companies will begin to support them as it should be done.