Paul

This is more a function of proration than package term. Nobody wants to get an invoice every hour. I think the way this would work is that you'd enter the hourly price in the package, after hourly billing is enabled through some option there. You'd still have a term of say 1 month, and the customer would be charged hourly rate * 24 * 30 for the month. If they cancel early, a prorata credit refund of the remaining hours could be made. EDIT: Alternatively, we do nothing different in the configuration, other than to display the pricing on the order form as hourly. So, you'd save the price for the full term, and it would be converted to show the hourly price during checkout. I always thought this was a bit of a marketing strategy. 25 cents an hour sounds a lot better than $180/mo.

There's no automated way to do so, no. It would be a matter of updating the service to use the correct module row for the new module, and adding all the service meta fields that the new module expects.. and maybe something else I'm not thinking of at the moment. Basically, it's not supported, but you can give it a try at your own risk. We will be adding more cPanel Extended like features to the current cPanel module. We converted the client views for cPanel Extended to bootstrap for 3.2, so that module will work with 3.2.. but it also smooths out the views necessary for us to update our original cPanel module with these features more easily.

Would you say that you can create a package with a monthly term, edit it, add the one time, and remove the monthly to get past this issue? If so, that may be the way around it until we get a fix out.

Thanks for the report, not sure what's going on there. I've assigned this to CORE-1056 and we'll be taking a look at it shortly.

Settings > Company > General: Timezone. Ensure your timezone is set properly here. All dates & times are stored in the database as UTC, and displayed in the timezone selected.

Probably a good idea

CORE-1049, not completed yet. You can track progress through that link though.

I've added this to CORE-1055, tentatively set for 3.2

It's tentatively assigned to version 3.2, but it's not complete. This is one of those we hope to get into the next release, but it all depends on how quickly we can wrap up the must haves. It may be bumped to 3.3.

This belongs to CORE-547 and is tentatively scheduled for 3.2. It's not complete yet, and is not guaranteed to be in this release.. but because it's client related, and the theme for 3.2 is "client area" I'd like to see it.

Yeah, we finally got our project management system public so people can follow progress, view the roadmap. By default, all items are private, and we've been slowly opening them up as we work on them. Will probably make an official announcement next week, sort of rolled it out silently.

Consider this: You're typing something, and then you want to enter the predefined response. It appears as the end of what you're typing. Perfect. But it has no idea where your response ends, and where your signature begins. Either we have to enter the predefined response at the beginning of the reply, or the end. I'm sure a case could be made for both methods.

It's actually CORE-828. Not completed yet for 3.2, but if all goes according to plan it will be in there. A related task, CORE-961 allows for the selection of an entirely different set of templates for the client area. The main benefit here is that different companies can have vastly different and customized client templates.

CORE-828

I think all these pre-release licenses are going to start drying up and the resale market is going to go up.

Your rig is looking good! I need to ask my wife re: electricity costs. I know we pay somewhere between $50-$80/mo on average at home, but I'm not sure how that breaks down to KW/h.

The difference is Package Groups vs Package Option Groups. The video CubicWebs linked is a good one to watch for a basic understanding of Package Options. Package Groups contain 1 or more Packages Package Option Groups contain 1 or more Options On order forms, Package Groups are displayed like categories, with their member packages within them. When configuring a package to order during check out, package options will be requested, and ordered similarly within their package option groups. I hope this makes sense, and thanks for bearing with us. Our documentation can definitely use some help, we're updating it as we can and hope to be caught up soon.

We have more to do on this in the future, see CORE-1041

This is because register_argc_argv is disabled in your php.ini file for CLI. See http://us1.php.net/manual/en/ini.core.php#ini.register-argc-argv If you enable it, I believe it will correct this issue.

Yeah, patch just refers to the incremental release. You still want to overwrite your files and run /admin/upgrade in your browser.

Wow, that sounds like you've got that dialed in pretty well. 870Kh/s is fantastic. I haven't heard of sgminer before, how do you like it? The older version of cgminer I've been running (3.7.2) seems to be pretty stable, rarely crashes.

I'll second site5, uk2 brands (more virtual/dedicated), webhostingbuzz. Of course, there are a lot of hosting companies around the forums here too. Look up some reviews before you make a decision, and be sure to ask them if they support Blesta!

Before we make any feature changes to the coupon system, we need to refactor it. This is assigned to CORE-171. After we get this done, we'll be open to making feature changes.

It's currently assigned to 3.2, but it's one of those that depends on how much time we have left after we get the more critical items done. It may be pushed back, but I'd love to see it in here, so we'll see!

The only other thing you should do before logging into the new server is to re-issue your license. You can do this in the client area by clicking the "Manage" link next to your license, then Manage License, then check and save the re-issue option. It would also be a good idea to make sure the new server is configured to meet the minimum requirements. http://docs.blesta.com/display/user/Requirements