Image in object not appearing when using attribute_view_gui

Monday 15 November 2004 8:56:46 am

Bit of a bizarre problem happening here. I have an object called
"Partner" that contains an image as one of the attributes. These objects
are stored in various folders based on country (e.g., USA, Canada, etc.).
I display the folders using an override template that pulls the children
and displays them in a list. For nearly all of the objects, the image attribute
displays perfectly fine when I use this line in the template:

{attribute_view_gui attribute=$:item.object.data_map.logo}

Now here is the bizarre part; I created a few new folders and moved some of the
existing objects into these new folders. Suddenly, the image attribute
will no longer display on these moved objects. Also, I can create a new object
in any of the folders, either the new ones I created or the existing ones,
and the image will not display.

I have tried flushing all the caches, but the fact that new objects seem
to be affected as well concerns me that there might be a larger problem
going on. The image directories appear to be created fine, and doing

{$:item.object.data_map.logo|attribute(show)}

produces the output I would expect to see.

Any ideas what might be wrong? At the end of my tether on this one.

Monday 15 November 2004 1:57:44 pm

Yes, I have tried with images that worked before; also, it does not seem
to matter what type of image file you use. gif, jpeg, png... they do
not seem to show up at all. Disk space is not an issue; the disk ezpublish lives on is only 7% full.

The odd thing is that I have other, similar objects that are working fine under
similar template conditions. They have an image attribute that appears just
fine. However, any new or moved content in a particular section seems to
not have the images displayed. All of the old content in that section still
displays their images even after a flush of the cache.

Very odd; will have to flip on debug over the weekend or late at night
to see if anything shakes loose from that. But, again, I am completely
stumped by why this is just starting to happen only in one section.