Jonathan

Fair enough. Technically speaking that makes good sense. A password requirement criteria would be just as good if not better. All I'm looking to do is force people's "password123" passwords into something a bit better. Whether it's by means of an arbitrary score or set of requirements I don't really care as long as it's user-friendly. Perhaps with this criteria ruleset instead of a score a javascript list of requirements that'd "tick" when the requirement was met would be nice.

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.

+1, especially on the strength meter/requirement setting

+1 for all registrars

It works fine for the main contact's email address and info. It's non-primary contacts that it doesn't seem to work on.

The search utility should be able to search in contacts data, especially email address. Presently there's no way to locate a client/contact by means of the contact's email address.

I'd be interested in the final product here.

Surely someone else needs/wants this

+1

I agree this would be a wonderful and very useful thing to have!

I'm not saying add any ACLs for actions. I'm saying add the ability to make a name-only permission that can be assigned. Lets say I wanted to make one titled "Ticket Support" for use by another system. All it'd be is the ability to add a permission that says that which could then be assigned on contacts. This info would be stored on the database and could be queries directly or via the API, but it's nothing more than the storage of the permission setting. It wouldn't actually do anything.

It would be great if it were possible to create a pseudo-ACL which could be used for either manual billing, or by another system reading data from Blesta which is what I need it for. It would be much cleaner than making a dummy-plugin just to get an ACL to work with and I'd think it'd be rather easy to implement. EDIT: I'm referring to the new contact login ACLs by the way.

We don't use Blesta right now so I've not tackled this yet.

Since the problem here is DA and not Blesta, why threaten to drop Blesta which is a far superior product to the alternative you claim, WHMCS? Why not drop the problem - DirectAdmin, and go for a panel that it will work cleanly with, say cPanel?

crontab -e -u <username>

idevaffiliate. It seems to work alright most of the time. Definitely tons of room for improvement and looking forward to Blesta's iteration of an affiliate system.

Says the man named domaingood....not phishy at all It's all a conspiracy I tell ya!

Sounds good to me. Mass mail is definitely a big deal. The other two are just added bonuses but not necessarily a priority in my eyes.

Mass mail will be nice. A necessity really. Affiliate an added bonus. Domain manager, bleh.

Welp, time to start thinking about 3.5

Looks rather good, I do like it!

Welcome. Good stuff that Blesta thing is

I'm referring to the built in support manager. Already knew plugins can.

I don't use the built in support module (yet) but this would be extremely handy and very logical and I wil want it in a few months.

Doubt you'll get many people on-board wanting this. Solus's reseller design is totally flawed and simply doesn't work for most VPS providers and I don't know of anyone who uses their reseller model for reselling.