Changed main configuration page to split settings into tabs.

Try it in case of problems write a comment for this post and in the worst case go back to version 1.7.9

The best way to use “Pay To Register” feature:

1. Create a page with pay to register short code in it. It is described in how to section of are paypal administration.
2. Forbid new user registration. After user pays are-paypal will create the user under the hood.
3. Are Paypal will only ensure the user pays before he gets username and password.Use some other plugin to control access to your blogs content based on user groups, registration level, etc.

We installed your plugein 3 months ago with theese settings:
price 10
Expire 3
Expiration units month

Our purposewas that who pay a media could watch it for 3 mounth.

The problem is that out first client recived, in theese days, another automatic payment for the media he saw 3 months ago.

How can we solve this issue?

Are paypal plugin uses reccurent payment functionality of paypal. It means useer can be charged everytime period elapses.

Currently there is no nice way to have no automatic billing only a workaround.

Check your are paypal main settings page in your blog.
locate textareas – Recurent Payment Button Template and Instant Payment Button Template
Copy content of Instant Payment Button template to Recurent Payment Button Template and adjust it to your needs.
The main idea of this workaround is that paypal button must not send any information about expiration to paypal. Expiration and reblockage of the content will be done by the plugin after expiration limit is reached.

Found a bug on your plugin. Has to do with the more tag.  If you place the more tag, between the Are_PayPal tags, then the content before the Are_PayPal tag will not be hidden on the front page.  Perhaps, you can make the Are_PayPal tag integrate partially with the more tag, in that if there is a Are_PayPal tag, it can automatically close this tag? before the More?  But then if looking at the whole post, to leave it open?

In my opinion this is not a bug but a mistake of the blog editor. The best practice working with shortcodes to avoid intersections and/or nested shorttags. In this case please avoid any shorttags inside arepaypal and please dont put any shorttags around it.

• To add content hide shorttags around selected content
• To add purchased posts list placeholder shorttag at a position of the cursor

Parse error: syntax error, unexpected $end in <server path to your blog>\wp-content\plugins\are-paypal\are-paypal.php on line 819

this is probably due to php.ini setting short_open_tag is set to Off.

version 1.7.1 is fixed to contain only <?php tags so it will probably solve the problem. Let me know if the erro reappears.