Leaderboard

Custom fields are linked to the client group. If you want the fields to appear in more than one client group they need to be re-created for those groups. I believe Mike is referring to a previous discussion about being able to make the fields apply to all groups or easily clone them for multiple groups.

1. Two merchant gateways can be active, but cannot process payments the same currency. Merchant gateways are invisible to customers, all they know is they are paying with a credit card. 2. If you are not using tokens with BluePay (The official gateway does not support tokens), then you can switch to Stripe if you are using the "onsite" storage method for Stripe and not the token based method. So, you can switch back and forth between 2 or more merchant gateways if they all have the local/onsite storage method where Blesta stores the card details encrypted. If you switch to a gateway that uses tokens, any new payment accounts would be compatible only with that gateway and it would make switching to any other gateway difficult.

We've pre-made Blesta Integrations based on the Themeforest designs, so this is our little portfolio which we will update. If you need any support please contact our support team. All our pre-made themes also have a BlestaCMS Version for our customers. All pre-made themes are $5 per, you do however need the theme from Themeforest before you can get the theme from us. FlatHost Marketplace url: https://marketplace.blesta.com/#/extensions/7-FlatHost MyVPS Marketplace url: https://marketplace.blesta.com/#/extensions/16-MyVPS RealHost Marketplace Url: https://marketplace.blesta.com/#/extensions/18-RealHost[/size] Dataserv Marketplace Url: https://marketplace.blesta.com/#/extensions/19 Satria Marketplace Url: https://marketplace.blesta.com/#/extensions/28-Satria How cool pages you can make with the CMS plugin and the MyVPS theme: Cool things you can do with Satria:

No, there's no plan to allow logins via user IDs. User IDs are not shown in the system, so unless we make it available, admins/clients wouldn't know what ID to login with. Regardless, logging in with a user ID can present ambiguity. For instance, if one person has a username of "2" and a different user has the user ID "2", which person is logging in? Usernames need to be unique to avoid this kind of issue.

I was missing a simple step late at night and I got it taken care of. Thank you for your reply.

You have to have the same fields per client group and copy and paste the old value to the new one. This is going to be fixed soon I believe can't find the core number though.