Paul

What was it?

That looks like some custom installer, you'll need to contact them to determine what version it is. My guess is it's 2.5.

Hi Dennis, If you obtained your v2.5 license from midphase, you can request a v3 license from them. The license keys are different. Going from 2.5 to 3.0 is more of a migration than an upgrade because v3 has an entirely new codebase. See this for installing v3 http://docs.blesta.com/display/user/Installing+Blesta See this for then importing your data from 2.5 to 3.0 http://docs.blesta.com/display/user/Migrating+to+Blesta You can download v3 from the home page of www.blesta.com, and select to start a 30 day free trial during installation. This will allow you to get v3 running while you request and wait for a v3 license key from midphase.

Disabling the portal plugin should redirect requests to the root web to /clients/ automatically.

PHPMail is the default option, and will only work if your PHP supports the mail() function. SMTP is recommended as it's faster, and you would just plugin your SMTP server details under Settings > Company > Emails

It's true that the email comes from the same address, but the reply-to address is set to that for the department. When a user replies to a ticket email, it should go to the correct department.

Awesome, thanks!

If you haven't already, please rate us on Hotscripts at http://www.hotscripts.com/listing/blesta-billing-that-works/ Thanks guys! Paul

CORE-747, tentatively scheduled for 3.3.

The rotation policy is for logs stored in the database, and viewable under Tools > Logs. These logs can get quite large, so they need to be rotated. Any files written to /tmp (or the location you set) should be removed right away. Nothing is ever deleted from the uploads directory unless specifically done by the plugin who put it there.

Blesta uses different encryption and hashing algorithms for different purposes. Admin and client passwords are stored using bcrypt, computed from an HMAC-SHA-256 hash of the password. This is a one way, algorithm that is extremely difficult to brute force. User passwords are not reversible. Modules can store some or all of their meta data encrypted, and encryption is used throughout the system to securely store data that can be decrypted like credit card numbers, service meta data and more. I believe this is done through AES, and in the case of credit cards additionally an RSA public/private key pair. Cody can elaborate more on all of this and correct any errors in what I just said.

Price overrides are something we have thought about and would consider, but this would be a feature request.

CORE-746. On successful registration, redirect to the Dashboard and display a success message.

I believe matching packages is much simpler to do than importing packages, in terms of development. We'll see what Cody says, but I think the goal was package matching first, and revisit for package importing. In terms of usability, importing the packages is preferred so I definitely want to see it in there. We want to make migrating as simple and complete as possible, but it is a challenge considering how different these two products actually are.

Screenshots look really good!

I don't see how it would have come from the import, if these are newly created invoices. There was a directory path issue for sub directories that was corrected in 3.0.1 or 3.0.2, but it sounds like you may be running 3.0.2, so I'm not sure what's going on.

Is it suppose to be my.hostingdifferent.com? Are you running 3.0.2, and is the path under Settings > System > General > Root Web Directory correct? And is the hostname correct under Settings > System > Companies?

If the invoices were generated prior to the import, any payment URLs will be invalid. If the invoice was created in Blesta after the import, it should work. Email templates should not be imported.

In the PDF? Can you provide an example?

We haven't had many requests for an AWBS importer, I doubt it's one we'll be building soon. The first link I clicked on their "Who's running AWBS" page was actually running WHMCS, which may have been a coincidence but it doesn't look like they are being used by many people. The latest news is from Feb 2011.

Where are you seeing old URLs? Do you mean in the mail logs?

Blesta is less annoying about those kinds of things, the biggest thing is the cron.. though I can see mentioning the uploads directory as people generally don't set that until they try and fail at uploading something.

You could modify the invoice template file to remove the customer number. I believe the file you want is components/invoice_templates/default_invoice/defailt_invoice_pdf.php. Look at lines 409-413 in the drawInvoiceInfo() method.

We are planning to add some overall ticket stats like average response time, average resolution time, etc in the admin area. Do you think these averages should be displayed to the customer so they have a rough idea of when they can expect a response? If so, how and where?

Welcome, good to have you!