ToolKit Brain Cramp: Render Page Based On Conditional Custom Field?

[Siamese-Dream.Com]

Hi there, Everyone:

How do I render / vrender a page depending on a conditional in a custom product field?

My products have a custom field called "custom_cat_tree"

I will populate it with values like, cattree1, or cattree2, or cattree3, etc.,

If want to render a page that corresponds to that value, would it be like this?

<mvt:item name="toolkit" param="vrender|&mvt:product:customfield_values:cus tomfields:custom_cat_tree;" />

Or would I have to assign / vassign / sassign that custom field to a variable first? (and if so, how?)

Thanks in advance.

[wcw]

Re: ToolKit Brain Cramp: Render Page Based On Conditional Custom Field?

Replace &mvt: with l.all_settings:

[Siamese-Dream.Com]

Re: ToolKit Brain Cramp: Render Page Based On Conditional Custom Field?

Hi there, Bill:

Unfortunately, this doesn't seem to be working for me.

<mvt:item name="toolkit" param="vrender|l.all_settings:product:customfield_values:customfields:custom_cat_tree;" />

This doesn't return anything.

there IS a custom field assigned to the product, and I can display the value of the custom field contents by doing this:

&mvt:product:customfield_values:customfields:custom_cat_tree;

and there IS a page created with the appropriate code (the same as the value in the custom field)

but that page doesn't render.

I DO have toolkit assigned to the PROD screen that had the vrender code.

Any other suggestions?

Thanks in advance.

[Siamese-Dream.Com]

Re: ToolKit Brain Cramp: Render Page Based On Conditional Custom Field?

Has anybody else tried doing this? I seem to have hit a wall...

[wcw]

Re: ToolKit Brain Cramp: Render Page Based On Conditional Custom Field?

Remove the ; at the end where you have custom_cat_tree;

[Siamese-Dream.Com]

Re: ToolKit Brain Cramp: Render Page Based On Conditional Custom Field?

Thanks!!! That took care of it.

It will be a lot easier to maintain a single product page template made up of various pieces (which are dependent on custom fields) than it will be to have to maintain several different PROD page templates.