Leaderboard

sometimes i feel you are against any complialt to blesta even if is true . we know the stuff is busy in coding new feature and making big changes , but answering here or in tickets should be regular and quick as soos as possible , even if the feature/request will not implemented , but if the client/visitor see a anwser that give a good sensation about the active staff .

Fraud Record, for Blesta would be amazing in my opinion, it checks a database for unwanted customers, it's a bit like a neighbourhood watch team, but for webhosting. Any fraud gets submitted to the database, and you can check to ensure you don't get the same unwanted customers. Stop Fraud Clients, Report Abusive Customers. Combine your efforts to fight misbehaving clients. I used to use it on the last billing system I used and it helped much better than Maxmind, because bad clients are bad clients. http://www.fraudrecord.com/ API: http://www.fraudrecord.com/developers.php

Hello, I'm glad to join the family of blesta software users. Was thinking to buy a whmcs license but after taking a close look at both I made a choice: Blesta. Hoping nothing but good things to happen from now on. Kind regards, George.

even if you use the var innodb_file_per_table = 1 i have though this var can avoid this situation , because every database in a separate file .

i have created a separate plugin for testing purpose to do the same thing , the only thing i ahev not stored the info in crypted stat . what i have do : when i invoice/proforma are generated , i get the info from the event add.invoice , i have stored this infor in a new table called "invoice_clients_data" , in my html invoice template i have chenged the database query to get the info from my table and not from the client table . now even if the client change the info the invoice data should remaing the same . tested and is working fine at the moment in my test server . maybe i will release it soon , or i will include it in the admin tools plugins . BUT FINNALLY I HOPE THIS SHOULD BE IN CORE FEATURE .

1+ for no to ediditing core file 1+ disallow customer from editing invoices .

Thanks We are going to wait for blesta to natively disallow customer from editing invoices. I don't mind editing the core for the other parts but this one is to big to patch as we don't know yet how they will implement it.

Tutorials used on our main website "Dewlance.com" is made by me and only for our hosting/reseller/vps customers(not for PremadeKB) PremadeKB.com tutorials are made by English speakers and there is no any grammar error on our professinally written tutorials. Example tutorial for PremadeKB: http://www.dewlance.com/client/knowledgebase/2023/How-to-update-DNS-Nameserver-on-DynaDot.html

@Licensecart: I have to agree with wanah, blesta team should view and answer presales questions. 3 days without oficial answer gives bad image to blesta Thats why I have answer because wanah was waiting for an answer There is no excuse for this even for Blesta 3.5 busy day. 24 houra is OK to wait but more than that gives some people something to think about @wanah: Dont worry this situation is not normal and im shure you will be amazed what blesta team and all of us will do for it and for help you

Tyson, please consider that this is a very important fix. We're using proforma as default, and so for every order we need to resend manually the invoices after payment: this isn't the best for us and for our clients. Thanks

Now that cPanel add MariaDB as option insted MySQL lol, and we go to PDO connectors pressure from PHP7, what the future will old? We use CloudLinux on shared enviorments on all our servers, so we use betwin PHP 4.6 and php 5.6 eheh all with latest satable MySQL from cPanel. Off topic: I hate innodb engine (if DB is corrupted it can compromise all databases stored on that engine), MyISAM is good wen corrupted but a litle slow running. In developing some APP's and Websites we sitll use old fashion MySQL with MyISAM Engine, so it will take some time for us to adapt