Don't create new db records for empty nodewords values

Is this going to mess up the functionality of not wanting to provide specifically no meta tags for an item rather than the default meta tags?

This is still a good issue to track. I'd say that our strategy should be as follows:

- If a default value is set and the default is unchanged when saving a metatag, nothing should be saved to the database.
- If a default value is not set and the field is left blank, nothing should be saved to the database.
- If a default value is set and the default is changed, the values should be saved to the database.
- If a default value is set and the default is left blank, the blank value should be saved to the database.

Or in a chart, here's what it would look like:

                                      |  Default exists | No default set
--------------------------------------|-----------------|---------------
Field is blank                        |   no db entry   |  no db entry
Anything other than default in field  |   save to db    |  save to db
Default value in field                |   no db entry   |      N/A

subscribing

- If a default value is set and the default is unchanged when saving a metatag, nothing should be saved to the database.
- If a default value is not set and the field is left blank, nothing should be saved to the database.

I see two problems with that.
How can the module know if nothing saved in the database means to use the default value or the empty value?
If the default values are changed, what should the module do? Should the module find any meta tag without a value in the database, and save the default value for them? If the answer to the last question is yes, how can the module distinguish between the case where the meta tag value has been left blank, and the case where the default value has not been changed?

I closed #1145010: Database performance and space efficiency as a duplicate of this.

To properly handle this we'd almost need a checkbox to go with each tag to decide if the override should be used, then a bit of JS gravy to enable/disable the text field. Obviously that would need API changes and would make the module more difficult to use.

Bumping this to v2.

Marking all v2 issues as postponed while v1 is finished off.

Unfortunately this module is no longer supported, so I'm closing this issue.