Paul

We stopped shipping Blesta with Google Checkout. We have not implemented a Google Wallet gateway, as some have reported that Google was not friendly to accepting payments for hosting providers.

I added an info box toward the bottom above the currency listings for Bitpay in the documentation here - http://docs.blesta.com/display/user/Bitpay

That looks really nice, you should start a new thread and include the theme export file when you're happy with it.

I can't understand any of the language, but it looks really good!

I recommend using your native currency, not BTC.. Bitpay will convert it to bitcoin.

Nice work!

I don't believe it is a bug, but rather how the prices needed to be imported in order to maintain the same prices each customer was paying for each domain/TLD. Similar behavior occurs when importing from a competitor which is definitely expected, however it's possible that it could be a bug. Cody would know more on this. Still, the safest bet is to mark the package as inactive and create new packages. 3.x handles domains differently anyway, so this is preferable for more reasons than just this.

looking good!

My suggestion is to make this package "Inactive", then create a new package for it and sell new domains with the new package. Since the pricing options are all associated with a service, this is the simplest way to go. EDIT: Clients will still be billed when using an inactive package, so there's nothing to worry about by doing this.

It's included in the blesta-3.2.0.zip file, look for the hotfix-php5.5 directory, and overwrite your files with those in the hotfix directory.

You should definitely enter!

The license is valid and eligible for transfer.

The ability to modify countries does not currently exist in the UI. As you noticed, we plan to support it in the future but it's low priority. A plugin would work really well for this!

Tell your friends! We may have to extend the contest if there are not enough entries.

Looking good! I wonder how a cloud with a slider in it would look. A lot of people like to use sliders to select VPS packages, sliding to the right to get more resources.

Yeah, it looks like you may not have overwritten the files from the 3.2.0 build. Try downloading it to your computer, unpacking it, and uploading it via SFTP or FTP, being sure to overwrite the existing files. Then, try running the upgrader again.

That looks pretty awesome! Nice work!

Your database credentials for your Blesta 2.5 database may not be correct. packages.p_id refers to the packages table in Blesta 2.5, so it's unable to connect to that field, because it can't connect to the database, or the column doesn't exist for some reason. Check your Blesta 2.5 database, is there a packages table with a p_id column?

When you invoice daily and bill say 5 days in advance, it will actually create multiple invoices right away to "catch up". Not necessarily at the time of order, but I think the following day. For example, today is the 18th and say I bill 5 days in advance. Normally services that renew on the 23rd are invoiced today. So, an invoice would be generated on the 18th, 19th, 20th, etc to the 23rd (which is 5 days). Then after that, just 1 invoice per day will be generated. It has to catch up since you bill so many days in advance.

It may not be loading the javascript

We may add third party two factor services in the future, but we went through the effort to create our own TOTP and MOTP libraries based on the open standards because a self contained system is by nature more secure.. plus, it's free. Perhaps a more modular system, by which third party developers can create different OTP options, and drop them into Blesta would be ideal. There will undoubtedly be more and more options available over time.

That's correct. Most people will set term to 1, and period to month. Some people may prefer to bill every 30 days instead of 1 month, so with our flexible options that is possible. But, if you want to invoice the customer daily, you can certainly do so -- they might not be very happy about that though. When creating a package, you can also set the option Cancel at end of term. This option will automatically cancel any services created from the package after the end of the term ordered.

Have you had a trial on that subdomain before? Not sure why it would give an error, but since Softaculous installs with a trial key, if you already had a trial key for that hostname it would cause Blesta to prompt you to enter a valid key. That shouldn't create an error in Softaculous though I don't think. Have you tried contacting their support? I do see quite a few trial licenses issued through Softaculous today and yesterday that activated fine, so it probably doesn't affect everyone. Interesting.

Doesn't sound like a Blesta error, anyone else having trouble installing 3.2 through Softaculous?

I think it's better if they don't look identical, because then you can easily tell which is the staff and which is client areas.