[Bug 39812] New: Add the ability to replace an uploaded image
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 Bug ID: 39812 Summary: Add the ability to replace an uploaded image Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs@lists.koha-community.org Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org It would streamline the process of replacing an image if we could simply replace the upload file without changing the link or anything else. If we have to replace an image, we have to upload a new one, copy the link, and replace any references to the old image. Replacing the file would allow a quick and simple process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 --- Comment #1 from Owen Leonard <oleonard@myacpl.org> --- Replace images where? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 --- Comment #2 from Christopher Brannon <cbrannon@cdalibrary.org> --- (In reply to Owen Leonard from comment #1)
Replace images where?
Where ever Koha stores images when you upload them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #3 from David Cook <dcook@prosentient.com.au> --- Are you referring to the "Tools > Uploads" feature? -- It looks like the key is a MD5 hash of a whole bunch of different parameters. For temporary uploads, the time of the upload is one of the parameters, which is weird. For permanent up loads, time isn't used. But for all uploads, the first 2048 bytes of the file is also used as one of the parameters. Honestly, I find that a bit... wild. Surely just hashing the category + filename would've been sufficient. That said... if you replace the contents of a file and don't change the hashvalue, you could experience caching problems. Pros and cons to the different methods. I suppose there could be a system preference that allows for different methods for computing the hash value. Not something I'm likely to work on, but it's an interesting idea. It actually makes you think a bit about the philosophy of files and documents in general. What IS the document? Is it the name, is it the content, etc. Anyway, if you're not referring to "Tools > Uploads", then the answer might be something else. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 --- Comment #4 from Christopher Brannon <cbrannon@cdalibrary.org> --- Honestly, I am referring to any file that can be uploaded. Yes, the Tools --> Uploads is one example, but cover images, patron images, documents linked in records. There should be a process to replace these files without having to break any links to them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 --- Comment #5 from David Cook <dcook@prosentient.com.au> --- (In reply to Christopher Brannon from comment #4)
Honestly, I am referring to any file that can be uploaded. Yes, the Tools --> Uploads is one example, but cover images, patron images, documents linked in records. There should be a process to replace these files without having to break any links to them.
So they all use different mechanisms. Cover images should already be replaceable I think. Same for patron images. Not sure what you mean by "documents linked in records". That might be the upload.pl cataloguing plugin? That one would be the same as what I've described above. But then changing a URL when editing a record shouldn't be a big deal. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 --- Comment #6 from Christopher Brannon <cbrannon@cdalibrary.org> --- Yes, upload.pl. That is not a plugin as far as I can tell. But this one definitely does not have a mechanism for replacing a file. I can delete, and I can upload (which is goofed up, by the way - if I delete a file, then try to upload, it doesn't do anything, and I have to do it again). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 --- Comment #7 from David Cook <dcook@prosentient.com.au> --- (In reply to Christopher Brannon from comment #6)
Yes, upload.pl. That is not a plugin as far as I can tell. But this one definitely does not have a mechanism for replacing a file. I can delete, and I can upload (which is goofed up, by the way - if I delete a file, then try to upload, it doesn't do anything, and I have to do it again).
Is it the one that you access through the cataloguing editor? The underlying script used for that is "cataloguing/value_builder/upload.pl" which sometimes gets referred to as a "cataloguing plugin" - different thing from a Koha Plugin. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39812 --- Comment #8 from Christopher Brannon <cbrannon@cdalibrary.org> --- (In reply to David Cook from comment #7)
(In reply to Christopher Brannon from comment #6)
Yes, upload.pl. That is not a plugin as far as I can tell. But this one definitely does not have a mechanism for replacing a file. I can delete, and I can upload (which is goofed up, by the way - if I delete a file, then try to upload, it doesn't do anything, and I have to do it again).
Is it the one that you access through the cataloguing editor?
The underlying script used for that is "cataloguing/value_builder/upload.pl" which sometimes gets referred to as a "cataloguing plugin" - different thing from a Koha Plugin.
No, it is through tools: /cgi-bin/koha/tools/upload.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org