activa

Merchant processors are fickle. Braintree wouldn't take us because we bill quarterly. This in spite of the fact we have been in business nearly 30 years.
Stripe doesn't have a problem with our business model, so we'll stick with them.

You can do that in your blesta installation 
English Version : https://blesta-addons.com/order/main/packages/subscription/?group_id=7
French Version : https://blesta-addons.com/fr/order/main/packages/subscription/?group_id=7
Note the Plugin is not providing the languages translation . you should download them from blesta website .
 
 
 

all the world are agreed in this subject. Domains are services and should remain as services. how it should displayed and how the order form should treated is another story.
 

Hello,

By default it is set to upgrade instantly, however you can change your settings so that the upgrade only takes place after invoice has been paid.
To change settings, follow steps below:
Go to Settings > Company > Billing/Payment > Invoice and Charge Options
Scroll down and you can find this at very end: Queue Service Changes Until Paid
You can tick that and save the settings to enable upgrade only after invoice is paid.

the module should be uploaded to /components/modules/  do not upload to /components/plugins/  as is a blesta directory and is not pluggable to other third party addons .
and normally the final folders hosuld be like these /components/modules/universal_domains/

Hi all,
This worked well - thanks for the input.

the limit is based on the username not email address. so if the username is the email then is limited .

You can create manual invoices due in 30 days. If you want to also bill them in 30 days (on the invoice due date) you can configure this. If it conflicts with other billing, create a new client group with these settings for these customers.

Blesta version 4.3.0-b3 (BETA 3) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2018/06/15/blesta-4.3-beta-released/
This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT.
Please report any bugs you find in the v4.3 beta bug forum.
Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 4.3.0-b3.

For older releases see all Change Logs.

Blesta version 4.3.0-b2 (BETA 2) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2018/06/15/blesta-4.3-beta-released/
This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT.
Please report any bugs you find in the v4.3 beta bug forum.
Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Release Notes

See Blesta Core - Version 4.3.0-b2.

For older releases see all Change Logs.

The plugin can inject a item menu to blesta, see download manager,  order an support manager to see a example .

I think any update we would integrate for this would be to simply require a non-empty format to be set on the settings page.

beta release has been added to blesta-adons, only VIP members has access to test the plugin . actually we have upload storage, Custom Local storage, and dropbox as destination .
 

Oh great, thanks will install that tonight and let you know if I find any problems or have any suggestions :)  Great work!
 
 

In v4.3 you can delete a client and all of it's related information, including services.
Packages can be deleted so long as no services exist that use it. So in v4.3, if you delete your test client that has test services, you can then delete the test package afterward.

the second option is more logical .
normally it shoudn't register any transaction even if it register as pending . i think if the module return null in success or activate fucntion it wouldn't register a transaction and that is the normal behavior .
another option is to add field for url, so we can put a page url then when the client click pay offline button it redirect them to the page where we add offline payment information and/or a section to select from cms pages if installed could be nice also .
 

retention period is included in our first release for local backup only . then we will add it to cloud storage instances.
This already included in our plugin, we have two crons, 1 for database that has interval from min to 24 hours, so you can set  every 3 hours or  hours ect ... for files we have time, that mean the backup is run 1 time a day, also you can disable the cron to disable the files backups . 
we have the intention to have a internal settings for files to be (weekly or monthly ..ect )
exlude folders is not implemented yet, but we have thre option for backup folders :
Root Blesta Directory
Uploads Directory
Blesta Logs Directory
so you can check wich of them are included in the backup, so you can exclude Uploads directory that include the support ticket attachements.
Our Plugin is totally bulot to be more flexible in term of options and settings, so you can set a backup rule to include only database and send it to Dropbox, and other rule to include files to a custom local folder  or Dropbox ect ...

 

 
 

this is something I really want, retention period in one form or another.  I have Blesta backing up to an account in a different location and it hits 20gb often before I remember to remove the old backups.
Apart from file changes for support desk attachments I don't think the files change that often at all, are you able to have different period backups for files and database, for example?
Backup frequency:
Files - Weekly/daily/hourly etc
Database - Daily/hourly etc
Or whatever period is selected
Also for the file backup are you able to set a folder(s) to exclude as well?  We don't really worry about the email attachments files for the support desk and as time goes by that will just get larger and larger to a point where we would not want to be backing it up all the time, there is no reason really not to but there is also no reason to.  We do full cPanel backup before we make any changes so this backup is just for disaster recovery and email attachments don't rank for recovery.
 
Looking forward to this please do let us know when you finish it.
 
 

today we want to share with the community our upcoming release "Auto Backup System" .
this plugin is a revolutionary backup system for Blesta, it has some features that is not exist in Blesta and either in other Competitors. the New Plugin is making backups in two sense, Database and Files, then they are send to cloud storages system like dropbox and gdrive, amazon s3 (more storages will be added ) .
some features
- The backup System store the backup files and database in upload directory .
- The database backup is made with a native php function and not by the mysqldump command that a lot of hosting providers disable it for accounts .
- The backup system send files/database to configured remote cloud storages .
- Option to exclude tables from database .
we have the intention to add this features after the first release :
1 - Email Summary for the backup done
2 - Add Microsoft Drive as Cloud Storage
3 - Option To restore Files, Database
 
the plugin already done, and we are testing it in live production now to see the results .
What do you think? any feature you want to see in this plugin?

I've created a task for us to look into this in the future, CORE-2736

In 4.3.0 you can due to the EU GDPR.
 
Packages no.

Open up components/modules/logicboxes/config/logicboxes.php and add the TLD's that you want to sell (that aren't already there)

A package group can contain both restricted and non-restricted packages, and the group itself isn't restricted or not restricted. I would suggest mixing restricted and non-restricted packages in the same groups.
There is a known bug with this right now though, where the restricted packages can mess up the order form, causing all packages in a package group to be displayed incorrectly. Should be resolved in beta 2 this week.

They would request a copy of their data by whatever means you specify. The ticket system is likely to be commonly used, but you should define this in your terms as they relate to GDPR. If there is demand for it, we would consider adding a self-service option for this in the future, but most companies will prefer to perform the export and review the JSON file to ensure it doesn't contain any information they don't want to provide before passing it along.

If you are using funnels and collecting order amounts to pass into Google Analytics, then your embed code may look a little different, and you'd want to make user of variables and possibly page conditions to set the right values. I'll have to look at an example of this using funnels and see if it's possible to provide a generic example that'll work.
If you are not using funnels, and just want Google Analytics to appear on order pages, you can paste in the entire code and not use any conditionals.