[confirmed] Nominet Module not passing Company Number again

[Mark Donne]

The Nominet module has stopped passing the Company number again when you choose "UK Limited Company".

 

We are running 5.2.10 but the Nominet module shows v5.2.8 (updated on the 3rd October 2013)

 

Here is the xml post that our module logs show was sent to Nominet.

 

<?xml version="1.0" encoding="UTF-8"?>

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">

<command>

<create>

<contact:create

xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"

xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0

contact-1.0.xsd">

<contact:id>SECRET SECRET</contact:id>

<contact:postalInfo type="loc">

<contact:name>SECRET SECRET</contact:name>

<contact:org>SECRET SECRET</contact:org>

<contact:addr>

<contact:street>SECRET SECRET</contact:street>

<contact:city>SECRET SECRET</contact:city>

<contact:sp>SECRET SECRET</contact:sp>

<contact:pc>SECRET SECRET</contact:pc>

<contact:cc>GB</contact:cc>

</contact:addr>

</contact:postalInfo>

<contact:voice>+44.12345678</contact:voice>

<contact:email>SECRET SECRET</contact:email>

<contact:authInfo>

<contact:pw>SECRET SECRET</contact:pw>

</contact:authInfo>

</contact:create>

</create>

<extension>

<contact-ext:create

xmlns:contact-ext="http://www.nominet.org.uk/epp/xml/contact-nom-ext-1.0">

<contact-ext:trad-name>SECRET SECRET</contact-ext:trad-name>

<contact-ext:type>LTD</contact-ext:type>

<contact-ext:opt-out>N</contact-ext:opt-out>

</contact-ext:create>

</extension>

<clTRID>ABC-12345</clTRID>

</command>

</epp>

 

Regards

Mark Donne

 

- - - Updated - - -

 

As an update to my own bug report, I replaced the updated Nominet files with the ones back from August 2013 and its working again.

[xperience]

This is a major problem for us too - have you had any negative effects from switching to the August 2013 files? WHMCS appear to be in no hurry to resolve this.

[WHMCS Nate]

I have reproduced this issue and created case 3681 to make sure it gets resolved.