Leaderboard

What do you mean by this? Also, Form::fieldText is generic. While it defaults to 'text', you can override this with attributes, e.g. // Email field $this->Form->fieldText('name', 'value', array('type' => 'email'));

In addition to naja7host I've added some code so the selected language stays selected: <?php if (!isset($this->Session)) Loader::loadComponents($this, array("Session")); ?> <form method="GET" class="form-inline text-center"> <select name="set_language" class="form-control input-sm" id="set_language"> <option value="en_us" <?php if ($this->Session->read('language') == 'en_us') echo 'selected' ?>>English</option> <option value="fr_fr" <?php if ($this->Session->read('language') == 'fr_fr') echo 'selected' ?>>French</option> </select> </form> <script type="text/javascript"> jQuery(document).ready(function() { jQuery("#set_language").change(function() { jQuery(this).closest("form").attr('action', window.location.href); jQuery(this).closest("form").submit(); }); }); </script> Just in case anyone needs this.

I bumped CORE-562 into the short-term bucket. Naja's events thread is a good one, but it has a lot of events in it and it's fairly old now. I'm interested mostly in a short prioritized list of most needed events.

This issue is fixed in CORE-2011 for v4.0.0 of Blesta.

You should be able to find the IP address by clicking on the service table row. As an admin, go to the client's profile page. In the Services widget is the list of services. Click on the table row (not the links) for that service. A section will appear below it that shows you the username and IP address. The same can be done in the client interface. I'm not sure if SSH credentials are available via the API for them to be displayed in the UI, but if so, the module would need to be updated to fetch them. Currently, only the VNC console information is fetched for the console page. For the email that the client receives, you'll need to set tags in your package welcome email template in order for them to be included with the Service Creation email. These are the tags with a brief description: {service.proxmox_vserver_id} - VM ID {service.proxmox_hostname} - The hostname {service.proxmox_node} - The node ID the VM is on {service.proxmox_type} - VM type [openvz, qemu (KVM)] {service.proxmox_username} - Account username {service.proxmox_password} - Account password {service.proxmox_cpu} - Number of CPUs {service.proxmox_memory} - RAM in megabytes {service.proxmox_hdd} - Storage in gigabytes {service.proxmox_netspeed} - Network speed in megabytes per second {module.host} - Proxmox server hostname {module.port} - Proxmox server port If you want the ip address to be available to the welcome email, you'll need to update the module. Open /components/modules/proxmox/proxmox.php and find this line: 'service' => array("proxmox_vserver_id", "proxmox_hostname", Update that line to: 'service' => array("proxmox_vserver_id", "proxmox_hostname", "proxmox_ip", Once that is updated, this tag will also be available to the welcome email template: {service.proxmox_ip} - The IP address

This issue and another bizarre one seems to be resolved now.

It's a nice addition. I just hate to see templates making calls to the session. I think you can use the configured language, no? // User's language $language = Configure::get('Blesta.language');

Hello all, this thread will show you how to add a langaueg selection for clients/visitors . first thing , the admin tools plugins should be installed and activated to get this working . now what we should add is the language selector in the cleint area , something like <form method="GET" class="form-inline" id="change_language"> <label for="set_language">Language:</label> <select name="set_language" class="form-control input-sm" id="set_language"> <option value="en_us">English</option> <option value="fr_fr">Français</option> <option value="es_es">Spanish</option> <option value="ar_sa">Arabic</option> </select> </form> you can add your own html markup but you should conserve only the selector name "set_language" . didn't change GET with POST form . also add the jquery code inthe footer of the view // Process change Language request $("#set_language").change(function() { $(this).closest("form").attr('action', window.location.href); $(this).closest("form").submit(); }); note any language should be exist in your blesta installation . now the clients/visitor can change language in the client portal/login/order page . best regards

More features and other things in the pipeline Including new features suggested by LicenseCart aka Michael Dance. This release will come out soon though I am not going to say any release date to keep my sanity lol and to make sure I don't have to rush to release it at said date to make sure it is the best it can be including being tested & quality assurance tested!

hello all ... is long time that i have not come here for some projects .I have found that the cart/index page has a no closed html tag . no sure where but I support is in the cart.pdt . I have check this multiple time and I have the same result . a missing HTML tag in that page . to reproduce this just use the standard template and go to the cart index page , even if is empty . you wil fond a missind HTML tag .

The received date issue is resolved in CORE-2069 for v4.0.0 of Blesta.

That's a really great deal for 12 Years!

Found a small typo by accident I was not going to order, but to check how the site works: https://eidolonhost.com/billing/order/config/index/vps/?group_id=22&pricing_id=25 I guess it should be 12 MONTHS not years! Otherwise seems pretty good offer.

From them or here. https://docs.blesta.com/display/support/Getting+Support#GettingSupport-SupportAccess Yes it does. Yes it does.

The company language will be the default when not logged in, and en_us will be the default if no other language is known. I haven't looked at the AdminTools plugin, but I think it should probably be setting the language like this: // Selected language $language_code = 'en_us'; // Set the language Configure::set('Blesta.language', $language_code); Language::setLang(Configure::get('Blesta.language')); Then the configuration value I mentioned above would be accurate. The system also uses this configuration value for various actions/queries and does not look at the session, so I think it's important that it be updated.

these this

Great! Thanks for the update. Cheers

@naja7host are there any specific events that you would find particularly useful that I can look into? Ones that you would use? We can't add a whole bunch of events, there isn't enough time for it, but it *might* be possible to add one or two, or at least get those prioritized.

Currently Using v2, and I will only selling Steam Games GMOD, CS:GO, TF2. Those are the 3 games that we are going to start. Then we might sell ts3 servers.

Hi! No, we don't have any updates yet. The module works for our (rather restricted) use at the moment, so we won't continue developing it until the new "domain management" is released with blesta core. When that happens, we plan to upgrade and extend this module. As far as I know, that will happen with Blesta 4.1 (fingers crossed).

i suggest adding the type "email" in the form helper class . that way we can use some validation jquery to that input . input "email" is a standard now in HTML5 .

ohh , yes , your code is working , i have thought that the input type aren't override by the attributes .

Updated ... 1.0.1 now with full screen option . and fixed the title windows . just re-download the plugin again .

It's a limitation of plugin actions. See CORE-1697. You can add as many as you want if you add it under a primary navigation link you create, similar to the Support Manager.

thanks for the donations . some great newplugins/modules in the road . but i think iw ill wait until the new v4 released .

my world is a small worlda and private one , nothing to have with the real world

Thanks. I don't see any missing </html> tag, though. I think the problem is as you described--the Widget object is not closed, so it does not end a couple div tags. CORE-2011

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