Site Verification Fix Targets Drupal 10-to-11 Upgrade Failure

Site Verification's recent 3.x releases address an upgrade problem that can appear when Drupal core and the module cross major versions together. The issue was documented for sites moving from Drupal 10 with Site Verification 2.x to Drupal 11 while updating the module to its 3.x branch, where update 10301 could fail while saving roles before required routes had been rebuilt. Site Verification 3.0.1 introduced a fix on 22 September, and 3.0.2 followed on 23 September as the current stable 3.x release.

Two other contributed-project updates affect different parts of site administration. Timezone Picker 1.0.0 establishes its first stable release for Drupal 11 and Drupal 12 with a redesigned SVG map, while Navigation Extra 1.0.5 fixes an invalid Content navigation entry. The releases address separate upgrade, interface and administration concerns rather than forming a coordinated Drupal update.

Site Verification Upgrade Fix Moves to 3.0.2

According to the Site Verification 3.0.1 release information, update 10301 could fail when Drupal 10 was upgraded to Drupal 11 at the same time as Site Verification moved from 2.x to 3.0.0. The underlying issue involved saving roles before the routes required by that operation had been rebuilt.

Drupal.org now lists Site Verification 3.0.2, released on 23 September, as the current stable 3.x release for Drupal ^10.3 || ^11. The release retains the major-version update fix and adds another follow-up task, while its notes also instruct administrators to flush and rebuild caches after updating the code. Teams following the 3.x upgrade path should therefore use the current 3.0.2 release rather than stop at 3.0.1.

The problem concerns a specific combined upgrade path rather than Drupal 11 compatibility in general. The available release information does not establish data loss or show that every site crossing those Drupal and Site Verification branches will encounter the failure. Site Verification 4.0.0-rc3 is meanwhile available for Drupal ^11.3 || ^12, while 3.0.2 remains the stable branch covering Drupal 10.3 and Drupal 11.

Timezone Picker 1.0.0 Replaces the Legacy Map

Timezone Picker 1.0.0, released on 21 September 2026, is the project's first stable release for Drupal 11 and Drupal 12. It replaces the legacy image map with an accessible, responsive SVG world map and adds keyboard navigation with visible hover and selected states.

Browser geolocation remains available with permission and HTTPS guidance, while configurable map colours have been added. The release removes jQuery and other runtime JavaScript dependencies and preserves the module's integration with Drupal's regional settings and user-profile timezone fields.

Existing users moving to the stable branch should test the updated map, keyboard interaction and any geolocation behaviour in the context of their own theme and forms. New Drupal 11 and Drupal 12 sites can also use the module as a map-based alternative to Drupal's standard timezone selection interface.

Navigation Extra 1.0.5 Repairs Content Menu Administration

Navigation Extra 1.0.5, released on 22 September 2026, fixes a narrower administration problem. The module could create a navigation.create.user menu-tree entry with an empty route name, which could break administration of the Content menu. Version 1.0.5 prevents the affected invalid entry from being created.

Navigation Extra 1.0.5 supports Drupal ^10.3 || ^11 || ^12. The maintenance release is relevant to sites using the module and encountering the affected Content administration behaviour rather than to Drupal installations generally.

The three releases carry different operational weight. Site Verification has the clearest upgrade implication because the affected update can interrupt a combined Drupal and module major-version transition. Timezone Picker 1.0.0 establishes a stable Drupal 11 and Drupal 12 interface, while Navigation Extra 1.0.5 corrects a specific administration defect. Teams should assess each release against the modules and workflows present on their own sites.