Paul

Much better!

Version 4.5.2 is now available, please see the release announcement. Patching Blesta See Patching Blesta in the User Manual for instructions. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.5.2. For older releases see all Change Logs.

You can try uninstalling and re-installing the payment gateway, that may cause it to recognize the change if you translated it properly.

From the source docs, you may be able to use this for client login http://source-docs.blesta.com/class-ClientLogin.html API docs https://docs.blesta.com/display/dev/API That's where I would start.

Eeew. Hold my trash can while I fill it with my lunch.

Normally someone would have to buy the theme directly, and buy the integration from you.

Contact @Blesta.Store through the forums here via PM. Mike should be able to get you sorted.

Each extension has its own language, look under /components/gateways/nonmerchant/ for each gateway.

If you check the box, then Blesta will not store the cards. Checking this option is recommended. Blesta will store a token to use to charge cards.

You should be able to re-issue the license in blesta.store's client area.

Yes, as Tyson mentioned check the module log. Also check your firewall. Your Blesta server needs to make an outgoing connection to CWP, so your Blesta server should allow the egress connection and your CWP server should allow the ingress connection.

We do not make users create an account to start a trial for a couple reasons, including: More people install the free trial when we don't require them to create an account. I can say that this is true, because prior to Blesta v3 we did require them to create an account and way more people install the free trial now. There are many hundreds of active trials at all times. Not every trial user converts to a paid user, we don't want to collect names and addresses of people who aren't going to become a customer. I guess we could market to them, but in the end we care more about privacy -- and we want the most people possible to install a free trial, which they are more likely to do if it's easy and they don't have to provide any personal details. Maybe we should send an introductory email to users who install the free trial.. and actually, we have plans to do this to help users that have a trial. We can include more information about how to become a paid user and what they need to do. But we aren't going to make an account for them unless they place an order. Thanks for your feedback!

If you have the token, you may be able to create a payment account in the database directly that uses the token. The problem is that some other information may be missing. Also, we have not tested this, so I can't say for sure whether it will work, but I don't see why not.

We are considering a change or option that would allow the new term to take affect immediately. To get around that you could make the change, then change the renew date to the desired renew date and it will prorate that. There will be 2 invoices, but the sum should be correct.

And then it lets you continue?

When you check the box "Store Card Information Offsite" Blesta does not store the card number, just the last 4. It's no less secure than using Authorize.net with CIM for tokenization. Stripe just doesn't like that there is passthrough of card details. How safe it is is subjective, but I don't see anything wrong with it.

@mhofer We have deleted the bad language definitions that included "A Google translation is currently unavailable." and a new file zip download will be generated in the morning automatically. If you notice any other issues with the German translation, please copy down the language strings that are very bad and paste them in this thread. We can search to see what user is responsible for them.

I'll see about removing all of those records, and the file will regenerate. Any missing translations will fall back to English.

Please see https://docs.blesta.com/display/user/Stripe#Stripe-PossibleIssues

When upgrading to a different package and changing the term, the renew date is not changed. The prorated amount should reflect the difference between the current package and the new package for the current term. Then, when the package renews it will renew at the new term/period. For example, current service renews May 1, 2019 on a 3-month term. You upgrade to a package with a 1 year term. It will be prorated to May 1, then when it renews (on or near May 1) it will renew for 1 year.

For domains we suggest creating a package for each TLD, and assigning all to a package group just for domains.. call it Domains or whatever you want. Then you can add it in Blesta as a service to the client's account. When you add it, UNCHECK the "Use Module" option so that it doesn't try to register it. Then, edit the service and make sure the data is correct. I think logic boxes has an order ID.. the order ID should be correct. Uncheck "Use Module" again and save. You may also want to adjust the renew date so that it's in sync with the domain expiry. Each time uncheck "Use Module" so that the changes occur in Blesta only.

Now you can use No/None module instead of the Universal Module since you can create text field configurable options, but if asking for a domain or anything the Universal Module is probably better.

You could even do this over the HTTP API https://docs.blesta.com/display/dev/API via it's own cron, like what Tyson suggested but more standalone.

Welcome! You can take a look at extensions that ship with Blesta at https://docs.blesta.com/display/user/Extensions and on the marketplace at https://marketplace.blesta.com/#/

zomex.com and blestaintegrations.com do this