View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
13457 | Feature requests | Other | public | 2018-03-07 17:37 | 2018-03-13 16:56 |
Reporter | tbart | Assigned To | |||
Priority | none | Severity | feature | ||
Status | new | Resolution | open | ||
Summary | 13457: surveyIDs longer than 6 digits | ||||
Description | I have a special case here: I want to match survey IDs to IDs of another application. The DB has int(11) for surveyID, so I took a bold step, edited the maxlength="6" property in the input when cloning a survey, set it to 10, entered a longer surveyID and everything seems to work out flawlessly. Is this safe? Will I run into problems further on? Why is the input restricted to 6 digits when the backend seems to be designed for more? If it is just this single location of code that restricts the input to 6 digits - may I ask to increase it to the limit the backend is capable of, so others can benefit as well? There's no real downside to this - people can choose shorter IDs any time. | ||||
Tags | No tags attached. | ||||
Bug heat | 2 | ||||
Story point estimate | |||||
Users affected % | |||||
The PDF queXML produces cuts down the surveyID to 6 digits, so ootb this does not seem to be supported. I am not enough into the actual PDF generation step to see whether it would be possible to change that behavior.. |
|
It can be changed in application/libraries/admin/quexmlpdf.php ! protected $idLength = 6; |
|