Cody

Really not sure how you could get that. You should only get the unknown status if the local license data can not be decrypted.
 
When you receive the unknown status, what do you have stored for the license data on the client side? It should be the same data both before and after the client changes location before the next call home.

That is the desired behavior of the License Module. The license_module_status field will only contain "reissue" if the license is in a reissue state. If not in a reissue state, then it contains no data.

I think you are referring to LicenseManager::validate() on line 155 of license_manager.php. That method only returns a status of unknown if no license data is given, or the license data signature is invalid.

The expired status will only be provided if the last call-home is date is more than $ttl seconds past. Where $ttl is passed into LicenseManager::validate().
 
You'll only receive a suspended status if the service for the license is suspended in Blesta, and the client makes a call-home to fetch this update. This is one reason why you should perform at least a daily call-home.
 
The invalid_location status is given if the IP, path, or domain of the client no longer matches the value stored in the encrypted license data stored on the client.

I see the issue.
 
In some cases LicenseManager::decryptData can't decrypt the data, so it returns null. When null is unserialized it returns boolean false.
 
Added CORE-1643.
 
We'll work on a fix. Thanks!

I see the issue.
 
In some cases LicenseManager::decryptData can't decrypt the data, so it returns null. When null is unserialized it returns boolean false.
 
Added CORE-1643.
 
We'll work on a fix. Thanks!

That is the desired behavior of the License Module. The license_module_status field will only contain "reissue" if the license is in a reissue state. If not in a reissue state, then it contains no data.

I think you are referring to LicenseManager::validate() on line 155 of license_manager.php. That method only returns a status of unknown if no license data is given, or the license data signature is invalid.

The expired status will only be provided if the last call-home is date is more than $ttl seconds past. Where $ttl is passed into LicenseManager::validate().
 
You'll only receive a suspended status if the service for the license is suspended in Blesta, and the client makes a call-home to fetch this update. This is one reason why you should perform at least a daily call-home.
 
The invalid_location status is given if the IP, path, or domain of the client no longer matches the value stored in the encrypted license data stored on the client.

At any rate, should be a moot issue when Blesta 4 comes out.

In all likelihood it would be completely provider agnostic. You'd simply enter the authentication URL for each of the providers you wish to support, or perhaps check boxes from a set of supported (e.g. tested) ones.

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

This is a patch release that corrects issues with 3.4.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.4.3.

See all Change Logs.

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

This is a patch release that corrects issues with 3.4.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.4.3.

See all Change Logs.

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

This is a patch release that corrects issues with 3.4.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.4.3.

See all Change Logs.

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

This is a patch release that corrects issues with 3.4.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.4.3.

See all Change Logs.

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

This is a patch release that corrects issues with 3.4.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.4.3.

See all Change Logs.

Simplest option is to add a few settings under "Display on Invoice" in [settings] > [Company] > [billing/Payment]:
 
[ x ] Date Due for Drafts
[ x ] Date Due for Standard Invoices
[ x ] Date Due for Pro forma Invoices

Simplest option is to add a few settings under "Display on Invoice" in [settings] > [Company] > [billing/Payment]:
 
[ x ] Date Due for Drafts
[ x ] Date Due for Standard Invoices
[ x ] Date Due for Pro forma Invoices

Simplest option is to add a few settings under "Display on Invoice" in [settings] > [Company] > [billing/Payment]:
 
[ x ] Date Due for Drafts
[ x ] Date Due for Standard Invoices
[ x ] Date Due for Pro forma Invoices

I wouldn't suggest putting much effort in modifying the admin interface. Since it sees so much activity each release, it will be a pain to keep up to date.

My guess is there was whitespace in the username somewhere, which you failed to enter during the login attempt. Blesta doesn't care if you use numbers, letters, symbols, or any combinations of those.

If you want a 2-digit year just change the invoice format:
 
FA15{month}A{num}
 
Yes you have to update it manually each year, but that's much easier and safer than modifying files.
 
As for zero padding. That's something we want to do. If that's truly some sort of EU compliance requirement, and you can document it as such, we'd be much more inclined to push that to the top of our queue.

If you want a 2-digit year just change the invoice format:
 
FA15{month}A{num}
 
Yes you have to update it manually each year, but that's much easier and safer than modifying files.
 
As for zero padding. That's something we want to do. If that's truly some sort of EU compliance requirement, and you can document it as such, we'd be much more inclined to push that to the top of our queue.

Well, you can't even install Blesta without phpseclib working correctly, so I don't think that an additional check in the installer is necessary. The error displayed in that case is actually quite specific. Moreover, the issue is not with CentOS per se, as we have dozens of installs of CentOS and this is not an isuse for any one of those.
 
 
Just because php can't find a particular resource being requested on the include path doesn't mean the php.ini file is configured incorrectly. While it may be the issue if you are running exactly CentOS 6.5 with php 5.4 and nginx, it is not definitively the reason.
Also, CentOS 7 has been out for quite a while, has anyone been able to duplicate there? We haven't, just FYI.

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

This is a patch release that corrects issues with 3.4.0.

Patching Blesta

See Patching Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 3.4.2.

See all Change Logs.