Jump to content

bluesteam

Member
  • Posts

    220
  • Joined

  • Last visited

  • Days Won

    2

bluesteam last won the day on September 10 2020

bluesteam had the most liked content!

1 Follower

About bluesteam

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bluesteam's Achievements

Senior Member

Senior Member (3/3)

7

Reputation

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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?
  7. Nope, still a problem. Don't hold your breath for a solution.
  8. 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??
  9. @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.
  10. I ran the command from the terminal in cPanel and received an exception stating the following:
  11. Hello, Yes, hitting the refresh now definitely corrects the issue but I just feel that we shouldn't have to write any hooks or mods just to get this to work like it should. Don't you agree?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated