Leaderboard

If you're looking to have an extension developed, email Eric. We've talked with him, and taken a look at some of his work and you can't beat his pricing. He has real experience building extensions for Blesta and we feel comfortable recommending him.

Looks like a solution now exists: http://www.blesta.com/forums/index.php?/topic/1898-multi-company-login/

Blesta uses the JSON API when communicating with cPanel. This is the preferred method according to cPanel. From: http://docs.cpanel.net/twiki/bin/view/SoftwareDevelopmentKit/XmlApi I would suggest you point your host to this and tell them to enable JSON API support. I'm actually amazed it can be disabled.

Why not just use $_SERVER['HTTP_X_FORWARDED_FOR'], as that is the variable for the X-Forwarded-For header and requires no user configuration in Blesta?

Part of being "Visible to Client" means that they should see it. The distinction that they should not see it on the client registration order form if it is disabled may not be what most people expect. I'd be curious to hear what people think about this, or if it's preferred to have a new setting to make that distinction. I'd recommend opening a feature request for this. As for the original bug report, I'm going to close this thread as not a bug.

I thought we would have had something there. It certainly worked for me at least. If you can provide a Blesta admin account and FTP access to update the cPanel module, I can take a look.

To debug update /plugins/import_manager/components/migrators/blesta/2.5/blesta2_5.php. From: //echo $e->getMessage(); //echo $e->getTraceAsString(); To: echo $e->getMessage(); echo $e->getTraceAsString(); die; Then rerun the import on a fresh version 3 database. Paste all of the output here.

This will require some work for sure, but I already have an idea on how to handle this. I'll create the test scenario today and start work on it.