Leaderboard

This might help a few people, you can't use PHPIDs with this at the moment. This is designed for my business but edit as you please, you can keep it the same and just edit the business name, etc. please make sure your Service Creation template only has these: Html: {package.email_html} Text: {package.email_text} Then in the welcome emails put the following: Dear {client.first_name} {client.last_name}, PLEASE READ THIS EMAIL IN FULL AND PRINT IT FOR YOUR RECORDS Thank you for your order from us! Your hosting account has now been setup and this email contains all the information you will need in order to begin using your account. If you have requested a domain name during sign up, please keep in mind that your domain name will not be visible on the internet instantly. This process is called propagation and can take up to 48 hours. Until your domain has propagated, your website and email will not function, we have provided a temporary url which you may use to view your website and upload files in the meantime. New Account Information Hosting Package: {package.package} Domain: {service.cpanel_domain} Package Price: {pricing.price | numberformat 2, ".", ","} Package Period: {pricing.period} Cancellation Fee after 10 days of your first product with us: {pricing.cancel_fee | numberformat 2, ".", ","} Login Details Username: {service.cpanel_username} Password: **** [Password Hidden for security reasons] Control Panel URL: http://{module.host_name}:2082/ Once your domain has propogated, you may also use http://www.{service.cpanel_domain}:2082/'>http://www.{service.cpanel_domain}:2082/ Server Information Server IP: {module.host_name} If you are using an existing domain with your new hosting account, you will need to update the nameservers to point to the nameservers listed below. {% for name_server in module.name_servers %} Name server: {name_server}{% endfor %} Uploading Your Website Temporarily you may use one of the addresses given below to manage your web site: Temporary FTP Hostname: {module.host_name} Temporary FTP Username: {service.cpanel_username} Temporary FTP Password: cPanel Password And once your domain has propagated you may use the details below: FTP Hostname: {service.cpanel_domain} Webpage URL: http://www.{service.cpanel_domain} Email Settings For email accounts that you setup, you should use the following connection details in your email program: POP3 Host Address: mail.{service.cpanel_domain} SMTP Host Address: mail.{service.cpanel_domain} Username: The email address you are checking email for. Password: As specified in your control panel. Thank you for choosing CubicWebs. It will look like this: ======================================================= ======================================================= InterWorx Version ======================================================= Dear {client.first_name} {client.last_name}, PLEASE READ THIS EMAIL IN FULL AND PRINT IT FOR YOUR RECORDS Thank you for your order from us! Your hosting account has now been setup and this email contains all the information you will need in order to begin using your account. If you have requested a domain name during sign up, please keep in mind that your domain name will not be visible on the internet instantly. This process is called propagation and can take up to 48 hours. Until your domain has propagated, your website and email will not function, we have provided a temporary url which you may use to view your website and upload files in the meantime. To get your account password, please go to your dashboard and click on your service row, you will see your username, password and a direct login link. New Account Information Hosting Package: {package.name} Domain: {service.interworx_domain} Package Price: {pricing.price | numberformat 2, ".", ","} Package Period: {pricing.period} Cancellation Fee after 10 days of your first product with us: {pricing.cancel_fee | numberformat 2, ".", ","} Login Details Username: {service.interworx_email} Password: **** [Password Hidden for security reasons] Control Panel URL: http://{module.host_name}:2443/siteworx/ Once your domain has propogated, you may also use http://www.{service.interworx_domain}:2443/siteworx/ Temp domain: http://{module.host_name}/~{service.interworx_username} Server Information Server IP: {module.host_name} If you are using an existing domain with your new hosting account, you will need to update the nameservers to point to the nameservers listed below. {% for name_server in module.name_servers %} Name server: {name_server}{% endfor %} And once your domain has propagated you may use the details below: Webpage URL: http://{service.interworx_domain} Thank you for choosing CubicWebs. ======================================================= ======================================================= SolusVM Version ======================================================= Dear {client.first_name} {client.last_name}, PLEASE READ THIS EMAIL IN FULL AND PRINT IT FOR YOUR RECORDS Thank you for your order from us! Your virtual server has now been setup and this email contains all the information you will need in order to begin using your account. Package Information Hosting Package: {package.name} Plan name: {service.solusvm_plan} Virtualization: {service.solusvm_type} Package Price: {pricing.price} Package Period: {pricing.period} Cancellation Fee after 10 days of your first product with us: {pricing.cancel_fee} Server Information Hostname: {service.solusvm_hostname} Primary IP: {service.solusvm_main_ip_address} Root Password: {service.solusvm_password} (This will be blank if more than one service is on your account.) Console Information Control Panel: https://{module.host}:{module.port} Console Username: {service.solusvm_console_user} Console Password: {service.solusvm_console_password} {% if service.solusvm_type == "kvm" %} KVM Extras VNC IP address: {service.solusvm_vnc_ip} VNC Port: {service.solusvm_vnc_port} VNC Password: {service.solusvm_vnc_password} {% endif %} Thank you for choosing [Enter Company Name here]. PS: The If statement is a guess and might not work, please remove it if it doesn't and post here. It should show up only if the type is KVM.

Hi, Blesta Devs! It would be awesome if you guys could help the VestaCP developers create a method for Blesta to communicate with VestaCP, or vice versa. VestaCP's website says they already work with WHMCS... though I don't have a WHMCS instance to test this claim. But I would suggest that this might be a good idea to have in place early. Right now though, I'm working on figuring out how to integrate VestaCP with the Universal Module, but it would be amazing to have a VestaCP module directly from the Blesta devs. Sidenote: You guys are amazing. Seriously, amazing.

Version 3.0.6 is now available. You can download it in the Client Area. This is a patch release that corrects issues with 3.0.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes - Blesta Core - Version 3.0.6 ## Version 3.0.6 2013-11-13 ### Bug * [CORE-611] - Logicboxes Module: Add order-id field to Manage Settings * [CORE-844] - Copy contact information when paying as an unauthenticated client does not work * [CORE-845] - Service pagination results in 404 * [CORE-846] - Client Group 'Allow Clients To Cancel Services' setting is unused and defaults to the company setting instead * [CORE-847] - Subsequent addon services use the qty value of an addon service added before it if one does not exist * [CORE-854] - Plesk: Service plans may not be fetched if using a reseller account * [CORE-856] - Cron: Service renew date may update if add invoice fails * [CORE-858] - Recurring coupons are not applied * [CORE-859] - Currencies::add() should always return void * [CORE-860] - Import Manager: Blesta 2.5 migrator creates error if currency already exists * [CORE-863] - Resetting password shows success message when no username is given * [CORE-864] - Cannot delete a pending or in review service from the billing section * [CORE-865] - Order plugin: Order form package WYSIWYG descriptions inheriting invalid styles for OL, UL * [CORE-866] - Adding service with a coupon resets coupon used quantity to 1 * [CORE-868] - Coupon discount not affected by service quantity * [CORE-869] - Create Client Group missing "Suspend Services Days After Due" select values * [CORE-870] - Authorize.net gateway does not set x_invoice_num * [CORE-871] - Transactions::getTotalCredit() lists $currency as optional * [CORE-872] - API fails to return false equivalent values * [CORE-875] - Delete client group always reassigns clients to group ID 1 ---

I doubt there will be time, but even if we release 3.1 without Multicraft, we can release Multicraft on the forums when it's ready. There are already going to be some other modules included with 3.1, so it wouldn't be exclusive anyway.

I'm somewhat surprised how many requests we are starting to get for Multicraft. I think in order to do it right, we need to build it with native support for configurable options which are coming in 3.1. ie, select the number of slots from a drop down, or the data center location. Being able to charge more for a premium data center location, or a discounted rate for more slots is going to be important.

We considered sending to Rack911 so they can follow through on confirming resolution, and so they can back us up in the event it's swept under the rug or dismissed. In this case, we've opted to trust they will do the right thing, even though they haven't in the past. And if they don't do the right thing, and silently fix the issues instead -- at least their customer base will be more secure as a result, which is the most important part. Either way, we've done our part.

Zomex is doing Blesta designs and integrations?! Awesome, I can keep my business with Zomex, then. I was hoping I wouldn't have to look elsewhere for a template.

Great news mate

Hi Guys, We have just released a newer version of CSF plugin 1.1, in which we can restrict staff/client to unblock his IP only. Admin can decide whether to give client the option to unblock any IP or just unblock client's IP. Newer version can be downloaded from here.

It's a unique feature, XXXX Day/Week/Month/Year or One Time! Many options for those that don't like to conform to the basic 1/3/6/12/24/36 months.

Yeah, Got a few RPi's 1 gets use as a media Server - XBMC connected to the NAS Does a great job. Still playing with one to use as a remote (solar powered) internet gateway for Ham Radio. Until the Pi it was simply not feasible to do this due to the power requirements to have something running all the time. Now at about 4W power it is very feasible. Have not used the GPIO pins for any control, but have thought about it - that is what Ardruino's are for - much lower power and quite simple code.

@eversmile_hostHappy to know that. we started its development. I might need commnets from you before releasing it. I'll send demo link after couple of days to know your thoughts.

Not sure if they have API docs. I suspect they do, also, apologies on the late response. Yup, Russian. Though they're working on translating it into English and other languages. Good to know that you found the WHMCS one... I should've found that, myself. Obviously though, I didn't think about it. Heh. Edit: Looking at the module in question, it's in English... and that is a very good thing. Also unencoded! I imagine you could do a Blesta one, based on this... Edit2: Chrome auto-translated for me: In the panel, it has a full API, but unfortunately, the documentation on how to use it is not ready yet. I'll try to briefly describe the key points, but if something is not clear, ask. in the folder / usr / local / vesta / bin scripts are located, which are both functions of the API. If you need to create a user, you need a script v-add-user, if you want to delete the database, it will make the script v-delete-database, and so on, by analogy. In other words, if you do ls / usr / local / vesta / bin, then you can get an idea of the options available. If you run the script without any parameters, it issues a statement on the use of: [Root @ V-test ~] # V-Add-User Error: not enought arguments Usage: V-Add-User USER PASSWORD EMAIL [PACKAGE] [FNAME] [LNAME] Each script returns return_code. If return_code is 0, then the operation completed successfully. Any other number will indicate an error. Actual table return codes can always be found in the file / usr / local / vesta / func / main.sh OK=0 E_ARGS=1 E_INVALID=2 E_NOTEXIST=3 E_EXISTS=4 E_SUSPENDED=5 E_UNSUSPENDED=6 E_INUSE=7 E_LIMIT=8 E_PASSWORD=9 E_FORBIDEN=10 E_DISABLED=11 E_PARSING=12 E_DISK=13 E_LA=14 E_FTP=15 E_SSH=16 E_DB=17 E_RRD=18 E_UPDATE=19 E_RESTART=20 UNIX API inspired ideas and therefore all information is stored in plain text files. Each script solves only one task. Upon successful completion of the script, for nothing is displayed. If an error occurs, the script immediately exits and displays a message on the screen. Returning to the creation of user and check the return code. [Root @ V-test ~] # V-Add-User Error: not enought arguments Usage: V-Add-User USER PASSWORD EMAIL [PACKAGE] [FNAME] [LNAME] [root @ V-test ~] # echo $? 1 From Table 1 above it E_ARGS, which means that an insufficient number of arguments. Optional parameters are enclosed in brackets kvadtratnye. To successfully create a user need only 3 azadt argument - user name, password, and email address. If the package is not specified, will be replaced by the default package, which is called the default. [Root @ V-test ~] # V-Add-User Demo d3mo0p4ssw0rd demo@vestacp.com [root @ V-test ~] # echo $? 0 In addition to the categories of scripts for creating and changing, there is a category for display, such sripta fall into the pattern v-list-*. Scripts can display information in several formats. Currently, these 3 formats: shell, plain and json. The first two are convenient to work from the command line. [Root @ V-test ~] # V-list-users Shell USER PACKAGE U_DISK U_BANDWIDTH SUSPENDED DATE ----------------------------- ------------------------- admin Default no 2013-02-11 3 0 1 0 Default test no 2013-03-10 Demo Default 0 0 no 2013-03-18 The third format is used for the operation of the web interface, which work uses the same API. For the operation of the web-based interface to the system is installed an additional web server nginx and php-fpm, to handle php. All requests made ​​under the user interface admin, which is allowed to serve api via sudo. now specifically try to answer your question about the creation of users. There are 2 options: 1) You can ipolzovat api directly executing scripts in / usr / local / vesta / bin, as it makes the web interface 2) You can use the wrapper-om the web interface to access the api. In most cases, the second option would be relevant. Further about it. By the way, just recently been implemented billing system integration WHMSC its wrapper-a. In the module for whmcs implemented key features that interest you and probably. The module is able to: * Create Customer service area * delete users * change the user's password * add web / mail / dns domain to wrapper-u need to handle POST requests, passing the user name and password admin. Here are a few examples of the most vsotrebovannyh: # Create user Add a user to a domain Delete user domains including its https://server-ip/api/?&user=admin&password=currentpwd&cmd=v-delete-user&arg1=demo And reproduced for you here, in English for the most part.