Jonathan

What logic is used to assign it when a service is added?  The same logic should be used to keep it associated with the correct module of the pricing_id.

See CORE-2610

It would be great if the default status when creating a service as an admin was "pending" instead of "active".  By having it as active it adds a huge likelihood that human error will cause a service to be activated upon submission of this page without having received payment.
Further, if it's "pending" and the person intended it to be active, they can still go activate it manually.  If it's "active" and "pending" was intended...well there's no undoing that easily in most cases

It would be great if the default status when creating a service as an admin was "pending" instead of "active".  By having it as active it adds a huge likelihood that human error will cause a service to be activated upon submission of this page without having received payment.
Further, if it's "pending" and the person intended it to be active, they can still go activate it manually.  If it's "active" and "pending" was intended...well there's no undoing that easily in most cases

It would be great if the default status when creating a service as an admin was "pending" instead of "active".  By having it as active it adds a huge likelihood that human error will cause a service to be activated upon submission of this page without having received payment.
Further, if it's "pending" and the person intended it to be active, they can still go activate it manually.  If it's "active" and "pending" was intended...well there's no undoing that easily in most cases

Allowing cron tasks, database access, etc. for modules makes them basically plugins at that point. We're re-evaluating the design of these extensions to be more accommodating.

This should be treated as a bug.  It breaks addons which look at package_group_id to see if they should be available or not.
When this is patched a way to scan/fix the DB should also be released.  Should be pretty easy since Blesta knows what package_group_id goes with what pricing_id.

This is the best approach.

This is the best approach.

#dropioncube

By default Hong Kong cannot be used as there's no state to select and Blesta does not like this and won't accept it.

By default Hong Kong cannot be used as there's no state to select and Blesta does not like this and won't accept it.

This look wonderful!  Great work.
I'll try to check it out soon.

Just a quick and dirty script I threw together to email some stats.
https://github.com/neonardo1/blesta-ytd-rev

Looks good! I'll try it out soon. Thanks!

Just a quick and dirty script I threw together to email some stats.
https://github.com/neonardo1/blesta-ytd-rev

The Reassign Pricing function in the staff control panel doesn't update the package_group_id in the services table.  It should definitely do this for consistency.

#dropioncube

#dropioncube

#dropioncube

#dropioncube

#dropioncube

Seems you shouldn't be running a business.  You knew this was going on, you knew you were taking a second job, you knew many things.  You could've emailed your customers.  You could've taken 5 minutes to send an email blast using Blesta's mass email plugin.
You are full of excuses and no solutions.  Take some responsibility and stop making excuses and for goodness sake don't start another "business" until you perhaps take some business management classes.

We feel awfully sorry that you think that way. Rest assured that we never consider any of offered feedback to be insignificant. All suggestions put forward by our customers are carefully verified and used in the course of product development.

When provisioning a new service it's possible to end up with 2 services provisioned when only 1 should've been.
If you manually activate the services on the pending service's "manage" page after the cron run has already started and queued it for provisioning (but not yet finished), both actions will provision said service.
This appears to be a general bug and not tied to any module in particular as I can confirm it with both cPanel module and SolusVM module.  I've noticed this situation since the 3.x branch.