Paul

Did you complete the upgrade process by running /admin/upgrade? If the tasks are not completing, they may be encountering an error. If the database hasn't been upgraded, there could be errors related to a query which hangs the task.

Are you saying it is creating 3 new invoices per day? Or, he is getting a copy of the same invoice 3 times per day? If the service was removed, I don't see how new invoices could be created. If the invoices were removed, I don't see how it could be sent out. I think we may need some clarification.

They never really versioned things properly which is why they were stuck on 11 for so long. They introduced numerous backwards incompatible changes and kept incrementing the minor release only. In a sense, their new versioning scheme just removes the redundancy and allows them to continue as they were. The bright side is that yes, it will probably be less confusing for people.

11 to 54, wow. I understand their reasoning, but why not 11.54, then 12, 13, 14 if they want to break semver. Interesting re OpenID, though their cPanel login screen is looking pretty confusing with so many options. Probably a much better way to present these options. 2FA is nice, sounds like they plan to implement TOTP. We implemented TOTP for Blesta in 2010. Some of the performance improvements sound really good.

See CORE-1864 I believe you are affected by this. A fix has been implemented for 3.6.1, and I'm including the hotfix here if you'd like to manually resolve it on your system in the interim. In /plugins/billing_overview/models/billing_overview_statistics.php update lines 44 and 45 FROM: $this->Record->innerJoin("transaction_types", "transaction_types.id", "=", "transactions.transaction_type_id", false)-> where("transaction_types.type", "=", "debit"); TO: $this->Record->on("transaction_types.type", "=", "debit")-> leftJoin("transaction_types", "transaction_types.id", "=", "transactions.transaction_type_id", false); In /plugins/billing_overview/models/billing_overview_plugin.php update line 16 FROM: private static $version = "1.3.0"; TO: private static $version = "1.3.1";

Go to Settings > System > General > Payment Types. Make sure your payment types for revenue are of the type "Debit", if not change this. This should have happened automatically so make sure you ran /admin/upgrade in your browser and upgraded the database first Types of the type "Credit" will not appear in the rev graph

Braintree said no hosting companies? First BluePay, and now Braintree? wow I was told that Wells Fargo added hosting providers to the naughty list, which makes no sense.

This should work: wget https://account.blesta.com/client/plugin/download_manager/client_main/download/79/blesta-3.6.0.zip

3.6 should be out later today

Tasty cPanel https://github.com/blesta/module-tastycpanel Tasty Interworx https://github.com/blesta/module-tastyinterworx Digital Ocean https://github.com/blesta/module-digitalocean All released as FOSS (free open source software) under the MIT license.

Addon services are invoiced together on the same invoice, so that is one way to link them.

100% correct. And, if you decide Stripe is not a good fit, you can switch back, or to any other merchant gateway that is configured to not use tokens.

Custom fields are linked to the client group. If you want the fields to appear in more than one client group they need to be re-created for those groups. I believe Mike is referring to a previous discussion about being able to make the fields apply to all groups or easily clone them for multiple groups.

1. Two merchant gateways can be active, but cannot process payments the same currency. Merchant gateways are invisible to customers, all they know is they are paying with a credit card. 2. If you are not using tokens with BluePay (The official gateway does not support tokens), then you can switch to Stripe if you are using the "onsite" storage method for Stripe and not the token based method. So, you can switch back and forth between 2 or more merchant gateways if they all have the local/onsite storage method where Blesta stores the card details encrypted. If you switch to a gateway that uses tokens, any new payment accounts would be compatible only with that gateway and it would make switching to any other gateway difficult.

+1 Anyone aware of an open source library or API docs that facilitate this?

Yes, CORE-1764 done for 3.6.0-b1 and included in 3.6 final next week.

Open up your /config/blesta.php config file. Are there values for your database in there? Or is the file identical to the config/blesta-new.php file in the zip file? It sounds like there may be permission issues with writing the config file. I would suggest attempting a new install, making sure that /config/ and all the files within it are writable by your web server. The installer does a check, but it's possible there may still be some type of permission issue that it's not catching.

I have bumped this up in the backlog.

White pages do indicate errors, please turn error reporting on. To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1); Then try again, hopefully you'll be able to see any errors.

We do have plans to allow simpler integration with third parties like Facebook, Twitter, etc. If I recall, there is a change that must be done to the authentication system, and then such an integration would be possible via a plugin.

OpenSRS requires the Domain Manager, which requires Blesta 4.0 and PHP 5.4+. There's an OpenSRS module already, that seems to be regularly maintained, which I would recommend for the interim: http://www.blesta.com/forums/index.php?/topic/3344-opensrs-beta-107-relesed Chances are we will likely be focusing on the domain manager and domain registrar modules for 4.1. We know that better support for domains has been highly requested and long awaited, and are working on implementing the best solution.

Nobody is blaming you, we're just trying to help figure out the issue. If you open a ticket with your Blesta login details, I would be happy to take a look and see if I can determine the cause.

All usernames must be unique already. We do have a task planned for username recovery, see https://dev.blesta.com/browse/CORE-1094

This is resolved in 3.6.0 beta 1, and will be included in 3.6. Please see https://dev.blesta.com/browse/CORE-1516 For a hotfix, see http://www.blesta.com/forums/index.php?/topic/4761-cpanel-8-char-username-restriction/?p=35458

Great! We would appreciate your contributions. We absolutely will post a link to it here when ready. We are in the process of auditing the code, and will publish it when complete.