Jonathan

Here's the code for that: https://github.com/NETLINK/Blesta-Namesilo/pull/15 It should make it into master in the next few days once @NETLINK approves the pull.

This is addressed in https://github.com/NETLINK/Blesta-Namesilo/pull/13 I did find some issues with the way nameservers and other fields were processed for anyone using the cron to setup services after payment is received. It's also addressed in the pull request above.

I can't recreate this. I think you might be hitting this per their API docs: Can you check your module logs for an error relating to the setup?

I'm looking into the latter issue first. I have some ideas on the former I'll just have to see if Blesta will let me selectively display the extra input fields required if it's a .us domain. I'm assuming .ca suffers the same fate but based on the Namesilo API it's a much more complex issue to tackle as it takes more than few questions.

4.3 should contain the ability for modules to create cron tasks. Once this is indeed the case I intend to develop exactly this type of system. There's another module that does this already but it does so by way of a helper plugin.

Stick a request on github under issues and I'll look into it. I've been actively contributing code I'm just waiting on @netlink to accept my pull requests.

They don't use Blesta. This is a generic feature request.

That seems a logical solution then. We don't use packages in multiple groups together but I'm sure others do. Perhaps it wouldn't take much logic for if the target package is only in one group for it to do the logic automatically?

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.

Any updates on getting this fixed in core? It prevents a service from seeing the correct addon packages available and has no fix except manually in the database.

Yeah it'd take a callback for sure.

It would be great if the module would update the user's email address on the cPanel/WHM server when the primary email in Blesta is changed.

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

Looks like https://dev.blesta.com/browse/CORE-2435 is slated for 4.3.

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.

There is no affiliate system in Blesta.

This is the best approach.

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.

What benefit would that give you over standalone? Do you just want the information displayed live versus in an email or do you just want the plugin to send the email?

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.

How do you do the rDNS management? I'm not aware of any Solus API call that makes this possible.

#dropioncube

While it shouldn't be impacting anything, it's the only error I can associate with "provision paid services" cron hanging a few times a day. By hanging I mean Blesta thinks it's running and it's indeed not, so I assume it died before updating log_cron.end_date. [2017-09-15 14:55:01] general.NOTICE: E_NOTICE: ob_flush(): failed to flush buffer. No buffer to flush {"code":8,"message":"ob_flush(): failed to flush buffer. No buffer to flush","file":"/path/to/blesta/app/controllers/cron.php","line": 3260} Any ideas if this could be causing odd stuff or the cron to die?