-
Notifications
You must be signed in to change notification settings - Fork 6
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
Data model class for Taxon Attribute is incorrect #1229
Open
grantfitzsimmons opened this issue
Oct 18, 2023
· 2 comments
· May be fixed by specify/specify7#5367
Open
Data model class for Taxon Attribute is incorrect #1229
grantfitzsimmons opened this issue
Oct 18, 2023
· 2 comments
· May be fixed by specify/specify7#5367
Comments
grantfitzsimmons
changed the title
Data model class for Taxon Attribute is incorrect
Oct 18, 2023
xml-editor
: Form for Taxon Attribute is showing up under Collection Object Attribute
It looks like the class="edu.ku.brc.specify.datamodel.CollectionObjectAttribute" This is what is making it show up there. specify6/config/backstop/global.views.xml Lines 284 to 292 in 945d28f
<view name="TaxonAttributes"
class="edu.ku.brc.specify.datamodel.CollectionObjectAttribute"
resourcelabels="false">
<desc><![CDATA[Subform within the Collection Object form.]]></desc>
<altviews>
<altview name="TaxonAttributes View" viewdef="TaxonAttributes" mode="view"/>
<altview name="TaxonAttributes Edit" viewdef="TaxonAttributes" mode="edit" default="true"/>
</altviews>
</view> |
Solved in specify/specify7@c9e509d |
36 tasks
36 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Even though a form is defined to show up under the Taxon Attribute table, it is showing up under Collection Object Attribute and not Taxon Attribute.
See below: (https://nbmmnb5523-xml-editor.test.specifysystems.org/specify/resources/view-set/2/CollectionObjectAttribute/TaxonAttributes)
In the XML editor:
In the Visual Editor:
❓ ❗
The text was updated successfully, but these errors were encountered: