Paul
-
Posts
6,687 -
Joined
-
Last visited
-
Days Won
839
Everything posted by Paul
-
Thanks, and welcome!
-
If you leave the logo field blank, Blesta will use the color or the white logo depending on the contrast of the header background. If it's a light color, it should use the color version. If it's a dark color, it should use the white version.
-
We are familiar with this technology, and actually looked into it a bit probably 6 months ago. I don't think it was Clef, but it's certainly an awesome new way of authenticating and I think it has a good chance of becoming the standard in the future (not necessarily clef, but this type of authentication).
-
Very nice work, love the design! Button colors look great, all around an awesome integration. What do you use for your server status?
-
We considered it, and it may be a possibility in the future. For now, we try to update the feature request threads with a task number from our project management when a task is accepted. You can see all public tasks at http://dev.blesta.com/browse/CORE For the most part, it has been working pretty well. A direct vote count type system would be nice though.
-
Hi Mike, welcome! Mike from Licensecart is right. But whoever you buy from, we hope to see you around the forums!
-
Looks like a problem with the billing overview plugin. If so, the core is probably fine. You might uninstall and re-install the billing overview plugin widget under Settings > Company > Plugins.
-
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 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.
-
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!
- 1 reply
-
- 2
-
-
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.
- 33 replies
-
- 3
-
-
- blesta order forms
- cloud oder forms
- (and 7 more)
-
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!
- 33 replies
-
- 1
-
-
- blesta order forms
- cloud oder forms
- (and 7 more)
-
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?
