Posts by dtbaker

This is an ongoing problem and they are still trying to figure it all out, see here for more information: http://codecanyon.net/forums/thread/issues-when-making-payments-with-paypal/71934?page=15

You can also try the instructions here to see if that works: http://wordpress-help.org/themeforest-paypal-problem-solution/

Pick an hourly rate and then work out how long the change + emails back and forward will take.

eg: Hourly rate of $40. 15 minutes for performing the change and uploading it for them, 10 minutes for emails back/forward, 5 minutes for testing the change after uploading it.

^^ half an hours work = $20

Make sure you specify the currency (eg: USD) because a lot of buyers are international.

Over the past 3 days I’ve had heaps of buyers complain that they cannot verify using the item purchase code. Does anybody know if the API is having issues? Every time I test using their codes it works fine.

Trying to debug but I’m not getting any errors anywhere.

This thread about issues accessing analytics recently made me think it was a wider problem and not just me hitting my API limit or an issue with my server.

Yes please obfuscate / domain lock / hidden php generated expiry redirect to a “please purchase a licence” page (my personal favorite)

Anything you do is certainly a lot better than doing nothing at all

Just re-verify all support system purchase codes from time to time. Anyone who registers in my email support system with an item purchase code gets their code saved in my system. This code gets re-verified from time to time (eg: when they send me a new email). A history of their purchases is shown and it will show if an item purchase code is no longer valid.

This support-after-reversal problem has been around long before this recent change… everyone should implement this check in their custom support systems, as authors could request a refund and then continue to receive support / product updates / freebies.

It’s just another simple call to the verify-purchase API. The only complicated part is making sure you don’t call this API too many times, otherwise you will be banned from the API. Only re-verify a purchase code max once a day when the user is active (eg: sends an email, posts a forum thread) to avoid getting banned by the API.

Looks good! Can’t wait for it to go live and see how everyone uses this feature. I’m sure it will change over time as more feedback is presented. Excellent start!

Curious what happens if someone doesn’t enter anything into the “additional information” box. Or if someone just clicks “Save” on the settings page without changing the default text. Or what displays if someone never even visits the settings page to change the defaults.

Default Text Suggestion
Maybe try to re-work the default text area a bit so that it has a better default that can just be “saved” (current default text would make no sense if displayed as-is to a buyer).

eg:

yayyy babbiiessss!!! big congrats!!!

I see a growing number of authors with the little Aussie flag on their profile.

Is anyone else from SE QLD ?

An unofficial meetup could be organised if a few of us are nearby.

Feel free to submit your creation to the growing list of awesome apps, scripts and gizmos available here: http://extras.envato.com/

yay for aussie devs!

Sweet. Yep that Method Not Allowed from Ubuntu was a common sight, haven’t seen it recently though, hopefully it’s gone for good!