Paul

In terms of what you recommend for the client side, this is almost identical to what the task describes in CORE-2058. From the admin side, an option under Actions would be fine unless we allow bulk-renewal as specified in the task.

Just an update on this. I've created CORE-2062 to force port 25565 when using a dedicated IP, since Multicraft doesn't default to that behavior (oddly enough).

Just an update, I've created CORE-2062 to address this within the module.

This was mentioned in http://www.blesta.com/forums/index.php?/topic/5527-multicraft-not-setting-dedicated-ips-properly/ In the following post, Tyson says what you can do to force 25565 as the port # for all servers: http://www.blesta.com/forums/index.php?/topic/4201-questions-regarding-multicraft-module/?p=31118 I wonder, if the module could be updated so that if it pulls an IP from the pool, that it specifies the port as 25565 rather than allowing Multicraft to select the port. That's really the issue here -- Multicraft is not using port 25565 for dedicated IPs by default, but perhaps we can force it.

Yes, it creates a problem though if as an admin you invoice for multiple cycles and a single invoice is created per-service as I suggested in the task. I wonder if we should create an individual invoice for each cycle or handle it differently.

Please see CORE-2058. This thread will serve as a point of discussion on this task.

Please see CORE-2057. This thread will serve as discussion on this task, if you have any comments, please let us know. There is additional planning required for this task prior to development.

This event should make this possible in the future: CORE-977

Please see CORE-2056

I've met Matt Pugh several times and he's always been nice to me in person. We are competitors, but there's no reason we can't get along. @zmjwong give the import a try, if you run into any trouble let us know.

I think we discussed this over the phone. Is it the suggestion that Blesta would communicate with the customer through the PayPal email address they paid with? For example, send welcome email to their PayPal email address? Since they can provide a different email address when signing up, and likely prefer to be contacted at that address, there isn't a clear answer. For example, many companies use an address like paypal@domain.com which goes to their accounting department. If Blesta ignored the clients contact email address and sent a notice to the PayPal one, it may end up in the hands of someone else, who it's not really intended for. I'm curious what the suggestion is, specifically, in how Blesta should handle this.

Your best bet is to open a feature request for this in the feature request forum. We haven't had any other requests for this, so if you can include some real use cases it may help rally support.

Yep Hidden departments clients see not.

If I understand it, this BungeeCord is a sort of proxy to Minecraft, is that right? And BungeeCord lets users switch between servers on the fly? Sounds pretty cool. Not sure what you're trying to do with it exactly though -- the Multicraft module does not know anything about BungeeCord. What are you trying to accomplish?

I personally suggest setting the price on the package for the Brazilian currency. Most customers don't like it if the price continuously changes each time it renews. Setting the price in that currency for the package will cause it to renew at that price rather than using any currency conversion.

The license is valid and eligible for transfer. I have redacted part of the license key above as it's not good for it to be public.

People have been asking for OnApp support for a while, though I think someone was working on this.

Are you configuring your package to automatically cancel the service at the end of the term? Unfortunately there is no simple solution to this, we are planning to add an option for Package switching after order, which would accomplish what you are after. What I would suggest is this: Allow users to sign up for a 1 day package, then after they sign up, change their term to monthly manually.

I agree, please see CORE-2016

If the invoice is unpaid, when it's delivered it will be using "Invoice Delivery (Unpaid)". Check both the HTML *and* Text versions of your template to ensure they say the same thing.

There seems to be a couple different parts to this: Setting a contract length for a package term, and communicating that to the client during order & What to do about early terminations Regarding #1 above, the way I envision this working is that when you set pricing for a package term, you can specify that it's part of a contract and then set the contract length. The contract length may be able to be displayed to the user in the drop down menu when selecting the term. For example: "1 Month @ $12.95 USD (1 year initial contract)" Regarding #2, either we have a separate contract termination fee, or we piggyback off the cancellation fee field (my personal recommendation) Thoughts?

If your module doesn't appear under Settings > Company > Modules > Available, it's probably missing something. If you'd like us to take a look, you can open a ticket and include the module.

Blesta does not handle or enforce contract lengths, but this would be a good feature request and something we would be willing to consider. Feel free to post a feature request in the feature request forum if you'd like to make an official suggestion.

As Mike suggested, Record Payment (Under Actions on Client Profile page) and use "In House Credit" to make the payment for any invoices you wish to close. You may also void the invoices, but that may not be desirable.