Remove the deprecated #used_fields from the address element

Created on 27 December 2023, 11 months ago
Updated 11 January 2024, 11 months ago

When we released Address 1.4 (5.5 years ago) we introduced #field_overrides and deprecated #used_fields. We then added code that converted #used_fields into #field_overrides and removed all #used_fields examples. We released 2.0.0 but forgot to remove #used_fields when we were removing the other deprecations. We'll have to remove it now.

📌 Task
Status

Fixed

Version

2.0

Component

Code

Created by

🇷🇸Serbia bojanz

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @bojanz
  • Status changed to Needs review 11 months ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
    last update 11 months ago
    43 pass
  • Status changed to RTBC 11 months ago
  • 🇦🇷Argentina tguerineau

    I have tested the patch 3411071-2.patch in drupal 10 and am providing feedback.

    Testing Process and Observations:

    1. Functionality: After applying the patch, I created and edited content with address fields to assess any impacts from the removal of #used_fields. The module behaved as expected, with no issues in creating, displaying, or editing addresses.
    2. Cross-Browser Testing: The module functioned correctly across different browsers.
    3. Role-Based Testing: Different user roles interacted with the address fields without any issues.
    4. Error Checks: No related errors were observed in Drupal logs or browser consoles.

    The patch, which focuses on removing deprecated code (#used_fields), appears to be functioning correctly without any adverse effects on the module's operation. Based on my tests, I believe the patch is successful in its intended purpose and does not introduce new issues.

    • bojanz committed 47e437e9 on 2.0.x
      Issue #3411071 by bojanz: Remove the deprecated #used_fields from the...
  • Status changed to Fixed 11 months ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024