Jonathan

Blesta should have the capability to allow upgrades between package groups in the admin interface. Here's a usage scenario: Packages 1-7 are all interchangeable and can upgrade between each other by admin & client. They belong to the same package group. Packages 8-11 are all interchangeable and can upgrade between each other by admin & client. They belong to the same (second) package group. Package 2 wants to upgrade to package 8. No problem, it just needs to be moved to different hardware since it's a different type of hosting package (SSD package versus HDD package but otherwise identical). There's no way to cleanly upgrade this person whereas there should be. This is a non-issue in all competing products I'm aware of. Since a hardware migration on the back-end is required, obviously we don't want the client doing this but forced package changes such as this should definitely be possible by an admin where you might want to override a normal scenario or end up in a situation like above.

What if you made a one-time coupon that'd only work for domain+hosting for the price of the domain off?

Why annoy them with another page? A checkbox is far superior.

+1

+1

Big +1

It will be in 3.5

This would make for a pretty good feature request - the ability to natively disallow email changes for the main contact or at least require them to re-accept the TOS or something.

It would be great if there were some events associated with contact addition, edit, and removal. We for example could use this when syncing certain data within our ticket system (Kayako) regarding email assigned to the account and change it if necessary as well as keeping the proper emails tied into the same client organization there so that the tickets between their sub-accounts are viewable properly by other sub-accounts and the primary account, etc.

WHMCS has it.

I second this. Such functionality is quite nice in other systems.

I think you're after Contacts->getNumbers() http://source-docs.blesta.com/class-Contacts.html#_getNumbers

Big +1 again. Had some domains expire due to this

+1 for @Licensecart's mockup.

Upload the full archive, overwriting your files. Navigate to mydomain.com/admin/upgrade Follow the instructions.

Just a friendly bump for more input so this one isn't forgotten about, especially given that it's implementation shouldn't be too hard

Just a friendly bump for more input so this one isn't forgotten about

It would be a simple text area or input box for the customer on the cancelation form. In the admin side this reason would be best displayed on the scheduled services page I suppose. Perhaps like this:

A comment/reason box for customers when requesting cancellation would be great.

The latter is what I'm after. The package price isn't a big deal since we already see the plan listed there. It's the total that we need. Perhaps adding another DB column to store a "cached"? copy of this might make it easier to deal with so there's not so much logic involved in making this total available in the template?

Hmm yep it sure is.

The majority of payment gateways and merchant accounts charge a $0.10+ transaction fee, so processing amounts of less than say a quarter ($0.25) really make little sense and often times you'll be losing money. A setting in Blesta of a minimum amount due allowed to be paid would be awesome. Naturally this threshold should also be tied to the suspension system as to not suspend for any amount due equal to or less than this setting so basically a tiny charge could sit on the account and be paid with the next full package renewal or something. Pro-ration of little charges will generate a lot of these little charges.

Yeah I saw that. I'll have to use it in the interim if Blesta can't sneak this in natively.

Big +1 on this. Billing Overview widget takes forever when you have tons of data so without some form of a loading icon you never know if it's coming or not in the 3.5 ajax updates (http://dev.blesta.com/browse/CORE-1547) since it doesn't block the page.

When looking for something in Blesta that your mind is unable to recall the location of, a faint giggling noise to lead you in the right direction would be especially helpful. This will require quite an overhaul of Blesta's automation I'd imagine but should be a huge selling point. A real-world scenario where such a feature being especially useful is in humans. This feature often comes to light in the common child's game, hide and seek in which the hidden child will oft giggle when the seeker is near thus helping the seeker locate the hidden.