Enhance + WHMCS: Integration Module for Community Testing and Feedback

insave

Adam
My question is related to the current topic of the Enhance+WHMCS module. I simply don't understand why this module creates organizations and user access in Enhance, even if the client hasn't purchased the shared hosting service (Enhance).

Adam

insave

Maybe I'm still not understanding the question. If the customer is purchasing a managed VPS within your existing cluster then they need a customer organisation and user access so they can manage their websites. If they're purchasing a root server with an Enhance licence through our partner program then this should be provisioned using the partner WHMCS module which is a separate module entirely.

insave

Adam. Customer is purchasing a dedicated server not affiliated with Enhance, just another product(any another product). So why does this module creates orgid in Enhance?

Adam

insave

The Enhance module creates a client custom field called enhanceOrgId which stores the Enhance org ID so that a customer can have multiple packages under the same Enhance account.

However this is only populated the first time that Enhance hosting is provisioned for the customer. If the customer has no Enhance products then the field will be blank.

insave

Adam I know it. As I say, this modules creates orgid in Enhance panel, if I just look client profile in WHMCS.

Dan

It'll show the client field for an orgID in their profile, but it should be empty unless they have an Enhance based service.

The empty field is just a WHMCS custom field and will show for everyone.

PradeepC

webdig Hey @webdig, Just wanted to know if your module will just create the customer and has an option to not provision a website?

webdig

Hi PradeepC,

After reviewing this behaviour and checking several real customer accounts, I can confirm that the module does not create an Enhance Organization for customers who only have domains or other non-Enhance services.

The enhanceOrgId custom field is available on all client profiles because it is part of the integration, but it remains empty unless the customer is actually associated with Enhance.

The module also supports linking a WHMCS client to an existing Enhance Organization when required.

In my tests, customers with only domains and no Enhance hosting services had no enhanceOrgId assigned and no corresponding Organization created in Enhance.

So yes, a customer can exist in WHMCS without an Enhance Organization being created, and website provisioning is not automatically triggered simply by having a client account.

PradeepC

webdig Hi, I think you misread by comment, and seems to have replied to someone else.
Anyways, Just wanted to know if your module will just create the customer and has an option to not provision a website? i.e. the customer can then create the website in the Enhance panel when he is logged in.

insave

webdig
Hello. Please go to the profile of any customer, change any field(maybe not necessary), save changes.
After that, your module will create OrgID and user in Enhance.

webdig

Hi @Pradeep,

Sorry, I completely misread your question.

Too many tasks, too many tabs open, and sometimes my brain decides to provision confusion instead of hosting accounts. 😄

Regarding your actual question: at the moment, no. My module provisions the hosting service and website as part of the normal provisioning process.

I haven't implemented a "create customer only" option yet, where the client is created in Enhance and can then log in and create their own websites manually.

That said, it's an interesting use case and something I can look into adding in a future version if there is enough interest.

Thanks for pointing it out.

infinitum

Hi, can someone tell me if the EnhanceOrgId and enhOrgId in the profile page are the same? Should I write the client's Org ID in both fields?

Screenshot:
[https://icecream.me/55975d7e632605f234e2567223bdfd47]

infinitum

Anyone?? I just want to know what is the difference between EnhanceOrgId and enhOrgId?

webdig

Hi @infinitum,

First of all, sorry for the late reply.

They are two different WHMCS custom fields, although both can store the same Enhance Organization ID.

The enhanceOrgId field is the one used by my module to associate WHMCS services with the corresponding Organization in Enhance.

The EnhanceOrgId field is not created or used by my module, so it most likely belongs to another integration, an older implementation, or a different Enhance-related module.

For my module, you do not need to populate both fields. Only enhanceOrgId is required (or you can let the module populate it automatically, where applicable).

I'm currently working on a new, more up-to-date version of the module and I'm already testing it internally. If everything goes as planned, I expect to release it within the next few days. I'll also review this naming to make it clearer and avoid this kind of confusion in future versions.

« Previous Page