DandyDandy

Hi,

It would be great if you could maybe consider adding a basic internal knowledgebase so any admin/staff member can view for important internal information. It doesn't need to be all the features of the world but something where you can add a basic article or information piece for techs is great maybe also a basic ACL which prevents which admins/staff can edit, remove, add articles.

Knowledge Is Power

Which then checks it against the Google Maps API to ensure it is actually a valid address/street

Which then checks it against the Google Maps API to ensure it is actually a valid address/street

Hi,

It would be great if you could maybe consider adding a basic internal knowledgebase so any admin/staff member can view for important internal information. It doesn't need to be all the features of the world but something where you can add a basic article or information piece for techs is great maybe also a basic ACL which prevents which admins/staff can edit, remove, add articles.

Knowledge Is Power

Really appreciate the progress on this.  I know some people think an importer is their entitlement; however, having used competing billing systems importers or got into dialogue with the devs regarding one Blesta has been the best experience so far.

I've just gone back over this topic a couple of times and some of the posts are shocking me with the lack of patience and damn right rudeness some are displaying here I would like to remind people the WHMCS Migrator is still in "BETA" also seen those asking the same stuff which has been address previously I feel strongly the Blesta guys need to add a basic F.A.Q for those moving from WHMCS to Blesta.

Oh yes commonly referred to as "host hoppers" within the hosting industry.
I think the importer is great considering how much work it needs to do to even move the database let alone import it as well. I think adding some type of "verbose option" to the migrator will be good as it will display in verbose output which is "real time" what it is doing and which stage it's at. Also maybe consider adding some type of "option based" menu on the migrator in the future so those with bigger databases can migrate everything but tickets over first then re-run after to migrate the tickets solely this will prevent everything being done at once and hopefully would make the migration seem a little less painful to some.

Hi,

I write this because over recent weeks I have seen multiple people trying to run Blesta on one of the more latest PHP releases such as PHP 5.4 with the Suhosin PHP hardening patch applied. Because problems are happening with the setup they seem to be blaming Blesta for the issue when actually the issue is residing from the Suhosin PHP patch.

As I write Suhosin barely has support for PHP 5.4 and doesn't even currently support PHP 5.5 at all some providers are now starting to drop the usage of Suhosin and consider it a dead project because the development of the project is no longer moving forward to cater for the changes within PHP.

I can confirm that Blesta will happily run with Suhosin using PHP 5.3 alhough PHP 5.3 is now End Of Life security fixes will still be released into 2014 as they generally keep the security fixes coming for about 1 year once EOL status is declared.

Based on the current status of Suhosin moving forward I wouldn't recommend running it any further in production until it becomes a stable project again with regular releases to keep supporting more current PHP builds.

Am sure this will help those who are facing such issues.

Hi,

I write this because over recent weeks I have seen multiple people trying to run Blesta on one of the more latest PHP releases such as PHP 5.4 with the Suhosin PHP hardening patch applied. Because problems are happening with the setup they seem to be blaming Blesta for the issue when actually the issue is residing from the Suhosin PHP patch.

As I write Suhosin barely has support for PHP 5.4 and doesn't even currently support PHP 5.5 at all some providers are now starting to drop the usage of Suhosin and consider it a dead project because the development of the project is no longer moving forward to cater for the changes within PHP.

I can confirm that Blesta will happily run with Suhosin using PHP 5.3 alhough PHP 5.3 is now End Of Life security fixes will still be released into 2014 as they generally keep the security fixes coming for about 1 year once EOL status is declared.

Based on the current status of Suhosin moving forward I wouldn't recommend running it any further in production until it becomes a stable project again with regular releases to keep supporting more current PHP builds.

Am sure this will help those who are facing such issues.

This means one of your clients or admin users is missing an entry to there last name within your WHMCS installation.
It would be better if this error was changed to "Please review your WHMCS installation for any users or administrators missing a last name entry"