Separate the types of verifications

Created on 4 November 2009, about 15 years ago

Updated 15 October 2024, about 2 months ago

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.

📌 Task

Status

Postponed

Version

2.0

Component

Code

Created by

🇺🇸United States dave reid Nebraska USA

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment about 2 months ago →
🇦🇺Australia elc
This would be achieved as a side effect of of ✨ Provide exportable configuration Active .
Comment 2 days ago →
🇦🇺Australia elc
Fixed as part of ✨ Provide exportable configuration Active .

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.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024