Closed (fixed)
Project:
Site verification
Version:
3.0.x-dev
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Jul 2009 at 18:52 UTC
Updated:
16 Dec 2024 at 04:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
andypostTake a look at patch #12 #467582: Change the settings page
Comment #2
dave reidLet's keep this as a separate patch please.
Comment #3
andypostPatch adds a new field to database, changes add|edit forms, remove "useless" field Verification from table (for now only Yes is possible inside)
Suppose Edit-Delete actions should be placed in 1 column separated by " " - this brings more "good-looking" in most themes.
Comment #4
dave reidOperations get their own column. That's the standard/pattern set by core, so we don't need to change that.
Comment #5
andypostLet's postpone this till #467582: Change the settings page
Comment is very useful but changing listing page is #1 task
Comment #6
tsvenson commentedJust added a custom verification in the Drupal 7 version and yes, it would be very nice to be able to change the name to the engine added.
Comment #7
elc commentedThis could be done as part of #3008860: Use ConfigEntityType for exportable SiteVerification storage - it very much makes sense for the addition of a site verification record to be generic and allow admin description. Admin could set the machine_name + name instead of it being set by the module.
Changing name, but leaving as postponed as it would be part of the other issue.
It would be a new field/column in a D7 patch, but due to the pending EOL of D7 it would not be ported.
Comment #8
elc commentedFixed as part of #3008860: Use ConfigEntityType for exportable SiteVerification storage.
The SiteVerification content entity allows the admin to set the label, id, and description which are displayed in the entity list.