Paul

A cron job and a cron tab are pretty interchangeable, I think. I agree, assigned to CORE-791 - thanks! I'll see what we can do about that, there is definitely room for improvement here. Not sure why that is, your web server isn't doing any caching is it? Can anyone reproduce? Forcing HTTPS was actually added to 3.1. We need to split the documentation for 3.0 and 3.1, and will be doing that shortly. Often times we have people asking how they can force HTTPS for their Blesta installation. It's a good idea to use SSL whenever possible, especially when personal and financial information may be at risk. Since not all servers have SSL, we added the rule and commented it out so that it can easily be enabled. If your cron job is set up and running, then installation is complete. I suggest checking out common tasks in the manual http://docs.blesta.com/display/user/Common+Tasks for what to do next. This forum is also a great place to ask for help! Thank you for your suggestions!

I've linked to it in the manual here - http://docs.blesta.com/display/user/Company+%3E+General A tooltip here would probably be a good idea though.

I think he means everyone in this thread who posted a review

Thanks!

You can set up a package with multiple price options for the same term.. for example.. Package A 1 Month $89.99 1 Month $99.99 1 Month $79.99 Then just select the appropriate price point for the legacy package. This wouldn't make sense if offering it for order, since the customer would simply select the cheapest option, but for legacy services it might help with what you are trying to do and reduce the number of package permutations that are required.

Thanks for the suggestion. Do you think this could be accomplished by using conditionals in the welcome email template now? It's likely we will add the ability to create custom email templates in the system in the future, and a method by which they can be utilized by the core, manually, or by other extensions.

What happens if you log out entirely, and log in directly to that other company? Does the ticket still appear? Can anyone else reproduce this?

If you originally imported from 2.5, the passwords as stored in Blesta 3 will be the same MD5 hashes unless/until the user logs in and the password is updated. If you look at the users table, password field, it should be pretty obvious which passwords are MD5 and which are not. MD5 passwords are 16 byte, and will appear shorter than new passwords.

Thanks for the report on this guys, I have not confirmed but I have assigned this to CORE-789 so we can investigate.

A service price override option is assigned to CORE-747 and tentatively scheduled for 3.3. We might be able to bump it to 3.2, but even then it's still a little ways out. I wonder if you're able to use recurring coupons to get the pricing the way you want, though it may be simpler to use legacy packages.

Which CSS files did you find to be poorly formatted? I'm happy to take a look.

What do you mean by post to host? Can you provide more details?

We did design the invoice system to be able to support multiple formats, like PDF, HTML, and more. I'm pretty sure we will be implementing an HTML version. However, others, like the aforementioned generate their PDF invoices from HTML directly which we think results in a poorer quality PDF. So, the challenge will by to try to re-create the PDF version in HTML such that it looks similar.

In Chrome for me, it just downloads it and doesn't give the option to open without saving. So, it can vary depending on the browser and the PDF reader installed.

I've added a little bit to the documentation for contact types - http://docs.blesta.com/display/user/Company+%3E+General I think contact types start to become extremely useful once they are able to login, and have unique ACL permissions. At the moment, they are primarily useful to admins when responding to inquiries about an account, or reaching out to the company for whatever reason.

Can you post a screenshot of what it looks like with unlimited set? I'd like to make some improvements overall with the graphs here.

You need to enable legacy password support in config/blesta.php http://docs.blesta.com/display/user/Configuration Blesta 2 uses MD5 passwords for user accounts. Blesta 3.0 uses bcrypted HMAC SHA 256 passwords. Enabling legacy support allows clients with imported MD5 passwords to login.. and once they do, they are converted to the new password format. We suggest enabling legacy password support, and then disabling it after a reasonable amount of time.

Stay positive, I like it!

Interesting, does this only occur for non-clients opening tickets? Can anyone else reproduce? I'm not seeing this is our environment, but only clients can open tickets.

What were you searching for an alternative to? I think the reviews show up, but the ratings seem to be stuck at 13 for some reason. Thanks to everyone who posted a review or rating though, it means a lot to us.

Or you can sponsor development for one

A direct cPanel reseller module would be good, but I could see a module that uses buycpanel.com work out a little better. Not only would there be no volume commitment, but we could include other software products that they offer.

If generating an invoice manually, or via the API you aren't even restricted to a particular term as supported in Blesta. You can bill for any term or any quantity you want. Only if it has a service, must the service follow a supported term & period.

That looks pretty good! And, a beer does sound pretty good. Cheers. There may have been another thread for this, but this issue (must have a field for a universal module) is corrected in 3.0.4 and should be released in the next week or two.

Then you'll have to fetch the information for the invoice template by doing a query yourself, the data will not be available automatically and there is no method that you can invoke to fetch the information. We suggest only making changes to the database structure or core files if necessary as it may eliminate an upgrade path. All of the areas you may need to modify to allow the field you added to be updated via the interface, and during check out, etc may be quite significant. Cody or Tyson may be able to point you in the right direction, but we can't provide any official support for this.