[nickn]

Hi All,

We are now releasing a major rewrite/update to the WHMCS plugin. In other good news, we'll also be maintaining this plugin ourselves from here forward.

http://www.vps.net/w...whmcs-beta4.tgz

= Installation =

Simply copy everything inside the 'whmcs-root' directory into your WHMCS install's root directory.

If you use a client area template other than 'default' you may need move the templates and edit paths inside them due to the way WHMCS mangles smarty.
All the vps.net templates are in templates/default/vps/ - simply move the 'vps' directory to the template you are using, and edit the paths.

= Configuration =

To configure the vps.net module first you will need to create a server type vpsnet.

Don't worry about the number of slots, set it to a big number because you can create as many as these accounts as you like.

In the server configuration page you need will add your VPS.net login email in the 'Username' box and add your VPS.net API key in the 'Access Hash' textarea.


Now need to create a configurable options group (Setup->Configurable Option) for VPS nodes, and add an option for 'vpsnetNumNodes|Nodes', option type of 'dropdown' (snapshot1.png).

Then add an option from 1 to <max number of nodes you wish clients to have>.

Now go to Products/Services and add Group Name e.g. Cloud Hosting

and add new product Cloud nodes under this group.

Product Type = VPS/Dedicated Server
Product Group = Cloud Hosting
Payment Type = Recurring

You may live prices as zero because you'll charge customer for nodes he select. But it important to set payment type as recurring!

Module Name =vpsnet
Assigned Option Groups - select Cloude Hosting


********************** new for beta 4 *****************

Now you add following Product Addons (Setup->Product Addons) (snapshot2.png):

vpsnetBackup|R1Soft
vpsnetBackup|Rsynci
vpsnetBackup|Snapshot
vpsnetCpanel|Cpanel
vpsnetCpanel|ISP manager


Please define Monthly Billing Cycle and "Recurring price" (setup fee is ignored for now). Description if you add any will be visible for end user. (snapshot3.png)

Do not assign it to any product this options should (it should be hidden from end-user.)

********************** new for beta 4 *****************


The last thing you will want to do is add a link in the user's client area to vps-cloud.php which is the client's VPS cloud management page, this can be done by editing the client area templates.

Links:

your_whmcs_url/nodecart.php to order and open could hosting accout.

your_whmcs_url/vps-cloud.php to manage everything (for logged in customers)

Its good idea to add link to vps-cloud.php at end user templates e.g for default style it's templates/default/header.tpl


new features of beta 4:

* A lot of bug fixes (power buttons / unavailable clouds and templates and etc.)
* Improved design (snapshot4.png/snapshot5.png)
* Added all options of backup support include billing for it.
* Added Cpanel and ISP manager Licenses include billing for it. (snapshot6.png)
* Improved new and edit VPS pages

But most of all, this beta should be looked as the beta that you need to provide us what you want on it...

[Dmart]

This is going to be a noob question but should we delete the whmcs version of the module as it has the same name in the servers folder before uploading VPS.net version ?

[nickn]

Dmart said:

This is going to be a noob question but should we delete the whmcs version of the module as it has the same name in the servers folder before uploading VPS.net version ?

Yep. Sorry that should've been clarified.

[Waves]

nodecart.php give a blank page. Checked install instructions twice. What am I missing?

[Dmart]

i spent hours last night trying to get this to work but with no luck...

On nodecart i have the node selection graphics to chose how many nodes you want... and nothing else is this correct ?

It then takes me to the cart to pay for it, this go through to VPS.NET and generates an invoice...

At what point does snapshot 6 show itself ?

[nickn]

If anyone has any questions on this, feel free to open a ticket and we can assist you through there. I've ran through the install personally, so I know it works - but there could be variables that change that or you guys...

[Dmart]

Thanks Nick

will pop one in now......

ticket 47980

This post has been edited by Dmart: 28 September 2010 - 11:00 AM

[Waves]

:-) making one now

[Dmart]

Ok Module is up and running

is anyone else having issues with the console in the module where it wont connect ?

I can not access the console in the VPS.NET dashboard either it just sits there with the following error

Network Error: could not connect to server:www.vps.net:30300

[s1rk3ls]

I was able to get into the console once.. When I tried to come back to that page to get to the console again, it stopped working. I didn't try it from the VPS.net dashboard.

[s1rk3ls]

My previous post never showed up - so I'll briefly re-post this...

My biggest problem was not having the templates setup correctly (they are all pointing to the default templates directory instead of the active template I'm using)

You can change all the lines with

 include file='default/vps/filename.tpl'

To

 include file="$template/vps/filename.tpl"

Note the change from single to double quotes is required.

This will allow it to pick-up the currently active template.

Or just leave them in the default folder :)

-Kris

[Dmart]

Hi Kris

Yeh all my templates are all setup and everything works apart from the console and bandwidth/cpu graphs in the whmcs

guess i will have to revert back to WHMCS module....

[Dmart]

Quote

Finely I figured out that it's specific for cloud you selected. problem. (depend on software cloud is build). So no solution except of recreate VPS on another cloud for now

Just had the response above from support...

only clouds they know it works on is Atlanta A/B & Chicago C/B for now so looks like we will have to wait until it is fixed to work with the others... Like UK clouds...

Also you can not terminate an account in the backend of whmcs until the customer deletes there VPS/machine, then you are able to terminate the service. This needs to be fixed also in the next version...

This post has been edited by Dmart: 29 September 2010 - 01:34 PM

[eseelke]

This is great news! I wished I had read this earlier. I spent the entire week trying to get the old one working.

Any chance of adding storage nodes or ip addresses to this? What about daily nodes or an anonymous version of server density?

Keep up the great work and many thanks.
Eddie

[eseelke]

s1rk3ls said:

 include file="$template/vps/filename.tpl"

Shouldn't it be:

{include file='templates/($template}/vps/header.tpl'}

[eseelke]

I should have tried that before posting. s1rk3ls was right!

[s1rk3ls]

Just curious if anybody else is having the same issues as me?

1. Incorrect cloud listed on manage VPSs page.

i.e. I created a VPS in (Chicago) - Zone C But when logged as client and at vps-cloud.php it shows (Atlanta) - Zone A - It shows correctly in the overview and on the vps.net site.



2. Unable to get it to add an ISP manager license either. I can add cPanel, but the ISP manager option doesn't work. I thought it was a mis-spelling or case sensitive but all the variations I tried resulted the same. (ISPManager, ISPmanager, ISP Manager, ISP manager, etc...)


3. I added all three backup options and it shows they were added, but Rsync doesn't remain checked in the module. (even though it is enabled on the VPS at the vps.net site)

...still testing for other bugs. Unfortunately the sandbox doesn't work for testing, I can't get past selecting which zone to put the cluster in, keeps returning no template selected even though I've selected the only template available (Ubuntu dummy)

I hope I'm not the only one with these issues? Please tell me you've tested the module too and found the same issue(s) as me, so I'm not alone!!

-Kris

[eseelke]

s1rk3ls said:

1. Incorrect cloud listed on manage VPSs page.

i.e. I created a VPS in (Chicago) - Zone C But when logged as client and at vps-cloud.php it shows (Atlanta) - Zone A - It shows correctly in the overview and on the vps.net site.

I can confirm this too. On the vps-cloud.php page, I get the location as "(Atlanta) - Zone A". But, when I click on the Label name, it shows "Cloud (Chicago) - Zone C" which is correct.

[eseelke]

I setup four VPSs using this module. They are all working, but two of them will no longer allow access. I am getting the following error:

Quote

Fatal error: Uncaught exception 'Exception' with message 'Unknown VPS template' in /home/username/public_html/modules/servers/vpsnet/class.php:299 Stack trace: #0 /home/username/public_html/vps-cloud.php(304): vps->getTemplateName(11, 887) #1 {main} thrown in /home/username/public_html/modules/servers/vpsnet/class.php on line 299

They were working, but suddenly stopped.

Any ideas?

[s1rk3ls]

eseelke said:

They were working, but suddenly stopped.

I haven't had this problem yet (fortunately) but in playing with the module, I figured out it uses a function of the API to assign a "consumer_id" to a node or VPS which is how WHMCS ties a customers account to any nodes or VPS accounts. This "consumer_id" is neither visible nor changeable anywhere that I've found except through the API.

If you do something that changes/erases this id, WHMCS will no longer know it exists...

I think there needs to be an additional admin module for WHMCS to manage nodes and VPSs, and see what's assigned to whom or change/correct assignments. i.e. if a customer buys 2 nodes but doesn't create a VPS and I accidentally delete those unused nodes from the VPS.NET site - then I would have to re-create the account to get them back. I don't know what this would do to any other nodes or VPSs the same customer already has. If would be nice to see an overview of the nodes/VPSs in my account and what (if any) "consumer_id" they are associated with - and allow me to assign them if needed.

-Kris