Paul

Only one way to find out, my guess is, probably. They haven't changed much with their database schema I don't believe. However, it's probably better to copy your install, upgrade the copied version, and then import from that database.

Mike is right, you can upgrade.. however, couple things to note.. 1. If you upgrade from 3.0.x to 3.1.0-b1, you MUST run the upgrader via CLI, ie php ./index.php admin/upgrade 2. If you do a fresh install of 3.1.0-b1, you should be able to upgrade to 3.1.0-b2, and 3.1.0 final via GUI or CLI methods. This is due to a bug in 3.1.0-b1 that breaks the CLI upgrader.

What would be the benefit of a per-product override? You are either under EU rules, or you aren't, right?

Do you happen to have 4 client groups? If so, have you upgraded to 3.0.7?

Yes, the simplest thing would be to develop a plugin that calculates the price each month based on the # of days, and updates the package price prior to renewals. It can do so via an automation task it registers. Soon it will be possible to have packages defer their pricing to a plugin, in which case your plugin would be able to control the price directly vs updating the package.

I'm not sure there's a way to do exactly what you're asking as the monthly amount would be variable. You could adjust the package price ahead of each month to accommodate this, or you could set the package price to "30 days". The renew date would not be the same each month depending on the # of days in the month, but then you'll be billing on a 30 day cycle rather than a monthly cycle. (Or 28 days, or whatever you want to do). If you bill on a 1 day basis, it will invoice daily.

The plan is to add a company and perhaps client group setting to enable proforma invoicing. Then, Blesta would create proforma invoices by default, and once paid, these proforma invoices would become normal invoices. Proforma invoices have their own numbering scheme, and are not simply converted to an invoice. Someone named Bjorn emailed us what I believe to be a clear description of proforma invoices. I'm including what he wrote here, so that we can solicit your feedback and provide some dialogue as we lead up to development on this.

Did you run the migrator twice? You'll need to re-install Blesta before attempting another import. What we recommend is after installing 3.0, do a backup of your 3.0 database. Then, do the import. If for any reason you need to run the importer again, first restore your 3.0 database. Importing to a clean database is the only supported import method.

If you are considering developing your own system, consider this.. Blesta is 99.9% open, you can modify it to include proforma invoices. You might even be able to re-purpose draft invoices for this without too much trouble.

Proforma invoices are coming, part of CORE-497. I don't have an ETA for you yet, tentatively scheduled for 3.2 but not guaranteed to be in this release.

b2 has not been released yet

It may not show up for you because you have reseller licenses only. Open a ticket (medium priority), with FTP details and I will FTP the zip file to your server where you can retrieve it. Please note that a beta is not intended for production use, and you should do a fresh installation. Also, support is only provided on the forum for betas.

Both are in 3.1

Are you running Blesta in a NAT or reverse proxy? It may be possible that their IP address is seen as your servers for this reason, but not sure why it would sometimes show the correct IP address.

Check your schedule under Settings > Company > Automation. If auto debit is set to run before invoice generation, then it will run before the invoice is generated and thus be unable to auto debit it for that same day.

The only other thing I can think of is that Auto Debit was enabled on the client profile, and that a payment account was set for auto debit. If the answer to both of these is yes, I'm not sure what the issue was unless there is a bug in here someplace.

The cron log seems to indicate that there was nothing to charge. On 12/23/13, was there an invoice due on 12/23/13? When did you manually process it? If the auto debit cron runs after your invoice cron, then it wouldn't try until the next day.

If the payment account was created and then Stripe was changed and "Store card information offsite" was checked or unchecked then the payment account *may* need to be recreated. Also, check the auto debit cron task log under Tools > Logs > Cron to see if there are any errors with processing auto debit. It should display which invoices should be charged and whether they were successful.

Happy New Year! I have a feeling it's going to be a great year!

It was caching it, thanks. Probably should redirect blesta.* to blesta.com, will try to do that soon. Thanks for the heads up.

Hi Larry, Since Blesta didn't create the VPS, it's probably missing the solusvm_vserver_id key in the service_fields table. Search the service_fields for the service_id for this particular service. Among the results should be a key that matches solusvm_vserver_id with a value that matches the id for the server in solusvm. If this row is missing, or wrong, you can add it or update it in MySQL, respectively.

Make sure that the email address as configured in Blesta for your PayPal gateway is the same email address that is set as the "default" email address in PayPal. If they don't match, Blesta will not record the payment.

Yes major.minor.patch ie 3.0.8 So the next minor release is 3.1, then 3.2. Betas are designated like this: 3.1.0-b1 (Or a1 for an alpha 1 release) 3.1 stable will be released in January within the next couple weeks most likely, and then it will be full steam on 3.2.

Tell me you're not a spammer.

I'd love to include it in 3.1, but the majority of the work remains to integrate the markup into the existing templates, plugins, and modules. Hoping to get 3.2 out in record time after 3.1, we're definitely going to hit the ground running. Some other features we're planning to add to 3.2 also.