Importing data in field: user-picker or Date picker can end in non valid data / loose data
- Status
- Open
- Subject
- Importing data in field: user-picker or Date picker can end in non valid data / loose data
- Category
- Bug
- Feature
- Trackers
Import-Export - Resolution status
- New
- Submitted by
- Chris
- Lastmod by
- Chris
- Rating
- Description
AD-Field / User-Picker
When importing tracker data (tested via the "old" way as via the tracker tabular) into a user-picker-field, the imported user-name is NOT checked against the Tiki list of users. In the end the user-picker-field behaves just like a normal text-field while importing, accepting just every string and not only valid user-names.This could also be a security problem cause someone could inject non-valid user-names in a internal list of valid users.
What should happen is that when importing values into that field, that every value get's checked against the Tiki user list.
If this heavily slows down the import speed, there should be a checkbox that gives the user the ability to enable/disable the check against the Tiki user list, given the user the deccission to check the user names externally before importing those names.Date field
When importing dates into a date-field every date is accepted. This is also valid if the date is outside the allowed scope which is defined in the settings "Start Year" and "First year in the dropdown". As result everything seems fine as long as nobody edits that item. As soon as someone edits the item (any other field) and saves it, the content of the date fields gets silently deleted, resulting in damaged/lost data.
- Solution
- For me the problem is that the importer just don't check the data if it's valid. This could be a valid way of importing data, but for sure not a secure way. At least there should be a checkbox to enable/disable data checks against the various settings or other data that could interfere with the imported data.
- Workaround
- Check the data carefully before importing and know the system well enough to know the possible problems
- Importance
- 5
- Easy to solve?
- 6
- Priority
- 30
- Demonstrate Bug (Tiki 19+)
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
Version: Create show2.tiki.org instanceAbout show2.tiki.orgTo help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
- Ticket ID
- 7828
- Created
- Saturday 18 September, 2021 08:51:49 GMT-0000
by Chris - LastModif
- Tuesday 05 October, 2021 15:56:22 GMT-0000
Attachments
| filename | created | hits | comment | version | filetype | ||
|---|---|---|---|---|---|---|---|
| No attachments for this item | |||||||
;){kind=link}
;){kind=link}
- fresh opening of tiki home page tiki-index (I removed a warning) is it OK
- Tracker with field type "Numeric" won't
- tiki 25.1 Database 'xxxx'. Unable to connect to database (when 25.0 will connect)
- Kanban plugin; the Swimlane field throw an error if using a category field type
- Kanban plugin: Error if the fields Description and Swimlane are empty
;){kind=link}
;){kind=link}