Leaderboard

Password scores can be useful to end-users by simply making them think about their password selection. If they want to choose something we arbitrarily deem as "poor" security-wise, then at least they are making a conscience decision about it. It may nudge people into creating a better password, and save us the headache of a breached account. In terms of arbitrary, the link Jonathan posted -- https://tech.dropbox.com/2012/04/zxcvbn-realistic-password-strength-estimation/ probably best fits with our understanding of secure passwords. Length is better than special characters, and passwords that are difficult for computers to guess but easy for people to remember. Worth considering.

i have often asked myself: what i can do with "calendar"? It's nice, Blesta team spent so much time to develop it, but it's so "useless" as if it missing something... Yes! Why not add checkbox (or a select box with predefined options, eg. "Not send memo"/"Send a memo 15 minture before"/"Send memo 30 minutes before"....) to select if send or not a memo before event starting? Only a new field in database and a new task for cron, .... ...so we can use only Blesta in our work, and we can say "good bye" to Wunderlist!

That could be an option, but it wouldn't resolve the issue of code changes related to authentication. If we're going to add an option to the config, we might as well add a token, and simply prompt users for this token when they wish process an upgrade through the web interface. That way the user can simply change it at any time via SFTP, and it doesn't rely on the authentication system matching the db schema.

A simple "visual note" about a selected password, is good and not invasive: user can choose arbitrarily if accept or not. https://www.dropbox.com/register (based on https://tech.dropbox.com/2012/04/zxcvbn-realistic-password-strength-estimation/) is a great sample.

Hi to all :-) We are UK based company that offer anything you need for Blesta, servers or webpages (we are doing little upgrades, or little modules/plugins for your blesta) for only 35$. If you have any problems with Blesta, webpage or server you can contact us on www.webbera.co.uk or here (inbox). For now we are working with: PHP, HTML, CSS, JavaScript, Java, ... Apache, Dovecot, MySQL, .... We are cheap and fast if you want to contact us you can reach us here, on email or from webpage. P.S. We are using blesta (currently 3.4) and we have few plugins that we are going to publish soon :-)

Here is a little update of Namecheap Module, with: - added support for a Promotion Code (coupon) (providers, as WebHostingBuzz, offers a Namecheap coupon to their reseller); - fixed of fields related to specific TLD (e.g. ".eu", ".ca",... requires additional fields in order); - fix of a misspelling (EN). namecheap.zip

wich plugins you have ?

all this ideas is good , the important here is not to let the upgrade directly anyone . but if i'm forced to vote , i will vote for licence number option .

++1 This is very usefull also for "Tasks" or "Todo" things like for exemple check domain transfer status after 5 days

my opinion The best option is "license number", to get the upgrade download you have to login to the client area to download correct?, why not check the license? this way is more usefull for all and more secure on every aspect the outher options are: Wen uploading and executing the upgrade link, it will generate a token and send by email to all administrators staff this way we know the token to execute the upgrade

I like this idea, what does everyone else think? The question then, is whether to use http basic-auth or simply add a text input, if a token is set in the config.

e.g. Loader::loadModels($this, array("Transactions")); $transaction = $this->Transactions->getByTransactionId($transaction_id, $client_id); if ($transaction) { // Transaction already exists }

Split and Quote are when replying to a ticket. Either split specific replies into a separate ticket, or quote replies in the current ticket for your reply. The merge, as shown in Licensecart's screenshot, is on the ticket listing page, where you merge entire tickets (all replies within them) with each other. Are you suggesting that after you perform a merge, the ticket that replies have been merged into have an entry stating the old ticket #? Similar to how the old ticket gets closed with the message "This ticket has been merged into ticket #2695697."? In the future (CORE-1120), we plan to make that message a log entry rather than a System reply. I think your message would be best as a log message instead of a reply.

Scores for passwords in applications are generally derived by meeting certain criteria, most often times javascript is use to determine this "on the fly". For example: https://tech.dropbox.com/2012/04/zxcvbn-realistic-password-strength-estimation/ Sure it's somewhat arbitrary, but creating secure passwords really isn't hard so having an arbitrary meter to help guide people would be very useful.

I confirm the issue and add the following: in "invoice delivery" log, i see that "invoice" was sent at the date/time of "proforma". Try to explain better with an use case: - System generates a "proforma" for a service renewal; - System sends an email with "proforma" attached, at 2015-01-19 12:00:00; - Client pays at 2015-01-19 12:35:00; - System converts "proforma" to "invoice"; "invoice" is "closed" and "sent"; - In Tools > Logs > "Invoice delivery" there is the "invoice" as sent at 2015-01-19 12:00:00 (this is the problem!!! so the client will not receive the invoice!). Thanks

Great news, PauloV. Thanks

+1 we will add this on next release for opensrs and internetbs module

Also Add Password Score to must need score 50+ otherwise basic password not taken Like (Ex: 123456).because Here is customer domain and hosting. Thank you

I would really like to have that password generator sooner rather than later.

If the check did not go through, change the transaction from Approved to Returned. I recommend Returned for bounced checks, as that's effectively what happened. Voiding it as Mike describes will work as well. Once the transaction is no longer Approved, it will be unapplied from the Invoice automatically, re-opening it.