Why some form fields reject spaces, dashes, and special characters

You type a campaign name with a space in it, or a user ID with a dash, hit save, and the characters vanish. It looks broken, but it is doing exactly what it was built to do. VICIdial filters many form fields so that spaces, dashes, and other special characters are stripped before they ever reach the database.

Why the filtering exists

This is a security and data-integrity guard. Certain combinations of non-letter, non-number characters in a field like a login prompt can corrupt or even delete data once they pass through the system. Rather than trust every operator to never paste a stray quote or semicolon, VICIdial removes the risky characters from the input. The harm is gone, and so is the character you typed.

The reason this matters more in VICIdial than in an average web form is what the values get used for. A user ID or a campaign ID does not just sit in a record. It gets woven into database queries, into the dialplan that routes calls, and into filenames and login strings. A character that means nothing in plain English can mean something specific to a database or a shell. The filter exists so that a value typed by a busy operator can never accidentally become an instruction.

Where you will hit it

The fields most likely to filter are the ones that become identifiers or get reused inside the dialplan and the database:

• User IDs, passwords, and phone logins, which are matched against the database on every Agent session login.
• Campaign IDs, list IDs, and ingroup IDs, which are wired into call routing.
• Status codes and Disposition labels, where a clean code matters because it is stored on every Lead and counted in reports.
• Anything used as a key or prefix that downstream queries depend on.

What gets decided when you save

flowchart TD
  A[You submit a form field] --> B{Field is filtered?}
  B -->|No| C[Value saved as typed]
  B -->|Yes| D{Contains special chars?}
  D -->|No| C
  D -->|Yes| E[Strip dashes spaces and symbols]
  E --> F[Save the cleaned value]
  F --> G[You see characters missing]

How to work with it

• Stick to letters, numbers, and underscores for IDs and codes. Underscores read cleanly and survive the filter.
• Put the human-readable name in the description or name field, not the ID field. Descriptions are far more permissive.
• If a value silently shortens after saving, that is the filter, not a save error. Re-enter it without the special characters.
• Never try to disable the filtering to force a character through. The protection is load-bearing.

A common source of confusion is pasting from a spreadsheet or a document. Those tools love to insert smart quotes, non-breaking spaces, and invisible formatting that look identical to plain text on screen. The filter strips them, and you are left wondering why half your pasted value disappeared. When in doubt, type the value by hand into a plain field rather than pasting it, especially for anything that becomes an identifier.

If a clean ID still will not save, the problem is elsewhere, and a stuck admin form can have the same feel as a frozen agent screen. The fixes in fixing a frozen agent screen cover the browser and session side of stuck UIs. For the broader checklist, see the VICIdial troubleshooting playbook.

Let the guardrails do their job

The character filter is one of the quiet things that keeps a VICIdial database from eating itself. VICIfast ships a hardened, managed box with those defaults in place and a server live in under 40 seconds. See our plans and pricing.