Jonathan

For one reason or another, we do get a lot of requests to go ahead and generate the next renewal invoice for a service early. The ability to forcibly generate these from an admin standpoint would be excellent!

+1

+1 This would be very handy. I'll be using the universal module for a few things and would certainly make things convenient for staff and clients.

Perfect

Glad to have ya on board Shh, don't tell that I'm hanging out here. Can't let that cat out of the bag yet.

Way ahead of y'all http://www.blesta.com/forums/index.php?/topic/3529-hide-invoice-method-change-box-if-only-one-method-is-available/

It's pretty self explanatory, no need to display it if only one option is available.

+1 on Paul's idea.

Dang thanks! I'd been searching for this and couln't find it. Guess it was so obvious I just was blind to it. Thanks!

Competing systems offer customers the ability to add credits to their own account by making a payment. This is actually a commonly used feature in some of our systems run on competing products and it'd be wonderful if Blesta could do it as well

I just got caught up on this too. I'm sure if the docs could be updated it'd save the next person the hour it took me to track this down

This is not something I thought about as we don't use such a workflow. If a customer is technically "active" they have at least one service in the active or suspended state but I guess this is where the tickbox to enable/disable this functionality would come in. The setting could be "Tick this box to enable inactive clients to sign up for new services and reactivate their account". Another for "Deactivate accounts with no active services" on a cron would be handy as well like Daniel said. I do also agree that having another possible entry for "banned user" or something similar would be nice in the event you want to disallow a single user or set of users from signing back up.

This would be a nice added bonus.

Precisely!

We mark clients as inactive which have no active services. When an account is inactive, that account then cannot be used to login when placing a new order. If there's something I'm missing here that would allow this functionality then great, please do enlighten me.

It would be great if it were possible to allow inactive accounts to be used to sign up for new services, at which point it should be marked back to "active". I guess for those who may want to forcibly keep an account inactive an override on the account to prevent it from being used in this way would be good.

+1

It would be great if the PayPal API could be used so that subscriptions can be canceled/modified via Blesta. This would prevent a lot of headache refunding payments where customers forget to cancel subscriptions.

+1 for LastPass. I need to go check out PasswordBox now. What is it that you like about them over LastPass?

Missed that thread. Vote added.

+1

Currently we have Services.add and Services.edit. It would be great to have Services.terminate (cancel?) and Services.suspend to greatly increase what can be done using events Personally I need to use these to trigger some licensing functions.

Assuming that means it will be fixed, so thanks It will certainly save someone from a headache.

http://source-docs.blesta.com/class-Services.html#_add "pricing_id The package pricing schedule ID for this service" refers to the "id" column in the package_pricing table. Since there's also a "pricing_id" column in the package_pricing table this is what I thought it was referring to. Spent about 2 hours banging my head against the wall before figuring this out...

I made the same mistake. If you try to import services there's also a very misleading part of the docs that caused me to use the wrong ID for one of the calls.