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 with Site Verification 3.x, where an update operation could attempt to save roles before Drupal's routing data 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 a stable interface based on an SVG world map, while Navigation Extra 1.0.5 addresses an invalid Content navigation entry. These are targeted maintenance and feature releases rather than a coordinated Drupal update.

Site Verification Upgrade Fix Moves to 3.0.2

The Site Verification problem concerns a specific combined upgrade path rather than Drupal 11 compatibility in general. According to the 3.0.1 release information, the failure could occur when the module's update process saved roles before the routes required by that operation were available. That could interrupt an upgrade involving Drupal 10, Site Verification 2.x, Drupal 11 and the module's 3.x branch.

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. Its release summary describes another fix for updating between major core releases and references CacheableMetadata. Teams following the 3.x upgrade path should therefore use the current 3.0.2 release rather than stop at 3.0.1.

The fix remains specific to an upgrade sequence. The available information does not establish data loss or show that every site moving between those Drupal and Site Verification branches will encounter the failure. Site Verification 4.0.0-rc3 is meanwhile the current release candidate for Drupal ^11.3 || ^12, while 3.0.2 remains the stable release for the Drupal 10.3 and Drupal 11 compatibility line.

Timezone Picker 1.0.0 Replaces the Legacy Map

Timezone Picker 1.0.0, released on 21 September 2026, moves the project onto its first stable 1.0 release. Its release information describes a replacement for the legacy image-map interface using a responsive SVG world map, with keyboard interaction for selecting a timezone.

The release also provides optional browser geolocation and removes runtime jQuery dependencies. For site builders, the practical change is a newer timezone-selection interface with keyboard interaction and an optional location-based shortcut rather than the older map implementation.

Existing users moving onto the stable branch should test the updated map, keyboard interaction and any geolocation behaviour in the context of their own theme and user-profile forms. The interface change is also relevant to new sites considering the module as an alternative to Drupal's standard timezone list.

Navigation Extra 1.0.5 Repairs Content Menu Administration

Navigation Extra 1.0.5, released on 22 September 2026, addresses a narrower administration problem. According to its release information, the module could create a navigation entry with an empty route name, producing an invalid entry that could interfere with administration of the Content menu. Version 1.0.5 prevents that entry from being created.

The release is therefore relevant to sites using Navigation Extra that encounter the affected Content administration behaviour rather than to Drupal installations generally. Users of the module can apply the maintenance update and confirm that the Content navigation behaves normally afterward.

The three changes have different operational significance. Site Verification has the clearest upgrade implication because the original problem can interrupt a combined Drupal and module major-version transition. Timezone Picker 1.0.0 establishes a stable replacement for its older map interface, while Navigation Extra 1.0.5 addresses a specific administration defect. Teams should assess each release against the module and workflow they actually use rather than treating the three as a common update requirement.