Tyson

The [billing] -> [invoices] listing, as Ken mentioned, shows the client name when you hover over the Client #. If you want to sort by the client name, you can update /app/views/admin/default/admin_billing_invoices.pdt to either add a new column for the client's name, or replace the Client # column with the client name. Each column only supports one field for sorting, so you would use either the client's first name (client_first_name) or client's last name (client_last_name) as the field to sort on. If you're familiar with HTML and PHP, it should be fairly straight-forward to add this in through the template.

How many servers and server groups do you have setup in Blesta (under [settings] -> [Company] -> [Modules] -> [Manage DirectAdmin])? What version of the DirectAdmin module are you using? What are the names of all of the fields that do not re-populate? Is it just the "DirectAdmin Package" field? If by empty, you mean the drop-down contains no options, then it's likely that the API request to fetch packages from DirectAdmin has failed because of any of several reasons, e.g. No module row (server) could be found in order to make the API request The Account Type selected is invalid and results in no DirectAdmin packages There was an error attempting to make the API request

Are you still experiencing this issue? If so, can you provide steps to duplicate it?

Issues related to dates were resolved in CORE-962 for v3.1.0-b2.

Are you still experiencing this issue?

Fixed in CORE-974 for v3.0.8.

Closing this thread as unable to duplicate. You can create a new thread if you continue to have this problem.

Moving this to the Feature Requests forum. Blesta cannot determine whether a domain is transferable or not because that action is not supported by the API as Cody mentioned here. The other issues are feature requests/improvements.

Are you still having this issue? Is anyone else able to duplicate?

Blesta doesn't invoice for 'credits' or negative sums. Instead, the credit will remain in the client's account until it can be applied to an open invoice.

Setup fees, currently, cannot be removed on a per-service basis. But you can request this feature by creating a new thread under the Feature Requests forum. As a possible work-around, you can temporarily edit the package to remove the setup fee, then add the service to the client, and go back to re-add the setup fee for the package.

Go to the client's profile page. On the left, under Actions, click Record Payment Enter your payment amount of 100 Set the payment type to In House Credit Set the currency the payment should be credited in Do not select any invoices, if any are listed, unless you want to apply the credit to those invoices manually Continue to the next step Submit payment Go to the client's profile page. Look at the Transactions list, and find the approved transaction. If there are too many, you can instead look for the closed invoice, and click on the invoice row to see a list of transactions applied to it. In this case you would click to edit the transaction. Click Unapply to unapply a payment from the invoice. The transaction amount that was unapplied will be added as a credit. Then you can edit the invoice and Void it.

Thanks. This is fixed in CORE-973 for v3.0.8.

There may be a difference between what you want displayed in the admin interface versus the client interface.

Under the Service Options when you create a product, set the Name field to "qty". You can take a look at the Universal Module documentation for additional info.

Make sure that: The Auto Debit cron task is enabled under [settings] -> [Company] -> [Automation]. The Auto Debit Days Before Due Date setting under [settings] -> [Company] -> [billing/Payment] -> [invoice and Charge Options] matches the date of any invoice(s) that you expect to be autodebited today. This setting can be overwritten by specific client groups under [settings] -> [Company] -> [Client Groups]. i.e. if today is Jan 8, 2014, and this setting is set to "3 days" it will attempt to auto debit the account on Jan 5, 2014. The client has Auto Debit enabled on their account profile page. The client has a payment account, and that payment account is selected for auto debit (the left radio button on the payment account listing page). The client has open invoice(s) in a currency with which the payment account (via the payment gateway) is currently set to accept.

Looks like you have some of those values set as serialized. The null values should be serialized (i.e. "N;"), but I don't believe the others should be.

Thanks. Added to our bug tracker as CORE-964.

Was an invoice created for the client after ordering the hosting service? And was that invoice marked paid? If it's not paid, it will not be automatically provisioned. Do you have your cron setup and running? Is it set to provision paid pending services (see [settings] -> [Automation])? You may need to wait up to the interval set there before it will be provisioned automatically. If you're still having issues, check the module log under [Tools] -> [Logs]. Click on a row corresponding to the service provision attempt and look for errors. If cPanel failed to provision the service, an error would be shown in the logs.

I believe OpenSRS is currently in progress and scheduled for v3.2. Blesta supported OpenSRS before v3 with limited functionality.

Make a backup of your database, then drop the database tables, reinstall, and then import your previous database backup. However, without knowing what SQL errors you're experiencing, we can't determine whether that will fix anything. If your database is corrupt, missing records, fields, etc., or you made manual modifications, you will most-likely continue to have the same problems you're having now. The real solution is to fix the SQL errors.

Modules, like Logicboxes, won't provision unpaid services. However, you should be able to mark the invoice paid manually, and the service should be provisioned by cron shortly afterward. It sounds like, for whatever reason, the payment notification from PayPal is not making it to Blesta. You created another thread about having this issue, and that is likely where the problem lies. Check the gateway logs, and double-check your PayPal configuration settings (in PayPal) to make sure PayPal can and is sending data to your server running Blesta. You may want to also take a look at this thread.

Yes. Everything in v3.0.x will be in v3.1.x

I was able to duplicate this issue, and it looks like a couple minor issues worked together to cause it. When you assign a server to a server group with the cPanel module, you need to assign it from right to left. If you don't assign a server, the server group uses none, and would be unusable with packages. However, when you create a package, the "Server Group" field is initally "Any", which loads your cPanel server, and sets a valid value for the "cPanel Package" field. When you change to a specific "Server Group", the module options should reload using a server from that specific server group. But due to #1, if you do not have a server assigned to the group, a separate error occurs, preventing the AJAX request from completing. This, then, does not update the module option fields as it should, and so you are allowed to save your package with a "cPanel Package" unavailable to the server group. Because no module is actually being used (none are assigned to the group), you get a "No host defined" error when trying to create a service. This is now fixed in CORE-789 for v3.0.8.

Attached is the Payza gateway for Blesta. Special thanks to Kiran at Nirays Technologies for creating the gateway and giving us rights to it. We'll be including this gateway with v3.1 of Blesta. To install, you can upload the contents of the attached zip to your Blesta installation directory, and then head into Blesta's admin interface to install the gateway under [settings] -> [Payment Gateways] -> [Available]. Additional information on configuring the gateway is available in the gateway's documentation. payza.zip