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

Misses proper documentation/handling of what to do when a stored value does not match requirements any more #19

Open
do3cc opened this issue Mar 9, 2015 · 0 comments

Comments

@do3cc
Copy link
Member

do3cc commented Mar 9, 2015

We get a traceback that ends like this:

  File "home/starzel/.buildout/eggs/z3c.form-3.0.5-py2.7.egg/z3c/form/field.py", line 277, in update
    widget.update()
  File "home/starzel/.buildout/eggs/z3c.formwidget.query-0.10-py2.7.egg/z3c/formwidget/query/widget.py", line 152, in update
    terms.append(source.getTerm(value))
  File "home/starzel/.buildout/eggs/plone.formwidget.contenttree-1.0.7-py2.7.egg/plone/formwidget/contenttree/source.py", line 130, in getTerm
    % str(value))

We are using an UUID Binder. The object the UUID is refering to does still exist, but the UUIDBinder has some constraints that this object does not contain anymore. In hindsight, one should not add such a filter. In hindsight

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

No branches or pull requests

1 participant