Paul

You need to upload the .htaccess file that ships with Blesta, *and* make sure your server supports mod_rewrite, which is an Apache module. Then, URLs will work without index.php in them.

We typically do not merge 3rd party modifications into the core. At least not blindly. We adhere to a strict Programming Style Guide, and look at each feature individually. Often times, we'll choose to implement a feature in a different way than someone else has, if we feel we can improve upon it. This modification should be considered an unsupported fork (At least not supported by us directly, forums are good for community support), and users should be aware that it is incompatible with any future releases of our support manager. As is the case with any modification.

Registration only

Not sure what you mean by the order checkout stays the same. What do you expect to be different? If you're using a merchant gateway, the user is paying with a credit card or ACH, the gateway you're using is irrelevant to them. If it's a non-merchant gateway, like PayPal, a button should appear during checkout for that. If it's not, check Packages > Order Forms. Edit the order form, and make sure all the gateways you want to accept payment in are checked for that order form.

I remember making that video, and I love this feature. I use fractions for time based billing every month.

Ah, one time price option. I wonder if that's related to CORE-1056.

That's odd, it shouldn't affect changing the price. Anyone else experiencing this?

We discussed this in a ticket, but it did result in CORE-1066. Adding that here, for future reference, it adds an option to staff service management to add and edit recurring coupons.

Thanks for the contribution!

Multiple domain registrars can be used, with different TLDs going to different registrars. This is all set up on the package level. When you add a package, you select the module and what TLDs the package applies to. Then, you add your domain packages to a package group. During checkout, all TLDs valid across all packages within the group are available for order. The order system determines which package to use for the TLD being registered, which in turn determines the module. Just to add -- in the future, when we release the registrar plugin, a pricing matrix will be available. That will simplify the current method of having to have a new package for virtually each TLD (Or at least TLDs where the pricing needs to be different).

We issued a trial key manually for you (At least I think that was you!) and I noticed it has been installed. Everything working now?

If you've already had a trial, the same trial key will be fetched. Also, Softaculous should be performing the entire install, so all you should have to do is go to /admin/login to login. If it's requesting a trial key and admin setup then the Softaculous install may not have completed correctly.

Probably. You'd need to merge these changes with any future updates to the support manager if you want to upgrade. This plugin should probably be forked and renamed.

Did you remove any terms, or just change the price of an existing term? In 3.1, we made it so that terms can't be removed if they are attached to an existing service, because it effectively removes pricing from the service.

The purpose of the group is to allow staff members to subscribe to those BCC emails if they wish. Go to My Info > Notices tab to subscribe to notices that are allowed for your staff group.

The download manager allows you to restrict downloads by client group, or by package. If a user purchases a certain package, it can unlock the restricted download on the download page. Doesn't that work in this case, or am I missing something at this late hour

You're cranking along pretty nice for 1 GPU. Our rates are $0.13 tier 1, $0.18 tier 2, $0.27 tier 3, and $0.30 tier 4 per kwh, through Southern California Edison. We're in Tier 3, which blows my mind since we hardly use anything. Expensive.

I believe the goal is to keep it backwards compatible. Existing modules that are not updated to take advantage of features of the new plugin should work, they just won't make use of any plugin features.

Awesome, thanks for the contribution. I've added a note to CORE-1036, we'll review your implementation.

The PayPal subscription payment would be applied to the invoice though, it would just leave a balance still due on the invoice for the other services. That remaining balance could be paid separately. I don't believe they would be able to set up a new subscription, post order, for such an invoice though because we detect whether all the services are recurring before displaying a PayPal subscription button.

Nice mod! Mass operations are not a bad idea.

Services that are billed on the same day, are added to the same invoice, regardless of their term.

An option to require a user reset their password on next login is not a bad idea. That could potentially be used for new accounts like this. However, the password reset method that is currently implemented is preferable for that purpose. It allows the user to request a password reset, receive a time sensitive link via email, and change the password to one they want.

The license is legit and transferrable.

The task was originally tagged for 3.1.2 and 3.2.0, so we will make an effort to look at this for inclusion in 3.1.2, which already has some other completed items.