Tyson

Could you provide the settings set for that coupon? Was the service updated before it renewed to add a new coupon? Was the service ever upgraded before it was renewed? Was the service renewed manually or by cron?

Changing the prices on the order form wouldn't affect the pricing that is used when the invoice is created. The order form just shows what a service should cost, in order to show it to the customer. It cannot specify override pricing itself. For something like this to work, it would need to either work as Paul described, or additional support needs to be integrated that allows you to specify which clients have override pricing for which packages (however that would be designed), and the rest of the system would need to observe that. It wouldn't be a simple change to get something like this to work properly.

There seems to be confusion on what the username affects. On an order form, when a customer is asked to register for an account, that is for a client account in Blesta--not for cPanel. When ordering a cPanel package from the order form, a customer is only asked for a domain. The cPanel username and password is automatically generated and created in cPanel if it does not already exist. If you're having trouble getting a cPanel service to be synced up in Blesta, try adding the service as an admin from a test client you have in the system. Click the Add Service link as shown in this screenshot under Actions on the left. You can set it to "Do not invoice" for the service, and then create it. The service should be provisioned immediately, and appear as an "Active" service in Blesta. If that occurs, then your cPanel settings are correct. In that case, the issue you're probably having is that the orders from the order form are set to require manual approval, and you simply have not manually approved them yet, as Paul mentioned earlier.

There is currently no event triggered when a package is created, so no plugin could be notified of the package creation.

With the way pricing is structured, I don't see a way for a plugin to force a package to be charged for a different price than it has set.

The change I suggested is relevant to your first screenshot. There are several other places in order plugin where the tax percent may still show to four decimals.

Config options will adjust based on package/term in v3.5.

The tax rate isn't formatted much on the order form, and is always shown out to 4 decimal places. In the future, we will likely update this to show only the significant digits. However, changing this yourself would require you to update the template files where the tax rate is displayed. For example, the tax rate on the AJAX order template could be changed by updating /plugins/order/views/templates/ajax/summary.pdt in your Blesta installation by finding: <td><?php $this->_("Summary.index.totals.tax", false, $tax['name'], $tax['percentage']);?></td> and updating it to <td><?php $this->_("Summary.index.totals.tax", false, $tax['name'], $tax['percentage'] + 0);?></td>

Where are you trying to sort packages? Packages on the order form are shown within their package group. Packages within a package group can be sorted in the admin interface under [Packages] -> [Groups], clicking a package group table row, and clicking+dragging the package table rows around relative to each other. Sorting the packages by price may not be working because of your comparison function. It is best if the comparison function return an integer of 3 possible values: -1 ($a > $, 0 ($a == $, or 1 ($a < $

I'm going to move this to the Support forum. You're not able to use a coupon at /order/config/ because that functionality is only available since v3.5.0, which is yet to be released. It will be available to everyone during the upcoming beta.

You said you removed autodebit from those clients? You can either set autodebit to 'disabled' on their profile page, or remove the payment account from being their autodebit payment account. Blesta doesn't charge for a paid invoice via cron. Neither does it autodebit a client whose autodebit status is disabled. So it sounds like something else is going on, such as a separate Blesta install with a cron job still setup, or perhaps Stripe is setup to autodebit a card it has on file for a specific amount each month. I don't think Stripe supports that functionality (does it?). Since a transaction is not created in Blesta when an autodebit payment is processed, the gateway either cannot respond to Blesta in order to process the payment (check the gateway logs), or its responding to a different Blesta installation altogether.

I will upgrade from win7 if I can get < 2 BSODs/day.

The root web directory is expected to be the system's root web directory, not Blesta's installed web directory. The cron needs to know this information, for example, to properly generate URL's used in email templates. If the value is incorrect, links in emails may not be valid either. You should check emails sent automatically by cron to make sure the links are working properly.

The Root Web Directory setting is configurable through the admin interrface under [settings] -> [system] -> [General]. No need to manually edit the database.

How was the invoice created? I see the bill date is the same as the due date, which is usually the case when manually adding a new service.

Yes. Once your support and updates is current, you can upgrade to any version we release until your yearly support and updates expires. If the support and updates expire, you cannot upgrade to a new major/minor version, but you can still apply patch (bug fix) releases for the current minor release you are using.

Both sub nav items should appear. You may need to reinstall the plugin from the admin interface to get the links to be added again. Plugins set links when the plugin is installed or upgraded. If you change the links in the plugin without then installing or upgrading the plugin, they won't appear.

The module enforces an 8 character username limit as described in the docs. You may be able to support up to 16 character usernames if 'database prefixes are disabled'. You can update the module to increase the character limit to 16 if you'd like. Open /components/modules/cpanel/cpanel.php and find: 'rule' => array("betweenLength", 1, 8), Change it to 'rule' => array("betweenLength", 1, 16), and try adding the service in Blesta again.

The module always logs a success result for requests (Input). Responses from cPanel (Output) may not result in success. If you don't receive a response, then you may have a log with an Input value but no corresponding Output. The error check you removed from the module appears to be accurate. Blesta is unable to communicate with the server, or the credentials are incorrect. Make sure that the server Blesta is installed on meets the system requirements. If no outbound connections are being attempted, make sure you have curl available to php. If you're still not able to find out where the problem lies, you can check if the module is throwing an exception. You will need to add a line of code to the module. Open /components/modules/cpanel/cpanel.php and find: $this->log($module_row->meta->host_name . "|listpkgs", null, "input", true); Just below that is a catch statement: catch (Exception $e) { // API request failed } Update it to log the exception message: catch (Exception $e) { // API request failed $this->log($module_row->meta->host_name, $e->getMessage() . " \n\n" . $e->getTraceAsString(), "output", false); } Then go to add/edit a cPanel package in Blesta. A request will be made to fetch the packages from cPanel. If an exception is thrown by the module, the module will now log an entry into the Module Logs table under [Tools] -> [Logs] that should give more insight into the problem.

There is a nested conditional with else statements for each of them. {% if autodebit %} {% if invoice.autodebit_date_formatted %} Auto debit is enabled for your account, so we'll automatically process the card you have on file on {invoice.autodebit_date_formatted} unless payment has been applied sooner. {% else %} If you would like us to automatically charge your card, please log in to your account at http://{client_url} to set up auto debit. {% endif %} {% else %} If you would like us to automatically charge your card, please log in to your account at https://{client_url} to set up auto debit. {% endif %} It sounds like you removed more than just that else statement. There is no endfor tag in the template you included, so it may be an error caused somewhere else, or due to broken syntax (e.g. missing endif). Examples in the docs.

I've added a language to the translator for Taiwan that you can use for translating Chinese Traditional.

I'm not sure what you're asking. My example included 2 sub nav links that link to the methods "subnav1()" and "subnav2()" that you have created in your controller: AplicacaoCliente::subnav1() and AplicacaoCliente::subnav2()

Something like this: public function getActions(){ return array( array( 'action' => "nav_primary_staff", 'uri' => "plugin/pagamento/aplicacao_cliente/", 'name' => "Pagamento", 'options' => array( 'sub' => array( array( 'uri' => "plugin/pagamento/aplicacao_cliente/subnav1/", 'name' => "Sub Nav 1" ), array( 'uri' => "plugin/pagamento/aplicacao_cliente/subnav2/", 'name' => "Sub Nav 2" ), ) ) ) ); }

There is no mechanism to import multiple accounts into Blesta at once. However, you can link up existing cPanel accounts with a new service you create in Blesta. You will need to make sure that you have setup the cPanel module properly, and created a Package for the cPanel service. Then create a new service for a client, and ensure that you uncheck the checkbox "Provision using the cPanel module". This will only add the service to Blesta, and will not attempt to provision it with cPanel (since it already exists). Domains should be handled through a registrar (e.g. eNom, LogicBoxes). We have modules for some registrars, and you would set them up similar to other services. i.e., setup the module, create a package based on that module, and then create services for clients. If we don't have a module for a registrar you use, you could either create one, or use the Universal Module instead, and setup any orders you receive manually. If you want customers to order domains from an order form, you may want to install the Order plugin, if it's not installed already, and create a new order form of the "Domain and Other" type. Order Forms can be managed under [Packages] -> [Order Forms] in Blesta. You may want to read up on how to create a package, adding services, and creating an order form.

You can take a look at this thread for an explanation on why the URLs are structured as they are. Essentially, the structure is in its most logical form, and reducing it to a shorter URL as you described could lead to conflicts with other aspects of the system, or to the plugin itself if you were to create arbitrary routes or incorrect overrides. I think for something like this to work effectively, a route manager would need to exist that allowed for the definition of custom simplified URLs, and every link in the system would need to be updated to use it.