The Topics have been created as specific project, but still all node types add their own Topics implementation. This leads to problems, like this: #1960694: Questions are missing the "Topics" field.

I'm now having issues with the Topics field being in a collapsed box on the node/add/event but it misses the fieldset on node/add/document.
Can we add it dynamic on all commons_files_entity_types? The Commons Topics module already has the field_base, but misses the field_instances.

I'll add a patch that will add this field separate, just like the og_content_access field.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

BarisW’s picture

Here's what I've done:

- Added a way to add the topic field to all nodes types that implemented hook_commons_entity_integration(), except those that have set 'exclude_topics' to TRUE.
- Moved the field instance creation from commons_groups to commons_topics.
- Removed all field instances from the current entity types.
- Moved the topics form alter and JS to the commons_topics module.
- Added depencies to commons types that use topics.

jpontani’s picture

Assigned: Unassigned » jpontani

Reviewing now. Related to #1960694: Questions are missing the "Topics" field. Going to mark that as a duplicate of this, since it will be fixed when this is committed.

jpontani’s picture

Forgot to add in a features pipe alter. We want to prevent the topics field instances from being exported to new features since it's being added dynamically.

http://drupalcode.org/project/commons_topics.git/commit/c6620a0

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.