Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Excluded elements in fields sometimes won't bootsrap #220

Closed
paxtonhare opened this issue Apr 25, 2014 · 1 comment
Closed

Excluded elements in fields sometimes won't bootsrap #220

paxtonhare opened this issue Apr 25, 2014 · 1 comment
Assignees
Labels
Milestone

Comments

@paxtonhare
Copy link
Contributor

When defining a field with excluded elements in ml-config.xml you might be tempted to leave out unused options:

              <field-name>stuff</field-name>
              <include-root>true</include-root>
              <included-elements></included-elements>
              <excluded-elements>
                  <excluded-element>
                      <namespace-uri>http://www.namespace.com</namespace-uri>
                      <localname>things</localname>
                  </excluded-element>
              </excluded-elements>
          </field>

Left out of the above xml are:

                      <attribute-namespace-uri/>
                      <attribute-localname/>
                      <attribute-value/>

The roxy code to create an excluded element passes these to the function as () but the admin api really wants "".

@paxtonhare
Copy link
Contributor Author

fixed

@dmcassel dmcassel added this to the v1.6 milestone Apr 25, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants