- 🇦🇺Australia elc
Use ConfigEntity bundles to store the two types - meta and file.
- 🇦🇺Australia elc
Updating version to 3.0.x as this has become a full re-write of the module.
- Merge request !15[#3008860] Migration from database storage to exportable ConfigEntityType. → (Merged) created by elc
- 🇦🇺Australia elc
The "phpstan (next minor)" error is unavoidable until 📌 Backport Hook and LegacyHook Attribute Active lands. At that point both of the errors in the phpstan.neon file can be removed.
Very much open on feedback and patches on this! Will be making a 3.0.0-beta1 release in about a week if I don't get feedback, and that'll be out in the world for testing from then on.
One item of note is the simplification of the admin form for creating and editing the entities - it now only includes the name and the content fields, and does not have a full metatag entry, or a file upload field. There was already confusion about the file uploading part, fixed in 2.1.0-rc1, but it was added complexity that I didn't feel was needed in what was already a full re-write of the module.
- 🇦🇺Australia elc
Still @todo
- Update README with current usage instructions (file/meta entry has changed to just name/content entry with parsing html meta line and file upload field processing no longer included)
- Finish adding help hooks (code completed, not pushed)
- Confirm if the forced validation currently coded breaks sync import of config, which was the entire point of this change - Status changed to Needs work
22 days ago 5:22am 17 December 2024 - 🇦🇺Australia elc
Confirmed that importing did not work with validation being a requirement but it not being automatic. Made validation automatic and required.
@todo
- ➖ Add test to import SiteVerification entities through config.
- ➖ Update project home page
Still waiting on release of 11.1 and 10.4 to get rid of the phpstan error about Hook/LegacyHook not existing yet.
- 🇦🇺Australia elc
Drupal 11.1.0 and 10.4.0 have been released, fixing the Legacy/Hook false positive.
This will be merged into 3.0.x when I get the chance to update/write the release notes for dev/beta. Reviews always welcome, but not blocking.
I feel the review will effectively be on the release which will be a new branch and a beta, and will not remove support from any of the existing branches, so this makes it safe enough for it to be released as is.
- 🇦🇺Australia elc
Released as 3.0.0-beta1 or 3.0.0-beta2
Follow up task 📌 Update project page Active
Automatically closed - issue fixed for 2 weeks with no activity.