I TRIED TO SUBMIT THIS BUG BUT I CAN'T FIND IT AFTER SUBMIT. SO I AM TRYING TO RESUBMIT IT AGAIN. SORRY IF IT CAUSES A DUPLICATE.
I upload an image to the File Gallery, which gets assigned id=19.
Then I go to a page and insert the following Tiki markup:
To (a) provide a link to download the image, and (b) insert the image inside the page.
Works up to here.
But then, I do:
The problem however, is that the new image has id=20, not the old id=19. But the id has not been changed on the link and IMG plugin that I inserted on the page. So they still point to the old image with id=19.
The weird thing is that I can still download image id=19 (even after clearing my cache), eventhough I can't see that image in the gallery anymore. In other words, the image is still in the DB and can still be accessed.
This is definitely not how things should work. If I upload a new version of an image, then all references to that image should be updated accordingly, and I should not be able to access the old version, except in a "view history" kind of context. No?
It appears that this is not a bug per se, but rather a bad choice of default for a preference.
Indeed, if you set the following preference:
Then TikiWiki behaves as I (and I suspect most users) expect. When you upload a new version of the file, it keeps the old fileID, and replace the file's content with the new version. All references to the file or image therefore point to the new content.
Unfortunately, this option is not active by default, eventhough in my opinion, it corresponds to what 99% of users would want.
The solution is simple: just make that option be set to on by default.
Marc Laporte pointed out also that there is another option that allows you to keep prior versions of the file in some form of history. This option is supposedly off by default. I couldn't find it, but if it exists, then it should probably be set to "on" by default (unless we are concerned about increasing the size of the DB because of keeping many versions of large binary objects).
Could this be working in recent Tiki versions? Please retest.
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|