Paul

You should add this to the marketplace

Please see http://www.blesta.com/forums/index.php?/topic/1954-cron-job/

This? http://fancybox.net/

Cody is right. Additionally, you can prevent session hijacking by enabling the "Log Out On IP Address Change" option for your staff group under Settings > System > Staff > Staff Groups Edit. If enabled, staff belonging to the group will be logged out if their IP address changes.

Blesta just needs to be able to make an egress connection to our license servers over port 443 TCP (https) periodically. Your installation does not need to be accessible over the public Internet. If your local IP, hostname, or installation path changes, you will need to re-issue your license.

For reference, email templates are located under Settings > Company > Emails and can be changed individually in the UI. We recommend looking through each of them and understanding them. While the default language is not bad, it's generic and most people will want to tweak with the wording for each template (And update the from addresses!).

We've soft launched the Marketplace (beta). https://marketplace.blesta.com/ You need to have a valid account with us as well as a developer license to list extensions on The Marketplace. No account is necessary to browse or download extensions from The Marketplace. Click "Developer? Log in / Sign up" in the bottom left. Enter your Blesta client area credentials from https://account.blesta.com/client/login. (You will always login with your current user/pass from the client area) Then, you may add and manage your extensions. Please only list extensions that you have created. There is no moderation process, so please play nice, we don't want to disable anyone's account. Also, this is a beta, so please report any issues or suggestions you may have. We'll be adding support for Github in the future, as well as many other improvements. The Marketplace will also be tightly integrated into Blesta in a future release.

The module docs are here - https://docs.blesta.com/display/dev/Modules And, all modules that ship with Blesta are open, so they serve as good examples. I'd look at one that's most similar to what you're trying to accomplish.

A setting for minimum and maximum payments for credit may be a good idea.

I think it's a good suggestion for people not to use language that can make people think a release is imminent (ie, coming soon), especially if it's not. But, I don't think a rule would be appropriate, we don't want to discourage people from sharing.

As Mike mentioned, you are almost certainly missing the text content. Both HTML and text is sent, only text is displayed in the logs.

I use nmap all of the time, it's even good for checking a variety of different things, including what SSL/TLS versions and ciphers are supported by a web server. Good for making sure you have SSL v2 and v3 disabled. Of course ssllabs.com is great too.

It sounds like you had piping set up correctly, but were receiving a lot of spam. The permissions of pipe.php have nothing to do with that if the emails are legitimately sent to your mail server. My suggestion is to use a different email address, or put a hardware spam filter between the Internet and your mail server. Or, you can allow only clients to open tickets, in which case the email will be rejected if it doesn't match a client email address. (This is a department setting)

This doesn't look like something we would be likely to build ourselves. I would strongly suggest reaching out to some third party developers. modulesbakery.com, and some other devs on the forums here may be interested (paulov, naja7host, and others)

That will be resolved as part of this task - https://dev.blesta.com/browse/CORE-1516 In the meantime, you can increase the limit yourself, please see http://www.blesta.com/forums/index.php?/topic/4761-cpanel-8-char-username-restriction/?p=35458

I am starting to like systemd and getting use to running systemctl, it's logical. I just have many many years doing it the old way so that's what wants to flow out of my finger tips.

Yep, we were able to automatically upgrade extensions as well during a normal /admin/upgrade. It's not a bad idea to check these post-upgrade, but this feature eliminated some issues, as you can imagine.

Well, that's good! What version were you running?

Interesting issue. I'm not aware of there have ever being a fix for such a problem, and I haven't experienced that myself or heard of anyone else having that issue. My concern would be that possibly your fields have the same name. You could inspect the element in your browser and compare the field names to each other. They should all be unique.

We recommend setting your packages for SSL to "cancel at end of term", and they can reorder if they want to renew the certificate. As they have to provide information in order to renew, auto renew could be problematic. Mention Blesta if you sign up with either GoGetSSL or TheSSLStore and they may be able to offer better pricing.

As naja mentioned, /support/vendors/ckeditor/skins/v2/footer.php in not part of Blesta. You should remove footer.php immediately, and investigate how it was uploaded to that directory. If you have any other software running on the server like Wordpress, make sure they are up to date. Wordpress is responsible for a lot of exploited websites. We highly recommend running Blesta on its own server without any other applications, keeping the server up to date, and locking it down with a firewall.

When an invoice is generated depends on your "Invoice Days Before Renewal" setting under Settings > Company > Billing/Payment. The default is 5, but can be adjusted. So, for example, if a customer orders tomorrow September 1st 1 month of service, they pay at the time of order and it covers the subsequent month. (Sept 1 - Oct 1). 5 days before Oct 1, on Sept 26th, an invoice will be generated for another month and due on Oct 1st, covering Oct 1 - Nov 1, and so on. You can change this setting to 1 day before, if you'd prefer to bill them 1 day in advance of the service renewing.

Prepay. Blesta does not currently bill in arrears. However, if you are manually invoicing, you can certainly bill in arrears.

You need 1 or more payment accounts, and for 1 of them to be set for auto debit. Also, auto debit needs to be enable for the client. If you want the box to be checked to save CC details for clients when they make payment, you can edit the template.

Did they change the name to netcash or is it still sagepay? Is this a payment gateway you need in order to switch to Blesta? If so, we may be able to create it for you.