Fake domain transfer orders

[ody]

Hello we have lastly a lot of fake domain transfer orders even with our master domain name,

when they order any hosting plan and system redirect them to domain choose page they proceed with the transfer option they setting our master domain and systems output result is that "Your domain is eligible for transfer"

this is happening also with other domains even these domain are only registered or even are registered with a hosting plan!

The problem must be somewhere in .js files

We still use 7.4.2 version

Thank you in advance

[brian!]

3 hours ago, ody said:

Hello we have lastly a lot of fake domain transfer orders even with our master domain name

you know the farce of this is that if you try to transfer a domain that is already in the database from the domain transfer page, it correctly prevents you from doing it in v7.4.2...

but as you have found, the same isn't true for when you use the transfer option with a hosting product.

3 hours ago, ody said:

We still use 7.4.2 version

I think I can give you some good news and bad news about this...

  good news is that I think it's fixed in v7.5.1

  bad news is that the error message is wrong.

so in v7.5.1, if you try to transfer a domain, when ordering a hosting product, and it is already in the database, you'll see this...

Quote

Not Eligible for Transfer

The domain you entered does not appear to be registered.

If the domain was registered recently, you may need to try again later.

Alternatively, you can perform a search to register this domain.

so there's a bug in the logic as it displays the above text whether it's in the database, or an unregistered domain.. but at the end of the day, it would prevent the transfer from progressing and that's what you want to do.

if the explanation is not going to be accurate in the output, then you could just remove those last three lines using Language Overrides or from the template and just let it say "Not Eligible for Transfer"...

so you could download the v7.5.1zip and compare the js files against your v7.4.1 version... or upgrade to v7.5.1 (after first testing that other addons, templates, hooks etc will work)... if it were just your main domain, you could use a html5 pattern as we've previously discussed, but that's not really applicable if they're using other existing domains... though you'll never be able to stop this from occurring, just limit their options to not using any domains in your database.

[ody]

Thank you Brian for you info and for your good news,

we haven't upgrade till now to 7.5.0. or 7.5.1 because any new WHMCS have bugs which most times appearing after clients use so we waiting from WHMCS to fix them and then we upgrading to a stable version,

in any way we shall download the 7.5.1 and we'll compare both of them and who knows we might find the code which is missing from 7.4.2

Thank you again

[brian!]

10 minutes ago, ody said:

we haven't upgrade till now to 7.5.0. or 7.5.1 because any new WHMCS have bugs which most times appearing after clients use so we waiting from WHMCS to fix them and then we upgrading to a stable version,

a wise man.

the usual update lottery - which old bugs have been fixed and what news ones have been introduced... the endless joy of WHMCS.

13 minutes ago, ody said:

in any way we shall download the 7.5.1 and we'll compare both of them and who knows we might find the code which is missing from 7.4.2

i'm not sure if it's purely a js issue and whether there are some internal functions involved as well...

[ody]

Quote

the endless joy of WHMCS

It's not only WHMCS because if you use also some 15 WHMCS Modules then.....