Paul

It's possible to make changes to routes in /config/routes.php If you're asking why we haven't for some reason changed the default route, there are multiple things at play as to whether we accept a suggestion. 1. How many people have asked for the feature? In this example, only 3 people have replied to this thread in 9 years which suggests the demand for such a change is extremely low. 2. We also consider whether the change fits with our goals for Blesta, and whether it would have a negative effect on anyone. Changing the URL to the knowledgebase for thousands of Blesta users would have a negative impact on existing links for existing installations. I hope that helps.

Under Packages > Package Groups, click on the Group name and then drag and drop the Packages into the desired order. Like so: If you want to make a particular price the default option, edit the Package and check the box for "Default", like so:

We weren't chatting via email recently were we? If not, I've recently been discussing the display of configurable option value data on invoice line items with someone else. It's likely we will be adding a setting for this, at least as it relates to invoices. I've asked someone on the team to make a core change to add this data to invoices, that we could potentially share, and then we'd add it as a setting in a future release. That change relates to the actual invoice itself though, and not the cart summary, but that is another area I think we'd be willing to explore.

What kind of questions do you add? Maybe an example will help with a recommendation. However, if there's not a module for it I would recommend using the Universal Module and creating service fields for any questions/details you need. If the field will affect the price, then the field should be created as a Configurable Option under Packages > Configurable Options, by creating the option, assigning the option to an option group, and assigning that Configurable Option Group to the Package itself.

If you are running 5.10.0, 5.10.1, or 5.10.2 you can use the 5.10.3 patch. It works as long as you are running 5.10.x. If you were running 5.9.x or older, then you'd need the full version. DO NOT use the hotfix-php8 directory unless you do not have ioncube but instead have sourceguardian. Default files work for PHP 7.2, 7.3, 7.4, 8.1, 8.2, 8.3 with Ioncube.

Does your DA server have a valid SSL certificate on the secure port? Is the secure port open at your firewall for egress? Those are 2 reasons that it may not work with SSL.

The / URL of Blesta by default is the Portal page. If you uninstall the Portal plugin under Settings > Company > Plugins, then / will redirect to /client/ and if the client is not logged in they will be prompted to login. Does that accomplish what you are after?

What version of PHP are you running? Under Settings > Modules > Universal Module, edit the product. What service fields do you have set and what are the options? A screenshot would be helpful.

I'm not able to reproduce this, what version of PHP are you running? What version of Blesta is it? I tried "Invoice Creation", and "Transactions Applied", with CSV and the report was downloaded. PHP 8.2.

If the issue is that email sent from the support system is coming from support@my.rippinhost.com then there are 2 places in Blesta to check for this. Under Settings > Company > Emails, edit all the templates for the "Support Manager". On ticket receipt, the template used to auto reply is "Ticket Received". Edit and check the From Address. Now, there is an option to OVERRIDE the from address on the templates on the department. Support > Departments: Edit. Make sure the department email is correct, and the option "Override the from address set in email templates with the email address set for this department" is checked.

There is a temporary code fix in the comment on the task https://dev.blesta.com/browse/CORE-5237 An official fix will be in the next release, but if you follow the steps in the comment you can get it working now.

The hostname should not include "https://" in it, here's an example of another TLD from the file: {"zone": ".com", "host": "whois.verisign-grs.com"}, the host should be the whois server for the TLD. You'll need to add a line for each extension. I tried to find what the whois server is for .pk, but they seem to have implemented something non-standard, a webpage lookup essentially than a true whois. However, I did a test with whois.pknic.net.pk and I got a response, so I would suggest trying it with that hostname. # jwhois -h whois.pknic.net.pk domain.pk [Querying whois.pknic.net.pk] [whois.pknic.net.pk] # WHOIS .PK Domains (PKNIC) Domain: domain.pk Status: Domain is Registered Creation Date: 2006-01-20 Expiry Date: 2026-01-20 Name Server: carol.ns.cloudflare.com Name Server: johnny.ns.cloudflare.com Name Server: Name Server: So maybe something like this might work: {"zone": ".pk", "host": "whois.pknic.net.pk"},

Congrats on the new marketplace! Looking great! I hear people are waiting on the release of the new Virtus theme.

The license is eligible for transfer. Seller must open a ticket to initiate a transfer and pay the transfer fee ($25) when ready. Support and Updates is current so that does not need to be renewed first (Until after June 15, 2025).

We have a sample configuration for Nginx here https://docs.blesta.com/display/user/Installing+Blesta#InstallingBlesta-Nginx but Nginx use should be reserved for experts. The sample config is reported to work pretty well, but that doesn't mean it's perfect. If you've copied the important bits from the sample config and still have problems, you might consider switching to Apache.

The TLD list is included in /components/modules/generic_domains/config/generic_domains.php You can try adding the TLD to the list exactly like the others. If the whois library has support for the TLD for looking up availability, then than may be all you need to do.

Deleting a client within the interface also removes any/all data associated with that customer. Transactions, services, etc. Only clients with no active services or open invoices can be deleted via the UI. If you simply delete the client, you may be leaving orphaned data. I would recommend digging deeper into how the delete client code works, it's possible you need to perform some other steps also.

This has been added to version 5.11 already, so it will ship with 5.11 when released.

You need to determine what module is required. MyOrderBox sounds like Logicboxes, but I'm not certain. Registrar modules can be installed under Packages > Domain Options: Registrars. TLDs configured under TLD Pricing, and to sell create an order form (Packages > Order Forms) of the type "Domain and Other".

If this is the settings in the module for limits, then yes, set a reasonably high number for what you expect to fit on the server.

Hi there, the default is no limit. When creating a Package, just leave both these options Unlimited.

Can you provide some details/context? By WEB3 domains are you talking about crypto domains that do not work like typical domains? How would you see this working with Blesta? Please be specific.

It looks like you are mixing the old Package method with the domain manager. The domain manager automatically creates and manages hidden Packages, so all your pricing should be set under Packages > Domain Options ONLY. The domain manager also never enables more than 1 TLD per hidden Package, that will break everything. You should delete any manually created Packages and use the Domain Manager to create your TLDs only. If the module does not support TLD import or price sync, then you need to add them manually in the pricing grid under Packages > Domain Options > TLD Pricing. Click the "+ Add TLD" button to manually add new TLDs one at a time, then click Edit to set pricing, and enable after pricing is set.

That will likely cause other issues and we do not recommend anyone do this.

Looks like a bug, I've created the following task: https://dev.blesta.com/browse/CORE-5237 If you are not selling domains on the other company, you can uninstall the plugin. Then you should be able to install it on the other company. This one may be fairly complex to resolve.