Paul

These would be good feature requests, and I would just move the thread but it's better if there's 1 request per thread.

Looking really good, thanks for sharing and glad you're happy with what we've done!

We don't mind.

I would do a backup of the database after you do a fresh install. Then, you can just restore the database without having to do a whole new install.

Please provide steps so that we can try to duplicate the issue.

I think this is a result of a missing mbstring extension. If you install mbstring in your php, it should resolve it. I have assigned this to CORE-680 as I don't think we want mbstring to be a system requirement. If we have to use it we may have to check for it before allowing GeoIP to be enabled.

i'm not sure this is a bug, Blesta is attempting to use the language define to display the language, which is the intended purpose except that a language define does not exist.

Try this.. Try the following to enable debugging during import. Then attempt to import again. Open /config/blesta.php and change (line 11): Configure::errorReporting(0); to Configure::errorReporting(-1); Then open /plugins/import_managers/components/migrators/blesta/2.5/blesta2_5.php and change (lines 199-201): //echo $e->getMessage(); //echo $e->getTraceAsString(); //continue; to: echo $e->getMessage(); echo $e->getTraceAsString(); die;

If someone answers, and their answer provides a resolution to the OPs question then mark it as solved. This helps other people who may be searching for a similar issue.

We'll post it as soon as there is something to test. I don't have an ETA yet, we've been fixing any bugs that have surfaced this week and are preparing to release a patch sometime next week.

suPHP is not a requirement, but it does eliminate many permissions issues. Still, I'd like determine the cause for what he is experiencing so we can debug it and implement a fix.

I'm guessing this was not compiled with suPHP? Just to be clear.. 1. Before install, you set the config directory to 777, and blesta-new.php to 666. 2. After you attempt to install it renames blesta-new.php to blesta.php but doesn't do tag replacement on database variables Question: What are the permissions of blesta.php after it is renamed? Is it still 666 or something else? If it's not writable by the web server at that point, my guess is that it may rename the file first and then attempt to do the variable replacements but it can't because it's no longer writable. If this is what's happening, we should be able to look into a fix. Can you confirm?

At this point I'm not too concerned about it, most licenses are unbranded since only orders after the 14th could be branded.

Yeah, that's why. In the past people have purchased a single license and installed dozens in sub-directories for their clients to use.

We may have it automatically remove branding on unbranded licenses in the future.

It looks like they may have written the modules for the other billing apps. I wonder if anyone has asked them for Blesta support? If they built these other integrations, they may be interested in doing so for Blesta as well.

Thanks for the tip!

I have assigned this to CORE-676, tentatively scheduled for 3.1.

Pretty cool video, and I'd like to go.. make a vacation out of it in New Orleans but it's not going to happen this year.

I think Cody is using a browser he created in the middle of the night at home, because he doesn't sleep. Doesn't need to, he's that awesome.

Both licenses will remain active, though most people probably won't use v2.5 after they finish migrating. We are working on an importer for you.

GoGetSSL is assigned to CORE-466 in our system, however we don't have an ETA for it. There are a lot of modules in the works and we are prioritizing them as best as we can by demand.

Please see How to report a bug - http://www.blesta.com/forums/index.php?/topic/738-read-first-how-to-report-a-bug/

We ran into an issue where if badly formatted characters were returned from GeoIP the widget would not load. We did implement a fix, but I wonder if it's related but different. I would go to Tools > Logs > User Logins and see if everything looks good there.

Just to follow up on this, as far as I'm aware LP has issued all keys. If anyone else is seeing this and hasn't received a key, or has a monthly license with LP or with us we are recommending downloading v3 and selecting the "Free 30-day Trial" during installation. This will get you up and running immediately and you can enter your final key once it's issued.