You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We recently upgraded to version 1.7.0, and now when I tried to edit one of our custom subnet fields with the set-type, I get the following error:
Error: SET functionality not fully implemented, please change to ENUM
Failed to edit field
When I change to ENUM I instead get this error:
Error: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'custom_Organisation' at row 824
Failed to edit field
I don't know when this was last working, this was the first time I tried to edit this setting.
phpIPAM version
V1.7.0
Your Environment (please supply the following information):
phpIPAM version: 1.7.0
OS: RHEL9
PHP version: 8.1.27 64bit
Webserver: Apache
Database: mariadb Ver 15.1 Distrib 10.5.22-MariaDB
Steps To Reproduce
Please include steps to reproduce the issue:
Go to 'Custom fields' under the IP RELATED MANAGEMENT section
Under Custom Subnet fields, click on '+' to make a new field
Fill in the required fields, select Type 'set'
See error
Screenshots and error logs
The text was updated successfully, but these errors were encountered:
Describe the bug
We recently upgraded to version 1.7.0, and now when I tried to edit one of our custom subnet fields with the set-type, I get the following error:
Error: SET functionality not fully implemented, please change to ENUM
Failed to edit field
When I change to ENUM I instead get this error:
Error: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'custom_Organisation' at row 824
Failed to edit field
I don't know when this was last working, this was the first time I tried to edit this setting.
phpIPAM version
V1.7.0
Your Environment (please supply the following information):
Steps To Reproduce
Please include steps to reproduce the issue:
Screenshots and error logs
The text was updated successfully, but these errors were encountered: