Stefano

Hello!
How would that be useful? I mean, for users to write posts they have to have access to the admin area. So why wouldn’t they be able to see the plugin’s pages?

Coming version 2.0 will have a payment history holding all past payments with their counting data, yes! ??

The choice oh the publication time range is only a displaying one. As the tooltip says: “With this [weekly option], the plugin will display in the stats all the published posts from the beginning of the week to the current day (week starts on Monday). This will be the default setting: you will still be able to change the time range the way you want it. You should select this if you usually pay your writers weekly.” Again, it’s just for displaying, it doesn’t delete anything after a week or anything like that.

Future release 2.0 will include the feature to stop the payment amount at a certain point, to set a maximum payment. Is this what you are talking about?

Have a nice day,
Stefano

I am afraid there’s nothing like that neither I am planning to implement such feature.

Yes, future release 2.0 (on which I am currently working on) will hold users’ paypal email addresses as user_meta; db table post_pay_counter won’t even exist anymore.

Call the user meta “ppc_paypal_email_address” and you should not encounter any problems with future releases. Things will change but at least your data will still be used. Hope this explains.

I understand what you mean. First, keep in mind that the plugin only records visits since when you install it, not before. Secondly, as of now it is not available an accurate and precise visits system, you can not distinguish between visits from this month and the previous ones, they all get grouped together. Future version 2.0 (coming hopefully as soon as Christmas) will add Google Analytics integration and everything will ve much better. Sorry for the delay.

As for the cookie expiration time, you change by hand line 380 of post-pay-counter.php.

As of now, it is:
setcookie( 'post_pay_counter_view-'.$_REQUEST['post_id'], 'post_pay_counter_view-'.home_url().'-'.$_REQUEST['post_id'], time()+86400, '/' );
You can change 86400 with the duration in seconds you would like.

As for your second question, it should be noted that only certain settings change trigger a stats regeneration. I understand this may not be the exact wished behaviour, and it will be fixed in future releases for sure (not more than a couple of months with a whole redesign).

Hope this helps.

It is not possible in the current version. Future versions will allow this.

Yes, it works exactly as you said. Have a nice day!

In the stats, do you see the troubled posts with a € 0 payment, or don’t you see them at all? I’m on holiday now and can’t troubleshoot properly, I’ll be back at the weekend.

Has it happened once, or does it occur frequently? (Sorry for the late answer, I was away…)

Hello,
you are right, there was a bug which should be fixed now with version 1.3.9. If you still have problems, let me know.

(Sorry for the late reply, I was away)

Changing options will always result in a conseguential stats change. It was designed this way to get the beet performance. If it was not this way, every time you wanted to edit options reflecting those changes on stats, the plugin would have to go through the whole database, probably resulting in a timeout on large ones.

A possible solution would be to give a payment bonus to each post of 2012 proportional to the number of words. That bonus would thus be added to the default payment of 0.02 by the plugin.

Hope this helps.

I may implement a more granular permission control, but I have no idea when I may have the time to do that.