Tyson

It sounds like you may not have installed his "CmsPages" plugin. He linked to it above in one of the posts.

Blesta always needs to check you have a valid license. If you decide to sell it to someone else later, why should your copy of it continue working?
I don't play the lottery, but if I did, it wouldn't change anything. There may be more money to spend making it better though.

Blesta always needs to check you have a valid license. If you decide to sell it to someone else later, why should your copy of it continue working?
I don't play the lottery, but if I did, it wouldn't change anything. There may be more money to spend making it better though.

it would be nice and totally usefull to have filters in transactions page (billing/transactions/) .
some times we need to filter by a gateway, amount or by dates ... ect. with the actual view i not possible we have ony option to order by or search option.

The module really should make several attempts at generating a username if one is already taken before it fails in Blesta. I've created CORE-3225 to look into adding that behavior.

The issue is a bug with TCPDF. See here. They have not yet included a fix in TCPDF.
You could fix this in your installation by updating /vendors/tecnickcom/tcpdf/tcpdf.php:6849 by commenting out the "return false":
if (!@TCPDF_STATIC::file_exists($file)) { return false; } to
if (!@TCPDF_STATIC::file_exists($file)) { //return false; } Note: I did not investigate what, if any, issues may arise because of this work-around.
I would consider updating Blesta to include a downgraded version (v6.2.19) of TCPDF for the last known working copy except that a security vulnerability was fixed in the same patch release as this issue.

You'll need to escape characters for JSON when entering them manually. In your example, the backslashes should be escaped:
/((?=.*\\d)(?=.*[a-z])(?=.*[A-Z])(?=.*[\\W_]).{6,18})/i  

You'll need to escape characters for JSON when entering them manually. In your example, the backslashes should be escaped:
/((?=.*\\d)(?=.*[a-z])(?=.*[A-Z])(?=.*[\\W_]).{6,18})/i  

In the Universal Module, you can define service options, which are fields that customers can enter when they order a service.
You mentioned using regular expressions to validate the input, which you can do by defining them in the "Input Rules" section for each of your fields as described in the Universal Module documentation.
e.g.
{ "hostname":{ "valid":{ "rule":["matches", "/^[a-z0-9]{1,24}$/i"], "message":"Please enter an alphanumeric hostname between 1 and 24 characters in length." } }, "password":{ "valid":{ "rule":["matches", "/^[a-z0-9\\!\\@\\#\\$\\%\\^\\&\\*\\(\\)\\+\\_\\-\\=]{10,24}$/i"], "message":"Please enter an alphanumeric password between 10 and 24 characters in length. You may also include any of the following characters: !@#$%^&*()+_-=" } } } My example does not enforce a minimum 1 lower case character, 1 upper case character, or 1 digit, but you can update the regular expression to whatever you need.

In the Universal Module, you can define service options, which are fields that customers can enter when they order a service.
You mentioned using regular expressions to validate the input, which you can do by defining them in the "Input Rules" section for each of your fields as described in the Universal Module documentation.
e.g.
{ "hostname":{ "valid":{ "rule":["matches", "/^[a-z0-9]{1,24}$/i"], "message":"Please enter an alphanumeric hostname between 1 and 24 characters in length." } }, "password":{ "valid":{ "rule":["matches", "/^[a-z0-9\\!\\@\\#\\$\\%\\^\\&\\*\\(\\)\\+\\_\\-\\=]{10,24}$/i"], "message":"Please enter an alphanumeric password between 10 and 24 characters in length. You may also include any of the following characters: !@#$%^&*()+_-=" } } } My example does not enforce a minimum 1 lower case character, 1 upper case character, or 1 digit, but you can update the regular expression to whatever you need.

@Tyson @MBH2006 @Nahuel
Hello
We have made some years in 2015 lol, long time ago a tool to map/move services from one module to outher   in this case was moving from "Blesta Universal Module" to "OpenSRS Module"
We only need the Services ID from Module A (cPanel) and Module B (Direct Admin)
Here is the code exemple on the Plugin:
public function install($plugin_id) { $sendreport = null; $module_A = array('1','2','3'); // put here the Service Package Id's from Module A $module_B = array('4','5','6'); // put here the Service Package Id's equivalent to Module A to migrate $module_migrate_map = array_map(null, $module_A, $module_B); foreach ($module_migrate_map as &$value) { $upackages = $this->Record->select(array("pricing_id","package_id"))->from("package_pricing")->where("package_pricing.package_id", "=", $value[0])->fetchAll(); $sendreport .= "Module A Package ID = ". $value[0]."\n"; foreach ($upackages as $upackage) { $upricings = $this->Record->select(array("id","period","term"))->from("pricings")->where("pricings.id", "=", $upackage->pricing_id)->fetchAll(); $sendreport .= "Module A Package Price ID = ". $upackage->pricing_id."\n"; foreach ($upricings as $upricing) { $gterm = $upricing->term; if ($upricing->period == "month") $gterm = ($upricing->term / 12); $sendreport .= "Module A Price Period = ". $upricing->period."\n"; $sendreport .= "Module A Package Price Term = ". $gterm." -> Original Term = ".$upricing->term." \n\n"; $sendreport .= "Module B Package ID = ". $value[1]."\n"; $opackages = $this->Record->select(array("pricing_id","package_id"))->from("package_pricing")->where("package_pricing.package_id", "=", $value[1])->fetchAll(); foreach ($opackages as $opackage) { $sendreport .= "Module B Price ID = ". $opackage->pricing_id."\n"; $opricings = $this->Record->select(array("id","period","term"))->from("pricings")->where("pricings.id", "=", $opackage->pricing_id)->where("pricings.period", "=", "year")->where("pricings.term", "=", $gterm)->fetchAll(); foreach ($opricings as $opricing) { $opricingid = $opricing->id; $sendreport .= "Module B Package Price Period = ". $opricing->period."\n"; $sendreport .= "Module B Package Price Term = ". $opricing->term."\n"; $sendreport .= "\n\n---------------BEGINING---------------\n"; $oservices = $this->Record->select(array("id"))->from("services")->where("pricing_id", "=", $upricing->id)->fetchAll(); foreach ($oservices as $oservice) { $sendreport .= "Migrate from A to B Imported Service ID = ". $oservice->id."\n"; $this->Record->where("pricing_id", "=", $upricing->id)->where("module_row_id", "=", "2")->update("services", array("pricing_id"=>$opricingid, "module_row_id"=>"3")); $this->Record->where("service_id", "=", $oservice->id)->where("key", "=", "user1")->update("service_fields", array("key"=>"domain")); $this->Record->from("service_fields")->where("service_id", "=", $oservice->id)->where("key", "in", array("opt1","opt2","pass","user2"))->delete(); } $sendreport .= "\n------------------END-------------------\n\n"; } } } } $sendreport .= "\n\n"; } mail("notify@mydomain.com", "Blesta - Migrate from Module A to Module B Report", $sendreport); } Hope this help someone  
Regards,
PV

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.

Hello
The Stack License team is happy to announce our free modification to the Blesta System Backups allowing you to use custom s3 endpoints such as DigitalOcean Spaces and StackPath Object Storage
You can view the modification at github.
https://github.com/stacklicense/custom-backup-s3-endpoints
If you want a custom s3 endpoint added just reply here or open an issue and we will get them added.
 

Hi everyone,
A new version of the ISPAPI registrar module has been released.
You can find the latest version of the module on HEXONET's website - https://www.hexonet.net/resellers/integration#blesta
More information you can find on Git too - https://github.com/hexonet/blesta-ispapi-registrar/releases
Happy domain selling with HEXONET's registrar module. ?
For support or any questions, you can reach us at - https://hexonet.support or help@hexonet.support

The module really should make several attempts at generating a username if one is already taken before it fails in Blesta. I've created CORE-3225 to look into adding that behavior.

The module really should make several attempts at generating a username if one is already taken before it fails in Blesta. I've created CORE-3225 to look into adding that behavior.

Blesta doesn't come with a ClientData plugin, which explains why it was not in your new installation of Blesta.
It looks like your ClientData plugin is a third-party plugin from @Blesta Addons. You should contact him if there are any compatibility issues.
 
 

The admin route you have set conflicts with other routes in the system, which is why you encounter that behavior. We may be able to resolve that issue though, which we will look into shortly. Thanks!

Having a specific solution is very useful, so if you can have a unique module dedicated to the management of each of your SaaS apps, then all the better. That makes it easier to manage changes granularly. The Universal Module (or even the None module) is there to use when you don't have a specific module or don't need one that is more complex than collecting a few extra fields and notifying you of an event.
It sounds like your solution right now may be to use the Universal Module until you create separate modules for your applications. Whenever you do that, you can make the packages using the Universal Module inactive, stop using them, and maybe even write an importer that will move them over to your other custom module. Whatever you decide to do will come down to what is the best trade-off for your business to pursue long term.

You don't want to upload the "Omnipay-Blesta-Module-1" folder to the server. You want to upload its contents. That folder should contain two folders: "components" and "vendors". Upload those to the Blesta web directory on your server. There should already be a "components" and "vendors" directory in Blesta's web directory, and the folders will be merged when you upload them. Then, you should have the gateways listed in Blesta.

You don't want to upload the "Omnipay-Blesta-Module-1" folder to the server. You want to upload its contents. That folder should contain two folders: "components" and "vendors". Upload those to the Blesta web directory on your server. There should already be a "components" and "vendors" directory in Blesta's web directory, and the folders will be merged when you upload them. Then, you should have the gateways listed in Blesta.

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

We'll have to duplicate the issue first and see what can be done to fix the ip/port. Not sure why that behavior would have changed with Multicraft though.

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

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