bear

Those of you getting fake account signups, are you allowing account creation without ordering something?

...until WHMCS complicates it further.

Disregard

See this thread:

Simple? Changing links used to be simple, now it requires coding skills and this clunky "use a hook to change a menu" thing. If someone was able to make an addon to edit these, why on Earth didn't WHMCS include one? It's like that claim on "you can't automatically keep the sidebar closed in the admin area", and truth is, you can, and simply (now that someone who codes well created it). Frustrating. Hooks are a good idea since it allows customizing the system, but not for something as basic as menu changes.

If there's a new version, with up to date code, can't you simply use that?

You did not, actually. See below. "Ok, no problem, stuff happens, report it to the devs, right? So, we did that."

Tried quoting your post, and this community software is just awful and wouldn't let me quote and respond outside of your quoted text. Namesilo is a registrar that gives free whois protection. As for the ownership, in the eyes of the registrar and the law, it's the registrant that owns it. If your name is on it, you own it. It doesn't matter if you have a paper that says they do, since in any dispute that won't matter.

You seem to be asking to make yourself the whois registrant contact for all domains purchased through you? That makes you the owner, and not them, legally speaking, and will cause all sorts of problems. In my opinion, that's not only not legal, but incredibly inadvisable. Explain it to the person buying domains from you that domain whois details are readily and easily harvested at the registrar level, and beyond your control. Explain further that the fix is to order whois protection at the time of registering. Make it a sales pitch for the paid protection, find a registrar that includes it for free; but at the least, have that explained in your FAQs. Don't just put your info on them, please, no matter your motivation.

You say you were working with a provider and contacted MG on their behalf, looks like. How is it you don't recall the specifics? You say you're not sure if it was work, or a module, and then say the "module was broken". Seems to me if you're going to bash them here (deserved or not), you should have those details at the ready, or leave readers with the appearance it actually is competitor related, despite the disclaimer.

Is there a leading "<" on that, and is it at the top of the page? It needs to appear before any of the page code.

Yes. Seems to be announcing a new version, but can't connect to the mothership for some reason. I assume that will clear itself at some point. Mine began today.

Nothing at all. They are relentless, and just another iteration of "Domain Registry of America" and others like them. They send these 6 months in advance of expiry to avoid crossing notices with legitimate renewals. Customer education is the key. Make sure they know you don't send any renewals via postal mail, and add an article to your KB about it as well. Link to that article in the emails that get sent on domain registration and renewal reminders. We get clients frequently checking with us about things like this, so they know to be cautious.

The workaround is to manually update. That was given to you early on. The rest is advice about moving to a more secure option, if possible. As for someone moving to a new billing system due to this? It will be exactly the same recommendation to isolate your business from shared hosting accounts, since the potential for disaster is there for *all* of them. It's just the inability to use fopen to use autoupdates that's not working. Manual is the only way if you need or want to stay on shared hosting.