#311 closed defect (wontfix)
Allowing users to embed local images into pages
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | wiki system | Version: | 0.6.1 |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Up to now users have been able to edit any page and add an URL to an image. If the image is located elsewhere in the Internet it's OK ; but people should be able to link a page to a local image stored in the same server as trac.
This implies:
- to allow users to upload images to a local directory, or into the SQLite database
- to define a convention as for the URL of such images
- to take care of the namespace for such images
For instance, one could imagine that these images are stored into the SQLite database and simply retrieved using their filename, say toto.png
; then there could exist but one single image named toto.png
for the whole wiki pages. An alternative would be to map the images to URLs such as WikiPage/imageName.png
Attachments (0)
Change History (3)
comment:1 by , 21 years ago
comment:2 by , 21 years ago
in 0.7-pre there are wiki attachments. its possible to embed an image with e.g:
{{{ #!html <img src="http://host/project/attachment/wiki/WikiPage/image.png?format=raw" /> }}}
unfortunately you have to add ?format=raw, so the html tag is needed. maybe it would have been better if wiki/WikiPage/attachment.foo would be the link for the raw download everywhere in trac (wiki/ticket attachment, browser)
comment:3 by , 21 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Works, in one of two (generic) ways:
- Like vittorio explained above, use attachments. See #358 for a complete example.
- Use a locally stored image 'pool' on you webserver and link directly too them.
Ahem… sorry for the bad formatting :-(