Tyson

If a ticket is closed, what purpose does that status serve if the ticket can still be replied to?
 
I can see having a Re-open Ticket option available X days after a ticket is closed, and which may be extended to replies being emailed in, but otherwise, I think the Closed status needs to be used as the ticket end-state.

You can modify the language used for these actions, and add "\n" at the end of the "The <action> completed successfully." definitions.

We get brush fires often, especially in this summer heat. But these are usually in the hills where homes are not lined up in rows, like in the cities. Being in a city, the threat of a fire is nil, and extends mostly to whether you left your stove on or not. But either way, the fire departments get on them so fast there really isn't much to worry about.

I believe Paul was referring to Payment Accounts in Blesta, as they do not save payment account details for Nonmerchant Gateways.
 
And as Paul mentioned, it would be helpful to us to see documentation from gateways that accept these fields.

The callback URL is set automatically by Blesta. IIRC, the PayPal setting for a callback URL is only used if one is not given.
 
If your Blesta installation is not on the Internet (i.e. on your local network), PayPal cannot communicate with it, and so Blesta will not receive any callback notification. If this is not the problem, is there any log information under [Tools] -> [Logs] -> [Gateway]?

Assigned as CORE-698. It would also be helpful to know any and all email templates this affects.

Assigned as CORE-699. Like the other report, it would also be helpful to know any and all email templates this affects.

We haven't implemented a fix yet, so I couldn't tell you how to patch it yourself.

This bug is not fixed in v3.0.1 since CraigA reported it just before we released the patch, but it should be in the next patch.

Thanks for the video. Have you noticed this applying only to order forms, or to any services created (e.g. 'Create Service' for a client from the admin interface)?
 
Added as CORE-696.

This is fixed in CORE-669 for v3.0.1.
 
This has also been added to it.

A login link will be in there with another update to the module and has already been assigned as CORE-622.

I think Cody's fix from the other thread should be
 
update /app/models/clients.php (line 89):
$this->setCustomField($field->name, $client_id, isset($vars['custom']) && array_key_exists($field->name, $vars['custom']) ? $vars['custom'][$field->name] : null); to
$this->setCustomField($field->id, $client_id, isset($vars['custom']) && array_key_exists($field->id, $vars['custom']) ? $vars['custom'][$field->id] : null);

Go to [settings] -> [Emails] -> and click to edit "Invoice Delivery (Unpaid)". Paste the contents of the HTML and text versions of the email template here.
 
Your error points to a missing {% endfor %} tag, and sanetcy's solution should resolve it:
 

Sounds like a bug with how the order form passes custom field values for validation. I believe custom fields are validated one at a time, so even if all of them are erroneous, only the first error would show.

I've added this as CORE-688 and we'll take a look at the import issue.
 
The tax number will be shown on invoices regardless of whether tax is enabled for a client. I believe this is the intended purpose, especially considering the laws necessitating behavior in some european countries.

This happens when adding a new service? It sounds like your Plesk server is complaining about the data type it received for the webspace/subscription ID. We've tested this on Plesk v11.5 and haven't experienced this issue, so I wonder why Plesk complains about the data type for an empty string now.
 
If you're familiar with php, you can edit /components/modules/plesk/plesk.php and change:
$data = array('id' => $webspace_id); to
$data = array('id' => (empty($webspace_id) ? null : $webspace_id)); and let us know if that resolves your issue.

This is not a bug. If you read the tooltip next to the language checkbox when adding/editing a payment type, it will say that you should only check that box if you added the name to the language file. The language file is /languages/en_us/_custom.php. The same goes for custom fields and contact types.
 
You'll need to either add the name to the language file, or edit the payment type and uncheck that box.

sanetcy's solution should solve this issue. The email template needs to be syntactically correct. You can review the documentation to help with using tags in email templates.

Check your Service Creation email template. What tags are you using? If you use no tags, does the error go away? I suspect you are using a tag incorrectly. The documentation might help.

Some of us in the US still value freedom.
 
Why isn't TOR an option in the poll?

The Blesta Translator is an ongoing project designed to help translate Blesta into other languages. To get started translating yourself, simply sign up for an account at http://translate.ble...account/create/ and begin translating Blesta to another language.
 
You can now download translations from the Blesta Translator by clicking the download link next to the language you would like to use.
 
To install a language, you will need to:
Unzip the contents of the language zip you downloaded; Upload the contents of /public_html/ from the zip to the web directory that you have Blesta installed under (e.g. /public_html/ or /billing/). Log into Blesta and navigate to [settings] -> [General] -> [internationalization] and click Install to install the language. (optional) If you would like to use this language as your company's default language, navigate to [settings] -> [General] -> [Localization] and select it from the Default Language drop-down. Don't forget to save this change. IMPORTANT:
Due to caching, the primary navigation will not appear to be using the new default language. You must re-save your Staff Group settings for this to take effect. You can do this under [settings] -> [system] -> [staff] -> [staff Groups] by editing your staff group and clicking to save your settings.
 
If you install and use a language whose definitions are only partially complete, the remaining definitions will appear using English, US.
 
 
The languages that you download from the translator are updated periodically once per day automatically. New definitions that you translate are not immediately available for download in the language zip for the version you are translating.

The Blesta Translator is an ongoing project designed to help translate Blesta into other languages. To get started translating yourself, simply sign up for an account at http://translate.ble...account/create/ and begin translating Blesta to another language.
 
You can now download translations from the Blesta Translator by clicking the download link next to the language you would like to use.
 
To install a language, you will need to:
Unzip the contents of the language zip you downloaded; Upload the contents of /public_html/ from the zip to the web directory that you have Blesta installed under (e.g. /public_html/ or /billing/). Log into Blesta and navigate to [settings] -> [General] -> [internationalization] and click Install to install the language. (optional) If you would like to use this language as your company's default language, navigate to [settings] -> [General] -> [Localization] and select it from the Default Language drop-down. Don't forget to save this change. IMPORTANT:
Due to caching, the primary navigation will not appear to be using the new default language. You must re-save your Staff Group settings for this to take effect. You can do this under [settings] -> [system] -> [staff] -> [staff Groups] by editing your staff group and clicking to save your settings.
 
If you install and use a language whose definitions are only partially complete, the remaining definitions will appear using English, US.
 
 
The languages that you download from the translator are updated periodically once per day automatically. New definitions that you translate are not immediately available for download in the language zip for the version you are translating.

I think you should take a look at the reports coming in v3.0.0, which will export CSV data for at least a few of the items you listed above, like transaction amounts coming in, taxes, past-due invoices, etc.

If you have photoshop, you can save the images for the web, which optimizes them, decreases their quality (hardly noticable, if at all), and lowers the file size. Some of your images are very large, but are set to be resized by the browser when displayed. Those images load slower than necessary because the browser still must download the full-size image, so you should manually resize the image to the exact dimensions you plan to display them in first. Or if you're going for a more responsive feel, resize them to the largest they need to be so they can be resized down dynamically.