#183 Custom field name cannot contain spaces in 1.2, whereas they could in 1.1

[Anonymous]

If a Custom Field name has a space in it in 1.2, it is unable to save any information to it. Log files menu is showing that we are posting a NULL whenever changing the field. Actually, if you do any type of change to the device, all of the custom fields that have a space in the name will end up posting NULL, effectively deleting any data.

The Details section in the web log lists:
Object id=8 in devices edited id: 8 hostname: HOSTNAME ip_addr: 0.0.0.0 type: 10 vendor: Dell model: R320 description: DESCRIPTION sections: 3 version: CentOS 6 Switch Port: NULL Service Tag: NULL Warranty Date: NULL Rack U slot: NULL CPU: Xeon 2.8GHz Quad Core Memory: 16GB HDD 1: NULL HDD 2: NULL Power Outlet A: NULL Power Outlet B: NULL VM Host: NULL Console: NULL

All of that data was filled, and only one was edited, which resulted in every field containing a space in the name cleared.

If you rename the custom field and remove the space, it works OK (though obviously, you need to get a backup for the lost data)

This worked OK in 1.1 and 1.0

[Miha Petkovsek]

Hi, this was changed because in order to match custom fields in HTML POST the name cannot contain spaces. I did some workarounds to add triple _ instead of space.

http://www.w3.org/TR/html401/interact/forms.html#h-17.13.1

The "get" method restricts form data set values to ASCII characters. Only the "post" method (with enctype="multipart/form-data") is specified to cover the entire [ISO10646] character set.

Please change spaces to underscores.