The Post Pay Counter WordPress plugin allows you to easily calculate and handle author’s pay on a multi-author blog by computing every written post remuneration basing on admin defined rules.
With version 1.3, Post Pay Counter PRO introduced PayPal payments. Basically, you can now pay your writers without having to manually head to PayPal’s website and enter the amounts and emails. Up to 6 users can be paid at a time, each transaction needs to be explicitly authorized before it is completed (works just like a Checkout page), currency conversion is supported and it is possible to choose whom pays the PayPal fees, either the admin (sender) or the users (receivers). The plugin works with the Adaptive Payments API.
The UK Department of Transports has banned Google Glass from driving since it could divert drivers’ attention from the road. I guess it is better to use your hands to dial a number or text someone instead of telling your glasses to do so without getting your hands off the wheel, but whatever. Anyway, they have not banned something that does not distract drivers, they have banned a product that could dramatically increase safety on the road. I can think of two ways it would, but I am sure there are plenty more. Here my two ideas for Google Glass while driving:
There are two things I am currently working on:
- Integrating my Post Pay Counter WordPress plugin with PayPal, so that site administrators can pay their writers directly from their blog pages, without having to head to the PayPal website
Apparently, it turns out that you do not get to choose how much time you want to dedicate to the first point. That, matched with the fact that PayPal APIs are horrible and that the documentation is often useless, is making the whole process much longer than I thought. Meanwhile, I am sharing what I have come up with until now (which works pretty well, actually), scheduling a second part of the tutorial for when the job will be completed.
PayPal Adaptive Payments: what it is for
Adaptive payments handles payments between a sender of a payment and one or more receivers of the payment. You are an application owner, such as a merchant that owns a website, the owner of a widget on a social networking site, the provider of a payment application on mobile phones, and so on. Your application is the caller of Adaptive Payments API operations.
Standing to what I have been able to discover about PayPal’s different payment mechanisms over summer, Adaptive Payments represents the most flexible way to transfer funds from one account to another. Also, it seems the only method you can effectively integrate PayPal in your application. Adaptive Payments is in fact for those applications in which your account, as application developer, is not the one you are drawing funds from. Shortly, you need to move money on behalf of someone, and your application is the intermediary.
In my specific case, I needed a way to let administrators put their credentials into my plugin and have PayPal let me get money from their accounts and transfer it to their writers’ ones. Adaptive Payments method was really suitable because it allows six transactions per each request, so that it is possible to send different amounts to several people with only one API request. As bottom line (which I did not need and did not care to dive into), it also allows Chained Payments, in which the primary receiver passes part of the payment to other receivers, splitting the original amount.
I worked for several blogs and websites. In most of them, we often felt the need to share hints and ideas about future posts, about what each of us stumbled upon while surfing. Unfortunately, there was not a great way to fulfill that need, and we often told each other via email, or emailed the admin who would in turn forward to all the writers. That is the reason why I wanted to build a WordPress tool that could simplify this sharing process.
That WordPress tool is a plugin and is called Posts To Do List.