Cody

These can also be added to Blesta as Custom Reports, which is super cool, and would even allow you to customize them across dates or status values, etc.

You could create race conditions. Each PHP process is spun off in a new thread, so there's no guarantee one finishes before the next is requested. This is especially problematic when a task performs operations that result in the PHP process blocking for IO, such as processing payments, or receiving email. If you were to do this, you would need to verify that the task ended before starting up the next.

1 minute cron jobs are a bad idea. It's too easy for them to pile up and execute on top of each other.
 
If the point is to pull email from SMTP/IMAP server in near real time, create a script that runs constantly and polls the SMTP/IMAP server every 30 to 60 seconds.
 
For example:
<?php while (true) { $window = 60; $start = microtime(true); // TODO: do stuff $runtime = microtime(true) - $start; // wait until we can run again... sleep(max(0, (int) $window - $runtime)); }

Version 3.6.1 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.6.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.6.1.

See all Change Logs.

Version 3.6.1 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.6.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.6.1.

See all Change Logs.

Version 3.6.1 is now available. You can download it in the Client Area.

This is a patch release that corrects issues with 3.6.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.6.1.

See all Change Logs.

Version 3.6.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.6 beta bug forum.

Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.6.0-b2.

For older releases see all Change Logs.

Version 3.6.0 is now available. You can download it in the Client Area.

Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Migrating to Blesta

See Migrating to Blesta in the User Manual for instructions.
 
Overview
New Gateways: Converge (aka VirtualMerchant), and Braintree Payment types can be designated as non-income Automatically set Payment Accounts for auto-debit when saved Improved performance of Invoice and Transaction searches Added ability to invoice each service independently Added ability to mass schedule cancellation of services Show invoice line items on client pay page when paying a single invoice Much more... Release Notes

See Blesta Core - Version 3.6.0.

For older releases see all Change Logs.

Version 3.6.0 is now available. You can download it in the Client Area.

Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Migrating to Blesta

See Migrating to Blesta in the User Manual for instructions.
 
Overview
New Gateways: Converge (aka VirtualMerchant), and Braintree Payment types can be designated as non-income Automatically set Payment Accounts for auto-debit when saved Improved performance of Invoice and Transaction searches Added ability to invoice each service independently Added ability to mass schedule cancellation of services Show invoice line items on client pay page when paying a single invoice Much more... Release Notes

See Blesta Core - Version 3.6.0.

For older releases see all Change Logs.

Relates to CORE-1008

Version 3.6.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.6 beta bug forum.

Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.6.0-b2.

For older releases see all Change Logs.

Not a bug, but would make a good feature request.

As soon as it's ready.

As soon as it's ready.

You should be using
$api->post('clients', 'create', $vars); But aside from that, the 'Failed to retrieve the default value' error is the result of a bug in ionCube. I've never seen it happen in a non-encoding file, though. So it must be calling something in AppModel which is encoded. I hate ionCube so much.

You should be using
$api->post('clients', 'create', $vars); But aside from that, the 'Failed to retrieve the default value' error is the result of a bug in ionCube. I've never seen it happen in a non-encoding file, though. So it must be calling something in AppModel which is encoded. I hate ionCube so much.

This plugin doesn't send any emails. It only schedules the cancellation. Blesta doesn't send any email when service cancellations are processed.

As soon as it's ready.

Version 3.6.0-b1 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.6 beta bug forum.

Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.6.0-b1.

For older releases see all Change Logs.

One problem I think we'll have is determining which subdivisions to include in countries that have multiple levels of subdivisions. For example, GB's first level is country, of which there are 3 (England, Wales, and Scotland). Obviously we can't just include those three, we have to dig deeper. However, that's not necessarily the case for other countries.
 
I don't believe there is an automated way of determining that, which is probably why we included all subdivisions, rather than to exclude some. This is also probably why there are no correct complete data sets available. Even ISO doesn't identify which subdivisions are in common use within a country.

Here's what our data provider has for ISO 3166-2 for Morocco:
 
3166-1 3166-2 name MA AGD Agadir Ida-Outanane MA AOU Aousserd MA ASZ Assa-Zag MA AZI Azilal MA BEM Beni Mellal MA BER Berkane MA BES Ben Slimane MA BOD Boujdour MA BOM Boulmane MA CAS Casablanca MA CHE Chefchaouen MA CHI Chichaoua MA CHT Chtouka-Aït Baha MA ERR Errachidia MA ESI Essaouira MA ESM Es-Semara MA FAH Fahs-Beni Makada MA FES Fès-Dar-Dbibegh MA FIG Figuig MA GUE Guelmim MA HAJ El Hajeb MA HAO Al Haouz MA HOC Al-Hoceima MA IFR Ifrane MA INE Inezgane-Aït Melloul MA JDI El Jadida MA JRA Jerada MA KEN Kénitra MA KES Kelâat Es-Sraghna MA KHE Khémisset MA KHN Khénifra MA KHO Khouribga MA LAA Laâyoune MA LAR Larache MA MED Médiouna MA MEK Meknès MA MMD Marrakech-Médina MA MMN Marrakech-Ménara MA MOH Mohammédia MA MOU Moulay Yacoub MA NAD Nador MA NOU Nouaceur MA OUA Ouarzazate MA OUD Oued Ed-Dahab-Lagouira MA OUJ Oujda-Angad MA RAB Rabat MA SAF Safi MA SAL Salé MA SEF Sefrou MA SET Settat MA SIK Sidi Kacem MA SKH Skhirat-Témara MA SYB Sidi Youssef Ben Ali MA TAI Taourirt MA TAO Taounate MA TAR Taroudant MA TAT Tata MA TAZ Taza MA TET Tétouan MA TIZ Tiznit MA TNG Tanger-Asilah MA TNT Tan-Tan MA ZAG Zagora 3166-1 3166-2 name MA 1 Tanger-Tetouan MA 2 Gharb-Chrarda-Beni Hssen MA 3 Taza-Al Hoceima-Taounate MA 4 L'Oriental MA 5 Fes-Boulemane MA 6 Meknes-Tafilalet MA 7 Rabat-Salé-Zemmour-Zaer MA 8 Grand Casablanca MA 9 Chaouia-Ouardigh MA 10 Doukkala-Abda MA 11 Marrakech-Tensift-Al Haouz MA 12 Tadla-Azilal MA 13 Souss-Massa-Draa MA 14 Guelmim-Es Smar MA 15 Laayoune-Boujdour-Sakia El Hamra MA 16 Oued ed Dahab-Lagouira MA AGD Agadir-Ida-Outanane MA AOU Aousserd MA ASZ Assa-Zag MA AZI Azilal MA BEM Beni Mellal MA BER Berkane MA BES Ben Slimane MA BOD Boujdour MA BOM Boulemane MA CAS Casablanca [Dar el Beïda]* MA CHE Chefchaouen MA CHI Chichaoua MA CHT Chtouka-Ait Baha MA ERR Errachidia MA ESI Essaouira MA ESM Es Smara MA FAH Fahs-Beni Makada MA FES Fès-Dar-Dbibegh MA FIG Figuig MA GUE Guelmim MA HAJ El Hajeb MA HAO Al Haouz MA HOC Al Hoceïma MA IFR Ifrane MA INE Inezgane-Ait Melloul MA JDI El Jadida MA JRA Jrada MA KEN Kénitra MA KES Kelaat es Sraghna MA KHE Khemisset MA KHN Khenifra MA KHO Khouribga MA LAA Laâyoune* MA LAR Larache MA MED Mediouna MA MEK Meknès MA MMD Marrakech-Medina MA MMN Marrakech-Menara MA MOH Mohammadia MA MOU Moulay Yacoub MA NAD Nador MA NOU Nouaceur MA OUA Ouarzazate MA OUD Oued ed Dahab MA OUJ Oujda* MA RAB Rabat MA SAF Safi MA SAL Connaught Salé MA SEF Sefrou MA SET Settat MA SIK Sidi Kacem MA SKH Skhirate-Témara MA SYB Sidi Youssef Ben Ali MA TAI Taourirt MA TAO Taounate MA TAR Taroudant MA TAT Tata MA TAZ Taza MA TIZ Tiznit MA TNG Tanger-Assilah MA TNT Tan-Tan MA ZAG Zagora I think we may need to find a different data source, possibly directly from ISO, because the information does not appear to be correct.

@naja7host, why do you rely on modifying the core? You can easily create a new invoice template and simply extend the original template, without having to write much code.
 
/components/invoice_templates/custom_invoice/custom_invoice_pdf.php
<?php require_once '../default_invoice/default_invoice_pdf.php'; CustomInvoicePdf extends DefaultInvoicePdf {} /components/invoice_templates/custom_invoice/custom_invoice.php
<?php require_once '../default_invoice/default_invoice.php'; require_once 'customer_invoice_pdf.php'; CustomInvoice extends DefaultInvoice {     public function __construct() { parent::__construct(); Language::loadLang("custom_invoice", null, dirname(__FILE__) . DS . "language" . DS); }     public function setMeta($meta) { parent::setMeta($meta);                  // Load different language for this template if given         if (isset($meta['language']))             Language::loadLang("custom_invoice", $meta['language'], dirname(__FILE__) . DS . "language" . DS);         $this->pdf = new CustomInvoicePdf("P", "px", $this->meta['paper_size'], true, 'UTF-8', false, $font);                  // Set the meta data to use for this invoice         $this->pdf->meta = $this->meta;     } } Then just supply your own custom language file, you can even extend the language:
 
/components/invoice_templates/custom_invoice/language/en_us/custom_invoice.php
<?php $lang['DefaultInvoice.invoice_id_code'] = "Number:"; $lang['DefaultInvoice.date_billed'] = "Date:";

@naja7host, why do you rely on modifying the core? You can easily create a new invoice template and simply extend the original template, without having to write much code.
 
/components/invoice_templates/custom_invoice/custom_invoice_pdf.php
<?php require_once '../default_invoice/default_invoice_pdf.php'; CustomInvoicePdf extends DefaultInvoicePdf {} /components/invoice_templates/custom_invoice/custom_invoice.php
<?php require_once '../default_invoice/default_invoice.php'; require_once 'customer_invoice_pdf.php'; CustomInvoice extends DefaultInvoice {     public function __construct() { parent::__construct(); Language::loadLang("custom_invoice", null, dirname(__FILE__) . DS . "language" . DS); }     public function setMeta($meta) { parent::setMeta($meta);                  // Load different language for this template if given         if (isset($meta['language']))             Language::loadLang("custom_invoice", $meta['language'], dirname(__FILE__) . DS . "language" . DS);         $this->pdf = new CustomInvoicePdf("P", "px", $this->meta['paper_size'], true, 'UTF-8', false, $font);                  // Set the meta data to use for this invoice         $this->pdf->meta = $this->meta;     } } Then just supply your own custom language file, you can even extend the language:
 
/components/invoice_templates/custom_invoice/language/en_us/custom_invoice.php
<?php $lang['DefaultInvoice.invoice_id_code'] = "Number:"; $lang['DefaultInvoice.date_billed'] = "Date:";

Blesta makes no distinction between a page refresh and visiting a separate page. Your browser probably received the HTTP 403 header and loaded from the cache instead.

This could be accomplished with a plugin. For users being a proxy, it would require reliance on the X-Forwarderd-For header (which we are looking to support in a future version). But I think two-factor authentication is a much better solution that IP restriction.