Opened 17 years ago
Closed 16 years ago
#5140 closed defect (duplicate)
Images versioning on the wiki
Reported by: | Filipe | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | attachment | Version: | |
Severity: | normal | Keywords: | attachment |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
As I understand it, images attached to wiki pages aren't versioned, and perhaps should. MediaWiki does this very nicely. This might be a sensible issue as disk space usage may rise quite a bit when images are replaced often, but then again, this may not be an issue in most trac usages. An admin option to establish the operation mode would be nice.
I see this feature as very useful specially when it comes to SVG images, as they are merely text (xml), and so one could easily compare the several existing versions (great for collaboratively drawn pictures).
This ticket depends on ticket #5139.
Attachments (0)
Change History (3)
comment:1 by , 17 years ago
Keywords: | attachment added |
---|---|
Milestone: | → 2.0 |
comment:2 by , 16 years ago
I think the title of this ticket could be more general: this is not an issue with images but with any kind of attached files.
Since disk constrains can be indeed an issue, this could be somehow related with ticket:65 (not implementation-wise, but functionally-wise).
At the same time, this could be seen as related to ticket:1132 too. Once you manage to get all your data integrated within your SCM tool (at the very least wiki pages and attachments), you could use it for revision maintenance.
In the mean time, when I feel it's worthing for a resource to be versioned, I don't managed it as an attachment, but I include it somewhere within the repo, and then I reference it with a source: link.
comment:3 by , 16 years ago
Component: | general → attachment |
---|---|
Milestone: | 2.0 |
Resolution: | → duplicate |
Status: | new → closed |
Indeed, duplicate of #1493.
I don't see how that depends on #5139…
Anyway, versioning is useful even if you don't have a direct way to visualize diffs between the versions. If that gets eventually done, it'll depend on #53.