Cody

CORE-562 slated for 3.2 will add an event to be triggered when a service's status is changed (i.e. suspended, unsuspend, canceled). That's probably what you're looking for.

This is intentional behavior.

Rotation Policy controls the amount of time to retain most log data, cron log being the exception as that is controlled by the Blesta.cron_log_retention_days configuration. Options that control what logs to delete can be found in the configuration. They include: Blesta.auto_delete_accountaccess_logs Blesta.auto_delete_contact_logs Blesta.auto_delete_email_logs Blesta.auto_delete_gateway_logs Blesta.auto_delete_module_logs Blesta.auto_delete_transaction_logs Blesta.auto_delete_user_logs

In 3.1: services.pricing_id -> package_pricing.id; package_pricing.pricing_id -> pricings.id; package_pricing.package_id -> packages.id There is a many to one relations between package_pricings and packages (e.g. a package can have many package_pricings). Where -> denotes functional dependency... (term, period, and service ID) -> (services.id, services.pricing_id, package_pricing.id, package_pricing.pricing_id, package_pricing.package_id, packages.id, pricings.id, pricings.term, pricings.period).

In 3.0: services.pricing_id -> package_pricing.id; package_pricing.package_id -> packages.id

Moved to feature requests.

You can add TLDs to the namecheap config under /components/modules/namecheap/config/namecheap.php. If you can provide documentation on namecheap supporting the TLDs you listed we'll update the module with them. EDIT: Found it: https://www.namecheap.com/domains/domain-pricing/by-type.aspx Added CORE-975 to update the list of supported TLDs.

Everything is available to you when editing an invoice template because invoice templates are PHP code. An example of how to view variable data in PHP: print_r($var_name); Within the context of an invoice template (e.g. /components/invoice_templates/default_invoice/default_invoice_pdf.php) public function drawInvoice() { print_r($this->invoice); print_r($this->meta); exit; } That data that is contained in $this->invoice is the same as returned from Invoices::get().

Alternatively, you could create the service and choose not to invoice it, or edit the invoice after it is created to remove the setup fee line item.

I would put in a feature request with Interworx to change this to UTF-8. 90+% of the web is UTF-8.

Start a new thread in the Bugs forums with steps to duplicate with items 1-6 from the How To Report A Bug thread.

Look in _custom.php, there are examples there, specifically on line 21.

Moved to support. It sounds like when you're adding a Contact Type you're checking Use Language Definition when the value for Name you're entering has no language definition. Just uncheck that box, or add the language term and definition to the _custom.php language file for each of your language packs. For info on creating language definitions see Translating Blesta.

Please see How to Report a Bug. We need information about your environment and detailed steps required to duplicate the issue.

Install a trial version of 3.1.0-b2 and try it out.

Here's the solution. In /plugins/import_manager/components/migrators/whmcs/whmcs_migrator.php change: if (version_compare(BLESTA_VERSION, "3.1.0", ">=")) { To: if (version_compare(BLESTA_VERSION, "3.1.0-b1", ">=")) { This fix will be included in 3.1.0 (CORE-969).

I've confirmed the issue and am working on a fix.

Version 3.1.0-b2 is now available. You can download it in the Client Area. This is a BETA feature release. This release is not considered stable enough for production use. Please report any bugs in the 3.1 beta bug forum. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes - Blesta Core - Version 3.1.0-b2 ## Version 3.1.0-b2 2014-01-08 ### Bug * [CORE-315] - DirectAdmin: Number of accounts on server does not change * [CORE-316] - cPanel: Number of accounts on server does not change * [CORE-317] - Interworx: Number of accounts on server does not change * [CORE-749] - Logicboxes: Manage tabs do not load due to undefined order-id when the service has not yet been created * [CORE-789] - cPanel Module: Servers within server groups produce a "no host defined" error. * [CORE-895] - Calling Accounts::add() without optional parameters causes undefined property error * [CORE-916] - Stripe: Undefined index error on invalid request * [CORE-930] - Managing a cancelled service allows fields to be updated * [CORE-946] - TheSSLStore: Referencing invalid property of object * [CORE-947] - Upgrade script SQL error in GUI * [CORE-948] - Undefined index 'pay_with' on Make Payment without any accepted payment types enabled * [CORE-950] - A minimum quantity of 0 is not allowed for configurable options. * [CORE-951] - Support Manager: Client replying to ticket does not change status from "Awaiting Reply" * [CORE-953] - Dashboard calendar date headings incorrect * [CORE-955] - Delete currency results in unknown column error * [CORE-956] - Support Manager: Client department list does not clear floats properly * [CORE-962] - Billing Overview: Incorrect start/end dates * [CORE-964] - Order plugin: Order form pagination links do not work ### Improvement * [CORE-655] - Email log shows no email content when an HTML copy is sent, but no text version was set * [CORE-874] - Order Plugin: Return error when attempting to transfer a blank domain * [CORE-954] - Support Manager: If reply contains only signature do not add reply * [CORE-965] - Log out clients who's status is not active. ### New Feature * [CORE-150] - Gateway: Payza (Formerly AlertPay) * [CORE-967] - Gateway: BitPay * [CORE-968] - Billing Overview Plugin: Yearly Revenue Graph not displaying graph when only January is available ---

I don't think the Universal Module should make that distinction, though, as it overly complicates things for the most part.

This might be something we can do by setting a checkbox next to each service field that you add.

What you can do (and I'd actually prefer this from a customer perspective), is update the invoice email template to send a unique link (unique for each client and invoice) to download the PDF that contains the time accounting report. See customizing emails for more details.

To request a quantity for something you need to have a module that supports quantity (like the Universal Module), or by creating a configurable option (available in 3.1). You can update the quantity stored in services.qty at any time, and the subsequent invoice will then use this updated quantity when billing the client.

To modify the way the invoice looks you have to create a new invoice template. Most of the rest of the text can simply be added as Terms on the invoice.

Sounds like you'd want a plugin that listens for the Invoices.add event, then looks up the invoice to check if any of the line items use the package that should be billed for daily usage, then append a line item to the invoice for the daily usage. The way I would make it work is create a base package for the base price (if there is no base price the price would be 0). Then create a restricted package that contains the daily price. No client would be subscribed to this package, it would simply be used to calculate the daily usage amount. Next, when the base service is invoiced your plugin would be notified and have the option to append a line item to the invoice for the daily usage. To recap: Plugin "listens" for Invoices.add event Plugin looks up invoice and checks line items for services that use the base package For all base package services, look up related daily usage package to obtain pricing Append line item to the invoice by setting qty to the number of days invoice covers, set amount to daily usage price

I am highly doubtful the migrator, which is designed for 5.2+, will work for version 4.x. WHMCS made a number of structural changes in 5.1 and 5.2, which will no doubt result in invalid queries on a version 4.x database. So while you might get some data out of it, it won't completely work without some changes. I don't know if WHMCS does a license validation check before upgrading, but you might be able to get away with it if you: Backup your WHMCS database Copy your WHMCS files to a new location Import your WHMCS database backup to a new database Update your WHMCS copy config to point to the new database Overwrite your WHMCS copy v4 files with the latest version of WHMCS Run the upgrade on your WHMCS copy Migrate from this (newly upgraded) database to Blesta You won't actually need to login to WHMCS backup copy you made, Blesta will simply import from this upgraded database.