I installed Drupal 6 today learned how to create pages and menus but I'm confused about adding images. The image module looks like its still in development, so I guess I could:

1. install 5.x instead and use the image module.

2. create html code in my editor (dreamweaver) then paste that into drupal page content form. How does html linking work? For example if I upload image.jpg to my root www folder what would be the relative path to a given page? because I don't even know where pages are saved to.

Comments

bikebeard’s picture

I had the same problem. I can add images though (installed lightboxV2 too) but can't figure out how to use images already uploaded.

For the linking I found this worked: Only local images are allowed.

/Bike

tm’s picture

the image module has a dev version for 6; maybe you can help them push it along by testing, etc.

have not played enough in v6 yet to say if the old manual syntax still works (src path relative to base_url), but in any case, the image file should be somewhere in the /files folder (wherever that is). if you are using the private file system, it should be uploaded through the drupal framework. if public, you can put it there and point.

i really should go look for the v6 handbook pages...

pcofran’s picture

I ended up uninstalling 6 and using 5.x instead and that has worked out fine for me.

although as a general comment I'm not sure how well drupal scales up. I come from using dreamweaver where it keeps track of what files are being used. so you can delete all the pictures that are no longer needed or move them and it updates all your site links.

Now that I've given users the ability to upload pictures what happens a year later when that folder is filled with hundreds of pictures. so when you upload a picture you'll have to wade through all those pics. there won't be anyway to tell which ones you can delete or if you move them to an another folder will it break all the links? From a maintenance point of view it could be a nightmare.

tm’s picture

drupal is pretty "flat;" all nodes are created "equal", no hierarchy. images and attachments are in the file system; everything else is in the db. since there are articles/recipes for creating flickr-like sites out there, scaling can't be too bad, as long as you keep expectations proportional to the allocated resources.

otherwise, don't know what to tell you regarding the file proliferation/management; it is one of those things with user-driven content. you decide whether or not you want to open the gate, then hope the stampede doesn't run you over. user/role-based quotas might help a little; just be careful about installing some sort of batch uploader.

2 cents