Cody

If you're sure that your registrar supports .id, you can add it to the list in /components/modules/logicboxes/config/logicboxes.php. According to our source at Logicboxes, the complete list of all TLDs supported by Logicboxes can be found here: http://www.logicboxes.com/product_pricing#domain-resellers

This was updated in 3.0.7.

You need to update them in the database directly. The field is called "id_value" in the "clients" table.

We follow semantic versioning. Every release is considered stable, unless it's a pre-release designated by a hyphen (-) after the version number.

Probably because no one ever requested it.

Sounds interesting!

You can see all under [settings] > [Company] > [Gateways] > [Available]. Look for ones labeled "ACH" or "ACH offsite".

ACH works just like credit card payments. The only difference is the user enters their routing and account number instead of their credit card number and expiration date. Everything else is exactly the same. One thing to keep in mind, as a merchant, is that bank transfers take time to clear and it's not known by the payment processor whether sufficient funds exist prior to the payment being cleared. This means that the bank account number could be invalid, or insufficient funds available, etc.; however the transaction may still be processed successfully. With ACH you'll need to ensure that the funds have cleared before you approve an order.

I think you might want to direct that +1 to aTech media.

CORE-954 is done in 3.1.0-b2.

CORE-60

Added CORE-954 to address this in 3.1.0-b2.

You could contact the people that created the WHMCS plugin: https://github.com/atech.

3.0 and 3.1 are separate branches, but any bugs in 3.0 that affect 3.1 are merged into 3.1.

Start a new thread in the Support forum.

Good catch. I think it should probably strip the signature from the reply if that is the only thing in the reply regardless of the status (thus no reply created).

This is included in the support manager plugin. Instructions here.

Fixed in 3.0.7. CORE-907.

This is in 3.1. CORE-810.

Closed as not a bug.

Added CORE-949. That line (line #40 in /plugins/order/views/templates/standard/main_summary.pdt), should be removed. $item['qty'] = $this->Html->safe($item['qty']);

Created CORE-948 to address the error. The solution is to either enable some payment types, or record the payment instead. The error affects all version (3.0.0 - 3.0.7).

There's no need to make any permission changes after installation. The only directories that should be writable are the upload and temp directories as configured in [settings] > [system] > [General] > [basic Setup]. However, it's a good idea to leave /config/blesta.php writable for future upgrades.

The final steps (post installation) is to creat your first administrative user and choose either a trial or an existing license key. Are you saying you didn't see this step, or are you saying this is the step that gave you trouble?

I suppose a payment gateway could be greated that prenteded to process a card, but instead sent an email to a staff member to notify them of a manual payment being required. The staff member would need to log into Blesta to view the card details. The CVV would, obviously, not be available at that point. If CVV is required the only logical solution is to either process payment with customer on the phone, in person, or via an online payment gateway.