I'm using image_assist (http://drupal.org/project/img_assist) to attach images to nodes. I've tried to attach an image to a biblio entry (use cases are showing the first page of a paper like in the commercial publication databases or the cover of a book).

This works, but it is only possible to attach it to the "Full Text" field (not sure why exactly, but it seems to be the only field allowing HTML input as formatting type). This is obviously not optimal, since when viewing the node the image will show up under "Full Text", but there's actually no text at all.

I've tried using a custom field for images, but again image assist does not work (because they are not html input fields(?)). So, the question is, is it possible to make the custom fields HTML-aware, or is there a better way to get images into biblio nodes?

Comments

rjerome’s picture

I'll look into this.

rene_w’s picture

Having played around with it a bit more, the actual problem is that the only field capable of HTML entry is the "Full Text" field (since this is where the input filters kick in).

So, the actual feature request is allow custom fields to have (full/filtered) HTML input as well, not just plain text.

It would also be good if it were possible to enable a different input format for other fields, like "Abstract": Currently, when I paste the abstract from papers, I loose all formatting (italics, bold, URLs, etc.).

rjerome’s picture

It used to be like that, and I will revert it to that mode.

rjerome’s picture

It would appear that image_assist can only put images into "textarea" type fields. The normal node body is a textarea, but biblio nodes are not "normal" nodes in terms of display,so it will take a little more digging to find a work around.

rene_w’s picture

Not sure what you mean. As I mentioned, it works fine with the "Full Text" field (which is HTML), but not with any other custom or non-custom field (because they are not html enabled).

liam morland’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.