jReviews :: Customer support forum

Thank you for the nice encouraging comments.

jReviews 2.0 has been released and the code has been completely re-written from jReviews 1.2 and this provides a great deal of improvement in terms of flexibility and easiness to customize. It is encouraged you alter the code to meet your requirements and in the ~2 years since jReviews was first released I've yet to see a situation where a user couldn't do what he wanted because of encoding. In jReviews 2.0, even though the number of encoded files is much larger, it's only because I exploded a couple of administration file into many pieces. Now it's even possible to change the layout of every administration screen and to translate the whole administration. I've yet to create a language file, but it's possible. So in summary, now you have even less restrictions due to encoding.

Regarding limiting the number of entries per user, again with jReviews 2.0, you would just need to change the model file for community builder in /jreviews/models, so it checks the number of entries and then in the view file where the form is shown, you check the community builder info and decide whether to show it or not. You could also check on submit in the form validation.