ChrisB Posted April 11, 2014 Report Share Posted April 11, 2014 Hey Guys, I've recently picked up Blesta for a new project that we're starting up here. I've had lots of experience with WHMCS in the past, but opted to go for Blesta as it's largely considered the most secure billing panel on the market. My primary concern, though, is it doesn't seem like you can specify templates to use besides the default. (Specifically the client facing section for orders and etc). I know you can go in and edit the pdt files and change the CSS (which I have done, fairly heavily). My concern is when an update comes out (obviously I'll back those up) I may end up missing features or possibly break certain pages that I may not have modified? Anyone able to shed light on this? Thanks. Quote Link to comment Share on other sites More sharing options...
PauloV Posted April 11, 2014 Report Share Posted April 11, 2014 For now we use WinMerge to compare and merge http://winmerge.org/ You can also use Vim to compare and merge: http://www.vim.org/download.php We are thinking in developing some new mods and plugins to blesta, after 3.2 release, one of the mods, is to be able by "Client Groups" select a default "template" from the "apps/views/client/" folder Quote Link to comment Share on other sites More sharing options...
Tyson Posted April 11, 2014 Report Share Posted April 11, 2014 The ability to change which client template to use has been added for v3.2 in CORE-961. You'll always want to keep backups of core template files you modify, and merge them into new releases accordingly. Even if you were using custom templates, you would still need to check them on new releases since data, structure, and language definitions can be added, changed, or removed that has the potential to break things in your templates. The beta releases would be a good time to update your custom templates with these kinds of changes. Michael and PauloV 2 Quote Link to comment Share on other sites More sharing options...
ChrisB Posted April 11, 2014 Author Report Share Posted April 11, 2014 The ability to change which client template to use has been added for v3.2 in CORE-961. You'll always want to keep backups of core template files you modify, and merge them into new releases accordingly. Even if you were using custom templates, you would still need to check them on new releases since data, structure, and language definitions can be added, changed, or removed that has the potential to break things in your templates. The beta releases would be a good time to update your custom templates with these kinds of changes. My site actually isn't live yet and I'd hate to push it live just to have to make a slew of changes come 3.2 - any ETA on when we can expect 3.2? (I apologize if this is mentioned elsewhere). Thanks. Quote Link to comment Share on other sites More sharing options...
Paul Posted April 11, 2014 Report Share Posted April 11, 2014 My site actually isn't live yet and I'd hate to push it live just to have to make a slew of changes come 3.2 - any ETA on when we can expect 3.2? (I apologize if this is mentioned elsewhere). Thanks. 3.2 beta will start very soon, final release is generally 2-3 weeks after beta but depends on how large the update is and how many bug fixes there are. Michael and flangefrog 2 Quote Link to comment Share on other sites More sharing options...
ChrisB Posted April 11, 2014 Author Report Share Posted April 11, 2014 Very soon *tm* or actually very soon? Quote Link to comment Share on other sites More sharing options...
Paul Posted April 11, 2014 Report Share Posted April 11, 2014 Very soon *tm* or actually very soon? The goal is by the end of next week, but we're cutting it close for that so no guarantees. Michael 1 Quote Link to comment Share on other sites More sharing options...
PauloV Posted April 11, 2014 Report Share Posted April 11, 2014 Better wait a few more days ar weeks and release 3.2 with more features, then release quickly without many features Quote Link to comment Share on other sites More sharing options...
Tyson Posted April 11, 2014 Report Share Posted April 11, 2014 Better wait a few more days ar weeks and release 3.2 with more features, then release quickly without many features I think we already did that! Michael and PauloV 2 Quote Link to comment Share on other sites More sharing options...
MemoryX2 Posted April 14, 2014 Report Share Posted April 14, 2014 The goal is by the end of next week, but we're cutting it close for that so no guarantees. This week right?!!!! Super excited!!! I'm even interested in alphas Can't wait!!! Quote Link to comment Share on other sites More sharing options...
eversmile_host Posted April 16, 2014 Report Share Posted April 16, 2014 wow. great work. can't wait for 3.2 Quote Link to comment Share on other sites More sharing options...
mitsos Posted May 1, 2014 Report Share Posted May 1, 2014 The ability to change which client template to use has been added for v3.2 in CORE-961. You'll always want to keep backups of core template files you modify, and merge them into new releases accordingly. Even if you were using custom templates, you would still need to check them on new releases since data, structure, and language definitions can be added, changed, or removed that has the potential to break things in your templates. The beta releases would be a good time to update your custom templates with these kinds of changes. I believe that the best way forward for you as developers, and us as users, is to at least let us edit the themes (and no, that doesn't mean going into all the css files poking around until we see what we need to change) and set up the preference in blesta. For this to work, the css files need to be combined, and an option to set X theme as default should be available. Maybe we could include local config files that override the defaults, which is an even better option, since that's how all the fast moving software (talking mostly about open source) does it anyway. You have a default settings file, where the software developers do all their stuff. That file checks and includes, at the end usually, a local settings file, in which there are your customizations. Since that file comes after the default one, the default settings are overriden. For my use case, the theme I'm applying consist of mainly changing the background color, and the border around the main article. Nothing complicated, but it is something that makes me think twice about upgrading. If the default file included the customizations, then the changes would be carried over without me even thinking about it. The devs get to implement new code, I get to keep my customizations. That and anxiously awaiting for a custom header and footer inclusion. One can only hope. Quote Link to comment Share on other sites More sharing options...
Paul Posted May 1, 2014 Report Share Posted May 1, 2014 I believe what you're recommending is part of CORE-828. The idea is persistence across upgrades. You add your CSS, Javascript overrides and when you upgrade those still exist. What I'd recommend doing in 3.2 b1 now is to edit the structure.pdt file and link your custom CSS. Then, when you upgrade you'll just have to add the link to your custom CSS back to structure.pdt. After CORE-828 is implemented, you obviously wouldn't have to do this. Keep in mind though, all the colors can be changed under Look and Feel in the settings, admin and client themes. Creating your own color scheme is the quickest way to get up and running with something that at least matches your website. I think of there being 3 levels of customization. 1. Change the theme, or create a custom theme in Settings > Look and Feel. (Simplest) 2. Override some CSS styles (edit structure.pdt and add your custom CSS override file) (More difficult) 3. Copy the template directory, rename it and go nuts. In 3.2 b1 you can select the new templates under Look and Feel > Templates. (Most difficult) PauloV 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.