Paul

You don't have to sponsor anything. We'll continue to add features based on demand, and when this rises in priority over other heavily requested items we'll consider adding it. Sponsored development lets you put your money where your mouth is. We find that people will up vote all kinds of features, but when they are willing to actually pay for them they show that they really need it. If you're not willing to pay for it, then it's probably not much of a requirement for you. Every feature we add has an internal cost to us, often significantly so, so we have to prioritize based on demand. Regarding paid modules, that is an option, but a module that only 3 or 4 people would use would be priced considerably higher than a module 3 or 4 hundred people would use. Modules that drive demand are already being created by 3rd party developers, quite a few of them, actually. But an authentication scheme is neither a module or a plugin, but a core feature, one we would not be able to charge extra for.

You want to sponsor it? Demand hasn't exceeded demand for most other new features we've been adding.

Are you sure you have enough disk space? Unable to create files and database tables sounds like maybe you're out of disk. I'd recommend trying to install manually https://docs.blesta.com/display/user/Installing+Blesta it's pretty painless.

Thanks, we've created this task https://dev.blesta.com/browse/CORE-5062 It's less so a bug and more so an oversight, so it's scheduled for 5.11.

If you're running 5.9.0, clients may not be able to open tickets while authenticated. A simple solution, pending an official patch release is: Edit /app/models/blacklist.php around line 255. Look for: public function verify(string $input, string $type) Replace with: public function verify(?string $input, string $type)

This should be corrected in the updated module included with 5.9.0.

Have you tried in 5.9.0? The module was updated.

What version of Blesta is this? Does the mail server have a valid SSL certificate? It may not. Make sure the TCP egress ports are open at your firewall. If you have SSH access to your server, you can try to telnet to the mail server over the port to see if it responds. telnet mail.server.com 587

There's a query at the bottom of the docs here https://docs.blesta.com/display/user/Migrating+to+Blesta that can assist in converting from Generic Domains to a specific registrar. This will update ALL TLDs from Generic Domains to a registrar you specify in the query. If you run it, make sure you enter the correct registrar, and backup your database first in case something goes wrong.

I received an error trying to add a domain with connectreseller as an admin, and created this task https://dev.blesta.com/browse/CORE-5051 It may be related. Do you experience the same issue?

Is the transfer initiated? Once a transfer is initiated, there is no need to keep the EPP code. Did it show up in the module log? Tools > Logs: Module

This may be related to https://dev.blesta.com/browse/CORE-4986 which is resolved in 5.9, currently in Beta.

We need more context to the issue. If this is step 4 on the order form, which order template is it? What payment gateway are you using? What version of Blesta is this? Do you have any customizations or 3rd party extensions? A payment account implies you are using a merchant gateway. Try deleting and re-creating the Payment Account. Check your gateway logs under Tools > Logs : Gateway

You can check Tools > Logs > Module log to see if there are more details when trying to provision. A 500 error is outside of Blesta, it could indicate you don't have enough memory_limit in your PHP, it could mean there are networking issues and it can't connect to your Plesk server (DNS, routing, Firewall). First step is to check module log, then try to provision manually in Blesta by clicking Manage for the pending service and click to activate it, while also watching the ../logs_blesta/ logs for any errors. If the logs do not exist because they can't be written, make sure your server has read/write access to the directory. Settings > System > General contains the paths and will tell you if it's writable. Check the log file ownership to make sure there's not a conflict.

Under Settings > Company > Billing/Payment > Accepted Payment Types ~/admin/settings/company/billing/acceptedtypes/ you can disable Credit Card and ACH for the entire company by unchecking the boxes and saving.

Upgrade docs are here: https://docs.blesta.com/display/user/Upgrading+Blesta To summarize: Backup your files + database Upload the new full release (not a patch). When going from 4.3->5.8 it's highly recommended you first go to 4.12.3, then 5.0.3. You're 17 versions behind. Backup files + database separately after each successful upgrade. Any errors during upgrade roll back. Always upgrade to the newest patch release in a version. major.minor.patch. Note that per the docs the system requirements changed in 5.0, you may need to adjust when going from 4.12.3 -> 5.x Any third party extensions or customizations may cause problems, check if they have compatible releases. To migrate Blesta read the docs here https://docs.blesta.com/display/user/Moving+Blesta at least the big red box at the top.

Adding that sub-domain functionality to Virtualmin would probably be about $500 USD to sponsor (We make the change, provide the updated module to you, and give you a shout out on our blog when we ship it with Blesta). This would add the same functionality on the Package configuration as cPanel has for setting your own domain/domains to offer subdomains at, then the user can select the domain and enter their desired subdomain during checkout. The cPanel module checks if there is a DNS record available to determine availability, if you are using Virtualmin DNS servers, then this should work similarly. Alternatively, there are 3rd party developers that could make this change to the Virtualmin module, they can usually be found on our Discord.

After you configure your TLDs and pricing under Packages > Domain Options, create an order form of the type "Domain and Other" under Packages > Order Forms. This will create an order form with a domain search box, then continue to hosting plans as you've assigned to the order form.

It's possible with the cPanel module, but would require a modification to do this with Virtualmin UNLESS you just tell the user to enter a subdomain at one of your domains. You can tell them to enter something.domain1.com or something.domain2.com, if they do it correctly then it should work, but the module itself doesn't support selecting a predefined domain like the cPanel module does.

We don't usually recommend using a beta in production, that's up to you, but since the module was just added in 5.9 that would be the version to use. You may also be able to download 5.9.0-b1 and unzip it and copy the module from the beta to a 5.8.2 installation, I believe it is compatible.

That would be best implemented as a plugin, and it's certainly possible. For Trustpilot, a lot of people automate that by creating a staff account with limited permissions and using the Trustpilot email to subscribe order notices or BCC emails, I forget which. That would allow Trustpilot to solicit reviews from new customers automatically.

Clear your browser cache. Either you have some CSS cached or didn't upload all the files for the 5.9.0-b1 release. It shouldn't look like that.

The package_pricing table contains the relationship between the Package ID and the pricings table. packages.module_id contains the module ID which links it to a particular module. package_names contains the name of the Package, which matches the TLD likeu ".com" in package_names.name. I hope that helps, I can't write a query for you but one of our devs or a community developer may be able to do that via our Discord developer channel.

Those are loaded from gravatar for the staff's email address. You can update the picture by updating it with gravatar. https://gravatar.com/

You maintain a separate excel/csv file with all TLD pricing? How is that updated? All pricing for everything in Blesta is stored in the pricings table, but you can't look at the records there and immediately know what TLD a record is for. It should be possible to write a query to export the pricings.id for all terms and TLDs to add as a column to your CSV, then with that relationship, you could update the pricing directly in the pricings table. Alternatively, you could update the registrar module you're using (if it's just 1) and change the way the price sync's so that instead of pulling it from the registrar API, it pulls it from your CSV file. That would allow better automation, because you could leave the automatic price sync enabled with 0 markup, and just replace your CSV file and it would update pricing on schedule.