# Updated issue info ## Summary The 1.0.0-beta3 release introduced Drupal 11-only hook discovery and API usage that breaks upgrades and runtime behavior on supported Drupal 10 sites. Failed upgrades can also leave context items with missing revision pointers. Enabling Drupal 10 CI further revealed that several attribute-based hooks were never invoked on Drupal 10, causing admin pages to error and Scheduler setup to be skipped. This issue covers: - Restoring Drupal 10 and PHP 8.1 compatibility. - Registering hook services explicitly for Drupal 10 (`DiffHooks`, `DynamicEntityReferenceHooks`, and `SchedulerHooks`). - Adding Drupal 10 procedural bridges for attribute-based hooks that Drupal 10 does not discover, including `hook_theme()` (so AI Context theme hooks such as `ai_context_overview` render) and `hook_modules_installed()` (so Scheduler setup and Content Moderation sync run). - Supporting entity original-value handling across Drupal 10 and 11. - Repairing recoverable missing revision pointers and safely removing incomplete records that cannot be recovered. - Replacing Drupal 11-only APIs in tests and supporting code. - Adding automated regression coverage for compatibility, hook registration, and data repair. - Running previous-major CI automatically. - Supporting Drupal 10 PHPUnit test discovery with legacy `@group` annotations across the module and its submodules. The expected result is that database updates complete successfully, existing context item revisions remain intact, AI Context pages and Scheduler integration work on Drupal 10, and the test suite runs and passes across all supported Drupal and PHP versions. ## Release note **Drupal 10 upgrade fix and data recovery** `1.0.0-beta3` introduced a Drupal 11-only API (`getOriginal()`) and dropped explicit hook service registration, which broke `drush updb` on Drupal 10 and could cause context item saves to fail. On Drupal 10, a failed save could commit a `NULL` revision pointer to the base table, leaving the item's data and prior revisions intact but invisible to the Entity API (it no longer loads). This release restores Drupal 10.5+ / PHP 8.1 compatibility and automatically repairs affected content: - **Update 10011** repairs recoverable items before its backfill runs. - **Update 10013** re-points such items at their latest default revision and safely removes empty rows left by failed first saves. **Action required:** run `drush updb` (or *Admin › Reports › Available updates › Run database updates*) after updating. The repair is idempotent and safe to run more than once. If an item cannot be safely recovered, the update stops with an error identifying the affected item IDs so it can be handled manually. Before manually repairing an affected item, back up the database and inspect the listed item's base, field-data, and revision rows. Restore a verified default revision pointer or remove the incomplete record only after confirming that it cannot be recovered, then rerun database updates. # Previous issue info ## Summary After upgrading to the beta3 release on our Drupal 10 site, drush complains about a few things. ## Steps to reproduce 1. Upgrade to 1.0.0-beta3 on a Drupal 10 project. 2. Run `drush updb.` 3. Watch it error out. ## Expected result The database updates complete without errors. ## Actual result Errors occur prior to/during the database updates (see below for more info). ## Environment - Drupal version: 10.6.13 - Module version: 1.0.0-beta3 - PHP version: 8.3 - Last known working version: 1.0.0-beta2 ### Error messages or logs Original error: You have requested a non-existent service "Drupal\\ai_context\\Hook\\DiffHooks". This is because the service definition was removed with beta3 from services.yml. Drupal 11 is able to pick it up via attributes, but Drupal 10 is not. It's the same for "Drupal\\ai_context\\Hook\\DynamicEntityReferenceHooks". After adding the service definitions back in, I was able to run DB updates, but they failed mid-way at update 10011 because of Call to undefined method Drupal\\ai_context\\Entity\\AiContextItem::getOriginal(). This method is not available in Drupal 10. After I reverted usages to use the magic property `->original`, the DB updates completed successfully. > [!note] > > Check the one that best describes your usage, or leave all unchecked if AI was not significantly used. > > * [x] AI **Assisted Issue** \ > _Mainly written by a human; AI used for partial generation under full human supervision._ > * [ ] AI **Generated Issue** \ > _Mainly generated by AI, reviewed and approved by a human before this issue was created._