Cody

In other words a client would only be allowed to pay the value listed on the invoice (e.g. not pay more, not pay less)? Obviously, the biggest caveat with this is nonmerchant payments that come in. Blesta has no control over those, so that would still allow payments to pay more or less than the amount due on an invoice and add credits willy-nilly.

Glade to hear. CORE-915 is done for 3.0.7.

P.S. There is an enom module. It will officially ship with version 3.1, but you can get it now.

You're probably getting that error because you've selected not to use the module for adding the domain. When you do that with the logicboxes module it attempts to fetch the "order-id" (required for all logicboxes services) using the domain name. The domain "dfhkayaking.com" does not exist in your logicboxes account so thus the error.

Added as task CORE-915.

Try this: Update /components/gateways/nonmerchant/_2checkout/_2checkout.php (line # 290) from $order_number = ($this->ifSet($post['demo']) == "Y") ? "1" : $this->ifSet($this->meta['transaction_id']); to $order_number = ($this->ifSet($post['demo']) == "Y") ? "1" : $this->ifSet($post['order_number']);

Moving to support as not a bug.

These are graphics created by their respective payment processors. I've had the idea for a while of removing these altogether and replacing them with standard buttons. PayPal, and I believe a few other (now defunct) gateways required that you use one of their payment button, but I think they have since become much more lax on this.

We've gotten reports with clients having the same client number after importing clients. It's a bug in Blesta we're working to fix for 3.0.7 The solution for now is to change the 'clients_start' company setting to '1'. This bug occurs because the default starting value is '1500', but the maximum number of your imported clients is less than that. Run the following query to find the 'clients_start' company setting: SELECT * FROM company_settings WHERE key='clients_start'; Run this query to set the value to '1':UPDATE company_settings SET value='1' WHERE key='clients_start';

"Required parameter missing: reg-contact-id" means there's something with the contact details that Logicboxes doesn't like. You need to look at the module log to determine what they're returning an error for. "Website doesn't exist for websitename.com" means that websitename.com is not a domain registered under your registrar account.

If that's a transfer request, ensure that your ResellerClub account allows that TLD.

It can even run on a Raspberry Pi.

Tokenizer is not used in Blesta. Hash is not required to run Blesta, though it will improve performance. Blesta works in a lot of different environments and libraries, but we don't claim support for them because we can't offer support for them.

I can't stress this enough. Always, always, always, check the System Requirements before moving to a different server.

What's the error?

Is the domain locked with enom?

I see. Well, Blesta has no way of knowing whether or not a domain can be transferred because the APIs that modules use to interface with registrars don't support such a query. So Blesta must assume that if you're intending to transfer a domain that you're aware of the steps required to perform the transfer from your existing registrar.

Check [Tools] > [Logs] > [Gateway]. PayPal must send the payment notification to Blesta and the address used for the notification must match that of your PayPal account in [settings] > [Company] > [Gateways] > [PayPal]. If you're behind a NAT or a local IP address PayPal may not be able to make a callback request to Blesta. The client's email address doesn't matter.

We have plans to make available a public roadmap. Paul's just been too busy lately to configure the permissions on our issue tracker.

Is the payment for a cpanel service? If so, check the module log ([Tools] > [Logs] > [Module]) to see why that cPanel account is failing to be provisioned.

Do you see the callback from 2checkout in the logs ([Tools] > [Logs] > [Gateway])?

What do you mean by validate a URL?

What does the log say [Tools] > [Logs] > [Module] when you perform the transfer? Sounds to me like whatever module you're using doesn't care that the domain is locked. That would be an issue outside of the control of Blesta.

Forcing HTTPS. Since you made the redirect a 301 you might need to clear you'll probably need to clear your cache to see the change.

The contact details on file for the client are resulting in an error from the registrar. Look at [Tools] > [Logs] > [Module] to see the exact reason and correct it.