Cataloguer feature lists

pgingao · Post by **pgingao** » Tue Nov 06, 2012 3:08 am

Hi all,

installed the latest cataloguer (0.11.1) on a CMSMS 1.11.2.1 "Isabela", I noticed the {process_page_data problem} and the images not showing and found the workarounds here on the forum. But one thing I can't solve and didn't find anyone complaining is the feature lists.

I have aded categories and items and have this code on one normal page: {Cataloger sub_template='Feature-CSS-based' action='all'} but the result is empty. Also tried to put it on the template but no luck.

Any one had the same?

Many thanks

Paulo

pgingao · Post by **pgingao** » Tue Nov 06, 2012 12:41 pm

Now the weirdest thing happened, the template main template markup changes on catalog-category pages. The </__body> goes first, and all the header bit "<__html><head>" goes last. Shows up fine on catalog-item pages.

Is anyone using this cataloguer version successfully?

Thanks

My developer Page on the Forge · Post by **Jo Morg** » Tue Nov 06, 2012 1:53 pm

pgingao wrote:Now the weirdest thing happened, the template main template markup changes on catalog-category pages. The </__body> goes first, and all the header bit "<__html><head>" goes last. Shows up fine on catalog-item pages.

Is anyone using this cataloguer version successfully?

Thanks

On:
Cataloger->Manage Preferences->Category Page Settings
do you have:
Flush category page buffers ticked?
Untick it and test if it works.

pgingao · Post by **pgingao** » Tue Nov 06, 2012 2:17 pm

Hi, unticked that box and the markup loads correctly now!
Many thanks.

Do you have an idea why feature lists show up empty?
My code is: {Cataloger sub_template='Feature-CSS-based' action='all'}

Thank you

My developer Page on the Forge · Post by **Jo Morg** » Tue Nov 06, 2012 2:24 pm

Without more data I don't have much to work with. It should be working, as that wasn't (or, at least shouldn't have been... ) 'touched' by the changes made to the code.

pgingao · Post by **pgingao** » Tue Nov 06, 2012 3:01 pm

Here it goes:

Running on MAMP localhost, PHP 5.2.17 with XCache
GD version 2
MySQL 5.5.9

CMSMS 1.11.2.1 "Isabela"
Cataloger 0.11.1

I have several category and item pages.

The feature list template is the standard:

{*Feature-CSS-based template*}
{section name=numimg loop=$image_url_array}
<div class="col_2">
<img src="{CGSmartImage src1=$src_image_1_url alias1='medium' notag=1}" alt="{$title}" title="{$title}" />
</div>
{/section}
<div class="col_6 omega">
{section name=numloop loop=$items}
<div class="feature_items">
{section name=numloop loop=$items}
<div class="feature_item"><a href="{$items[numloop].link}"><img src="{$items[numloop].image}" title="{$items[numloop].title}" alt="{$items[numloop].title}"/></a><br /><a href="{$items[numloop].link}">{$items[numloop].title}</a></div>
{/section}
</div>

Then I have this code on a normal static page:
{Cataloger sub_template='Feature-CSS-based' action='all'}

I can't see any JS errors, basicay the {section name=numloop loop=$items} renders empty.

Id it helps I can put this on a server so you can login and have a look? Let me know.

Thanks again.

My developer Page on the Forge · Post by **Jo Morg** » Wed Nov 07, 2012 5:34 pm

Ok, the issue has been reproduced. It should be fixed in next version.

My developer Page on the Forge · Post by **Jo Morg** » Wed Nov 07, 2012 10:07 pm

Jo Morg wrote:Ok, the issue has been reproduced. It should be fixed in next version.

Follow up:
That wasn't exactly a bug but a misunderstanding of what is stated (vaguely, I have to agree) on the Cataloger help:
the use should be {Cataloger action='all' sub_template='Feature-CSS-based'} on any template that has for sure a content type of either one of the 3 content types Cataloger provides, in which case it will work properly.
That NOT being the case, i.e when there is the need to use this tag on ANY other template than those with Cataloger content types the use is a bit different:
{Cataloger action='all' sub_template='Feature-CSS-based' alias='/'}
if you want a list from all categories starting from the root;
or:
{Cataloger action='all' sub_template='Feature-CSS-based' alias='a-cataloger-valid-category-alias'};

That being said, there was a bug that actually would have resulted in an error with {Cataloger action='all' sub_template='Feature-CSS-based' alias='/'} use...
That bug is fixed and will be on the forge ASAP.
Thanks.

CMS Made Simple Forums

Cataloguer feature lists

Cataloguer feature lists

Re: Cataloguer feature lists - weird behaviour

Re: Cataloguer feature lists - weird behaviour

Re: Cataloguer feature lists

Re: Cataloguer feature lists

Re: Cataloguer feature lists

Re: Cataloguer feature lists

Re: Cataloguer feature lists