Cody

I'm beginning to think we should simply mark the first created order form as the default order form.

You can already do this. Create the client in Blesta (takes 30 seconds or less) Click "Open Ticket" under "Account Actions"

This is almost always a server configuration issue. The cause varies drastically, so is incredibly difficult to diagnose. One thing to look into is the number of simultaneous connections allowed by the MySQL server. Increasing that value may solve the problem. Others have reported this issue when using nginx.

Hi and welcome. Blesta is already 30% off, no coupon neccessary. I'm not sure how much longer this discount will last though, it's a ridiculously good deal.

I imagine it would be pretty crazy to have 30+ clients with 30+ different due periods (# of days between invoice created and due date). Strictly from a customer support perspective it would difficult to manage. Generally due periods are set per company policy, so having client groups configure this setting is already quite flexible. I would say you could do this simply by defining the client setting that overrides the group setting, due to Blesta's settings hierachry, but you can't as the cron is simply not set up to work that way with respect to creating invoices. There's no question that doing such would be more resource intensive (e.g. slower to process). Nevertheless, a plugin could be created to do what you want. It would simply have to listen for into the Invoices.add event, and adjust the due date accordinly.

Just download and select free trial after installation.

That option is set upon installation. When you migrate over just be sure to update it to the correct path. This ensures that emails that are sent via cron have the correct URL paths in links.

Our thoughts are it is a bit odd to have tag support in signatures since signatures can be applied to multiple templates with varrying availability of tags. Signatures themselves have no tags, so as Tyson said, they could only inherit from the template they're injected into if we were to allow tags within them.

Plugins can only render widgets on designated pages as per the Plugin actions documentation. Keep in mind that plugins can create their own pages, and Blesta can not tell a plugin that it should render a widget, that's up to the plugin to decide. However, we are planning on adding some new features in 3.2 that will make it possible to add javascript code to every page. This could then be used to modify the DOM however you want.

Yup, it's on our list.

Moved to bug forum to diagnose.

That error may mean that one or more contacts failed to import because there was a state value for which the given country value did not exist. For example, if you have a contact with a state of "CA" and a country of "AUS" you would receive that error because "CA" is not a valid state/province for Australia.

That's a bummer because 3.0 is no longer in active development, and 3.2 will be out soon. Things are moving fast. Big changes!

Try the attached migrator. It contains a bug fix for the issue you're experiencing. Simply extract the zip to /plugins/import_manager/components/migrators/. blesta_migrator.zip

Version 3.1.1 is now available. You can download it in the Client Area. This is a patch release that corrects issues with 3.1.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes - Blesta Core - Version 3.1.1 ## Version 3.1.1 2014-02-12 ** Bug * [CORE-990] - Email parser syntax error with PHP < 5.3 * [CORE-997] - Removing package pricing that is in use causes the service to disappear * [CORE-1012] - Interworx: Remove check for domain name when creating a reseller account * [CORE-1013] - Appending a service to an existing invoice does not include tax for that service's line items * [CORE-1023] - VPS.NET: Undefined property r1soft_backups_enabled * [CORE-1026] - Support Manager: Missing loop back check for ticket notifications * [CORE-1030] - Nonmerchant transactions are listed as Other when editing. * [CORE-1032] - Adding a service with addons causes error attempting to pass a parameter by reference * [CORE-1040] - Cron task time format does not treat optional seconds as optional * [CORE-1045] - Security: Staff permission escalation through crafted URLs ---

Version 3.0.9 is now available. You can download it in the Client Area. This is a patch release that corrects issues with 3.0.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes - Blesta Core - Version 3.0.9 ## Version 3.0.9 2014-02-12 ** Bug * [CORE-1045] - Security: Staff permission escalation through crafted URLs ---

Sounds like all you need to do is enable mailparse in your CLI php.ini. Then you can get cron running via CLI again.

Yes.

You still have clients or contacts with non-existent countries. It's possible even invalid countries. If you can't figure out which clients or contacts the problem is occurring for, just update /plugins/import_manager/components/migrators/blesta/2.5/blesta2_5.php from: 'country' => $client->c_2char != "" ? $client->c_2char : null, To: 'country' => $client->c_2char != "" ? $client->c_2char : "US",

The default is INBOX. This is the box Blesta will look in for new messages. So it depends entirely on your particular email account setup.

Gateways can create their own database tables, if they find it necessary, and execute queries on there. They may do so during execution of the install method on the gateway. I don't know that a general solution is warranted here as almost all nonmerchant gateways return data regarding invoices that were submitted as included. As far as pending transactions go, a transaction is only pending if the nonmerchant gateway notified Blesta of the transaction and the transaction has not yet been fully processed by the gateway. In all these cases the gateway submits a new request once the transaction has been processed and Blesta updates the status of the transaction. I don't think deleting those transactions in these cases is a good idea, as the payment must either have failed (error/decline/etc.) or succeeded. In either cases Blesta should have been notified, and if it wasn't then it's important that manual action be taken from a staff member to identify what went wrong.

You probably don't have error reporting configured to display errors in your PHP CLI ini file.

Not sure there will be direct download links for client documents, since the client has to be logged in to download them.

Do you have the correct Box Name set?

Blesta doesn't support 3D secure at this time, and currently has no plans to do so. Feel free to make a feature request. Our current stance is that 3D secure is poor solution to card verification. Card security codes (CVV) pretty much solve the issue, and the future of payment processing is moving in the direction of the merchant never seeing or touching card numbers (leaving that task with the gateway entirely).