Leaderboard

If such fields were added to core as opposed to using custom fields it should also be possible to disable them completely as not everyone will want to use these fields or even allow customers to fill them in.

it would be nice to see a option to enable/disable adding new contacts for clients . https://requests.blesta.com/topic/prohibit-clients-from-adding-new-contacts

Thanks mate!

Your bootstrap file isn't loading: http://pay.subportal.io/app/views/client/bootstrap/css/bootstrap.min.css Not found if you linked to mine: <link href="https://blesta.store/app/views/client/blesta_store/css/bootstrap.min.css" rel="stylesheet" type="text/css"> The CSS will be fixed, so somehow yours is broken.

Managed to fix it today by re-installing CentosWebPanel and installing everything from scratch was an ioncube issue.

You can use our Universal Paypal Gateway to use your native currency with PayPal even if is not supported by PayPal .

Personally i prefer to be in the core, and can be for the primary contact or additional contacts, this will make blesta support COPPA laws, for gender field is needed for some industry law firms or any other service provider for social issues. this issue i have already talked about it here

Yes its working with USD Option! Thanx for the help!

have you set the order form to accept PayPal, is the currency accepted on PayPal (ticked the box on the PayPal gateway for the currency).

First, very nice integration, looks great! If it's prompting the user to login again, the session is not being maintained. I noticed that you mentioned www. your domain, and later http://domain, if this hostname difference exists from the URL the user logs into to the link in your client area, it could explain it.

what is the best approuch to achieve this task by a custom plugin? Core Table - Update Services to include the destination client_id - Update Invoices to include the destination client_id - Update Transactions to include the destination client_id - Update Invoices to include the destination client_id - Update Contacts to include the destination client_id - Update Packages Set to include the destination client_id - Update Emails Log to include the destination client_id - Update Payment Accounts to include the destination client_id Plugins Tables if the plugin is installed - Update Tickets/Replies to include the destination client_id - Update Client Documents to include the destination client_id - Update Downloads Manager to include the destination client_id After changing/migrate all to the destination client account, we will make the old client account as inactive. is this all for the blesta system, or there are some other think we should think about ?