Leaderboard

We do have plans, in the future, to add an option when adding an order form, to choose whether to authorize only and capture when approved, or authorize + capture when checking out. However, as others have pointed out, authorize will only work for gateways that support it. So others would still need to process the capture immediately.

The translations you made today are not immediately available for download, and do not affect the overall statistics until the page cache is updated. It will say 94% until the page cache is updated, but will not be available in the download until the language files are updated with them, which usually occurs every week or so. I can have them updated later today or tomorrow, at which time you can download the updates and you'll see it increase from 94%.

From what I recall, this has always been supported by the Support Manager. As LicenseCart mentioned, you should check your Support Manager email templates to ensure the subject contains the {ticket_hash_code} tag as described here.

Update your multicraft panel to the newest version. They then have a auto accept eula under Settings > Scroll Down and you will see "Minecraft EULA". Simple as that.

That might be something we can fix. Note that it does not occur when setting up a server in the admin UI, but from the order form instead. The error I receive is "Please set a name for the server." CORE-1967

You would either need to manually cancel the service, or use the Auto Cancel plugin to control when suspended services should be canceled.

The database_version may not be the same as the version shown in the footer of the admin UI. The database_version of '3.6.0-b1' is the latest version. Don't change this value or you won't be able to upgrade. The exchange_rates_auto_update setting from the `settings` table is not the value you would want to look at for your cron as the value from the `company_settings` table is used instead. Be careful making modifications to the database if you're unsure how it will affect the system. I'm not sure why the cron key would fail to update from the UI. Are you using the PHPIDS plugin by chance? If so, you might try disabling it and then trying to save the cron key to see if it works then.

What you've described is normal. I believe the 0.02% statistic you are referring to represents YOUR personal contribution to the Spanish language. The 94% statistic means that 94% of the entire Spanish language has been translated from all contributors, while 6% still remains untranslated (i.e., no Spanish definitions at all). If your account has the setting Show Terms set to either In Order or Randomly, then you will automatically be asked to translate terms from the untranslated 6% first. After there is at least 1 translation for every definition in the entire language (i.e. 100% translated), then any additional translations provided will be accepted to improve the quality of the translated definitions.

It seems as if the Support Manager upgrades have not been run, but if you're not seeing an Upgrade button for the plugin under Settings > Company > Plugins > Support Manager, then something went wrong. Normally we would suggest rolling back to a backup of your database prior to the upgrade, and attempting the upgrade again. If that's not feasible, you could install the same version in another location (start a trial) and compare the support manager tables between installations. Your live environment should match, structurally, the tables and columns across both. If it doesn't you can manually create those tables or columns.

We do not ask for host name until the server is actually provisioned. Module includes source though so you can change it to your liking.

Hi guys! Sorry for the delay. We were waiting for the new domain management of blesta to be finished, so the whole thing was put on ice. However, we now launched our blesta installation without domain management, and are using a workaround with universal module... The module is used by us in production. However it is definitely not finished as a module that works out of the box for everyone. But maybe some of you can use it, or use it with some modifications, or even as a starting point for your own development. I already wrote about the functions a bit a few posts back: http://www.blesta.com/forums/index.php?/topic/1210-ispconfig-module/?p=27826 Some Info, if you want to try the module: In our company, we have a free domain for every customer who orders a hosting package. To replicate this in the blesta module, i added a "domain" field, which the user can fill out during the order. If the customer entered a valid domain, the module automatically creates a DNS-Zone in ISPConfig for the user, using the default dns template configured in ISPConfig. The domain is also shown in the blesta UI, so the customer sees it as "included domain" This is a workaround, because it would be better to manage this with a domain module, but as I mentioned above, we are still waiting for the new domain management before managing domains correctly in blesta. This "domain functionality" can be rather easily "pulled out" of the module though. Just search for the word domain, and remove what you dont need. (there are some TODO notes reagarding the domain/zone-file functionality in the code - check those out too) Reseller functions are not implemented at all. Be aware that this module is a work in progress, and definitely test everything on a testserver before using it. I used the cpanel module which was implemented by the blesta devs themselves as a "guideline" for this module. And by "guideline" I mean that I copy pasted vigorously. The reason for that is, that many of the functions (managing Servers, Packages, Services etc) are very similar in all hosting-panel modules, so it made sense to work with the structure that the blesta developers provided in their modules. I did not really test the server-groups and the "use first non full server" option that blesta provides. That is one of the parts I copied from the cpanel module... It should work, but don't assume it before you tried. Generally read the TODO notes in the ispconfig.php file - they may offer some insight.. Install instructions: Install module as usual Create a remote user in your ispconfig installation (system -> remote users) You need to add some custom functions to the remoting.inc.php file of ispconfig. This is described in the remoting.inc.php file I included in the module. Go to blesta -> system -> modules -> ispconfig -> manage -> add server Server Label: any name Hostname Master Server: the hostname of your server (or Master-Server if it is a multi-server setup) Remote user name: the name of the remote user you created in ISPConfig SOAP Location: Something like 'https://servername.domain.tld:8080/remote/index.php' SOAP URI: something like 'https://servername.domain.tld:8080/remote/' We usually use gitlab in our company, however for this project I set up a GitHub repo. This is my first GitHub repo - so bear with me. I didn't create any issues or extensive readme yet - if some of you are interested in continuing development and organizing some collarboration, just let me know. GitHub URL: https://github.com/thynan/blesta-ispconfig

That is a pity. If that module is ready to go @thynan, maybe now is a good time to release it. Then, @loading can get a refund and use Blesta.

This plugin gives insigt to those who want to authenticate users with something other than MySQL (though this can be used along with). It does require editing some core files, however, which I'm going to test against vQmod so this isn't necessary just haven't gotten around to it today. Installing this plugin is easy, just place it in the plugin folder. It also comes with a readme file to go over some things such as what needs to be edited and how. Some LDAP servers require TLS support to perform actions like updating records, so this plugin offers this feature in the form of a switch. This plugin also supports multi-company environments by having the admin creating the profile choose the company to select. Change Log v0.0.1-a Initial release Allows only authentication (i.e.: does not add user to LDAP server) Detects if account is staff or client (not heavily tested so please post any issues) GitHub repo: https://github.com/anzenehansen/Blesta-Goodies/tree/master/plugins/ldap_auth Download: https://github.com/anzenehansen/Blesta-Goodies/raw/master/ldapauth_plugin.tar.gz