Michael

That's weird regarding your email, I see you're registered with that currently. Maybe the IPBoard Spam service had an issue with the address, because the email/domain is NOT blocked internally by us. We do block a lot of free email domains, but not yours.
I'd like to build a Lightsail module, a few people have asked for it but it hasn't risen to the level of demand we need to move forward with it yet. Anyone want to sponsor?

it's fixed in 4.6.x

1) Lightsail doesn't have a module built already but it seems like something fairly easy to create a module for.  You could even potentially use the universal module to call some scripts that manage it for you.
2) Domains are okay on a small/cursory level.  The basics work (registration/renewal) but are a bit rough around the edges on the admin side of things.
3) The forum is just Invision Community, if you email address has issues that is strange but it doesn't really reflect much on Blesta as a piece of software.

So you would like to integrate Blesta into your theme but don't know how to? Why pay for expensive integrations when you have to relay on them replying in time and giving you updates when you need them when you can do it yourself. If you can't do it I highly recommend you use a third party integration company. I personally recommend ExpertIntegrations.com but you can use Blestaintegrations.com, etc.

Today I will be using the theme Appy. It's a free theme if you KEEP the copyright otherwise you have to pay to have permission to do so.
Meaning you are not allowed to remove footer credits for that you must purchase a License.
 
Download the theme from: https://colorlib.com/wp/template/appy/
Extract the files to your computer and create the folder on Blesta in
/app/views/client/ In this tutorial we're calling it appy.
You'll need to copy the files from the default bootstrap folder to the new one appy.
After you want to upload the files from Appy to the custom theme folder you are creating.
/css /fonts /images /js /style.css
Next we need to add the images to the root of Blesta so the CMS can use them straight away. So simply copy the images folder to the root of blesta like so:


Back to the theme let's rename it to Appy.
In the folder:
/app/views/client/appy/ Find the following:
config.json with:
{ "version": "1.0.0", "name": "Bootstrap", "description": "Built on Bootstrap 3.1.", "authors": [ { "name": "Phillips Data, Inc.", "url": "http://www.blesta.com" } ], "require": { "blesta": ">=3.2.0" } } Rename the name to anything you like. I'm going with Appy. So mine looks like:
{ "version": "1.0.0", "name": "Appy", "description": "Built on Bootstrap 3.1.", "authors": [ { "name": "Phillips Data, Inc.", "url": "http://www.blesta.com" } ], "require": { "blesta": ">=3.2.0" } } Finally go to Blesta and enable the theme so we can start integrating the theme. Go to:
Settings > Company > Look and Feel Click on Template on the left and click Appy (or your chosen name).

There you go, you've now integrated your first Blesta theme.
Customers for the Premium CMS or have a Blesta license can download this integration already completed.
https://blesta.store/client/plugin/download_manager/client_main/download/42/appy-cms.zip
This post is reserved for any Questions you may have:
 
 
1. How to use the default Blesta logo but in white?
Find:
<?php } elseif (!empty($blesta_logo)) { ?> <img class="blesta" src="<?php $this->Html->_($blesta_logo);?>" alt="Blesta" /> Replace with:
<?php } elseif (!empty($blesta_logo)) { ?> <img class="blesta" src="<?php echo $this->view_dir;?>images/logo.svg" alt="Blesta" />

Correct you need a merchant payment gateway to use the dropdown card option but you can use Stripe and Square or PayPal for cards payments and you don't need a merchant account.

Hi, just to chime in on this.  Obviously it is still a work in progress but our goal in this process is to create a stripe integration that will address any security concerns that people have with the current one.  Primarily this includes adding 3DS through Stripe and using Stripe.js to save payment details without them every touching the Blesta server.   Both can be accomplished through the use of Stripe Elements through Stripe.js.  When I mention adding the ability for a gateway to modify the credit card form, that means for stripe it could use those things.  The 3DS process is already a part of Stripe.js and stripe elements as long as we set things up correctly.  That is not specifically laid out in the task so I hope to be able to update it and say more specifically and in depth how it will be implemented.

I think some things are getting mixed up in the comments on that issue.
Tokenization (stripe.js) has nothing to do with 3DS.
 
3DS/SCA is more about redirecting the customer to the website of his bank, to perform 2-factor-authentication there and authenticate the payment.
Customer not only needs a credit card number, but also confirm the payment through the app of his bank or a hardware token nowadays.
See the Payment Intents API for Stripe.

Paul is working with the guys to get Stripe 3DS and they are doing it in the core so other gateways can use 3D Secure.
Part of CORE-3068

I just tested this and didn't encounter that issue. One thing to consider is that if you are an admin whose language is set to English, you will see English even when you log in as a client whose language is set to Spanish. The client will see Spanish when they explicitly log in to their account (i.e. when you are not an admin masquerading as a client).
Another thing to consider is that when the language has not been completely translated in Blesta, there may be definitions that do not exist in Spanish, and so they will fallback to English.

Paul is working with the guys to get Stripe 3DS and they are doing it in the core so other gateways can use 3D Secure.
Part of CORE-3068

Our company is an .Eu Accredited Registrar,  and the .Eu registry - EURid, offers discounted registrations for the first year. We pass this discount to our clients, so is very useful to have lower registration pricing and higher renewal pricing.  

Welcome back again ?
in my opinion the renewal price is a good addition, sometimes you need to make a promo without offering promo code, this way you can offer promo for renewal or registering with a easy way. it left now the transfer price wit the same logic as renew price, the transfer price will be only used in order form as it happen only the first time of contract. after making a unified commands for domains modules will solve all other issues, after this two steps we can release our custom order form to the community. (used here https://nh.ma) we can't release it as we have some tweak in our modules and some core files .
 

With the increased demand in DirectAdmin from those migrating away from cPanel, we took a look at the module and made some modifications to improve it.
During checkout, clients will now only be asked for their domain (not username or password) Usernames and passwords are generated automatically (similar to the cPanel module) There is now a password generator when resetting a DirectAdmin password as a client or staff We'll include the updated DirectAdmin module with Blesta 4.7, but we're including it here for use now in currently supported versions.
Download Here:
direct_admin.zip
To Upgrade or Install:
Back up your installation. Unzip and upload to /components/modules/ to overwrite your current direct_admin directory. Visit Settings > Company > Modules to click the upgrade button for the module, or to install it for the first time. If you have any feedback, please provide it in this thread.

You can use this plugin to modify, create, or delete states and provinces. https://marketplace.blesta.com/#/extensions/1-States&Countries

Two of our Beta testers have allowed us to share their fantastic forums in our portfolio so we'll share them here too.
 

 

Be aware that using strong customer authentication methods such as Securecode/3Ds becomes mandatory when taking payments from European customers after 14 September 2019.
For subscriptions the first payment should be authenticated, but subsequent payments do not.
So all merchant payment gateways should be updated, or payment processing will simply stop working.
 
See the articles published by the various payment gateways for details. E.g.: https://stripe.com/en-US/guides/strong-customer-authentication

You never told us about any issues you were having, and you never opened any trouble tickets. Sales email is just that, for sales. We encourage everyone to install the 30-day free trial and evaluate before you buy, but I guess you didn't take advantage of that. You reported no issues post installation. You gave us no opportunity to help you.
</thread

Did you open a real ticket? as in account.blesta.com?
Languages depend on translate.blesta.com and why do you even have selinux enabled? most people disable it on Centos? 

it will have the license key for the trial and then Paul can pull up the IP and find the host, or something.

I recommend DirectAdmin.

Should do I'll make a new tutorial soon for you with 4.6.0.

Yes, the JavaScript file was updated to that in v4.4.

I just managed to solve this a minute ago.
Seems there is a change in blesta's template.
 
<script type="text/javascript" src="<?php echo $this->Html->safe($this->view_dir . 'javascript/app.min.js' . (!empty($hash_version) ? '?v=' . $hash_version : ''));?>"></script>

That would mean that the gateway is already installed, so you should look for it under the "Installed" tab of the gateway list.