Paul

That's right. With gateways that support tokenization, Blesta stores the last 4 encrypted and the expiry date. The last 4 are stored so the client can identify the card in the payment account, and the expiry so that the client can be notified when their card is expiring and needs to be updated. CVV data is NEVER stored in Blesta. If we implement token storage for eWay, it will then support both local and tokenized storage of card numbers. Some people prefer local storage, because it means they are not "locked" into using a particular gateway. Of course, tokens are much more secure and we recommend using token storage whenever possible.

http://docs.blesta.com/display/user/eWay Token Storage is not currently supported (I think this is it https://www.eway.com.au/developers/api/token), but would make a good feature request. Most likely it was not available when we initially implemented eWay.

Configurable options renew with the Package, so only the term and currency selected will be available. Selecting 1 month for the package will show all 1 month configurable options. If you need to be able to select different terms, and/or use a different module for the options, then they should be addon packages instead of configurable options. I'm curious though, why would you sell a dedicated server for 1 month, and extra RAM for 6 months?

Both are sent in the email, the HTML *and* text versions. If the customers email client can display HTML, then it uses the HTML version. If it doesn't support HTML, then it uses the text version. Both should always be updated when editing an email template.

CORE-1483

I'm not sure I understand what you're saying. If you are using configurable options for your extra drives, ram, raid card, etc then the price for the matching term will be offered. So, you can offer a matched discount on a longer term for the configurable options. Take a look at this example: This configurable option will add a drop down for IP addresses, 2 options are displayed in the screen, 6 IPs, or 14 IPs can be ordered. The price for 1 month and 3 months are different, with 3 months showing a discount.

We have plans for an IP management plugin, but our plate is full right now so it's going to be a while.

Nice and clean, looks good!

haha. Small update, but some good fixes. Now back to 3.4

Since it's a radio option, if "Do Not cancel" did not exist, and the user selected one of the other options by mistake they would not be able to unselect "At end of term" or "Immediately". They could still get out by clicking the "Cancel, do not change" button instead of "Save" but this might be more confusing.

Currently this would be done in 2 steps as an admin 1. Manually create the invoice 2. Manually bump the renew date In this case, the invoice is not physically linked to the service though, so the service would not be suspended if unpaid. The advantage of this method is that it allows the customer to pay however far in advance they want. It's not limited to a single additional term. The downside is that there's more work, and that it's not self-service for a client. How would you see such a feature being implemented, both as an admin, and as a client? What would this look like?

@MariusB, what version of Blesta are you running? The 3.3.0 official build should include the latest Multicraft module which addressed this issue. Thanks @naja7host

I see what you're saying, that makes sense.

It's called Cancellation Options because you can do more than just cancel the service, you can schedule it to be canceled at the end of the term, and even stop it from being cancelled if you previously scheduled it to be cancelled but later changed your mind. "Cancellation Options" may not be the best term to describe that, but "Cancel" would be misleading for the above mentioned reasons.

Service meta data (service_fields table values) can be encrypted with AES256. The module controls this, and an example is the cPanel module, which encrypts cPanel passwords. I believe module row data can also be encrypted, but Cody or Tyson will need to confirm.

Almost everything is now being assigned to no fix version, so that we can add them to a specific release as we plan out sprints. Previously, all tasks were assigned the next release, and then shoveled to the subsequent release if not completed.. it's not the right way to do it, and it's too messy. So, we're getting more organized

Good idea, CORE-1467

Yup, CORE-1324. I also suggest setting up 2FA for all staff, if you haven't already.

Have not decided if we are going to use that or not, open to other suggestions. The feature request forum is not terrible, but it's not really designed for feature requests either. Still, it gives us a pretty good idea what people want. When we hear "please add feature xyz" a lot, then we can't ignore it anymore. Making it easier for people to vote has it's upside, but also some people just vote for everything even if they will never need it.

I actually have useresponse.com written on our whiteboard here for possible consideration. Looks like they have a major new version in beta.

We are only fixing bugs and security related issues with the cPanel Extended module. You may be interested in this module - http://www.blesta.com/forums/index.php?/topic/3506-cpanel-module-enhanced-integration/

Also the OP mentions sending invoices once per day. This can be done under Settings > Company > Automation by changing the Interval for Deliver Invoices to 24 hours. Of course, you can't control the time that they are sent, but if the goal is to delay delivery such that the likelihood of someone getting an unpaid invoice that they are paying during checkout then it may suffice. Tyson's recommendation of disabling the delivery of unpaid invoices is probably the best solution however. Settings > Company > Emails. Edit "Invoice Delivery (Unpaid)" and uncheck the "Enabled" box.

Domain manager is a top priority along with mass mailer, and affiliate system. It's also the most complex, and is in the process of being spec'd out. I don't have a precise ETA on it yet, but a 3.5 or 3.6 is likely.

Are you using the Support Manager that ships with Blesta, or Support Manager Pro, a third party modification? I suggest testing with the Support Manager included with Blesta, verify that it is upgraded under Settings > Company > Plugins > Support Manager. If you are using the 3rd party plugin, it may need to be updated to work properly with 3.3.

Yeah, there have been too many tasks that just keep getting pushed forward, rather than assigned to the proper version. We're getting better about this, but it will take another release cycle or so to get everything organized well.