bluesteam

Apologies please ignore this reply.

Hello Has anyone else experienced an issue where if you have a pending order in a client's profile or even a terminated or cancelled hosting service, and you click on Services -> My Services and then you click on a hosting package that is cancelled/terminated/pending, it throws the following SiteJet error: We do allow SiteJet on our cpanel servers but what's happening here is that this error throws on any hosting package that has no associated account on cpanel. If the account does exist on cpanel, the error is not thrown. I would think that if the account doesn't exist, it should not throw this error. This happens on default whmcs templates. I'm running WHMCS 8.13.1 with PHP 8.3

oh wow! Thanks for clarifying that John. I must have been on HEAVY drugs the day I thought I saw a button there. Much appreciated that you clarified this for me.

Hello, I recently upgraded my WHMCS from 8.11.2 to 8.13.1 After the upgrade, I noticed that when trying to add a domain to a cart, the "Add to Cart" button was no longer there. then I tried from this screen and saw the button is still there: So at first I thought it was the template or order template so I set everything to default templates, cleared the cache but the same behaviour was there. Then I thought, maybe it was an addon or something so I disabled those as well but alas, the button was still missing. So I can only surmise that the button has been removed when search a domain through the checkout process? Anyone else notice this?

Thank you @slim 😄

Hello, I am a little confused about the OX App Suite product. The advertising material on the default page template that is created when enabling the OX App Suite product through MarketConnect, It states under the product features that mailboxes can have 10GB of storage. Is this an OVERALL 10GB for any mailboxes the client creates or is it 10GB per mailbox that the client creates? There is no mention of whether the client can create as many mailboxes as they want and there is also no mention that the product is only PER email? So which is it?

So what you're saying is that upon initial signup using an affiliate link, that order will be allocated towards the affiliate for commissions to be paid out. Any future orders, will not be unless I manually link the order to the affiliate?

Hello I only recently activated the affiliate system in WHMCS and I was wondering if the affiliate system pays out commissions for future purchases of that client or only the initial services that the client ordered. Hoping someone can answer this for me. ☺️

Would be nice if the vanilla system had the affiliate enter his bank details through a form on his profile so we can store it so that we have it on record for us to make payouts when their account reaches a certain threshold. Would also be nice if when the affiliate clicks the "Request Payout" that it asks the affiliate if they want the commission added as credit and it does it automatically without our intervention. This is exactly why the system needs an extra feature that suspends referral commissions if the payout grows too large based on an amount that we can set in the affiliates tab under general settings. I don't like to have to do so much admin.

sad day indeed. 42 views and noone can give me answers 😞

Hello, I just have a few questions around the affiliate system. 1. Why is there no CAP on payouts? If the affiliate decides to horde the money and bank all the referral commissions in his affiliate account and only request his payout once a year like right before christmas, it could end up with our company having to payout massive lump sums of money in one SINGLE shot. The affiliate system should have a payout limit and no more commissions earned until that payout is done because it could cripple a company if 100 clients all decide to horde their money and ask for a payout only after 2-3 years while it grows. In order for us as a company to mitigate this, we have to now go and make special payments to an alternative account to set the money aside until the client requests his payout?? Or have I missed something in the Affiliate system? 2. I don't see an option to aply referrals on specific billing cycles. We for example, offer our yearly packages by giving 2 months free if they pay annually. Now we are also going to give referral commission of 5% on top of that. Our margins become almost 0. So we only want to apply the affiliate links to specific billing cycles like month, quarterly or semi-annually but never annually. I would appreciate thoughts from other people that have used the affiliate system.

I upgraded today to 8.10.1 version. I also have this problem now but clearing the template cache in Utilities -> System -> System Cleanup has not done anything for me. I also went so far as to log on to cPanel and clear out the templates_c directory but the problem remains.

well, the only reason this thread started as "autorenew" ius because there is NO cancel option for a domain so the only cancel option IS autorenew being disabled. but from WHMCS point of view, in my opinion, if a client sets the auto-renew option to disabled him/herself, then notifications from WHMCS must stop altogether aside from 1 final notification of course stating that it has been cancelled and no more notifications will be sent. anyways, I think I have said our piece, I don't like or agree with the way WHMCS handles domain cancellations.

But what you guys are talking about are edge cases. Anyways...I still feel that if a client has cancelled a domain in WHMCS then notifications should stop altogether. One last notification after the client has cancelled could be sent out stating that the domain has been cancelled as requested. If this was done in error please contact support or whatever. But after that, no more bothersome notifications.unleas it comes from the registrar. Remember, as owners of our businesses, we are not just going to ignore cancellations so if a domain is cancelled then we should anyway reach out to the client and try and retain them. At least that's what I do In these cases a conversation has been had as well as the last notification that goes out to the client.

I respectfully disagree and for one reason only, there is no cancellation feature for domains in WHMCS. If there was a facility specific to cancellations for domain names, I would be able to agree. The only way a client can cancel a domain on its own is to either open a ticket and request it via support at which an admin has to manually set the domain to cancelled and disable the Auto Renew or set the client sets auto-renew to disabled. Unless there is another facility that I don't know about?? If they change their mind, they can just re-enable auto-renew.

I just feel that even though ICANN requires that we remind our clients, which is FINE if they themselves haven't set the auto renewal to be disabled, but if they have set it to be disabled, then why should I remind them again and again? anyways, I feel it's silly to remind someone of something when you absolutely KNOW they don't want to renew it.

It seems counterintuitive because if the client logs on and sets the domain to NOT autorenew, then the client doesn't want to receive reminders to pay for it. If the registry wants to send it then the registry must send it but if I tell WHMCS NOT to renew then everything should stop from WHMCS.

Hello, I set a domain name to not auto renew. So I fully expected this domain to never be renewed or notify the customer that the domain is up for renewal. However, even with the Disable Auto Renew ENABLED, reminders for the upcoming renewal were still sent out to the customer. Is this normal?

Nope, still a problem. Don't hold your breath for a solution.

So sadly it seems nobody knows 😞

Hello, Right off the bat, I want to say that I am very aware this must be something I am doing wrong but I need guidance nonetheless. We are planning on offering VPS options to our clients. We are just going to start small for now but later hopefully have more offerings. For now, we are limiting our offerings to only 4 different VPS server options that are identical except for CPUs and Disk Allocation. So I created 4 servers: SERVER 1: 2 vCPUS with 50gb Disk Space SERVER 2: 4 vCPUS with 125gb Disk Space SERVER 3: 6 vCPUS with 250gb Disk Space SERVER 4: 8 vCPUS with 500gb Disk Space However, we want to offer our clients to options of upgrading their package configuration to allow them to purchase extra vCPUs or extra Disk Space or whatever feature we want, without forcing the client to upgrade the entire server to the next package. In other words, if they want a server with 2 vCPUs and 50GB disk space, but want to upgrade only their disk space to say 100gb instead of just 50gb then they must be able to do so without being forced to move to the next tier of server. The same for vCPUs and any other feature we allow. To me, the most obvious choice here is to use the configurable options feature. Ok, so I proceed to create a configurable options group for the various features these servers can upgrade and downgrade to. However, I seem to either be misunderstanding how this feature works or I am simply doing it wrong If the client chooses Server 4 that has 8 vCPUS already and now wants to purchase more vCPUs, the client now also sees the lower spec'd options as well which they shouldn't because the default on this server is 8 vCPUs already. SEE SCREENSHOT: Now the only way I can see to get around this is to set up a SEPERATE configurable options groups with the same items in each for EVERY INDIVIDUAL server and just remove the lower spec'd options from each group listing depending on which server the group is for. HOWEVER, this makes things VERY tedious when you want to do things like update descriptions or prices across multiple server offerings as each item in the configurable options group must now be modified individually when the time comes Is the only way to do this to create individual configurable options groups per server offering or is there another way of doing this so that I don't have configure the same vCPU upgrade/downgrade MULTIPLE times across multiple configurable options groups. I am missing something??

@WHMCS John Hi John, I respectfully disagree. Actually what the client sees is what is shown below. I confirmed that in my post linked below as well as my original post: Not the stat at the top of the Product/Services page as you mentioned. And this is why it's an issue as the client is seeing old data that will only be updated the next day and now they pollute the help desk with queries as to why cPanel and their account is different and ask us why is WHMCS telling them to STILL upgrade after they have already cleared out their disk usage.

Yup, the same. 8.7.2

That did the trick but no errors:

Still not.