You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe that Drupal 7 sites would be better served by removing them and using this:
metatag
(Of course, if a site is already using one, we wouldn't want to change without migrating all the data already stored in the data stores of these modules.)
Metatags (Quick) and Page Title were only being used because they were available for Drupal 7 earlier than Metatag. Metatags (Quick) stores data in field storage, whereas the Metatag module uses its own database storage. Metatag also does take care of Page Titles. And, Metatag can be configured to populate the META tags using Tokens of other fields from the node or other content, so in some cases intelligent Meta tags could just use the body data or something else. Of course, this data can be overridden on a per-node or per-page basis. And finally, Metatag supports a ton of different meta tag options, including some for serving data to Twitter or Facebook (maybe module needed), settings for robots to not index that page, and many other things.
If we wanted to, we could also customize the setup of metatag via the slave1 profile if desired.
The text was updated successfully, but these errors were encountered:
Currrently, these two modules are installed:
I believe that Drupal 7 sites would be better served by removing them and using this:
(Of course, if a site is already using one, we wouldn't want to change without migrating all the data already stored in the data stores of these modules.)
Metatags (Quick) and Page Title were only being used because they were available for Drupal 7 earlier than Metatag. Metatags (Quick) stores data in field storage, whereas the Metatag module uses its own database storage. Metatag also does take care of Page Titles. And, Metatag can be configured to populate the META tags using Tokens of other fields from the node or other content, so in some cases intelligent Meta tags could just use the body data or something else. Of course, this data can be overridden on a per-node or per-page basis. And finally, Metatag supports a ton of different meta tag options, including some for serving data to Twitter or Facebook (maybe module needed), settings for robots to not index that page, and many other things.
If we wanted to, we could also customize the setup of metatag via the slave1 profile if desired.
The text was updated successfully, but these errors were encountered: