Feature Requests
Share ideas, discuss and vote on requests from other users in community
 

Reenable autorelease module for servers

GigaTux: VPS Hosting shared this idea 2 years ago
Under Consideration

This is a clear bug in my opinion, but the WHMCS team don't see it as one.

You can no longer select Autorelease as a server module. Autorelease is a module setting that simply raises a ticket when things such as provisioning and suspensions happen. It's designed for places where automation isn't set up.

The rationale for the removal is that this really is a product module setting and doesn't apply at the server level. However, the WHMCS team may have failed to consider the following:

1. When looking at a live service, you now can no longer change the Server field for this user. This is because the Server dropdown only lists servers which have a module which matches the Product/Service module. Because you cannot select Autorelease as a module for the server, this dropdown cannot populate these servers.

2. It just doesn't make sense to have servers listed with a module that's not configured properly. You get errors in certain places and it's ugly.

Sadly, I have to work around this by manually setting the server module type in SQL like:

UPDATE tblservers SET type='autorelease' WHERE name IN ('server1', 'server2', 'server3'');

Best Answer
photo

Allowing the auto-release module to be assigned to servers does not make sense for the majority of users since the module does not utilise or make use of servers, and this is why the change was made.

For those of you trying to use the Autorelease module for bare metal server assignment, we would not recommend doing it in the way you are using the Servers feature as that is intended for hosting servers for account provisioning only. However if you wish to continue working in this way, a very simple custom module would allow you to create products you can assign to servers - you probably wouldn't even have to write any code, the example we provide on our Github pages would work with a minimal amount of changes: https://github.com/WHMCS/sample-provisioning-module

Comments (13)

photo
1

Since the AutoRelease module does not require or use servers in any way for provisioning, allowing assigning of products that use this module to servers that serve no purpose seems counter-intuitive. We would however like to try and better understand what the workflow is that you are trying to accomplish with the servers to see if there are some alternatives we could recommend.

photo
1

I do appreciate that it's not really a server module per se, but not having it selectable does mean that I can't assign a service to a server, which doesn't seem sensible.

The workflow I have with everything on Autorelease is:

1. User signs up for a new product and pays.

2. Autorelease creates a 'Service Provisioned' ticket.

3. We provision the service manually and fill in details on the user's service including the Server, vserverid and IP addresses.

4. We send out a templated welcome email.

It's quite simple really, but we can't do this (especially point 3) if the server module isn't set to Autorelease.

photo
1

i believe whmcs is not getting the issue here

if we cannot select a server module like autorelease, we cannot assign a server to a client.

this meanst that stock control in server overview doesnt work.

however, it does assign to another module, but we dont need that

dedicated servers with plain root setup do not have a panel that connects to whmcs

so this is useless, we need autorelease in server config when setting up a server.

why cant the developers see this?

my cronjob fails halfway through because it cannot connect to a server because cpanel or another module is not installed on the server.

why is it so difficult to bring back that module?

it worked perfectly for servers that have no panel and all.

really you are def to your clients ears and dont seem to want to hear the issues

photo
1

Indeed, I've just taken to hacking the database to force the module to this.

It's a huge pain in the neck and a massive negative reason to upgrade.

photo
1

Could you explain how you added this to sql?

maybe you could contact me [email protected]

much appreciated

photo
1

I don't really remember now I'm afraid. However, the table names were quite intuitive so I just changed the module settings to be Autorelease for this server.

photo
1

ah too bad.

I have been looking into the tables but they have changed a lot since the past few updates.

whmcs doesnt seem to get the importance of this small feature and how it affects managing servers.

i think they're doing a bad job listening to clients when it comes to this item.

i dont see what the issue is with them adding this feature.

why not just do it and get it over with?

we are actually considering moving away from whmcs on 4 websites just because of this as we have no way managing occupied servers like we used to.

so WHMCS listen to us please and get this done in the next update, how much trouble could it be for you guys.

photo
photo
1

Let me explain this as clear as possible, if we cannot assign servers to a client we have no overview which server is occupied and which not.

Not all dedicated servers have software installed like cpanel and are delivered baremetal.

assigning a client would show the server occupied in the server overview which means our system wouldnt assign it again or our staff needing to assign it manually and search our inventory with 3400 servers which takes too much time.

photo
1

Right on. This seems to force some sort of daemon running on each server (to have a specific module) when people often just want baremetal servers.

photo
photo
1

Allowing the auto-release module to be assigned to servers does not make sense for the majority of users since the module does not utilise or make use of servers, and this is why the change was made.

For those of you trying to use the Autorelease module for bare metal server assignment, we would not recommend doing it in the way you are using the Servers feature as that is intended for hosting servers for account provisioning only. However if you wish to continue working in this way, a very simple custom module would allow you to create products you can assign to servers - you probably wouldn't even have to write any code, the example we provide on our Github pages would work with a minimal amount of changes: https://github.com/WHMCS/sample-provisioning-module

photo
1

Even though Autorelease doesn't care about the server field, we lose the ability for a user's service to be assigned to a server. This is the major issue here. At least three people at least seem to agree with this.

Was having the ability for services to be assigned to a server actually causing a problem for anyone? This seems surprising, considering the server can be just be set to "None" with Autorelease still.

It seems overkill to write a new module, even if it is simple, when all we need is for the removed functionality to be reinstated.

photo
1

'At least three people at least seem to agree with this.' out of 67,224 WHMCS members

photo
1

This was useful to track services that are not integrated with WHMcs yet, pity it was disabled.

photo