V7 Buglet: Section level CUSTOMVARS not being passed to Fragments.

[NormanRouxel]

Since V7 you can use Fragments in product sections.

The Fragment Templates can contain CUSTOMVAR's.

However only the top-level, Catalog property is used, regardless of whether there's a Section level property set.

This is completely different to how Products using CUSTOMVAR's operate.

[cdicken]

Thanks for this Norman. I have reported it as a bug.

[domino1]

Hi,
Any news on this bug. I'm using V7.06 and CUSTOMVARS still don't appear to work from fragments in my product sections.

[RobSollars]

This also occurs if you have a CUSTOMVAR inside a CUSTOMVAR. Took us a while to figure out what was going on.

[domino1]

Hi Rob,

My guess is that this is a separate issue from the bug. The behaviour when CUSTOMVARS are nested must be a function of how the actinic parser works. The parser won't see the second CUSTOMVAR until its parsed the first one so multiple passes would be needed. I can't find anything in the user guide relating to nested CUSTOMVARs and whether actinic allows them. Someone from Actinic would have to verify this.

[cdicken]

Any news on this bug. I'm using V7.06 and CUSTOMVARS still don't appear to work from fragments in my product sections.

I don't think this will be fixed in v7 I'm afraid. It works beautifully in v8 though.

[cdicken]

Someone from Actinic would have to verify this.

I think you're right here. But you can use an 'INCLUDE' tag of the format

NETQUOTEVAR:INCLUDE text.txt

to include the content of 'text.txt' in your site and that can include NETQUOTEVARs and CUSTOMVARs

[domino1]

I don't think this will be fixed in v7 I'm afraid. It works beautifully in v8 though.

Hi Chris.
Is this because it's particularly difficult to fix this bug in V7 or just because V7 is no longer being supported. I understand that old versions can't be supported indefinately but V8 is still a baby!

Dave

[cdicken]

Dave

The problem is that fixing a bug would be a fairly substantial change, and the fix would not benefit that many users - especially as we have already re-written this area with v8.

We would love to fix every single bug in the software, but unfortunately we just don't have the resources to do that and develop new software as well.

I know that answer will not benefit you a great deal practically, but I hope it helps you understand the issues involved.