Paul

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

Hi Barry, when emails are generated are they queued for delivery? If you edit the invoice, is the Email box checked? If you aren't able to check quickly after they are created, you can create a manual invoice. Do the invoice emails appear in the mail log under Tools > Logs > Email? Are you using Sendmail or SMTP for outgoing email? Settings > Emails > Setup If an invoice is queued for delivery, then marked as sent, then most likely an attempt to send it was made and did not return an error. If you are using as SMTP server and the messages are being filtered out or rejected on that side quietly, then that could explain it.

ini_set is called throughout Blesta and in vendor code for legitimate reasons. In your case, /vendors/minphp/session/src/Session.php ini_set is used to set session variables. As far as I know, this has not changed recently, so it may be that a change to PHP 8 is responsible. We would probably recommend not disabling ini_set, but @Jono may be able to take a look when he has some time.

Yes, they would be able to request a payout when their balance meets your minimum requirement for a payout for matured funds. This is pretty common to have them make the request. In the future we may tie in an outbound payment option(s), after which automatic payouts might be a good feature.

When affiliates reach the minimum payout amount you set, they can request a payout. The payout request would be available under Clients > Affiliates > Payouts. Not currently, but the current version of the affiliate system is the initial release for the most part and we are open to adding additional features and improvements. You can make a request at https://requests.blesta.com for a specific feature You can create whatever payout methods you want, so yes, Venmo would be an option. Payouts are made manually after you receive a payout request. To add payout methods, go to Clients > Affiliates > Payment Methods and add 1 or more options.

Do you mean each TLD? TLD pricing is set individually per TLD under Packages > Domain Options > TLD Pricing. Just click Edit next to the TLD. If you mean giving 1 customer a different price than the TLD, you can set a price override for them.

In case anyone else experiences this issue, this case was due to /config/blesta.php missing pagination settings. This could happen if the config file is not writable during upgrade.

If you moved Blesta, make sure that you moved it correctly including copying ALL files + database. Review the big red note in our moving Blesta guide here https://docs.blesta.com/display/user/Moving+Blesta If you moved Blesta correctly, then it's likely your new server doesn't meet the system requirements. See the requirements here https://docs.blesta.com/display/user/Requirements You can temporarily enable errorReporting in /config/blesta.php by changing it's value from 0 to -1 and any errors may be output to your browser, but be sure to switch it back to 0 when done.

In the Edit Signature, HTML tab you can use the "Insert HTML" option to paste in raw HTML. Ckeditor removed the "Source" option, then later they added it back. We have a task to update Ckeditor again to re-gain this option per https://dev.blesta.com/browse/CORE-4597 Using Insert HTML, you should be able to accomplish what you want, it just isn't as convenient.

Confirmed, thanks for the report. https://dev.blesta.com/browse/CORE-4704

How are you searching the domain? What registrar module are you using? What version of Blesta? What version of PHP?

The Enom module does not yet support DNS Management, Email Forwarding, or ID Protection yet. This is a new feature, which has yet to be updated for all registrar modules who's APIs support the actions. See https://docs.blesta.com/display/user/Enom