I really need to start reading the project pages before I blindly install updates. Okay..... here's my problem.

I have product pages on this site, http://www.chtech.com . The way things worked about 10 minutes ago was this. If you're logged into the site as an anonymous user you can get access to a PDF datasheet for a product. If you want to access the PDF manual then you have to log into the site. When you're no longer anonymous I used Web FM to create a window(looks like mini table) that you can click on to either the PDF manual or Datasheet to download. The attached file field I use for anonymous users disappears when you're logged into the site. Or you change roles.

Anyway... I had this appear towards the bottom of each product page/node. The rough placement of this window was controlled by "Manage Fields".... or basically the order in which it was listed.

Now, no matter what I do the table (generated by WebFM) that lists the PDF files appears at the very top of the NODE.... as you may have guessed I don't want it there. It's yucky there, I am at a bit of a loss here on how to fix this.

Any suggestions would be greatly appreciated.

Thank you,
Jeffrey

Comments

nhck’s picture

nhck commented
Assigned: Unassigned » nhck
Priority: Major » Critical

That is a bogus patch introduced by #753990: Webfm Field Weight not working -which didn't get flagged as an error. I tried to fix it this morning, but git wouldn't let me commit :-/ For quick fix see: #753990: Webfm Field Weight not working where they say to replace

extras['webfm-attach'] = array(

with

$extras['webfm_attachments'] = array(
zap-admin’s picture

zap-admin commented

Awesome, that fixed me right up. Thanks for posting the mod so I could fix that site.

nhck’s picture

nhck commented
Version: 6.x-2.13 » 6.x-2.15
Status: Active » Fixed

Packed a new release for this. Thank you very much!

roball’s picture

roball commented
Version: 6.x-2.15 » 6.x-2.13

The problem was in 2.13 and seems to have been fixed in 2.15 - thus the version number should be set to 2.13 (the one which had the bug).

zap-admin’s picture

zap-admin commented

Thanks for the heads up. Was just going through the release notes and saw you fixed the issue I was able to tweak with the small code change. Thanks for your hard work on the module.

Status: Fixed » Closed (fixed)

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