Paul

The API response is logged to the module log under Tools > Logs > Module tab. Click the row for the API call to expand it and see the raw input/output from the API call. Usually the output will provide more information. If there is some kind of PHP error, it would be logged to the file logs under ../logs_blesta (Path defined under Settings > System > General) so you may want to check this also. Only errors written during the registration attempt would be relevant.

If it marks it as read but doesn't import it, it is probably failing. Try disabling your cron job, and running it manually under Settings > System > Automation by clicking the button, after a 5-min wait with an email ready to be imported. At the same time, tail your logs via SSH. tail -f /path/to/logs_blesta/*.log Note any output and whether the email is imported when running the cron manually that way.

What version of Blesta are you running? Namesilo requires that you have a payment ID and a verified payment method to register/renew/transfer domains over the API. That is the most common reason it does not work as expected. It is possible to manually renew/transfer/register domains with Namesilo through their interface without a verified payment ID, but not over their API.

How are you importing tickets, using POP, IMAP, or piping? Are you saying that a new email to the department opens a ticket, but replying to the email sent to the client from a staff reply does not get imported? It's unusual that an email would be imported for a new ticket but not for a reply unless the reply is missing the required information in the subject line. I would check that mailparse and php-imap are installed. When changing PHP versions, this is most commonly overlooked. The errors you've included do not appear to be related.

It's a good idea for sure, but as you've noted it hasn't had that much support thus far. As a result, it isn't a very high priority, but definitely something we'd like to add support for.

If you installed Blesta in a subdirectory called "clientarea" then this is why. You would need to install Blesta in the document root. If you have a website, then you should use a subdomain.

You can change the path to the admin and client areas by changing their routes in a config file. See https://docs.blesta.com/display/user/Configuration+Files#ConfigurationFiles-routes.php for an example for these. If you change the admin route, you will need to clear your navigation cache which can be done by resaving your staff group (Settings > System > Staff > Staff Groups: Edit & Resave)

Stripe Payments supports ACH in Blesta 5.3, which is not out yet. Beta soon.

There may be a problem with the logo or background image you have set. Try removing them to see if it resolves the issue, and if so, try re-saving them differently from your photo editor.

Looks like you created a request here https://requests.blesta.com/topic/support-for-hosted-transactional-email-postmark-mandrill-mailgun-etc We are considering transactional email integration, it's something that I think we are likely to do, it's just not a very high priority at the moment. We'll keep an eye on your request

Check also that PHP IMAP and Mailparse are in your CLI PHP. Your ../logs_blesta/ error logs may have more information. Trying to pipe manually via SSH as in the test case described in the docs should help to narrow it down.

Blesta doesn't include a pipe2.php so if you are using multi-company, check that it is a copy of pipe.php but has the correct company ID defined in the files. Double check that the file is executable (chmod 755), and that the full and correct path to PHP is included in the hashbang on the 1st line of the file. If your account is in a chroot environment, it may not be possible for the mail server to pipe email into Blesta. The next step would be to test piping per https://docs.blesta.com/display/user/Support+Manager#SupportManager-TestingPiping via SSH.

We're revisiting custom ticket department fields, might be something we could do for version 5.4 or 5.5, we'll see. Requires some additional internal planning. Thanks for the suggestion.

FYI this was implemented in 5.0 https://dev.blesta.com/browse/CORE-1935

Did you try using the "Offline Payment" gateway? You can include your own message describing how to submit payment, even include a link to make payment through another website.

This error seems to indicate that MySQL crashed, are you still getting this error? If so, see that you meet the "Recommended Requirements" and options for MySQL/MariaDB https://docs.blesta.com/display/user/Requirements If you get past that error and still have trouble and want to get us a copy of the database securely so we can run a test import and debug in a local environment we will be able to resolve any issues and get an updated importer to you (and delete all copies of the data).

Thanks for the suggestion, we will discuss. If you want to make an official request for this, you can post it at https://requests.blesta.com

There are a few examples shown here https://docs.blesta.com/display/dev/API#API-Examples The API for Blesta is open, all public model methods including those of extensions can be accessed over the API. This makes it impossible to provide an example for every possible action, because it's so open. I'm sure we could use more examples, but we couldn't possibly cover it all because as we expand Blesta, the API expands automatically. Very easy, you can use PHP code in the template files directly. /app/views/client/bootstrap/ Yes, yes, and as mentioned there isn't much that can't be done given the architecture of the API. The demo has not yet been updated to include the domain manager, I would suggest installing the free trial to evaluate. Within the demo, we cannot integrate with real registrars because of the nature of public demos. You can create both configurable options and addon packages for offering other things. Addon packages are useful if the addon should use its own module. Clone /app/views/client/bootstrap/ and give it its own name, then select it under Settings > System > Look and Feel > Template and make your changes. We recently released a lot of updates to domains and we aren't finished, there is more to come. If anything, Blesta is not only on par for core billing functionality but exceeds WHMCS. They take a lot of shortcuts we do not take. In Blesta, changing a clients currency does not cause all preexisting transactions and invoices to switch currencies and maintain their values, for example. They have issues that just don't exist in Blesta.

Were we able to help?

What version of Blesta is this, and what OS/Browser version are you running? I was not able to reproduce on 5.2.2 with Chrome on Windows.

The downloads are updated automatically once a day, around midnight UTC if I recall. If you translate the language pack, and let us know, we can make it take priority in the download.

I believe the PayPal email you configure within Blesta must be the "primary" address in PayPal for it to work correctly. So while you can have multiple aliases in PayPal, whichever is the primary one must be the one set within the PayPal Payments Standard gateway within Blesta.

Interesting! I think the language is handled by PHP and PHP's date function defaults these to English. The simple solution would be to change the month from a name to a number instead. This can be done under Settings > Company > General > Localization by updating the Date Format from the default "M d, Y" to something else. Per https://www.php.net/manual/en/function.date.php you could use, for example: m.d.y to display the date in this format: 03.10.01 Take a look at the examples from that link and format as desired.

Where do you list multiple email accounts, within the PayPal gateway configuration? If multiple can be listed, how does it determine which to use? Or is this on the client-side?

Thanks https://dev.blesta.com/browse/CORE-4549