Paul

Interesting, your example looks a lot better. These buttons no longer exist in 3.2 though, so it's unlikely to be an issue going forward.

You could also manage the service after you set it up, and schedule a future cancel date out 24 months. They'll get billed until it's cancelled. Under Billing > Services, you can sort by Scheduled I believe to see one that will cancel soon.. if they renew, you can edit the cancel date out another 24 months.

We'll be making further updates to the migrator soon, especially once we have price overrides completed. Price overrides will solve a lot of the issues with package pricing since it's a well used feature in their software. SolusVM could probably be mapped better now, I'm not sure the exact reason it wasn't mapped to begin with, it may have been that it wasn't ready yet.

Thanks for the suggestion, I'll take a look at this shortly. When you use HTTPS it complains about some resources that link directly to http, so I need to figure out what's going on there first.

The summary/title field is VARCHAR 255 in the database, so it can only hold 255 characters. If fewer characters are being allowed via the importer or method that handles the summary, it could theoretically be expanded to 255. The detail field is a text field in the database which I believe can hold 64KB.

Click on notes on the left where the client name is on their profile. Then, click on the row (or edit) for the note in question. Chances are, the note appears in the detail field in its entirety. The summary would be truncated because it's a summary.

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.

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'd like to hear more from others about typical use of this feature. Is it better if you can choose the behavior on a per-ticket basis, or for it to be automatic for the department? We want to be careful about adding unnecessary elements to the UI, but if putting the option on the ticket reply page is the best option (what Cody suggested) then it may be the way to go.

I would prefer it to be a configuration option in the UI for the support manager. Perhaps a department setting. If we stay on the current page, I think we need a way to ajax-display new replies when viewing a specific ticket. We should have this anyway, but it becomes even more important.

@OP let me know if you'd like this thread moved to the feature requests forum

Avatars for the ticket system use Gravatar. You can sign up for Gravatar at http://en.gravatar.com/ and upload your avatars. They are associated with your email address, so as long as the email address matches the one in Blesta then it will be displayed.

Check that your temp directory is set properly under Settings > System > General. If Blesta can't temporarily write the invoice PDF to disk, it may not be able to send the email.

Unfortunately it didn't make it into this release.

I discovered the issue. A trial had already been issued in the past. When a trial has already been issued for the same domain, the original trial key is returned from our license server. This is to prevent perpetual use by trial licenses. So, I manually created a new trial key and it appears to be working. Please check your email from the login details.

Is the server load balanced with multiple IP addresses or behind a proxy? If so, that could be the reason. Also make sure that port 443 egress is open and curl-ssl is in your PHP.

Is this what you mean by WHMReseller? http://deasoft.com/whmreseller.php .. or, just a reseller account through WHM?

Did you take a look at the ticket system changes we made?

It should be in 3.3 which is invoice/payment related in theme.

That's the way to do it for getting BCC's on any system emails. Also check out Billing > Overview, click the cog/gear icon for the orders widget. Here you can set your email and mobile email notification preferences for new orders.

It's 2087 secure, and 2086 no ssl. You shouldn't use 2083, as that's for cPanel not WHM. If it's still not working, check your firewall. If it's still not working.. Can you post a screenshot of your module configuration, or PM it to me? You can mask the API key.

You use Interworx though, I think I heard Interworx uses LFD out of the box, is that right? I imagine you can install CSF on there if you want, but there's no integration into Interworx.

If all goes well, that will probably be tomorrow afternoon.

CORE-647, already part of 3.2. You can test it out in the beta. This applies to addon services only, not configurable options. Manage service, click Addons (Only exist if there are addons for this package group), then "Add Addon" button. It takes the client through the process of creating the addon, and to payment. The addon is "pending" until payment is made, and then the cron will activate it.

The domain plugin belongs to CORE-818. I've added a note to the task regarding domain privacy. The plugin would likely give the client the ability to disable and re-enable privacy protection as is often necessary (when purchasing an SSL certificate that requires verification for example). The price and ability to purchase the privacy protection would likely be set up through a configurable option, and the module / plugin would provision it automatically.