|
I am testing out batch registrations in the test
environment, and have experienced the following problem:
If I do a batch registration and select an existing
domain profile, then everything works as expected.
However, if I do a batch registration and enter a
new domain profile, the domains are *not* linked together. However, my reading
of the sample reg_system code is that they should be.
Example: try registering domaina.com, domaina.net, and domaina.org
When asked for a profile, create a new
one: newuser, newpass, newpass
Now approve the registration and go to manage
domains. Logging in as domaina.com, I am unable to see domaina.net and
domaina.org unless I explicity change the linking.
However, had I batch registered and select an
existing profile, then everything links properly.
Can someone else test a batch registration on the
test system using a new domain registration and see if they link properly? I
need to know if it's something that I've done that has caused this to break or
not.
Debugging the %data associative array that is
passed to send_cmd, I see the following:
domaina.com:
count is 1, link_domains is 1, data{link_domains} is 1, data{master_order_id} is
domaina.net: count is 2, link_domains is 1, data{link_domains} is 0, data{master_order_id} is 100478 domaina.org: count is 3, link_domains is 1, data{link_domains} is 0, data{master_order_id} is 100478 So domaina.com is registered and link_domains is 1.
This domain is assigned order ID 100478 and the latter two domains are
registered with master_order_id set to the correct value. So why aren' the
latter two domains linked?
And why does reg_system set link_domains=0 for the
second two? (the code does this, but I want to know why). I didn't see any
explanation of the linking methodology in the developers
documentation.
Thanks
|
