Leaderboard

Yes, the license manager comes with a class and associated libraries that handles all integration. It also includes example code to show how to embed within your software.

You need the open source PHP library phpseclib which handles encryption without adding any requirements to PHP. Of course, if you're selling an application that's not written in PHP, or you just don't like phpseclib, you can use a different encryption library. You aren't locked into using phpseclib but we use it and it works very well. Our documentation will include sample code that you can use within your application. The documentation will be available very soon, and we'll start selling the extension just after 3.2 is officially released. Mike is right, the license is good for a single installation of Blesta and there are no restrictions on how many companies you have it installed for.

thanks i was just see it . i have thinked is completly new plugin from scratch . is like an integrator of BLC script . the script is great and the way you have implement it in blesta is great . (your code has helped me in some of my new plugins

Oh yeah there's no changes to the client view, my mistake

Mate you should have two download links: 3.1.x: download link 3.2.x Beta: download link. Some people won't be migrating over yet so you'll loose a customer base.

New updated version that supports 3.2 Booststrap theme (you can install on 3.1.X or above, you will not loose any configurations), with some modifications and fixes (updated 01-05-2014) This the first Release Candidate for Blesta Live Chat. Please test, and if you find any bugs please tell us to fix it so we can go "Stable" See first post. Regards, PV

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)

I think the solution is to uncheck the box on the domain package page and restrict that package after the import is done. Then I'm going to create a new package for all of the domains to sort of start over fresh. I am excited to see this new domain module in v3.3 though.

I guess I completely misread this earlier and wasn't picking up on the 'domain' to 'domain-name' part for the key value.

ok I'm slowly figuring it out. Under the services_field table, the key is 'domain' right now. I'm manually updating the key to 'domain-name' right now and the label value is being filled in atleast. Let me see what happens as I go through more of them. Thanks!

A URL is supposed to be a logical resource, which is how they're built in Blesta. It's sometimes nice to have sort URLs, but that usually requires removing information about a particular resource, making it less logical. Logic aside, as-is, I think they are quite pretty. Much prettier than say, "cart.php?template=foo&package=12".

looks good..

There must be an error someplace, try the following -- Turn on error reporting. To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); Then open /plugins/import_managers/components/migrators/blesta/2.5/blesta2_5.php and change (lines 199-201 Note! Line #'s may be a little different): //echo $e->getMessage(); //echo $e->getTraceAsString(); //continue; to: echo $e->getMessage(); echo $e->getTraceAsString(); die; And then let us know if you get any errors. There may be something that's hanging these up from being imported that's different than anything we've encountered yet. Knowing why the import failed will help determine the fix.