Daniel B

So...I just decided to get with the times and secure my passwords...because I fail and use the same few passwords for like 300 websites. If anyone else is interested in PasswordBox (system to manage all of your passwords), I'd love if you could sign up with my referral link. I don't get any money or anything out of it, I just get a free unlimited account once I get 5 referrals. After I get 5 referrals I'm going to remove my link and someone else can post theres if they want http://j.pbox.io/noYhb3NM

naja, just curious...are you holding off on any updates on this until we hear more about the Blesta planned domains module/changes? Just wondering since my reseller (NetEarthOne) will start charging for Privacy Protect features (which means so will I) so it's something I'd love to be able to add into Blesta soon as an automated process of the module instead of using configurable options/manually doing it like I am now.

Yup, it's posted on WHT and ExtraLicense.

gotcha +won

lol Paul Guess I'll have to reduce the price to $150 and hope someone is interested, would really love to get this sold to get a few things going that we really need soon .

click the line in the services area...the login button is there.

correct, emails that you could read and then forget about, mean to do later, accidentally delete, etc. This way...it adds everything to a single spot. Could even expand a bit to add custom tasks (follow up with new clients in x days). A to-do list system would be awesome.

I think he explained it pretty well, he's requesting a to-do list plugin that creates a to-do list based on things that happen in Blesta. If an error happens, it automatically adds a review task to the to-do list. If someone places and order that requires review, automatically add that to the to-do list, etc.

+won, would love to see this

Still for sale, please feel free to send offers.

The purpose of requiring approval of orders is to ensure it is a legitamate order. If all you want to do is click a button and approve the order...why even require approval?

The domain listed on your clients account for their hosting package is completely separate from actually registering a domain. If the service of the client you are talking about is just showing the domain on a hosting package, then you need to create that same domain with the registrar module as well.

Hopefully Paul and Team won't mind me listing this here (also listed at WHT) since Paul already knows about my plans . ---------- With this purchase ($300 value if purchased direct from Blesta) you will receive a v3 owned unbranded license as well as a v2 owned unbranded license. The support for these licenses is expired, yearly renewal is $39. We are hoping to raise $200 through the sale of this license, lower offers are welcomed but please remember all proceeds from this sale will be directly donated to the formation of a non-profit and not for personal gain. Disclaimer: This license is being sold to provide direct monetary support to a non-profit that I am involved in forming. I have spoken with Paul about this and have his full support in this sale, I'm sure I can get him to come along and post as to the validity of this sale. Because said non-profit is still in it's formation stage we are not ready to provide info publically, but if anyone is interested further in that aspect of this sale please feel free to PM me.

+won definately something that should be default. Being able to select "manually review" orders, and then never being able to find them because nothing informs you that it needs to be activated is very offputting for new Blesta users.

It couldn't be built directly into the core (and shouldn't). Even Blesta uses modules for separate domain registrars, not the core. But I do +1 the request to have it added to the currently existing (and future made) Registrar modules. I would probably make it optional in the settings of each registrar if it were me, that way for people who only want to allow one contact it would be simple. Also if this is implemented, something like a "same as X contact" for each area would be nice, that way if you have 2 contact people, it would be easier to list 1 of them for 3 contact types, and 1 for the 4th...without having to retype the first persons info 3 times.

+won

I think so too, just went through updating 8 servers, all of the interworx ones were already complete.

+1 for me, though I don't use Plesk. I think there should be a separate IP and Hostname field for all modules that can use one truthfully, even if only for email template purposes .

Sounds like the only important stuff to me.

I'm not really understanding what issue you are having. Are you wanting the domain name that someone inputs when registering for a hosting service to be registered at the registrar? To do that you'll need to setup one of the registrar modules.

Yeah, on the scale of importance of security concerns, usernames are pretty much at the bottom for me...plenty of other things that control security better than keeping your username itself unknown...but every tiny little bit helps I guess. Though I'm curious, why can't your staff accounts on your site just be related to the staff account on Blesta? I guess I don't see why you are trying to associate a staff account on your site with a client account in blesta?

Thanks for the contribution. Just being a bit nitpicky I guess, but might be nice if it showed as "Cloudscale (New Zealand)" instead of just "Cloudscale" so it fits better with the existing format of the list.

Blesta logs would be nice. As well as knowing how the package is setup. You didn't really provide much information that we can use to help you.

I can guarantee you that most sites out there don't use their admin accounts to pay said bills...they'd have a separate client account, so that analogy doesn't make much sense. Not bashing you or anything, so hopefully you didn't take it like that...I just don't see the desire. A single sign-on system could work for client accounts, but I don't see a need to include admin accounts into that unless you are actually building the management section of Blesta into your website (in which case possibly doing it in the reverse method?...have your Blesta info work on your website, rather than your website info work on Blesta?)

Supporting 3rd Party CMS integration has nothing to do with a billing system. It's normally those 3rd Party CMS's that start that integration process, not the other way around. Blesta 3 is only about a year old, and I'm 100% happy that the devs are not wasting their time on doing stuff like this. It's a billing system, their focus should be on making the BILLING features top notch, and then worry about integration with 3rd party applications later...specially applications like CMS's that aren't specifically related in anyway. Integration with domain resellers, payment gateways, etc...those are things that a billing system SHOULD have...integration with CMS's?...completely optional and not required. The product works just fine, I think it's your expectations of what should come with a BILLING system is what's flawed. And your mention of open source, you do realize that Blesta is already 99%+ open source right, the only thing that isn't open source is the licensing files...and it's way more than "half baked". Blesta is built around a plugin/module system for a reason...and that is to make it easy for the open source community to do exactly the types of modules you are wanting.