jReviews Support Forum

General => Pre-sales questions => Topic started by: Tengu on June 15, 2008, 04:43:29 PM



Title: Ioncube / encoded code
Post by: Tengu on June 15, 2008, 04:43:29 PM
First of all WOW! It must be one of the best ever extensions. It is so much more professional than a lot of the other extensions around. Congrats and thanks for making this. It looks very impressive (I was most impressed about the Search function!)

Before I buy jReviews, I got a rather important question, or one-and-a-half really.

I am going to run jReviews / AEC / Jacl / CB on a site. Most important will be the jReviews / CB integration. I already seen this is somewhat linked. I do however need to modify some bits and bobs along the way. For example, I need to limit the user to add only a certain amount of entries into the jReviews system. I think I need mambots for this?

Now, the question ... can this be done? I ask this because I read (correctly?) that jReviews is encoded and after purchase only the frontend is decoded. Can a yet-to-be-hired PHP coder then figure out how to modify some inner workings?

Thanks in advance for a reply :)


Title: Re: Ioncube / encoded code
Post by: Alejandro on June 15, 2008, 05:24:04 PM
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.


Title: Re: Ioncube / encoded code
Post by: Tengu on June 16, 2008, 06:52:49 AM
You're a star Alejandro!

Thanks for the tips on modification. I will let my eveloper know. Now ... all I got to do is find a host that uses either Zend 3.3 or Ioncube and PHP5 that work together (I heard there were some problems with Ioncube / PHP5)