Logicboxes Issues

[evolvewh]

Blesta v3.6.2

Logicboxes Standard v2.2.1

 

I've got a client trying to update their Whois Info on their side (client portal side) and the changes say they are saved and I can see the success messages under Tools -->> Logs, however, the changes do not actually save. If they leave that screen and come back to it, it shows the old values.

I can force the changes on the admin side and they work but the client side does not work at all for the updates.

Has anyone else experienced this or have a solution?

Edited August 14, 2016 by evolvewh
Correction

[evolvewh]

Has anyone else experienced this? Here are the steps to reproduce it:

 

Log into the clients side of the account.

Go to manage and update any of the Whois information.

Click Save (you'll see the success message)

Leave the tab, go to a different page or tab and when you return to the Whois tab, the old information will still show.

[Blesta Addons]

i have modified logicboxes module and is working for me .

try to test my logicboxes reloaded module and see if you recieve the same error .

normally in the module logs you should see the response data .

 

[Tyson]

Both the admin and client whois tabs perform identical actions, so it's interesting that one works while the other doesn't. When you check the module logs, do you see identical requests/responses when updating the whois information? There must be something different in the input or output between submissions from the admin versus client interfaces. Can you include the logs (with sensitive data excluded/masked) from a successful and unsuccessful attempt?

[evolvewh]

I don't keep the log details that far back but I will have another case soon. I'm wondering if it has to do with the domain being locked?

[ExpertIntegrations]

If the client is trying to change the Nameservers within the client side of blesta system.  & the domain is locked within the registrar then the valued nameservers that was set prior to the locking will stay the same value until the domain is unlocked.  Even though you are forcing the changes in the admin side, the values are not going to 'really' change.   Please someone correct me if I am wrong here people.

[Rocketz]

the only time i've come across a locked domain preventing nameserver  changes is with .ca domains on opensrs i think. And that was 10 years ago

unless there's something very specific to the TLD, changing nameservers should work fine regardless if a domain is locked or not

[evolvewh]

  On 8/14/2016 at 5:26 AM, ExpertIntegrations said:

If the client is trying to change the Nameservers within the client side of blesta system.  & the domain is locked within the registrar then the valued nameservers that was set prior to the locking will stay the same value until the domain is unlocked.  Even though you are forcing the changes in the admin side, the values are not going to 'really' change.   Please someone correct me if I am wrong here people.

Expand  

The clent was trying to update the Whois information. Not the nameservers.

[evolvewh]

  On 8/14/2016 at 4:12 PM, AnthonyL said:

the only time i've come across a locked domain preventing nameserver  changes is with .ca domains on opensrs i think. And that was 10 years ago

unless there's something very specific to the TLD, changing nameservers should work fine regardless if a domain is locked or not

Expand  

It's the Whois information. Not the nameservers.

[Michael]

  On 8/14/2016 at 5:07 PM, evolvewh said:

It's the Whois information. Not the nameservers.

Expand  

Your first post says name servers, therefore people are replying to that, that's why you should post other issues in their own thread :).

[evolvewh]

  On 8/14/2016 at 5:52 PM, Licensecart said:

Your first post says name servers, therefore people are replying to that, that's why you should post other issues in their own thread :).

Expand  

Oops. Didn't realize that but I am referring to the Whois. Thanks!

[Blesta Addons]

Locked domain = can t change whois or nameservers or any other info related to the domain .

But normally it should return a error mesage not a success message .

Can you post the log module response and the domain status .

 

[ExpertIntegrations]

  On 8/14/2016 at 5:06 PM, evolvewh said:

The clent was trying to update the Whois information. Not the nameservers.

Expand  

Yeah I was just assuming you was still having issues w/ your initial original post.  But again w/ the whois & nameservers isn't going to be editable until the domain is unlocked.

[evolvewh]

My apologies for the confusion. Multi Tasking always seems to get me in trouble.

Here are the messages. The domain is locked and the client has tried to update the Whois information.

1) They make the changes and click save: The data was successfully updated.

 

2) I have the same input / output 4 times and a success message for each in the logs:

 

Input:

https://httpapi.com/api/contacts/modify.json
a:13:{s:10:"contact-id";s:8:"33189728";s:4:"name";s:21:"Name";s:7:"company";s:25:"Company";s:5:"email";s:19:"Enauk /address";s:14:"address-line-1";s:18:"Address 1";s:4:"city";s:8:"City";s:5:"state";s:8:"State";s:7:"zipcode";s:5:"Zip";s:7:"country";s:2:"US";s:8:"phone-cc";s:1:"1";s:5:"phone";s:10:"Phone Number";s:11:"auth-userid";s:6:"481018";s:7:"api-key";s:32:"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx";}

Of course I got rid of the clients details above to post this.

Output:

https://httpapi.com/api/contacts/modify.json
{"entityid":"33189728","status":"Success","eaqid":"379050693","actiontypedesc":"Modification of Contact Details in the Registry","actionstatusdesc":"Contact modification completed successfully in all registry","currentaction":"379050693","actiontype":"Mod","actionstatus":"Success","description":"DomainContact"}

[Michael]

From the two guys above you will not be able to edit the domain UNTIL the domain is UN-LOCKED. But you must have found a bug because it's not showing you an error.

[evolvewh]

  On 8/15/2016 at 7:00 AM, Licensecart said:

From the two guys above you will not be able to edit the domain UNTIL the domain is UN-LOCKED. But you must have found a bug because it's not showing you an error.

Expand  

That makese sense. I'll have to add text to tell clients to unlock it and I'll modify this text on the Settings tab: Release the registrar lock so the domain can be transferred.

Thanks!