Decouple G2 Glossary from dedicated type g2_entry, permit user chosen node type

Created on 30 January 2010, over 14 years ago

Updated 27 June 2023, about 1 year ago

The is no compelling reason I can see for restricting the handled node type to 'g2_entry'.

define('G2NODETYPE',          'g2_entry');

If we proceed to use this module to handle our highly customised Definition node type, which contains a LOT of data already, we currently have these choices:

Mimic our type into , and then use Node Type to convert them all (which I might be able to automate a bit).
Intervene in the G2 Glossary module code and set it to use our 'definition' type, which works like a charm, you are welcome to view it running at: http://ppi.webel.com.au/g2/initial/c (development site, temporary only)

Obviously for now I'm taking the last one :)

✨ Feature request

Status

Active

Version

1.0

Component

Code

Created by

🇦🇺Australia webel

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 year ago →
🇫🇷France fgm Paris, France
Progress note: in the D9/D10 8.x-1.0-alpha1 version, the node type is now a constant wherever it appears (or it should be: if not open an issue to fix it).

This will make it easier to support other bundles as a replacement for g2_entry. At that point the main hassle will be the configuration, which has to be aware of the bundle to create fields on it, meaning whenever/if this is introduced, all relevant config will have to be generated by code instead of a simple config import.

As to supporting other entity types, there is really no point and a lot of the logic depends on the NodeInterface property, so that one will be a won't fix AFAICS.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024