Paul

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

You can modify this if you want, but I don't know if it will accomplish what you're trying to do. This code tries to replace Vultr branding so the client doesn't see it. But if you are seeing Vultr branding elsewhere, then it either isn't being replaced like this or can't be replaced like this. I would like to see what you are seeing.

Where are you seeing this? Screenshot?

To change the logo, edit the theme under Settings > Company > Look and Feel. If using the default theme FOUR for client or admin, you must first EXPORT it to your computer, then IMPORT it to Blesta so it'll be a new theme, then you can edit it and set your logo URL and select it for use.

You can add it to Blesta by unchecking the "Use Module" option, and then it won't try to add it through the Virtualmin API, just to Blesta. You may need to edit it after and update any fields like the username field though (and uncheck use module again) and save.

What does the Blesta module log show? Tools > Logs: Module, click on the cPanel row to expand and display input/output.

Also, to add.. if you want to have /index.php/ in your URLs, it's usually sufficient to just delete the .htaccess file included with Blesta from your server. That would certainly be the fastest way to get things working if you don't want to mess with your Nginx config.

Blesta URLs rely on mod_rewrite, an Apache module. Nginx requires a special configuration to rewrite URLs to index.php, otherwise you must add /index.php/ in front of your URLs. See https://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-Nginx for a sample config and required steps. If Nginx is running as a reverse proxy in front of Apache, then you shouldn't have to do this.

Yes, it asks you to enter a one-time password as you would be requested going forward to ensure that you have set it up correctly. Because if you haven't, then you would effectively lock yourself out.

I noticed. Stuff is happening in the background.

I don't have any ETA's. I have no reason to believe that 4.6 won't follow our typical release cycle, but I'm not going to make any predictions about the domain update. There will be a beta when we are ready for a beta.

@Amit Kumar Mishra The license has been transferred.

The only update I have is to say that we are adding a special feature to the core in 4.6 that will make the domain update possible in a future release. The feature we're adding in 4.6 is necessary to the foundation of the domain update, which can only come after it's completed. The feature is useful by itself also, and we'll release more information about it as we get closer to releasing 4.6.

I believe you can do this through the Vultr module, have you installed the free trial and given it a try? If you want to sell WordPress VPS's through another provider, then you'll probably need to make some customizations.. a startup bash script with an OS image that will install on first boot could work.

We don't copy code from other extensions into our own. If there are features of this plugin that you want to see in ours, then make a feature request for each one individually at https://requests.blesta.com

I responded to your PM. The license needs valid support & updates to be transferred, and cannot be pushed off to a later time.