Paul

That would be nice, I could see that tying into client groups well.

The "Order" link? It's a nav item, so you could modify it in the database to say something else if you want, but it's not customizeable. The 2nd image, where the order forms are listed is customizable by adding a description (new field) on the order form.

Ok, so in v4 we added a couple things related to Order Forms. Clients now get an "Order" link in the client area. This takes them to a page to view all Order Forms they have access to. Here's the link in the nav: When they click the "Order" link, they can see all order forms they have access to: You can also add a description for an order form that will appear on this page for the order form. Staff can now set the "Visibility" of an order form to Public, Shared, or Client Only. Here's how that works: Public (Anyone can see order forms of this visibility if "Default Order Form" is "None - Show Listing") Shared (Only users that know the URL to this order form can access it) Client Only (Only authenticated clients can see and order from these order forms) Setting the visibility: Setting the "Default Order Form" (None - Show Listing) now recommended: What do you think? I think clients having access from the client area directly to the order form is great. Also, that they can have access to client only order forms. That opens up the possibilities for doing something special for existing customers. What do you think?

We would like feedback on the Mass Mailer, but it requires 4.0 so we'll have to wait for the beta to start. We did make some changes to the client area. For example, the navigation now appears whether clients are logged in or not. Really, a lot has changed, so we are hoping to get a lot of feedback during the beta.

I sort of prefer the "limit 1 service per client" option. I see this as a package option, only allowing a client to order 1 service from the package. Does this conflict with your suggestion @feezioxiii?

nice work! I just sent you a donation.

We need to refactor the coupon system before we can extend the functionality. Having coupons apply to specific terms/periods, and supporting free domains is planned. Right now, you can create inclusive coupons where you have to buy all of the items listed for the coupon to get the deal. This may not be ideal for domains because domains can belong to multiple packages and have various pricing. But it would work for any other type of package by making the coupon discount the same value of the "free" package. We don't like Pokemon Go. We are preparing for the Pokemon Go Apocalypse.

Yeah, make sure all services under the client are cancelled. Blesta will continue to invoice active services, regardless of the "status" of the client's account. If it's going to be marked inactive, it should be cleaned up first.

I would post each change you want made to DA to Feature Requests. Please open a new thread for each item as they would be considered individually.

I agree, a cron task with settings to specify how long a client has had no activity, however that is defined (active services, open invoices, etc), could mark a client inactive. Limited client area access would be difficult and we would have to have some type of ACL permission schema admins can define for this purpose. Probably not going to happen. A different login error message due to their status is a good idea.

An option to force email address as the username (default) and not allow clients to set a different username would be necessary. The problem is that some users may necessarily have multiple accounts that use the same email address, which wouldn't be possible under such a schema so we'd have to let admins decide how they want to handle it. Plus, backwards compatibility.

Let me know what you think of this CORE-2222 It includes a provision for an additional functionality change whereby new customers will not have access to the client area until their order is approved. Having a 4th status makes this possible.

There's 2 or 3 that actually need to get done for beta. We're working on it, will be done soon. Updating minPHP and a couple other tasks were really involved, and required some refactoring and creation of new libraries. So, taking longer than expected, but almost there

Yep, it's called damage control, and it's shady. People miss it, and don't change their password at other sites if they used the same one. It made me reset my password today but I couldn't log in on the page it directs you to, totally broken. Probably why not many people logged in right now.

We were able to duplicate the issue, and have someone working on it.

Thanks, I created a task, CORE-2221 and linked it in the other thread. We'll take a look.

Thanks SSy, I have created CORE-2221 so we can investigate. We have not tried to duplicate this yet, but it sounds plausible.

We have a task that would make this part of the core, and observed by the support system and other areas. See CORE-737. Do you think this would cover our bases?

Pending invoices are not created automatically, so for these you would have had to manually create the invoice and select a future bill date. If pending invoices are included in the total, I'll create a task so we can address this in a future release.

Settings > Company > Emails: - Staff Ticket Updated - Staff Ticket Updated (Mobile) Here's the default Staff Ticket Updated HTML Here's the default Staff Ticket Updated TEXT Here's the default Staff Ticket Updated (Mobile) HTML Here's the default Staff Ticket Updated (Mobile) TEXT

Probably because there is so much time between replies (10 minutes). You may have to sneak into that mailbox and delete the message before it gets imported into Blesta to kill the loop. I'd like to implement a blacklist that you can add domains and addresses to to ignore.

Do the emails show up in the mail log under Tools > Logs > Email? Also check the staff email support templates under Settings > Company > Emails (Under the Plugins section). Did you modify any of these? If so, if there is an invalid tag, the email won't be sent because of an error.

Blesta has some rate limiting built in, if you're using piping then it should not respond after, I believe the 5th email or so within a given period of time, which will kill the loop. Don't you love it when someone signs up with an email address that goes to their support system, and then opens tickets?

Can you provide steps to duplicate? What version of Blesta and the cPanel module are you using? Can anyone else duplicate this behavior? Deleting pending services should never issue a cancel command with the module. As for duplicate orders, the best way to go is to cancel those unpaid orders. @naja7host weren't you working on a plugin to cancel incomplete orders after a period of time? I believe we have plans to add this natively as well. For now, staff can perform this action manually.

Deleting a pending service deletes it within Blesta only, and does not make a module call to perform a cancel action. Whenever performing actions on a service, look for the "Use Module" option. If it exists, you can uncheck it to ensure that the action isn't made via the API. This does not exist for deleting pending services though, and will not delete the service on WHM/cPanel.