Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing error message after updating contact with disclosed attributes #2272

Closed
maricavor opened this issue Jan 14, 2022 · 2 comments
Closed
Assignees
Labels

Comments

@maricavor
Copy link
Contributor

When updating contact with disclosed attributes no error message is shown and syntax error in the log:

Screenshot 2022-01-13 at 20 08 38

Screenshot 2022-01-14 at 10 48 18 (2)

@maricavor maricavor self-assigned this Jan 14, 2022
@maricavor maricavor changed the title Missing error message for updating contact with disclosed attributes Missing error message after updating contact with disclosed attributes Jan 14, 2022
@vohmar vohmar added the bug label Apr 7, 2022
@vohmar
Copy link
Contributor

vohmar commented Apr 7, 2022

now any attempt to update contact with additional disclosed attributes results in this kind of response:

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="https://epp.tld.ee/schema/epp-ee-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="lib/schemas/epp-ee-1.0.xsd">
  <response>
    <result code="2005">
      <msg lang="en">Contact contains unsupported attribute(s) [disclosed_attributes]</msg>
    </result>
    <trID>
      <clTRID>Märi Änn ED-1649329505</clTRID>
      <svTRID>ccReg-7424268799</svTRID>
    </trID>
  </response>
</epp>

is this expected? i presume the issue was there before and this issue just resolved the blank error message problem?

@maricavor
Copy link
Contributor Author

No need to validate contact on disclosed attributes when updating

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants