Leaderboard

CORE-842 is fixed for 3.0.5.

The logicboxes module simplifies this by forcing all contacts to be natural persons/individuals only. That is, "es_form_juridica" is always "1".

Interesting. We'll take a look. Normally, yes, but this particular error throws an exception, which halts all further process for that particular batch. If you do as I suggested (edit line 818), it should continue processing services and skip those it can't find module row records for.

The only fields available for ES contacts (according to the logicboxes API docs) are: es_form_juridica es_tipo_identificacion es_identificacion If you can provide documentation outside of that we'll take a look, but from what I can tell the module fully implements the capabilities of the logicboxes API with respects to .es domains.

gotcha. Well I've got paul helping in a ticket now. So far I've determined it's not a firewall issue as I turned csf off completely and still happening. The search continues

My guess is you've got a lot of data. Seems like there's some correlation between a lot of data and this particular error given that you generally get about the same number of clients imported before the connection is reset. Try this. Update line 157 of whmcs_migrator.php: from: foreach ($this->WhmcsClients->get() as $client) { to: $clients = $this->WhmcsClients->get()->fetchAll(); foreach ($clients as $client) { This will, undoubtedly, require you to set your memory_limit in PHP to something very high (all dependent on how much data you have). But it's worth a shot.

This error hints at the importer not being able to determine the module row used for the service. Check to see that all of the modules were imported and all contain at least some data. If you can figure out the exact service that's attempted and triggers this error we might be able to investigate a little. Aside from that the only thing to do is to skip the service: Add the following to line 818 of /plugins/import_manager/components/migrators/whmcs/whmcs_migrator.php if (!$module_row_id) continue; These are just reflections of the original error above.

Next Marketing Buzz: Cloud Sprinkers! brought to you by Cody. Gotta love Pi's community and market share.

We have a roadmap but it's not public. We're working towards making our project management public, but we have to work out some permissions issues with items that we don't necessarily want to be public before we can do that. Step 1: Upgrade the system is complete.

The latest version of the import manager is included in the first post of this thread. Download it if you are running some version other than 1.0.3 of the import manager plugin. This plugin comes prepackaged with the WHMCS migrator, so no need to download that separately if you're upgrading the import manager. If you already have version 1.0.3 of the import manager plugin then simply download the WHMCS migrator as per the instructions. This update will display any errors encountered during the import process. Run it and report back any errors you receive.

Works great! Thank you.

Update to the import has been released. Get the latest version here.

It depends where you want to place the value in the PDF, but consider this example which places it below the "Due Date" field: Update /components/invoice_templates/default_invoice/default_invoice_pdf.php (line 402): private function drawInvoiceInfo() { $data = array( array( 'name'=>Language::_("DefaultInvoice.invoice_id_code", true), 'space'=>null, 'value'=>$this->invoice->id_code ), array( 'name'=>Language::_("DefaultInvoice.client_id_code", true), 'space'=>null, 'value'=>$this->invoice->client->id_code ), array( 'name'=>Language::_("DefaultInvoice.date_billed", true), 'space'=>null, 'value'=>date($this->invoice->client->settings['date_format'], strtotime($this->invoice->date_billed)) ), array( 'name'=>Language::_("DefaultInvoice.date_due", true), 'space'=>null, 'value'=>date($this->invoice->client->settings['date_format'], strtotime($this->invoice->date_due)) ) ); to private function drawInvoiceInfo() { $cf_data = array(); if (property_exists($this->invoice->client, "id")) { Loader::loadModels($this, array("Clients")); $field_id = 6; $values = $this->Clients->getCustomFieldValues($this->invoice->client->id); foreach ($values as $value) { if ($value->id == $field_id) { $cf_data = array( 'name' => $value->name . ":", 'space' => null, 'value' => $value->value ); break; } } unset($values, $value); } $data = array( array( 'name'=>Language::_("DefaultInvoice.invoice_id_code", true), 'space'=>null, 'value'=>$this->invoice->id_code ), array( 'name'=>Language::_("DefaultInvoice.client_id_code", true), 'space'=>null, 'value'=>$this->invoice->client->id_code ), array( 'name'=>Language::_("DefaultInvoice.date_billed", true), 'space'=>null, 'value'=>date($this->invoice->client->settings['date_format'], strtotime($this->invoice->date_billed)) ), array( 'name'=>Language::_("DefaultInvoice.date_due", true), 'space'=>null, 'value'=>date($this->invoice->client->settings['date_format'], strtotime($this->invoice->date_due)) ) ); if (!empty($cf_data)) $data[] = $cf_data; You need to update line 407 to set the integer to the correct custom field ID for your custom field. For example, if you go to edit the custom field in Blesta, the integer value will you're looking for appears at the end of the URL. Note that this is a core file in Blesta, and future patches/updates from us may overwrite this file, and you will need to merge these changes with any subsequent update accordingly.

No reason you can't do this yourself. Every time there is an update I add the patch to my version control which allows me to see what the diffs are as well as manage any conflicts.

CORE-824 is fixed in 3.0.5.