It almost has no documentation although the rest of WordPress codes / files are quite well documented.
This was a recent pain in the a.. so decided to share some code in case somebody else had the misfortune of trying to do the same….
Goal was to use the native WordPress media uploader code to create a custom dialog that would be used for adding multiple images to a metabox (or page builder) field
Here’s a video showing what i’m blabbing about
Just realized from February the Envato APIs changed how the “amount” field works (“statement” call)
The problem is that you cannot compute how much you earned from a sale anymore because there’s no way to link a “Sale” record to its “Author Fee” record (date can be off by 1s and won’t be realiable anyway since you could have 2 different items sold at the very same time)
To solve that, APIs should include a “Order ID” field for each record (“IVIPXXXXX” value). I really hope this gets fixed ASAP (the “Order ID” field is present in the CSV) because this change made impossible to compute earnings using APIs.
The big issue is that 10% of buyers abusing the support, the “ask first, read docs / try to do it yourself later” attitude. We have users with hundreds of posts in our support forum up to the point we had to do something about it.
So we introduced a rule: “1 question per thread” and have a queue which takes into account the threads count first and the post date last: the more you ask, the less priority you get.
And it works because abusers are penalized by the system by getting longer and longer response times up to the point their questions will not be answered anymore.
designcrumbs saidSure it’s a great plan to switch from the current “support not included” where 70% of the buyers thinks it is and 36% feels author should answer as many questions as they need to a “6 months mandatory support” + paid support packages where (some) buyers will want us to do everything because “I paid (insert a ridiculously low amount here) for it”.
After looking at all of the data, it seems Envato’s original support plan (6 months, 3 day response time) was right on the mark.
36% of TF buyers (highest value) right now expects a fair amount of support queries to be “as many as i need”. Now, think for a moment what will happen with mandatory/paid support.
Then I saw when the Lamb broke one of the seven seals, and I heard one of the four living creatures saying as with a voice of thunder, “Come.” I looked, and behold, a white horse, and he who sat on it had a bow; and a crown was given to him, and he went out conquering and to conquer.
After the transition from commissions to author fees (which according to Collis wasn’t a change since authors getting a commission was just all authors, buyers and probably 95% of envato staff itself getting the thing wrong to begin with), the mandatory support and now this, i’m really looking forward to knowing what the “big changes” mentioned a while ago in another will bring to the table.
And by “looking forward” i mean “to accept the inevitable outcome”.
As i did when flashden died.
Except this time there won’t be any adobe/apple to blame.
during the glorious flashden days, i was once contacted by someone who wanted to know the password to unrar my item.
designcrumbs saidthat’s like saying: “since i eat pasta everyday, i have nothing against a law that forces me to eat pasta everyday”
I have no issues with the original announcement. I already provide lifetime support and have less than a 72 hour response time (in fact, most threads are answered in the first 12 hours).