we should investigate the current data storage model in nodewords and figure out if we need to change how we are going to store meta tags and the meta tag settings from an architecture standpoint. A few things to consider:
1. We will likely want to use fields #864404: Make 'Meta tag' fields. This does a lot of work for us.
2. Do we want different meta tag settings based on entity type (node/term/user) or bundle (node type)?
3. We will likely want to be able to export any settings into code.

Comments

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

I think we first need to work out what we want to do from a UI & overall architecture perspective (see my ideas in #864386: Simplify the UI) before deciding the storage mechanism? As you may know I'm a huge fan of using variables as they can be hardcoded in the settings.php files thus a) help track changes, b) help prevent accidental data loss.

andypost’s picture

andypost
he/him
Primary language Russian
commented

Storage model as field (1 table per entity?)

1) Dashboard screen - List of "enable/editable list of features: entitys/bundles/fields/regions/menu-items (like taxonomy vocab list scree)
2) Edit/Add set of allowed tags per feature screen
3) metatag field widget - Summary/edit #796658: UI for field formatter settings

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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