Altegras

Not willing to argue about this ... it's your opinion but in mine there is virtually no risk giving out access to a template directory which cannot be accesed from browser, the webdesigner could do his own thing ... in the end you just audit the code and put it live, simple. We're doing this for all of our projects w/o no problem (twig / secured smarty / etc) I understand that devs considering security first, that's the most appreciate thing to consider using Blesta, but there is no software on earth which is 100% secure of any kind of exploits, this is a dream. (remember glibc exploit advisory ...) But I didn't said anything about blesta security, all I've said that we're using webdevelopers from freelancer / elance to do things when we need - that's why is a drawback for us, we do have a bunch of individuals who we like to work with and we have trust in them, but I just won't give them access to the sourcecode of the billing system.

Lack of any kind of template engine which separates php and html template is the biggest drawback for us (and for Blesta I guess), I know there is always the solution to manually do edits myself but I won't start doing a webdesigner job which is paid for that just to make sure he doesn't do anything nasty in there. With smarty you could strictly define security which you could use to completely lock out an webdesigner of any kind of unallowed functions. Also, I'm strongly against modifying the sourcecode as it would be a nightmare for future upgrades

Hello, First of all, I never installed Blesta before ... rolled over documentation over and over again trying to learn how it works and what's the logic of the development, read about modules, plugins, gateways and I find them developer/object oriented which is fine for me. But I haven't found an answer of the following questions: Blesta uses any kind of template system (smarty, twig, etc) ? I'm a php developer not a webdesigner ... and I need to give an access to various webdesigners which I don't fully trust in order to get the job done (only templating), is that possible ? I haven't found documentation about creating an empty / blank page (like: http://docs.whmcs.com/Creating_Pages) as we do have a couple of .php pages which generate dynamic content for our clients, please point me to it if it's supported. whmcs have a client_area output for a service module (http://docs.whmcs.com/Provisioning_Module_Developer_Docs#Client_Area_Output) haven't found something simillar on blesta, it's that possible ? Thank you!

Well, I saw this coming from a year ago ... expected it a little bit different tho. If they would price increase just for version 7 of the product, it would have seemed fairer but anyway. Blesta and other billing systems will get their cut of this whmcs bad practice, that's for sure ... but how do we know that Blesta won't do the same in the future ? We won't! Can we put our trust in the product ? That's some questions that needs to be answered by clients. We got 6 whmcs installations which we're willing to move, I've read most of the documentation and the project seems to be developer oriented (which is awesome for me) and I hope they'll keep it that way! Making a product "newbie" friendly with a ton of features (which on daily basis you only use a fraction) implies (possible) security risks which we're not willing to take (this happend to whmcs) - let's hope we won't see a rush for updates & features from blesta. We need a stable piece of software that works ... Yes but not by discounts, a hoster doesn't need discounts for migration to blesta ... it needs support and trust in the product & management, switching billing systems is NOT like a walk in the park, it's hard labor which implies a ton of documentation, support, todo's and resources.