KingDog saidSince the money were returned to my account, i’m positive we already established to whom they belongs. The problem is that your support refused to change the pending withdrawal so i won’t be allowed to get the amount before the 15th of july.
We want to get your money to you as quick as we can, but we also want to make sure it’s going to the right person We apologize that it’s taking longer than usual this month.
If you wanted me to get my money as quick as possible, considering it was all caused by human mistake / backend bug on your side, you should have answered with “Sorry, we’re going to add the missing $$$ to your pending withdrawal” and i would have got them the 15th of june.
By the look of things, the latter isn’t going to happen
just got a ticket update: “we can’t change pending withdrawals”, as if we missed the deadline.
There was no “we can’t” when it was about bulk orders but this time envato pokets are unaffected so why bother asking a dev to change a couple of DB records.
I can often read in the forums all those nice words about how much envato cares about us authors. Truth is, when it matters, you just don’t give a damn.
I’m so freaking mad i had to rewrite this 3 times. Long story short, in april a transfer to one of our partners failed due some kind of skrill issue, we got contacted from envato, the partner gave us a new payment address, we gave it to envato and the payment was done in may.
End of may we setup transfers and notice that somebody at envato forgot to remove the failed withdrawal from the system and, as a result, we are not allowed to withdraw that amount. We contact support and the money are returned to our account instead of getting added to the pending withdrawals for june as we had asked to.
Motivation was that we let them know about the issue on May 29th ….. Are you freaking serious ? “dog ate my homework” excuses ?
Show some respect for the work of your authors by giving them their money when you already got yours instead of having them to wait an additional month.
And don’t even try to blame the “system”. First of all, you wrote it so can do whatever you like and second you have no issues freezing money and withdrawals in case of a DMCA notice.
Don’t lock this thread with the “contact support” motivation because we already did and the post isn’t really about the money but rather a talk about how envato consider their authors.
KingDog saidThanks Travis, i know but timing is critical to avoid missing the withdrawal window. Often envato staff happens to read the forums so i thought it wouldn’t harm to post here too.
Heya The Help Team will be able to help you, but it will come through the help ticket and not the forums since it’s an account related issue. Thanks!
cough …. bribe offered … cough
Sorry to crosspost this here but end of the month is almost there and i can’t withdraw some earnings because there was a glitch in the system.
Dear Envato Support,
There’s a Locked withdrawal still registered in my account from a previous month which is blocking an amount of my May earnings making it unavailable to withdraw this month. As the deadline for May withdrawals is fast approaching, please review this issue as a matter of urgency. I’ve submitted a support ticket with all the details: Ticket ID: 226320
The only official response from Envato was “we’ll consider this in the future” by Stephen. Quite frankly, i don’t why we’re forced to use TGMPA.
StephenCronin saidI’m not suggesting authors who are using TGMPA class to immediately switch to a different solution but, after the add_query_args sh**storm is gone, they should be free to
We’re a little stretched right now (responding to the add_query_arg vulnerability issue), so we need to ask people to stick with their current solutions for the moment – but it’s something we can consider in future
For instance, we are in the process of releasing a new theme (not before may) and would like to use the proposed solution.
As the TGMPA author said himself, most hooks were not available when the the project started in 2011 but they are now and since WordPress already includes plugins/themes install/update features, why not just taking advantage of them ?
A solution which reduces custom code while allowing buyers to use the same wp native interface they’re used to for wp.org plugins at the same time should be favoured by Envato rather than forbidden.
edit: for those who asked, i included the js code in the github repo.