Tyson

Sorry, I don't have Skype. The problem could be that the node has an ID of 0 and is not included, but I'm not certain. You can try to add another node in Proxmox and see if it appears in Blesta. You might double-check your Proxmox settings in Blesta to ensure they are accurate--[settings] -> [Modules] -> (click "Manage" next to Proxmox). The fact you don't have a module log regarding Proxmox is concerning, since a remote request will be made via the API to retrieve the nodes, and details on that request will be logged. The nodes should be automatically populated after you choose a Type from the Module Options section of the package. JavaScript will need to be enabled in your browser.

I believe the signature is set in the ticket reply by default. A predefined response would be appended to the ticket reply making it appear at the end. I think this behavior is normal for most cases, but may be inconvenient if you are using a signature, and would require you to move the text to a more appropriate place. When you click to add a predefined response, it can be added either at the beginning or end of the reply text, and we opted for the end. Without more information (such as adding a second step), we couldn't choose a particular place in the reply text to insert the predefined response.

The AJAX order form types use the fewest steps. There isn't going to be a way to take an order for a service, configure it, add any optional add-ons, their configuration, set a coupon (if any), choose a payment method, login, and submit the payment from a single step.

Check your Module Logs under [Tools] -> [Logs]. Click on the table row for the Proxmox entry and look at the raw Input and Output. What data is the Proxmox server sending to Blesta?

What you've described is normal behavior. There's no way to alter this behavior from the UI. You could update the source code to achieve what you'd like, though. Making a single contact the dedicated recipient of tickets could lead to some issues. The client (or an admin) can choose to disable a contact's access to tickets, or delete the contact altogether, and then the client may be unaware of those tickets. The client would still need to be involved as a fallback in case something like this happens since all tickets are opened on their behalf.

You can set packages like Web Design as an add-on package (using Package Groups) so customers can choose whether they want to include that add-on with their domain order. For the Universal Module, all that is required is the name of the product. All other fields are optional. If you do not need to be notified of the product being added/updated/etc., you can leave those fields blank.

The order ID wouldn't be available in service notifications. I think you'd want to reference the service ID, which is not included at the moment. See CORE-1698. You can include it and any other fields by updating the module yourself to pass it along--look into UniversalModule::sendNotification and UniversalModule::processPackage.

Events don't necessarily need to return much data. The invoice creation event, as you mentioned, only returns the invoice ID. Since a plugin will be listening for these events, they can query for any additional information they need. The invoice ID alone is sufficient to derive the invoice line items, customer information, etc. I agree that more events would be more beneficial all around. Hopefully more can be added soon.

I said all implying that the entirety of the event list is described in the documentation from the link above. And yes, we do plan to continue adding more events, such as on user authentication, as well as others that have been requested such as the thread you replied to and this one.

By tip, you mean a payment that Blesta will not use toward the payment of any invoices?

All of the events are described here.

cPanel Extended is a module. You will need to upload it to /components/modules/. The States & Countries plugin would, indeed, be uploaded to /plugins/. My guess is the directory structure of the files you uploaded is not what Blesta expects, so it is not able to show them in the UI. Check your files, make sure that the first directory in the module (e.g. /components/modules/cpanel) contains the class file for the module (e.g. /components/modules/cpanel/cpanel.php). Afterward, head into Blesta under [settings] -> [Modules] -> [Available] to see the new module. Click the "Install" button and you should be good to go.

See your other thread.

Blesta doesn't make individual authorizations/captures in its normal operation as it processes them both at once using a single charge option with the gateway. The system supports performing authorizations and captures, depending on the gateway, but would require you to perform them yourself (e.g. from a plugin).

Is it possible someone changed the order-id that Blesta stores, or that the domain TLD for that order was updated in LogicBoxes?

What were the errors?

The error is in regards to having no username. It may be that the username is pre-populated with the email address, but the email address is blank, and therefore the username is blank. The email address itself is validated separately, only after the user is created.

The system doesn't think there are any invoices to be auto-debited. Error reporting would only show you php errors if something had gone wrong with a task running. You can usually tell if something had gone wrong with the task if it starts running but does not complete successfully.

You would need to include your module logs so we can better understand what actually happened. It sounds like the client has two services, one for each of the domains. Blesta only renews the service(s) attached to an invoice that has been paid. Did you edit the renewal invoice for that service at all? If so, what did you change? It could also be possible that ResellerClub renewed the wrong domain for some reason, and we could only know whether that occurred by checking the module logs.

Disabling the cron for a particular task can be done either by 1) disabling the entire cron from your control panel such that the cron no longer automatically runs, or 2) disabling a specific cron task under the [settings] -> [Automation] page before it's scheduled to be run. In the latter case, when the cron runs automatically, it will not run the task you disabled. At this point, re-enable that task under [settings] -> [Automation] and immediately run the cron manually to view it's output. Running the cron an hour before the task is scheduled to run will not run the task. This is because it is not time to run the task yet per your Automation settings. If you disable the automation task, it cannot be run manually or automatically because it is disabled. Tasks run only if they are enabled, and only when they're scheduled to run. The exception to this is if the task failed to run at its scheduled time. Depending on the task, it may be run the next time the cron runs or it will have to wait until the next time it is scheduled to run.

I'd probably do this $now = date('c'); $days_ago = date('c', strtotime($now . ' -7 days')); $results = $this->Record->select(array('date_transaction')) ->select(array('IFNULL(SUM(amount),?' => 'daily_sale'), false) ->appendValues(0) ->from('transactions') ->where('date_transaction', '>=', $days_ago) ->where('date_transaction', '<=', $now) ->group(array('date_transaction')) ->fetchAll();

Thanks for the report. This is assigned CORE-1879. The error is meant to say that the action failed because the category contains articles that do not belong to any other categories. Each article must belong to a category, or you need to set the article to a category of "-- None --" instead.

So you have two config options, but only one of them must be selected? Such a dependency is not yet resolvable. Is it not possible to make both options available in the same config option? We are planning to add config option logic in the future that would allow you to do something like this, but I don't have an ETA on its completion.

There is no way to say that a config option is required/optional other than to create option values that cost money or are free.

Is this for Blesta?