Leaderboard

I sent you a PM with a new trial key, let me know if it gives you any trouble!

Service Cancellation -- Service cancellation notice, sent when a service is cancelled (Automatically / Manual). So when a service is cancelled they can get a email. Maybe a manual / automatic templates one each?

Interestingly, your log mentions both daemon 1 and daemon 2. ​I think we need to know why Multicraft is not choosing a valid Daemon ID for you, when none is passed in to the API. I would suggest doing a test by creating a configurable option for daemon_id to specify the Daemon ID, and see if it works. Docs on creating a config option for this are here -- http://docs.blesta.com/display/user/Multicraft#Multicraft-CreatingConfigurableOptions Whether this works or not should tell us something.

Allowing multiple daemon's per location sounds good to me, although I am less-enthused with comma-separated values. I'd much rather have configurable options support a one-to-many type that can be used for a select/multi-select field, for example, to choose one, or some, of the values. That would accomplish the same thing here, but it would be a completely different task. IP management is a little more complex. I'm not sure how Multicraft chooses what port to use, but I imagine that it starts at one port (from a config setting in the Multicraft panel) and increments from there for additional servers, while checking to make sure the port is unused. This last part is what Blesta and the Multicraft API can't determine. Sure, we could have the module support a hard-coded or user-defined port range for a daemon, then randomly choose a port to use from the range, but that port could be in use by another multicraft server or a different service altogether. I don't see a way for us to determine whether a port we choose is actually available for use. Similarly for daemon IP addresses--it doesn't look like the Multicraft API allows us to determine what IP addresses are available to a daemon. If you take a look at the Multicraft Settings, there is an option to choose how an IP is chosen when a server is created ("All Interfaces (0.0.0.0)", "Daemon IP", "Daemon FTP IP"; default "Daemon IP"). I think that Multicraft should allow the kind of IP/port management configuration you suggest, rather than Blesta. All Blesta really needs to tell Multicraft is to "create a server for me" (as it currently does), and the IP:port associated with that server should be determined by Multicraft and your configured settings.

The ajax order template doesn't have a cart template file. Did you install version 3.2.1 of Blesta and the included Order plugin?

After discussing with Cody, I've added task CORE-1330 to address the display value for dropdown, checkbox, and radio fields within the client area. In these cases, the name and not the value should be displayed. This will correct the issue you describe where the Daemon ID is displayed, rather than the location name. It's a change to the core, and should be included in 3.2.2 (If there is one), and 3.3.0.

Or perhaps where configurable options are displayed, the name of the field should be shown instead for drop downs. This has more to do with the configurable options than the multicraft module so we'll need to evaluate. The result would be as you describe, showing the friendly location name rather than the Daemon ID, but the question is whether this is an acceptable solution across various other modules and uses of configurable options. I suspect it is.

It'd be good if it was configurable so this functionality could be enabled, disabled or enabled but only on paid invoices ie. invoices with transactions.

Another idea that just came to mind for the value of the location configurable option could be a JSON list of daemon IDs and arbitrary names that are displayed to the client. Right now, after the service is setup, the client sees "Location: 1" in the client area. Just to make it a little more intuitive, it could say "Location: Chicago, IL, USA" or whatever value is chosen. The JSON value for the Chicago location in the dropdown would then be something like: { "1": "Chicago, IL, USA", "3": "Chicago, IL, USA", "5": "Chicago, IL, USA", "7": "Chicago, IL, USA" } And each consecutive location in the dropdown would follow a similar format.

Yes, in this case Resell.biz is the best choise for any new or current buisness, for resell domains