Leaderboard

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.

When viewing the client area, all looks good except for not displaying the customer's services Also - The Return to Staff area is pointing to a variable my browser is not parsing: http://www.myste.com/blestalocation/client/%1$s I overwrote the files, and did the upgrade as I should normally do. I suspect something may not have gone in correctly, during the upgrade? Any ideas? NEVER MIND Filezilla did not upload all the files like it was supposed to. All fixed now.

Weel said I have been seeing WHT foruns and some billings systems are still a joke after being released as what they call "stable" lol

Haven't looked at the code in-depth, but what happens most likely is that it updates the contacts' table information but not the users' table. Blesta registration basically goes first to the users table, then creates a contact entry. When you update the contact's email, Blesta is only focused on the contacts table itself, leaving the users table to be untouched. This would be an easy fix to add into the code, and as long as the contacts.contact_type == "primary" update the user's information as well.

That because , i think , you have set generate invoice 3 days before expiration date . adjust it in the settings .

Hello Please try the fix i provided for you in your support ticket. Thanks.

Well I've been using the beta since .02 seconds after it released. But I wasn't able to go from beta to stable as fast as I would've liked. Well actually a Blesta beta is more stable than most companies actual stable so technically I've been running 3.2 stable for awhile