Images

I'm trying to upload multiple images via FTP. Although they are in the correct directory, they aren't displayed as a thumbnail. I just get the link instead which leads to the “show image-page”, but still no image. Is the reason for this the cache? How can i uplad 20 pictures for a page in a fast way?

• The filenames must be lowercase and without space. You can used Total Comander to convert multipli files from uppercase to lowercase

I'm trying to make an ordinary link (like THIS), just that it would link to an image. I just can't make it work. Can anyone tell me how I can do that?

A bit silly, but first put in your image regularly:

{{wiki:dokuwiki-128.png}}

And then right-click and “copy image location”. Go back and create the link:

[[http://wiki.splitbrain.org/_media/wiki:dokuwiki-128.png?w=&h=&cache=cache|wiki icon]]

wiki icon

I'm using the dev version of Doku 2005-11-09. It'll auto-create namespaces on the fly as pages are created but I can't seem to make it do the same thing for images. I would like for people with upload permission to be able to add images to the same namespace as the page but that requires me to manually create the directory for the namespace on the server. Given the way image uploads work.. can the code be modified to create the media/ subdir when it creates a pages/ subdir? Thanks, Chris - cjm2–earthling–net

since what version does DokuWiki support dynamic images? why mine not working? http://mypolaris.com/doku.php?id=online_status

test here
AIM:
Gabber:

at least we got broken images here, instead of just text…

Where do I put images so they show up on the page?

I don't see a broken image. I see an offline AIM icon. It sounds like image caching maybe the source of your problem as Doku will try to cache images locally to speed things up. I saw a page about turning it off just can't find it at the moment.
Here it is caching cjm 2006/01/24

I wanted to make it so that the image I insert is 'unclickable'… meaning it's just embedded in there and you cannot click it to see the actual picture at a new browser page. How can I do this?

This is not documented, but reading the mailing lists I found the solution:

{{image.png?nolink}}

I would like to make it so that image descriptions appear below the image, in a span as well as in the alt. Can anyone help me with this?

the key file & function are inc/format.php & format_link_media().
at the if block (around line #288), replace the existing code with the code below…

  //prepare name
  if($isimg){
  //--CS (begin changes)
           $link['name'] = '<div class="wikiimage" style="width:'.$w.'px;">';  // insert this line
  //       $link['name'] = '<img src="'.$cache.'"';  // comment out this existing line
           $link['name'] .= '<img src="'.$cache.'"'; // insert this line (changing above from assign to concatenate)
  //--CS (end changes)
    if($w) $link['name'] .= ' width="'.$w.'"';
    if($h) $link['name'] .= ' height="'.$h.'"';
    if($t) $link['name'] .= ' title="'.$t.'"';
    if($a) $link['name'] .= $a;
           $link['name'] .= ' class="media" border="0" alt="'.$t.'" />';
  //--CS (begin changes)
		   $link['name'] .= '<br />'$t.'</div>';          // insert this line
  //--CS (end changes)

then add suitable styles into your style sheet, (normally style.css). Below are two examples (don't use them both )

  /* plain */
  div.wikiimage { border-style:none; padding:0px; margin:3px; text-align:center; }  
  div.wikiimage img.media { padding: 0px; margin: 0px; border-style:none;}
 
  /* fancy */
  div.wikiimage { border-style:none; padding:2px; margin:2px; }  /* containing box style */
  div.wikiimage { color:#ffff00; background-color:#000000; text-align:center; font-weight: bold; } /* text style */
  div.wikiimage img.media { padding: 0px; margin: 0px;}

you don't need the div.wikiimage img.media style, in which case you must edit the img.media style to ensure there are no padding, margins, or borders. These add to the width required for the image and can lead to the text being off-centre. All of your current img.media styles should be transferred to div.wikiimage.

I have tried it in both Firefox and IE6 and the image and text show up ok. The only problem is in IE, where the image is no longer clickable as a link. But that may be because I disabled javascript in IE.

I hope this helps.

<chris@knowledge.teevee>

It doesn't seem like there is an inc/format.php file anymore unless I am completely missing something. Is there another way of going about this?

jsb [at] greatertalent [dot] com

Andi Gohr of DokuWiki fame, has provided a gallery plugin that does everything you ever dreamed of. So the discussion below is largely obsolete. (The plugin requires the development version of DokuWiki. Which development version? Is it still in development? — DGM2 2006-04-24 19:51) Thank you Andi! ~joe lapp

re: dev version - plugin works for me with stable release 2006-03-09, provided small change to syntax.php is made as described on the gallery plugin page - thanks to Mateusz GDS 2006-05-17

Another follow-up to the question of display more of images that you put on a wiki page. What does anyone think about implementing a gallery-like functionality? I was thinking something like:

  {{gallery>/wiki/photos/dogs}}

which would then scan the namespace given ('wiki/photos/dogs') for all images, and display thumbnails of the images. You could click the thumbnails to get full-size images, perhaps also extracting EXIF information. This could make the sharing of a large collection of photos very easy on the Wiki.

I'm planning to provide this extension and am thinking it through. Here are my requirements:

• Can include more than one gallery on a given page.
• Can say where on the wiki page a gallery goes.
• Can control the order in which images are presented.
• Can cycle forward/back through the image pages.
• Can control presentation of thumbnail gallery.
• Can control presentation of each image page.
• Can link each image page back to the gallery's wiki page (or pages?).

Here's what I'm currently thinking of doing:

• Use a syntax such as yours to specify the gallery directory.
• The syntax can specify the maximum thumbnail dimensions, so that all thumbnails are made to fit within the defined box. If no dimensions are specified, default dimensions are assumed.
• Images are presented in filename sort order. [But this approach makes it painful to reorder images when filenames are numbered.]
• A template specifies how the thumbnail gallery is generated as HTML.
• The EXIF title of each image becomes a tooltip for each thumbnail.
• A template specifies how an image page looks. This template says where each EXIF field goes on the page. Back/forward buttons can be put on the template to allow navigation through the image pages.

Some questions:

• Should the image pages be wiki-editable? I'd rather not do this if it's going to be time-consuming to implement.
• How does an image page link back to the wiki page containing the thumbnail gallery in which it appears? What if multiple wiki pages include the gallery? The problem is that google or an external link might point directly to the image page, which in itself has no clue what wiki pages are pointing to it. (I need to look into DokuWiki's existing backlink mechanism.)
• Is there an open-source PHP EXIF library I can include? I don't plan to write one. Must the EXIF library be compiled into PHP or otherwise linked into the web server? [Answer: Yes, since 4.3. PHP must be compiled with –enable-exif. Can we require PHP 4.3 or later?]
• Should I instead leverage the export-as-HTML feature that virtually every image management system provides? If the system's export templates were munged to export to a special syntax we require, then anyone could import image meta data, whether or not they have EXIF tools.

I'm hoping somebody out there will help me think this through. I can't really even start my DokuWiki site without the feature, because the site is going to be heavy on images. Thanks!

~joe www.spiderjoe.com

P.S. On second thought, I want all my text to be editor-editable, grep-searchable, and sed-replaceable. Can't do that if it's locked in EXIF fields. It seems to go against the DokuWiki philosophy to rely on EXIF. So now I'm thinking I'll rely on an image management system's ability to export to HTML and ask that users export to a custom syntax instead. I may have the user export thumbnails this way too, to take some of the burden off of the server.

I think I'll keep the first rev really simple and do something similar to the <gallery> tag in MediaWiki. The actual delimeters will depend on what best fits into the DokuWiki parser. For now, let's assume we can do this:

{{gallery>
thumbBox: 120x120
cropThumbs
image: someimagedir/image1.jpg | Ain't this a pretty photo?
image: someimagedir/image2.jpg | This one didn't quite come out.
image: elsewhereimage.jpg | Threw this one in for kicks.
}}

By default, thumbBox is the size of the box (in pixels) that the thumbnail should fit in. If thumbBox is 200×120, a 400×400 image would shrink to 120×120, retaining its proportions while keeping it in the box.

If cropThumbs is indicated, a thumbnail is created to fill the given box, possibly cropping either the left and right of the image or the top and bottom of the image in order to do the job. With thumbBox 200×120 and cropThumbs on, a 400×400 image would shrink to 200×200 and then have its top and bottom 40 pixels cropped off to fit it within the 200×120 box. This feature makes the thumbnails uniformly sized, ensures that oddly shaped images are still discernable in thumbnails, and generally provides the user with more detail about the image in thumbnail form.

I'm not going with the proposal to show all the images in a named directory for three reasons: (1) the order of the images is important to me, and the cleanest way to provide a order is to list the images by name; (2) I don't want to preclude having the same image in multiple image galleries; and (3) the proposal works with the current image upload facility and doesn't require FTP access or the addition of a special batch-upload feature.

I'll use the 'title' attribute to make the image caption available when the cursor hovers over the image. Upon clicking a thumbnail, the image will be rendered according to a template HTML file, and the template can choose to display the caption. In the future it should be possible to have this template show EXIF information. I'll provide a back-to-article button to make it easy to get back to the wiki page. I don't know whether the first go will provide left/right navigation buttons, but it should be possible to add these in the future.

I don't want make the image a popup. I have done a few sites where the images popped up when clicked and always find it annoying. But the biggest issue is that if google indexes the image page and it's a popup, the site's identity and navigation features aren't available to someone who comes to the page via google (it would be odd to pop up a fully-functional site page).

Lemme know if you have an suggestions or ideas. Thanks!

~joe www.spiderjoe.net

Couldn't you just make a namespace for the image files then create a template that determines how their shown on the page? Some extra syntax codes might be needed to tell it how to display the images though. Just a thought, I'm no expert in php or dokuwiki…

How can I make sure that any uploaded image (of any width and any height) is forced to be displayed in reduced (thumbnail) size on my wiki? Thanks! – Coen

It is giving me fits and I would just prefur to go static images. Is there a reason that fetch.php won't display an image after it is uploaded even if premissions on the media directory is 777 and everyfile is 777?

Tia!

– Steve

I had two installations, only one was not displaying images so I knew the problem was in the settings. The difference between the two in the config, I had specified the base url and directory in the one that wasn't working. Once I removed that, so that it autodetected, the images displayed fine.

$conf['basedir']     = '';                //absolute dir from serveroot - blank for autodetection
$conf['baseurl']     = '';                //URL to server including protocol - blank for autodetect

Hope that helps.

— leah 2006-03-07 22:26

When i want to update an image, i use the updated image with the same filename, which will get ignored. Makes sense to prevent accidential overwriting of other images .. hmm any idea?

In my development Version, there is a Checkbox [ ] Overwerite existing version

• For my dokumentation needs I would like to insert several images and add some descriptive Text beside every one. Using

{{image}} description... 

leeds to the following effect:

Image Description, wich is longer then a line, Description, wich is longer then a line, Description, wich is longer then a line,Description, wich is longer then a line,Description, wich is longer then a line

Image Description, wich is longer then a line, Description, wich is longer then a line, Description, wich is longer then a line,Description, wich is longer then a line,Description, wich is longer then a line

• I find out, that using

{{image }} description...

could help this, but there is a problem left, when I use several images. In this case the images get nested. Any Idea to solve this?

Image Description, wich is longer then a line, Description, wich is longer then a line, Description, wich is longer then a line,Description, wich is longer then a line,Description, wich is longer then a line

Image Description, wich is longer then a line, Description, wich is longer then a line, Description, wich is longer then a line,Description, wich is longer then a line,Description, wich is longer then a line

How can I force the second image to stay left like the first one?

— Konrad Bauckmeier 2005-10-20 11:32

A solution for your issue are new lines \\ \\ \\ between the both pictures. — Anja Vag 2005-10-24 13:38

Image Description, wich is longer then a line, Description, wich is longer then a line, Description, wich is longer then a line,Description, wich is longer then a line,Description, wich is longer then a line


Image Description, wich is longer then a line, Description, wich is longer then a line, Description, wich is longer then a line,Description, wich is longer then a line,Description, wich is longer then a line

— Zaher Dirkey 2007-6-8 5:27

Or you can enable in your setting htmlok and add <br clear=all /></html> instead of \\ \\ \\ I think it must be supported by parser somthing like as \\\

On my wiki I display some pictures but I want to prevent that everybody can download displayed pictures. I read about 2 possibilities to realize it. One is a transparent image which is layed in the forground of the real image. So that everyone who try to download the picture only downloads the transparent picture. The second one is to implement that nobody can take a click on the right mouse button if the pointer is over an image.
Have anyone an idea how to realize the protection or have a solution or know an other possiblity to realize it?
I am really glad if anybody can help me. — Anja Vag 2005-10-24 13:15

If you like to protect your pics against download you have to think about:

• saving the whole displayed page (incl pics) by browsers “save as” funktion or something like “safe for offline browsing”
• download the whole site / or just the pics with wget
• screenshots of your displayed page(incl pics)

So would you really like to spent time in protecting your pics? If you publish them over internet you should rather use watermarks and visible “stamps” with your copyright and url.
cu Mr_Snede

Is there a reasonably straight forward way of attaching credits to images, and having them automatically appear somewhere sensible?

If you have large amounts of pictures and want to ftp them to the media directory directly, do not forget to chmod them to 777 and watch out for strange names (like cyrillic filenames, spaces, dashes, dots) These may upset the caching mechanism / thumbnail creation.

chmod them to 777? –> what does it mean?

CHMOD is a command to change file permissions. You have to check over google on that command to know exactly what that means, but shortly, it means : The dir is writeable by anybody

Is there a possibility to grant gusts access to the media directory corresponding to a certain namespace, while not allowing them access to the namespace itself? I use dokuwiki as a CMS and I only want to allow guests to view certain pages 'ready for public access'. But they can't see the pictures…

One solution would be to create a namespace without protection and load all media to this one, but that would make it quite confusing to find them again. Or I could as well grant access to the namespace while protecting all non-public pages, but that is somewhat unsecure (I use the wiki also for my private documentation (i.e. a lot of copy 'n paste from other sites) and I don't want to forget to secure one page after creating it and getting trouble. Finally (NOW, while writing this, I get the ideas….) I could make a second, public installation and copy all the pages from the existing one for public view. But that's so much effort…
Any ideas how to allow media read access without namespace read access?