Before last DEV release I didn't have this problem and it worked perfectly.

I display my FileField with MIME icon and URL to download it.
This format is standard and not one of mines.
Here is example in FileField's screenshot http://drupal.org/files/images/filefield-progress.png

Few days ago I upgraded to last DEV version : 6.x-3.x-dev (2010-Jan-09)
And now no icon and no URL appears anymore.

In works in Admin "Node Edit" pages but not in users "Node View" pages.

Could it be due to a bug in last DEV release ?
How must I write code to display FileField in this format in my node.tpl.php pages ?

Comments

quicksketch’s picture

quicksketch
he/him
commented

Could you post a screenshot of the incorrect behavior? There are no database differences and very few code changes between the 3.2 version and the latest dev. You should confirm that the correct formatter ("Generic File") is selected on your admin/content/node-type/[type]/display page. Note if you've removed the $content variable then these formatters are not even used at all, it may be caused by a change in your theme.

srobert72’s picture

srobert72 commented

My field is "CCK FileField" with "File Upload" widget.

In "Display fields" dropdown list propose me Image style options and not File options.
I can't find "Generic file" but I see ImageCache alias for example.

I tried to create new FileField field and I have same problem.
Very surprising !

I use :
Content 6.x-2.x-dev
FileField 6.x-3.x-dev
ImageField 6.x-3.x-dev

quicksketch’s picture

quicksketch
he/him
commented

Hmm, that is very unusual. The "Generic files" formatter shows up for me on a clean install (running the latest 3.x dev). I would suggest checking that all the necessary files are in the "filefield" module directory (i.e. the filefield_field.inc and filefield_formatter.inc files). It's also possible that another module is altering the list of formatters and has removed the normal FileField formatters, though why it would do that I do not know.

srobert72’s picture

srobert72 commented

Hmm OK I think it's a conflict with ImageField_Extended module : http://drupal.org/project/imagefield_extended.
It works perfectly before and I upgraded it on 10/jan/2010. Same date I upgraded FileField module also.
ImageField_Extended CVS messages talk about theme : http://drupal.org/project/cvs/578084

I'will check if last version from 12/jan/2010 repairs this problem.
Instead I will transfer this issue to ImageField_Extended module.

I use :
Content 6.x-2.x-dev
FileField 6.x-3.x-dev
ImageField 6.x-3.x-dev
ImageField_Extended 6.x-3.x-dev

But something strange I don't understand.
For this particular field where I have problem, I use CCK FileField only, and not CCK ImageField or ImageField_Extended.
So I wonder how ImageField_Extended can interact here.

srobert72’s picture

srobert72 commented
Project: FileField » ImageField Extended
Priority: Normal » Critical

Hi all,

I changed this issue to FileField_Extended module.
I've just downgrade to FileField_Extended 3.1 and problem disapears.

It seems really due to last FileField_Extended 6.x-3.x-dev (since 2010-Jan-10)

Thanks a lot for your work.

alan d.’s picture

alan d. commented
Assigned: Unassigned » alan d.
Priority: Critical » Normal
Status: Active » Needs review

Hiya

Me bad. I never planned to handle any display options, but was pushed into creating on due to multiple request. This new feature created this issue.

I thought that CCK would have had a namespace per module as the theme callback suggests. It doesn't, so my default formatter nuked the FileFields' default formatter. I've committed directly to CVS with the namespace ife which should resolve any issues.

I'll take the dev version off for a day and release it tomorrow when the new one is packaged up. There is an update to do a full cache flush included.

Thanks for finding this.

Regards

srobert72’s picture

srobert72 commented
Status: Needs review » Reviewed & tested by the community

I updated today to FileField_Extended 6.x-3.x-dev (2010-Jan-14).
Correction is OK, problem solved.

Thanks for your work.

Regards

alan d.’s picture

alan d. commented
Status: Reviewed & tested by the community » Fixed

Excellent. The dev will be tagged as a new release in the next couple weeks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.