Thread

ahh.. okay i’ve had to really look into this—what’s happening is it’s not rendering the custom field with the url inside it for any member that’s not a super admin.

When we publish from the CP, we add a pdf to that field that’s specified as a file field.  On the front end our code looks like this:

{exp:channel:entries channel="morningcomments"  sort="desc" limit="1"}

<a href="http://{cattlemorningcommentspdf}">DOWNLOAD THE PDF</a>

{/exp:channel:entries}

This is what’s rendering if you’re any member besides a super admin:

<a href="http://">DOWNLOAD THE PDF</a>

Hi design132,

From which version did you upgrade? Also, if you check the exp_channel_data table, what value is in the column for the entry’s row/column. (You may have to check the exp_channel_fields to find the correct custom field_id)

– Wouter

exp_channel_data : 

Field Type Collation Attributes Null Default
entry_id int(10)            UNSIGNED No None

exp_channel_fields
Field Type Collation Attributes Null Default Extra
field_id int(6)            UNSIGNED No None AUTO_INCREMENT

I’m confused… but does that help?

Sorry… I actually meant the actual value of the cell that holds the field_type value.

It should be something like ‘{filedir_2 }‘your_image.png’.

– Wouter

The field_type is “file” so it looks like the attached file.

"https://ellislab.com/asset/images/ent-partner-work/GMC_11-28-12.pdf"

Again, what’s weird is it will work for superadmins.  But not for other members.  Kinda odd behavior.  It should just be rendering what I put in that field.  Are there some permission issues under member accounts that I have not seen?

okay, I’m going with a wild guess here… can you try to sync the upload directory in the filemanager?

I did just sync it but nothing happens ;-(

This is the first time I’ve ever experienced this.  It almost seems like there’s a permissions issue.  Why it’s allowing super admins to view it no problem, but not members.

Ok, so update… I have multiple member groups.  One for my client, and then super admin, we can both see the graphs, but anyone that’s not given access to the CP can’t.  Does that help?

I didn’t even see that part of your initial question… that complicates things a bit. There is nothing in the code that suggests that member groups come into play when outputting the tag.

Does this happen to every pdf you upload into that field, or just this particular one? And does it happen to all file fields you have on your site?

Actually after some testing, just this channel it’s happening on.  In fact, this was the only channel that I had previously had the field type as “text”, and then changed it to “file” so the client could upload the pdfs easier.  I’m wondering if this has something to do with it.  You made me think in a new direction and I think we’re getting close to the problem. (it’s the only channel that I changed the fieldtype)

Ah, finally! Some positive news 😊

Since you’ve changed it from a text-field it could be some kind of a formatting error, but that still doesn’t explain why it only happens for regular members…

Without actually getting hands-on, I’m afraid I’ve run out of ideas. Anyone else care to step in?

– Wouter

Ya I think it’s safe to say this could be a bug in EE.  The fact that it’s only affecting members but not those whom have access to the CP means it’s not even functioning as expected, but that all I’m doing is rendering an input field with a tag…. 

Perhaps those at EE can step in and suggest something, and I’m all for offering access to the system to take a better look.

Wouter—thank you for your help thus far!

*** bump***

Hoping an EE dev can help me out on this one… 😉

Please refer for the continuation to this thread at: http://ellislab.com/forums/viewthread/230332/