This topic contains 2 replies, has 3 voices. Last updated by Jason (Lead Developer) 4 years, 6 months ago.
Topic Author | Topic |
---|---|
Posted: Tuesday Jun 19th, 2012 at 1:37 pm #16916 | |
First, I have been reviewing your plugin documentation, codex, forums and FAQ for quite some time. Very impressed with the amount of development and support your team has put into this plugin. It seems to be absolutely wonderful and your user base seems to love you for it. I can appreciate the amount of time and effort put into this work and am interested in utilizing it for an upcoming site build I am beginning to scope out. My questions mostly concern two areas: Pay to Post & Publish content within Multisite/BuddyPress and Security. 1) The site I am going to be building will delivery 90% of its content free to the public for viewing, however members will be required to join, make a payment and agree to various TOS details prior to publishing content. Curious if s2member supports this in either the free or PRO version. Will it allow me to specify that users can post (1) or any other entered quantity of posts within a specific category. Imagine if you will that each user has a profile and they can publish an article about their pet (though this is not the actual content of the scope ;).) I want to allow each user to publish 1 post (pet) for $X.xx USD as well as publish (X) qty of posts (pets). 2) I noticed when I subscribed/joined your forums it mailed me the password. This concerns me. Are the passwords being stored, even temporarily in plain-text for the email then being hashed+salted? I imagine you’re using bbPress for this forum and it very well could be the overall functionality of it. Do you have any enhanced security considerations you’d like to share that are potential risks associated with s2Member? Do you regularly check it with XSS/CSRF and SQL injection vectors? I just want to know how many new mod_security rules I might be writing during this implementation. I appreciate your time and cooperation with my questions in advance. |