Share » Forums » Developer » Please, help me with images in 3.3!

Please, help me with images in 3.3!

Please, help me with images in 3.3!

Thursday 29 January 2004 1:31:07 pm - 4 replies

Author Message

Nicklas Lundgren

Friday 30 January 2004 1:24:49 am

Hi again,
I sorted it out myself.

It came down to the length of the data in ezcontentobject_attribute:s column data_text.
Apparently some of my paths to images were too long in ez 3.3.2 for this column. With the result that only a few images showed up.

I just now found the db update script from 3.3.2 to 3.3.3, where it is a fix for this.
After installing it, it all seem to work out fine.

So, if you come into the same trouble:
1) Upgrade to 3.3
2) Dont forget to run the db update script from 3.3.2 to 3.3.3.

I guess, if I would have stayed in version 3.3.2 I would never have gotten out of this trouble...

Regards,
Nicklas

Kåre Køhler Høvik

Friday 30 January 2004 1:32:23 am

Hi

I find this quite strange. The ezcontentobject_attribuet.data_text in 3.3-2 is able to store upto 64kB of data ( in mysql, unlimited in postgresql ). Are your paths actualy longer than this ?

btw, some code has been added to the soon to be released 3.3-3, to make the new image system more compatible with the old one.

--
Kåre Høvik

Kåre Høvik

Nicklas Lundgren

Friday 30 January 2004 2:31:41 am

Hi again,
Thanks for the reply, Kåre.

If the problem is not caused by the length of the column data_text, then I cant understand what finally solved my problems.

In the end, I started to debug the kernel/classes/datatypes/ezimage/ezimagealiashandler.php.
There I found out that the method aliasList checked if (domTree==false) . If so, the call to generateXMLData took care of creating the images in the right places.

In my case, event though the images had not been created before, the domTree was true!
With the result that the images never were created.

I suppose domTree became true due to the existense of the image in the ezcontentobject_attribute table. But something must have been wrong there, since the images didnt exist under the corresponding places in var/site/images...

Wheter it was due to the length of the data_text, or anything else, im not sure. But I am sure that my troubles were caused by the domtree returning true, when it shouldnt have.

It would be interesting to here your ideas about this.

Kind regards,
Nicklas Lundgren

Kåre Køhler Høvik

Friday 30 January 2004 6:13:27 am

I'm not sure about the domTree == false satement, but I did some changs to the ezimagealiashandler in rev. 4834 to to fix one bug regarding the dom tree.

--
Kåre Høvik

Kåre Høvik

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu