We instead of a per-engine storage record in {site_verify} we should store SVID, verification type (meta/file), associated engine (google/custom), and the data (meta tag, file name and contents, etc). In order to prevent duplicate entries, I might need to add a hash column that would store the MD5 hash of the meta tag or file name to prevent duplication.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Or split these into different tables, {verification_file} and {verification_meta}. :/ Hmm.

elc’s picture

elc commented
Version: 7.x-1.x-dev » 2.0.0-alpha2
Issue summary: View changes
Status: Active » Postponed
Parent issue: » #3008860: Use ConfigEntityType for exportable SiteVerification storage

This would be achieved as a side effect of of #3008860: Use ConfigEntityType for exportable SiteVerification storage.

elc’s picture

elc commented
Version: 2.0.0-alpha2 » 3.0.x-dev
Assigned: dave reid » Unassigned
Status: Postponed » Fixed

Fixed as part of #3008860: Use ConfigEntityType for exportable SiteVerification storage.

The SiteVerification content entity has validation constraints on duplicating the filename, but does still store both types in the same ConfigEntityType for simplicity of storage and handling.

Duplicate meta tag is not restricted as it is normal operation for their to be multiple of the same meta tag name.

Status: Fixed » Closed (fixed)

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