hi.
we just upgraded from 4.7 to 6. very happy with D6 UI and now happy with calendar/views (after some struggling). 2 problems re: images.
1) in 4.7, we used the image module and embedded images using TinyMCE into nodes (events and stories). when i upgraded to 6 (and updated to the latest Image module, none of our image nodes are showing the old images. they are still all there on the server, and i can manually embed them with WSIWYG, but why wont they show up on their own nodes? (i have checked permissions, btw). please help!
2) aside from the loss of all the old content... we are wondering how to move forward. Image_field has been suggested, but i cannot get it to display an attached image. for instance, this node: http://www.mediasanctuary.org/node/432 has an image embedded via image_field. it shows up in the edit mode, but not in the view mode. am i being stupid here?
there is a lot of debate around how to handle images. very frustrating. at this point (after much headbanging and a few days of unforseen volunteer labor) i am actually happy to recreate the clunky workflow of uploading images via the Image module and manually embedding with WSIWYG, but that still doesnt take care of all our back image content that will seemingly need to be reuploaded?!?! why did we upgrade!?
any answers out there?
Comments
Some stuff to check
First, the "missing" image content - look at the html output of the page. Do you see a proper image tag where you expect one? If the answer is yes, can you view the image directly (i.e. by copying the src path into your browser)? If you can't, then there could be something wrong with file settings or permissions.
If you don't see an image tag at all, are you sure that your current filter is set to allow the image tag (look in /admin/settings/filters)? If not, it's getting stripped out in the node render.
Concerning the image field module, the basic display settings are in the content type 'display settings' tab:
/admin/content/node-type/YOURTYPENAME/display
I have no idea what other problems could be caused by going from 4>6; many modules only expect to jump one major version at a time.
thanks 4 the reply. "If the
thanks 4 the reply.
"If the answer is yes, can you view the image directly (i.e. by copying the src path into your browser)? If you can't, then there could be something wrong with file settings or permissions."
No... i do not. my permissions are ok. what do you mean by file settings?
i go image_filed display worked out.
-a
there's basic settings at
there are basic settings at /admin/settings/file-system - if you're using the 'public' setting, and the file path is correct, you should be able to access the image directly.
If the file path is:
sites/mysite/filesthe page should render with
<img src="sites/mysite/files/file.jpg>"and you should be able to see the image at
http://mysite.com/sites/mysite/files/file.jpgIf that simple test fails, then double check your server file directory paths and permissions.
If you're using a 'private' files setting, then there may be something screwed up with drupal's translation.
NOTE: Other modules can also affect file paths, like IMCE or Image Cache.
so.... maybe??....
the old image module put files in files/images and thats still where they all are on the server and they are visible. for instance:
http://www.mediasanctuary.org/files/images/Little%20Caughnawaga1_2.previ... that image is visible where it is embedded in nodes via html, but not as the image node itself (from whence it twas embedded).
my settings at: /admin/settings/file-system say that the file system path is /file (and it IS set to public)
so... does that mean that shifting all my image content from the files/images directory to the /files files directory one level up could restore the visibility of the images on their nodes?
thanks for your help on this!!!
Go to /admin/settings/image
Go to /admin/settings/image and see what the Default image path is. (Should continue to be the default of 'images'). In that case, this is not the issue. If it is blank, then try setting that to 'images' first before doing anything rash to your filesystem.
Aaron Winborn
Drupal Multimedia (book, in October!)
AaronWinborn.com (blog)
Advomatic (work)
Aaron Winborn
Drupal Multimedia (my book, available now!)
AaronWinborn.com
Advomatic
it is set to images & examples
ok... yer right. that is not the issue. the image file path is indeed set to /images.
to further illustrate the issue....
image as viewed directly from server:
http://www.mediasanctuary.org/files/images/Little%20Caughnawaga1_2.previ...
image as embedded via html in an (old) event module
http://mediasanctuary.org/node/435
image node (nothin!!)
http://mediasanctuary.org/node/361
Image module vs. file attachment
Hi alynn - On the image node (http://mediasanctuary.org/node/361) - did you add the image to the image node as an attachment (via the upload module)? Or, via the image field? It should not be uploaded as an attachment (in fact I would suggest disabling attachments for image types to avoid this confusion).
not just an image problem
If these nodes are supposed to be the same, this seems to go beyond just a file problem (in fact, your files settings seem ok). The second example is rendering nothing at all in the content area, as you can see in the source:
<div class="content"></div>moving files won't help; you need to find out what's blocking the rendering of the content. Another module? Something in the theme? If you don't already use it, the devel module will let you see the before-render and after-render elements of the node, which might help.
images were uploaded in 4.7
yea... i saw what you are saying roger. weird, eh?
as for jm's comment... they were uploaded in 4.7 using create content>image
our workflow was to upload images, then embed them crudely by cutting & pasting the image location into the image embedder on TinyMCE (we could never get image assist to work in 4.7). that is the background.
then we upgraded 4.7 -> 5 -> 6, and now are images are on the server, and the nodes are intact, but the nodes are not displaying images.
i just want to make sure it is not something i am missing. my next move (if nothing is resolved here) is to try and use image import in D6 to import the images from there place on the server and assign them to (newly constructed) galleries.... then go through and delete the bad image nodes (eek. there are a bunch.)
thanks all. more commentary appreciated. i cant believe no one else i can find is having this issue. lots of people use the Image module and lots upgrade from 4->6.
a
Hm. jm... now that i think
Hm. jm... now that i think about it, perhaps the images were attached. they would still have nodes created for them right? if that is the case, what would you advise? and what do you think about the Image Import idea?
a
Image Assist?
Were you using Image Assist with TinyMCE to insert Image nodes? That's what it sounds like, but that wasn't clear from your workflow description.
Aaron Winborn
Drupal Multimedia (book, in October!)
AaronWinborn.com (blog)
Advomatic (work)
Aaron Winborn
Drupal Multimedia (my book, available now!)
AaronWinborn.com
Advomatic
image import
I think the image import does sound like your best bet. How many image nodes are there? Ideally I think figuring out a way to move away from image module to the image_field module is the best practice.
The other option would be to create a custom theme page for images that display the file attachments inline (if there is an attachment). That would be a lot easier.
other notes
re: rogers comments
the theme is aboutpeople - out of the box w/o modification
we dont currently use devel. i have used it on past jobs, but never really needed it all that much... (i was not doing the dirty work)