This question about Using an extension: Asked
TopicType inconsistent behavior on topic creation
Overview
I'm seeing inconsistent behavior when creating topics of custom
TopicType; sometimes the resulting topic gets its
TopicType formfield set correctly, but sometimes it does not. Behavior seems to depend on how the destination web was created and how the topic is being created.
I'm not sure if I'm misunderstanding how to correctly set up the forms in custom
TopicTypes, or if there may be a bug in one [or more] of these plugins...I just don't know. I'm looking for more eyes, and more experienced eyes, to help me figure out what's going on.
Using
Given
Observed Behavior
Within web
FromClassificationTemplate, no matter whether I create a new topic from
NatSkin +New (and select
VendorTopic), or from the New button on
VendorTopic, the resulting topic's dataform does not have
VendorTopic listed in the
TopicType formfield.
Default Webs
Within web
FromDefault:
Side Effects
Topics that don't get
VendorTopic properly set don't show up in the topic listing at
VendorTopic. Those topics are also not shown in form fields of type 'topic' (from
MoreFormfieldsPlugin) that have value set to
TopicType ="VendorTopic".
| *Name:*| *Type:* | *Size:* | *Values:* | *Description:* | *Attributes:* | *Default:* |
| TopicType | label | 1 | VendorTopic, ClassifiedTopic, WikiTopic | topic type | | VendorTopic, ClassifiedTopic, WikiTopic |
| TopicTitle | text | 75 | | Vendor Name | | |
| Summary | text | 75 | | short description or tagline | | |
| SalesContact | text | 75 | | Sales Rep name | | |
| TechContact | text | 75 | | Tech Contact name | | |
| CustomerNumber | text | 32 | | Customer # | | |
| Tag | tag | 30 | | keywords for this topic | c | |
| Category | cat | 1 | | categories this topic is field to | | |
--
DanGlassman - 15 Sep 2017
I updated the text above to show that:
- I'm using a TopicTemplate
- Additional observations about NatSkin behavior
- Added default values to my DataForm (which didn't change the described behavior, unfortunately)
--
DanGlassman - 19 Sep 2017