Upgradet to Ez 3.3-1. Several fatal errors on site.

Thursday 08 January 2004 6:46:50 am

Hi

I upgradet to EZ 3.3-1 today. However, this have led to several problems, some content objects are not shown instead this error is displayed:

Fatal error: Call to a member function on a non-object in c:\develop\ez_gsa\ezpublish-3.3-1\kernel\classes\datatypes\ezimage\ezimagealiashandler.php on line 601
Fatal error: eZ publish did not finish it's request

Secondly it does not seem to find any images, it is searching this path: Failed converting var/storage/images/news/... However, this path does not exsist, images are under var/storage/orginial/images/
It seems as ORginial is left out of the path! Anyone know what I might be doing wrong, or is this an error other people also have with 3.3.1

Cheers
TOre

Thursday 08 January 2004 7:17:39 am

Hi Claüs

Thanks for the tip about the new image system. I did not have a clue about that!

About the "call to member" error. It basically only came from one content class (i.e when its view template was called). As the image system had changed I removed my ad hoc image stuff in the template. Then it worked (images are of course not working:(). This was removed and caused the fatal error:

{section show=is_object($node.data_map.thumbnail.content)}
<div class="img_left"><a href={$node.data_map.thumbnail.content[original].full_path|ezroot} target="_blank">{attribute_view_gui attribute=$node.data_map.thumbnail image_class="inline"}</a></div>
{/section}

It was there in order to make an link to view the image in full size.

I am a bit afraid that now I will have to pay the price for the lack of basic functions in EZ (such as attribute!=null), this lack of basic funtions have led me to use extensive ad hoc variable checking in order to implement required functionality. However, this variable checking is probably going to be messed up in the future as the variables changes meaning or disapper.. Huhh looking at many hours going through template code....