Paul

Hey welcome! Yes, you can ask for information during checkout as it relates to the service you're selling. If there is not a provisioning module for what you're selling, you'd be using the Universal Module. You can set up a product for the Universal Module under Settings > Company > Modules > Universal Module that asks for the fields you want (service fields section). If any of the questions/options you want to ask for cost extra, then they should be set up as configurable options (Under Packages > Options).

Order #'s are listed in Blesta under Billing > Overview as part of the Orders Widget. If you don't see an "Orders" widget, click "Manage Widgets" on the left, and drag it from the right to the left in the modal box to add it.

Do you have a reference? I predicted this in one of those previous threads. Logically, your server sends the markup for stripe.js, so if your server was compromised an attacker could modify that javascript to capture the card data anyway. It was a loophole that has apparently been closed as I suspected.

Ok, I think your support department/ticket issue is related to a transaction lock, which may be because of the missing pricing option in [1] above. The first step would be to fix that and try a new fresh import, things will probably look much better at that point. The importer is trying to import a null price, which means that price is likely null in whmcs and Blesta requires a value. I'll ask Cody or Tyson to take a look at the error and see if they can provide instructions for identifying the record that's causing the issue.

1. Check that your staff account has been added under Support > Staff, and has access to all departments. If you don't have access to all departments, it's possible the tickets were imported and you just don't have access to them. 2. WHMCS allows you to create credits out of "thin air", and Blesta creates a transaction for the total amount of credit a client has in an effort to balance their account. 3. What's broken with the transaction list? 4. Revenue reports are based entirely on transactions. Since you're importing from WHMCS, if Blesta has to create transactions in place of manually entered "thin air" credits that existed in WHMCS, then this will skew revenue reports. Filter out transactions of type "In house credit" to get a more accurate picture. The error: Integrity constraint violation: 1048 Column 'option_pricing_id' cannot be null on line 124 sounds like there was a missing price in the data being imported. Cody or Tyson may be able to provide more information on how to identify any such records in WHMCS and correct them prior to performing a new, fresh import.

Just FYI, this field can be disabled in the next release, 3.4 per CORE-547 and CORE-1443

TCAdmin is likely to be the next GSP module we write, but I don't have an ETA for you at the moment.

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.