By rocketboy37 on

I'm using Drupal 6.9 on Suse Linux Enterprise with the following modules, imce, images, FCKEditor, views, and I have clean URL's enabled. The process is I upload an image into a gallery name the image and gallery. Create page go to add image to page I can see image in Editor but once i publish the page I get no image.

Does Drupal move the image after it has been applied to a page or a block this happens in both instances. I can see the image in the server using IMCE but for some reason I cant see the image once I add it to page, block, or a book.

Help please my annual review and pay depends on getting this done.

Addenum:

I'm creating a content type image I have not added any vocabulary or items to the taxonomy. I'm still getting the error above. Can anyone help, really? This is driving me mad, I have rebuild this server 3 times now.

Thanks

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

A) you should be upgraded to Drupal 6.11
B) ensure you are using the FULL HTML input format

rocketboy37’s picture

rocketboy37 commented

Why do i need to upgrade to 6.11 i will try to the full html mode.

dddave’s picture

dddave commented

Security!!

rocketboy37’s picture

rocketboy37 commented

I'm worried that some of modules wont work though, in fact several are probably not going to work.

marquardt’s picture

marquardt commented

It's almost certainly the input filter that strips out the img tags... I have upgraded from 6.10 to 6.11 (and before from 6.9 to 6.10) with the same modules you mention, and didn't experience problems. I would argue that within minor Drupal upgrades, chances for modules to break are very slim when they worked properly before. You see, minor version do not change the functionality or interfaces; they just fix bugs.

vm’s picture

vm commented

why would several modules NOT work on a 6.11 install if they work on a 6.9 install?

on one hand, protect the site from harm by updating <-> on the other, run a security risk of a site that someone could exploit if they wanted?

even if I had to give a up a module or two (which you shouldn't have to) it would be worth protecting the site itself.