Phone Field Validation Broken in 1.7.22 - Affects Registration & Profile Update[RESOLVED]

General HivePress
1

UPDATE - RESOLVED: The issue turned out to be a browser cache problem. Both Brave and Opera had cached a broken version of intlTelInput.min.js from the moment of the 1.7.22 update.

Solution: Hard refresh (Ctrl + Shift + R) or clearing browser cache (Ctrl + Shift + Delete) resolves the issue immediately.

The underlying getCoreNumber JavaScript error may still be worth investigating to prevent future caching issues, but the bug is not critical.

Hi HivePress Team,

I’m reporting a bug introduced in version 1.7.22 affecting the Phone type field under User Attributes.

The Problem: The Phone field shows a validation error “Please enter phone number” / “[Field Name] is a required field” even when filled with a valid phone number.

Steps to Reproduce:

  1. Create a User Attribute with Field Type: Phone and Required: enabled

  2. Go to the Registration modal OR the Edit Profile page

  3. Enter a valid phone number (e.g. +35989XXXXXXX)

  4. Attempt to submit — validation error appears despite the field being filled

Key Observations:

  • The bug affects BOTH the Registration modal AND the Edit Profile form

  • The HTML element shows: data-countries="[BG,BG]" (duplicate country code) in some cases

  • Browser console shows: Uncaught TypeError: Cannot read properties of undefined (reading 'getCoreNumber') at intlTelInput.min.js ver=1.7.22.27

  • The issue is NOT present on a staging site running an older version of HivePress

  • We attempted to downgrade but were unable to do so without causing additional site errors

  • The bug appears to be browser cache related — users with a fresh browser/incognito window do not experience the issue

  • A new user successfully registered during our testing, confirming the issue is not affecting all users

  • Another user reported the same issue: “Phone Field under user attributes still is required even after filling it” (Bug Reports, Feb 23)

Environment:

  • HivePress version: 1.7.22

  • WordPress: latest

  • The bug appears to be related to the intl-tel-input library update in 1.7.22

  • Hard refresh (Ctrl+Shift+R) or clearing browser cache resolves the issue for affected users

Impact: The bug is intermittent and browser cache related — not affecting all users. However the underlying getCoreNumber JavaScript error should be investigated and fixed to prevent the cached broken version from causing issues.

Happy to provide additional details, screenshots, or console logs if needed.

Thank you,
Ivan

1 Like
2

Hi,

Thanks for the update.

The recent two updates weren’t related to the phone attributes, so there shouldn’t be any issues with this field, as we hope to have resolved all bugs in previous updates.

1 Like