Paul

Under Packages > Order Forms, click to create an order form or edit an existing. For "Type" select "Domain and Other". For Domain Package Group, make sure "TLDs Pricing Packages" is selected, and under Package Groups drag any hosting package groups from the right to the left to assign them.

Currently the flow for domain and hosting orders, using the "Domain and Other" order form type, is to enter or search for a new domain first, then select the hosting plan after that. It sounds like you want to reverse this, and choose a hosting plan, then decide on the domain, whether to register a new domain, use an existing, etc.?

This was completed in Blesta 5.7.0

You're right, to do this currently you would update the primary contact (the client)'s details with the new contact, even if the new person already exists as a contact. It's a good suggestion, if it's not already at https://requests.blesta.com that would be the best place for it. Seems like something we'd be willing to do. We'd have to work out some details, as the permissions scheme on a contact does not apply to the client, and contacts are not required to have a login at all. Might be more of a "Update client from contact XYZ" kind of feature, but we'd need to explore it more.

The dates include time. A user may sign up at say 11am on Feb 5th, in which case the service coverage for 1 month would be 11am Feb 5th through 10:59:59am Mar 5th. Feb 5th to Mar 5th, but neither Feb 5th or Mar 5th are for the entire day.

We're reviewing a fix in this pull request https://github.com/blesta/module-namesilo/pull/74 Anyone having this issue can test the code in the pull request.

ModulesGarden appears to have removed these modules from their website for Blesta. Closing this thread.

Hi Jean, PHP 8.1 produces a lot of deprecated warnings, we are updating the code in each release to reduce this, but it's a side effect of running the latest supported PHP version at the moment. You can roll back to PHP 8.0 (with sourceguardian patch) or 7.4 if you want to reduce that, or make sure you're running the latest version, but everything should work fine either way. You just might have larger than usual log files for the next couple versions of Blesta as we update the many things that need to be updated. No vendor code can be updated independently, you'll want to be sure to run the official Blesta files, including any/all vendor libraries we ship with it.

The first thing I would do is clear the browser cache. Either files are missing or the cache needs to be cleared, as far as icons and buttons go. On the Dashboard, you should click to view XHR in the network inspector to see the AJAX requests the widgets make, and also make sure the widgets are enabled for the page under "Manage Widgets". Either it's not trying to load the widgets or there is an error loading the widgets. Also make sure, if this is PHP 8.1, that you are running 5.6.1 of Blesta, and if you've upgraded recently, that you've run /admin/upgrade in the browser. If your PHP is missing something important, you can find out by uploading a fresh copy of Blesta to a SUBDIRECTORY and accessing in your browser to launch the install wizard. Don't install, but review the system requirements check. You can delete the directory you created for this after without installing. The error messages you've included don't look like they are related. PHP 8.1 produces many deprecated errors, which is normal at this time.

You should never edit Blesta's CSS files directly. As with most applications, it is better if you create your own overrides.css file with your custom styles, and then simply load it in /app/views/client/bootstrap/structure.pdt after the other CSS files. This will let you update any styles you want by overloading the default styles. Some of Blesta's CSS files are dynamically generated, and editing them will cause any edits to be lost on upgrade.

The error about the EPP code means that the module doesn't support it. Per https://docs.blesta.com/display/user/Logicboxes the EPP code is technically supported, but not controlled through the Domain Manager. I believe in this case, you'd need to enable the option manually on raw Package. "Invalid Package group ID" sounds like something important may have been deleted. By Default TLDs are assigned to a Package Group called "TLDs Pricing Package". If this package was deleted, that could explain the issue. If that was the case, and you're not too far along, I would suggest uninstalling the Domain Manager plugin, and re-installing it, and see if that resolves.

Looking good!

Have you looked at the "Offline Payment" gateway that's included with Blesta? It allows a description to be set to communicate how payment can be made manually. Then, staff would record payment in Blesta once received. You can update the language to change the name of the gateway, or create your own based off of this gateway. To create your own, start with the Extension Generator plugin in Blesta and compare to the Offline Payment gateway.

Is there anything in Tools > Logs: Module log?

Thanks for the update. Yes, it checks for a valid MX or A record on the DNS to make sure it's a valid domain. Not having a working resolver will do that. Glad you figured it out!

You should open a ticket so we can reply to verify that it is a legitimate license and can be transferred. Then you can post the proof here and anywhere else you have listed it.

Did you find a solution to this? What version did you upgrade from? As far as I know, nothing has changed recently with Namesilo DNS. Are you using the official version?

1. Does the client have any contacts with login permissions? Contacts that login will link to the client, and the name of the client may not match the name of the contact. 2. There is a hotfix for this in this task https://dev.blesta.com/browse/CORE-4771 and a resolution shipping with 5.6. You may apply the fix to 5.5.x

I've re-assigned the task to 5.6.0. We will try to resolve during the 5.6 beta, to hopefully have a solution by the official release.

Yes, but you should use the latest release, Blesta 5.5.2. There are PHP 8 fixes since 5.4.

Blesta Addons has been a bit non-responsive, we're not sure what happened to him.

We have a task to more fully automate this and someone will be looking at it soon. It will require an update to Blesta, so it would be part of a future release. In the meantime, if you know your license key you can reach out directly and request that any hostnames be added or removed from the license.

Interesting, I'll mention this. I think the IP address is required as part of the API call. Perhaps the IP should be defined on the server/module row rather than the Package, in which case it would use the IP as defined there. Is there ever a need to select a different IP for the same server between Packages? That would be the concern there. The alternative at the moment, would be to select a server instead of a group for the Package, but obviously this would have to be updated more frequently.

We have a task CORE-3942 to allow a single login to access multiple accounts. This has not been in high demand, and the inability of a client to use the same username for multiple companies is not a bug. We'll take another look, it would be a nice to have feature. Would you be interested in sponsoring it?

We've created a task for this, see https://dev.blesta.com/browse/CORE-4756