Paul

We have plans to do this, but it the API does not currently support it.. so that will happen in a future release. (You'll also be able to generate an API key in the client area. If you do, then it will require you use your API key and not a password but maintain backwards compatibility)

I have added CORE-1750 Thanks!

The official Blesta License module for resellers is now available. It will be bundled with future Blesta releases, but you can download it here now. To install, download and unzip. Upload the "blesta_license" directory to /components/modules/, then follow the directions in the documentation at http://docs.blesta.com/display/user/Blesta+License If you don't have a reseller account, but have an owned license with us, you can sign up in the client area at https://account.blesta.com/client/login under the "Reseller" section. If you don't have an owned license and want to offer Blesta, email sales. If you have any comments or suggestions for this module, let us know! This module uses namespaces and requires PHP 5.4 Download the latest version: blesta_license_1.0.1.zip

I would suggest setting the "config" directory to 777 during installation if you're still having trouble. During the installation process, Blesta will need to create, and write to a file within the directory, so it's important that the directory is writable during this process.

Account access is a log of credit card accesses. If a staff member views a credit card, or the system decrypts a credit card, it is logged here. It's a PCI thing. Transactions are transaction status changed. For example, if you refund a transaction, or if it's pending and becomes approved.

It is still planned, it just hasn't been a very high priority. In the interim, I suggest smacking any staff members not using 2FA upside the head.

Looks really good! Seems like you have this down.

You can't reliably force the display of a PDF invoice in the browser. Some browsers will not know what to do with the PDF and prompt you to download it instead. Rather, I think the better solution is to have an HTML version of the invoice that can be viewed in the interface. Then you'd have the option "View" and "Download".. view displays the HTML invoice and perhaps allows you to pay, or links to make payment, and download sends the PDF version as it does now. We have a discussion going about this, but we welcome feedback on the details of how this should look.

Client groups are good for organization, but one cool feature of Blesta is that client groups can have different settings. See Settings > Company > Client Groups. You can invoice these customers at different intervals, auto-debit, suspend differently and a whole lot more. Some people will separate their business clients that want to get paper invoices, and maybe be billed further in advance (so they can pay by check). The possibilities are endless.

So the question really is, should we include the {ticket.summary} tag in the subject line for new installations of Blesta? If so, what would you consider the most appropriate placement? Give me some example subjects! EDIT: Mike, I had to use IE to view that video now that I've got flash disabled in Chrome and FF.. so many exploits, hopefully they will start using an HTML5 player.

Thanks for sharing, nice variety!

Some need to use /usr/local/bin/php on cPanel. You can always run the cron manually under Settings > System > Automation. If it runs fine there, then the cron may not be correct.

I reissued your trial key

We are going to improve the staff service management page, likely breaking it up into additional tabs as the default "Basic Options" tab has too much going on with it from features added since 3.0. An "Advanced" tab or similar may be beneficial for these kinds of actions, and possibly some other options not currently available.

Please see CORE-1061, which sets services to be included in the smart search by default, but allows which criteria are included in smart search to be defined. I've bumped this up on the backlog.

Well that's an important one. Does Windows 10 not have a compatibility mode to run older applications?

I have pushed CORE-1516 to the top of the backlog, this should take a couple minutes.

I believe this will do it for anyone wanting to make this change now. To change the character limit manually, edit /components/modules/cpanel/cpanel.php and look for: 'rule' => array("betweenLength", 1, 8), Change to: 'rule' => array("betweenLength", 1, 16),

EDIT: Hey, Tyson beat me to it. It looks like Linux allows usernames up to 32 characters, cPanel allows usernames up to 16 characters if database prefixing is disabled. Considering that the cPanel module generates usernames, an increase in the limit should not create any issues for clients. It could create issues for staff, but this would likely just result in an error from the module should cPanel reject the request. https://documentation.cpanel.net/display/SDK/WHM+API+1+Functions+-+createacct Would you say then, it would be reasonable to set the max length of a username to 16 characters?

Have you noticed incompatibility with any programs that run on Windows 7?

I'm pretty sure it is. Please watch for the 3.5.1 release in the next week or so and see if it corrects the issue. If you create a manual invoice that has only 2 decimal precision, ie ($4.55) and it works correctly then you are most likely impacted by this bug. And, you'll have confirmed that your gateway is working correctly.

You will have to update all email templates everywhere, including package welcome emails. Also, plugins that create email templates will still create them using the single braces for tags, so you'll always have to update any plugins you install. Also, other things I haven't thought of. You can make the change at your own risk. If you identify any other issues, let us know and we may create a guide on it.

We would definitely be interested in your ideas. Maybe a new thread for that?

CORE-818 and CORE-819 address the domain management plugin (These Epics are currently private). We are working out the details internally, and considering everything everyone has had to say regarding domains. It's likely that we will open these tasks up and start a discussion in the near future. These features will be dependent on 4.0 however, which we want to get out relatively quickly. There are a lot of major benefits to developers in 4.0, in part because of the PHP dependency change to PHP 5.4, namespaces, and more. Domain management won't be in 4.0, but we are continuing to make progress in designing the feature, and implementing some other core changes so that it will be easier to implement. (For example, plugins will be able to control package pricing. This allows for the domain plugin to set pricing for domains (Think pricing grid for new/renew/transfer, 1-10 years). It's a powerful feature that could be used by other plugins for a variety of purposes.)

Just an update. This may be related to the issue described here - http://www.blesta.com/forums/index.php?/topic/4754-paypal-payments-applied-as-account-credit-then-to-oldest-invoice/ A fix is in the works for 3.5.1