Paul

3.2 isn't out yet, but so far it has not been added. Do you guys think this plugin is useful enough in its current state to be included in our builds?

Nope Maybe in the future, but there are no plans to do that right now. It would take significantly longer than the client area.

By far most of the views are related to the admin area, which will remain the same. Only the client area has been updated to responsive bootstrap, and it's done. Yes, it was a fair amount of work but it was worth it.

Soon. It looks better than the screenshots.

Not sure what you mean exactly. Why do you want to change the customer ID, and how do client groups factor in?

The order system supports recaptcha and areyouhuman. Do you think both of these options should be available? It may make sense for us to move various human verification settings into the core, where plugins can take advantage of them. This way, you wouldn't have to provide account details in two places if you want recaptcha for both order and support.

You can edit the price on the package to make the change effective for everyone using the package. If you want to make the change affect only certain customers, I suggest creating a new restricted package with the new pricing. As long as it uses the same module, you'll be able to change the associated package for the customer to the new package by editing the service. If it's a restricted package though, you'll just need to make sure the customer has access to the package. You can grant access under their client profile page, Actions > Set Packages. Then, edit the service to change the package. This method won't add another line item on invoices to show the discount, but you could put that in the package name. The other method is the use of recurring coupons which would apply a recurring discount to the service. I believe this discount would appear as it's own line item on invoices. The issue here is that coupons cannot currently be edited/added after a service has already been created. There's a task for this though, CORE-1066, and it will be in a future release. The last method, which probably isn't ideal for this situation but is worth mentioning are price overrides, CORE-747. This one isn't available yet either but will be in a future release.

It sounds like you have tried setting up the SSH option via a Configurable Option, and also as an Addon. This should probably be a Configurable Option only, and not an Addon. If I understand right, the checkbox would toggle itself during checkout as a Configurable Option. This doesn't sound right, but it does make me wonder if the option is fully configured. Edit the Configurable Option under Package > Options > Options link. Within the Options section, there should be a Name and Value. Both of these must be configured, and a pricing term must be set, even if the price is 0.00. A price term must be set for your 1, 3, 6 month and 1 year terms in order for the option to be visible for each term. If you only want the SSH checkbox to appear for 1 year terms, you can just enter a 1 Year price for the option, for example. If that doesn't work, maybe you can post (or email me sales@) a screenshot of your configurable option settings for this item.

That's certainly a possibility. It's just not something we've given a lot of thought to yet, because not many people have asked about it but I can definitely see it being a useful feature.

I don't think there will be any issues with importing in terms of making configuration changes first. It's best if there is no customer data though, and the importer will install the necessary extensions. However you do it, you should do a dry run to ensure everything works as expected. I also recommend keeping a database backup from the initial fresh installation, and one post-configuration so that you can easily roll it back. If you buy another hosting company and want to import that data, you would be able to import it easily into a new company within the same Blesta installation. Importing into the same company could be an issue because the same customer numbers are likely to already exist and would cause an error. There may be other issues as well, and Cody could elaborate on those.

We recommend marking the package and client as inactive rather than deleting them.

We have plans to implement Net D, see CORE-492. It's tentatively assigned to v3.3, but this is not very likely.

I think he means reinstall the support manager only. Not sure why you'd have issues deleting via POP, unless it's related to your particular mail server. I suggest setting it to mark as read and see if it does that. If so, that may be a good temporary solution as it will not import tickets again that are marked read.

It'll be around $100, most likely. Our license manage is better than anything comparable on the market today, in terms of inability to circumvent without nulling it in the code. It'll be out soon, not sure we need anymore testers at the moment.

Chances are good that your web server doesn't allow files to be written above its document root for security reasons. This could be a feature of Cloud Linux, or something else.

Plugins can create navigation items.. perhaps a plugin that allows you to create navigation items that point wherever you want them to?

We were calling this service price override, and it's assigned to CORE-747 scheduled for 3.3. This one is becoming a big priority for us.

Assigned to CORE-1093

Invoices are always in PDF format, so I'm not sure I understand what you mean.

You can also clear the cache by editing and saving the affected Staff Group. Did this resolve it?

Are you running the official support manager plugin that we ship with Blesta, or the modified version? Have you changed anything, like the date/time format in the settings, or upgraded/downgraded anything on the server?

Most people are running older versions of the Ioncube loaders, and PHP 5.5 supported builds of Blesta are not backwards compatible with these legacy loaders. Additionally, Blesta must be encoded for PHP 5.3 or 5.4 support in order to work with PHP 5.5, per this thread on Ioncube's forums, quoted below -- But, the minimum requirement for Blesta is PHP 5.1.3, so we have been releasing builds that are compatible for the majority (PHP 5.1.3 through 5.4.x), but not compatible with PHP 5.5. Adoption rates for PHP 5.5 are increasing, and we recognize the need to support it. At this time, due to Ioncube's limitations, we would be required to have 2 separate builds in order to support PHP 5.1.3-5.4.x and PHP 5.5. We are releasing this hotfix to allow PHP 5.5 support for Blesta 3.1.2. The zip contains only the 3 files we encode, to protect licensing. If you are not running Blesta 3.1.2 DO NOT apply the hotfix. blesta-3.1.2-php5.5-hotfix.zip If you are doing a fresh install, first download blesta-3.1.2.zip and overwrite the files in 3.1.2 from the hotfix above before attempting the installation. If you are planning to upgrade your existing server to PHP 5.5 and have Blesta 3.1.2 installed, overwrite the files in the hotfix above after you upgrade your PHP.

I've created a task for it, CORE-1091 and it can be tracked there. It is tentatively assigned to v3.3, but it's not guaranteed to be in that release.

Added as CORE-1090

We have had a similar experience. We operated as a sole proprietorship for years before incorporating and it was never an issue, customers never brought it up except to ask for W-9's and issue 1099's. Running a sole-prop in CA can be the absolute best option for a small business. We're incorporated in California and have to pay $800/yr, every year to the state, not counting taxes on profit. That's the cost of admittance, and many small businesses can't afford it. There are lots of reasons why a business may want to be a sole-prop, LLC, S-Corp, or C-Corp. My suggestion is that anyone starting a new business should do some research, understand the different legal entities and make a decision that is in their best interest. What is best for one person isn't necessarily best for another, but if you understand your options you can make a better decision.