Saturday 18 December 2004 5:56:09 am
Well, now I see that problem is much deeper than it appears from the first sight. Finally - I solved the case, but it revealed something for me that makes me now doubt about Ez engine at all. I believe this is wrong topic, but... anyway, I gone though most known major CMS systems (yeah I even did a few sites in Typo3) so it's pretty much not a problem for me to catch up with a new one, also I stick with PHP from the version 3.0.8 - so I "think" I know what php-based CMSs are internally. But this case just made me lost for a few hours wondering around, searching Ez forum, docs and so on. I dont know what's that now, maybe some Ez gurus would explain? here's a code that finally worked just fine:
{attribute_view_gui image_class=medium attribute=$Article:item.data_map.image.content.data_map.image}
it accepts all the changes I put - image_class, alignments etc w/o a problem. Ie it does display the image, uses my classes when said to, uses href if said... Behaves normally and as expected. So I assume correct object has been passed to attribute_view_gui function. Now old case:
{attribute_view_gui image_class=medium attribute=$Article:item.data_map.image}
This one DOES display an image, but uses some default way - wraps it with link and shows the caption under it linked to image view, ignores any extra parameters like class, alignment etc. So this one does display an image which seems OK to me and indicates I passed correct object to the function, but obviously - this is wrong and not expected behaviour. Now - what about the object model at all? Using <b>attribute(show)</b> operator IS useless for above case should I attempt to dig into the object, docs on the site are not mentioning this "feature" at all. How do I - developer should explain above to myself? Or I missed a reference somewhere on the site?
|