Thread

I recently upgraded a client’s site from 2.1.0 to 2.5.3 and everything seems to have gone through fine, except when I look at the site, in one place where images are supposed to be pulled in (from a file field in a channel), the image paths aren’t being pulled. This is the code in the template:

{exp:channel:entries channel="home_logos" dynamic="no" limit="10" orderby="id" sort="asc"}
      {home_logo}
{/exp:channel:entries}

And this is how it renders:

" width=
" width=
" width=

As you can see, it pulls the {title} just fine, but not the image field. What could be causing this? I’m about to roll back to 2.1.0 because it’s unacceptable that the site has no images displaying on the front-end, but I will need to upgrade and I do need a solution for this.

Ok, this is weird and it might be a bug worth looking into. I went to one of the entries which contained an image, removed the image from the file field and added it back. All of a sudden, once that entry was saved, all the images showed up again.

Hi antiuser,

Be on the lookout for an email from me. I’ve seen this happen once before, but it seemed to be an isolated case. I’d love to have a first-hand look at your system to see what happened.

Just wanted to check in to make sure you got my email, antiuser. Do you need me to send it again?

Kevin,

We are having a similar issue. All of our src attrs are blank when the page renders, but only when you are a logged in member. If you are logged out or if you are a member of group 1 everything works fine. If you are a member of any other group however half of the image tags are missing the src value.

Kevin,

We tracked it down. The function _get_upload_prefs in file_field.php is not returning any data due to the users not being able to upload to the directory that the images are in, this is causing the file to stop processing and not parse the tag for any viewable image on the site that was uploaded with the file manager and that user group does not have access to. Do you feel that this is a feature or bug?

Hey VIM,

I think that’s been fixed up in this bug, reported here. Could you apply the fix and see if that takes care of it for you?