Insert Query problem

Good catch by @smvec — a missing value in the VALUES list is a very common cause of an INSERT failing when you supply an explicit column list. @pritaeas was also right to suggest checking the database error first; the native error text usually tells you whether it is a column/value count mismatch, a duplicate key, a bad date format, etc.

Quick troubleshooting checklist:

• Log or echo the final SQL string before execution and verify the number of columns equals the number of values.
• Check for stray commas or unbalanced quotes that can change the value count.
• Confirm NOT NULL columns are getting values (or have defaults).
• Make sure date fields are supplied in a valid format (YYYY-MM-DD) or use a TIMESTAMP/DATETIME default.
• If the failure is a duplicate key, check the primary key value rather than column counts.

Schema and safety suggestions (practical, years-later advice):

• Store phone numbers as text (VARCHAR) not INT — INT(20) does not increase storage and loses formatting/leading zeros; see MySQL integer types (reference: https://dev.mysql.com/doc/refman/8.0/en/integer-types.html).
• Use TIMESTAMP or DATETIME with DEFAULT CURRENT_TIMESTAMP for registration time when appropriate.
• Never store plain-text passwords; use PHP's password_hash()/password_verify() (reference: https://www.php.net/manual/en/function.password-hash.php) and allocate sufficient column length.

Modernize the database access:

• The old mysql_* extension is removed in current PHP versions. Move to mysqli or PDO and use prepared statements to avoid quoting/count mistakes and SQL injection (see mysqli prepared statements: https://www.php.net/manual/en/mysqli.quickstart.prepared-statements.php).

Actionable next steps: reproduce the failing SQL string, count columns vs values, fix schema/data types as needed, and migrate to prepared statements for safer, more reliable inserts.