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.
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.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To 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.
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot
|No attachments for this item|