Bug with Additional Fields for Domain Transfer?

[jacksony]

Hi all,

For a domain extension eg. .com.XXX, we have already use additonal fields to remove the default fields for it.

We noted the default fields for .com.XXX has 2 required fields for it.

 

For the 2 custom fields we have added for .com.XXX, if we did not make the fields compulsory, there is no issue for domain registration and domain transfer.

However, once we set '"Required" => true,' for for these custom fields, the strange thing is for domain transfer, it suddenly displayed error saying that the required fields for the DEFAULT fields is missing. However it shouldn't be there since it was removed initially already.

There is no issue for domain registration if '"Required" => true,' is set for the 2 custom fields.

 

This seems to be an obvious bug? Since if the default fields are removed, it should not be referenceing to default fields at all (as displayed by the error when we tried to transfer domain with compulsory custom fields). Or is there any thing we have missed out for custom fields?

[brian!]

9 hours ago, jacksony said:

This seems to be an obvious bug?

I wouldn't rule out, nor surprise me, that there might be - but it would have been useful if you had posted your custom additionalfields file, or at least the lines relevant to this TLD, just in case there is an error in there somewhere.

[jacksony]

Thanks Brian,

As usual, sad that it seems to be only us again, facing such issue.

But yes, it is an absurb issue.

eg: setting compulsory fields for custom fields for domains, but ended up, causing default domain fields (deactivated) to throw errors due during domain transfer.

[brian!]

assuming there isn't an issue with your additionalfields.json file and you're testing on new transfers, the temporary fix might be, instead of removing those two default fields via the custom file, to physically remove them from the dist.additionalfields.json file - yeah I know the docs say not to edit that file, but that's only because it will get overwritten during an update.

it's going to be months before v8 goes in and out of beta, so unless there's an imminent maintenance update, you should be update-free for a while... and it should stop the error being shown to users.

... and then when v8 is in beta, or just comes out, see if the issue has been fixed - even if you report it as a bug today, and assuming it is and they don't hotfix it, then you're still going to have to wait until v8 - and at least by modifying the default file, it should remove the error.

btw - I assume this is about .com.au additional fields ?