Support for Exportables (Features)

Created on 27 July 2011, over 13 years ago
Updated 4 November 2024, 30 days ago

Since Site Verification stores its data in its own table {site_verify}, it isn't possible to add them to a Feature module.

Would be very useful to be able to do so on an individual basis so that each entry can be put in different feature modules when so is required.

✨ Feature request
Status

Postponed

Version

1.0

Component

Code

Created by

πŸ‡ΈπŸ‡ͺSweden tsvenson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • πŸ‡¦πŸ‡ΊAustralia elc

    The first set of patches in there completely replaces the admin ui with ctools, which would add a dependency to an otherwise lightweight module just before D7 EOL. If it was looked at 12 years ago, it would be part of it but there's no point making such a huge change now.

    The second set of patches implement the features ctools export part, seem incomplete, but would be a way to get this done, however the requirement and functionality of the export should be offloaded to a sub-module "site_verify_ctools" which when enabled would abuse the hook naming possibilities to provide the parent module's hooks. The aim of the trickery would be allow site_verify to continue on without a hard ctools dependency. 2 months out from D7 EOL.

    Postponing unless someone is really keen to work through making this feature.

    For Drupal 10/11 see ✨ Provide exportable configuration Active .

Production build 0.71.5 2024