Issues with global keywords on Paint Layout's conditional keywords

Ratherbesurfing · 2015-02-02 00:22:53 UTC

Hi all

Are global keywords known to cause issues when mixing with Conditional Keywords within a Paint Layout's default layout?

I wouldn't expect so, but as I'm having no luck with the conditional keywords below or attempting Barts suggestions here and here I'm running out of tools to blame ;) (5.1.6.3)

<!-- not working? -->
%begin_has_quicklinks%
  secondaryID = "assetID"
%else_has_quicklinks% 
  secondaryID != "assetID"
%end_has_quicklinks%

Conditional Keywords screen

[attachment=736:Capture.PNG]

Capture.PNG (6.37 KB)

Bart · 2015-02-02 22:28:59 UTC

Are you using a paint layout to set the conditions? As in, are you using the conditional keywords screen for the paint layout's default format bodycopy? Or are you using the conditions screen of a standard page?

Also, where are you printing that content? Inside the paint layout's default format?

I just tested it and it works fine. Would be curious to know more details about your implementation.

Ratherbesurfing · 2015-02-03 02:49:08 UTC

Thanks for testing that Bart.

I'm using a paint layout to set the conditions and am printing the above inside the default format.

To verify that my metadata exists I used the below keyword which prints True.

%globals_asset_metadata_secondaryID^eq:assetID:True:False%

Bart · 2015-02-09 22:08:58 UTC

Thanks for testing that Bart.

I'm using a paint layout to set the conditions and am printing the above inside the default format.

To verify that my metadata exists I used the below keyword which prints True.
%globals_asset_metadata_secondaryID^eq:assetID:True:False%

Hmm, that's weird. That's exactly how I tested it. What type of metadata field is it? A text field?

Also, have you tried testing against just %asset_metadata_secondaryID% instead of globals to see if it makes a difference?

Ratherbesurfing · 2015-02-11 05:02:40 UTC

Hmm, that's weird. That's exactly how I tested it. What type of metadata field is it? A text field?

Also, have you tried testing against just %asset_metadata_secondaryID% instead of globals to see if it makes a difference?

Cheers again, I originally had a related asset field then a text metadata field with no avail.

I had also previously tried sans-globals keywords too.

Not sure if it makes a difference, but the paint layout is being applied on the Design's Details screen of a Nest Content Design Area.

Bart · 2015-02-15 22:33:36 UTC

Not sure if it makes a difference, but the paint layout is being applied on the Design's Details screen of a Nest Content Design Area.

Ah, that's different to how I tested it. I set out a test like that though and couldn't replicate the issue. If you are a Squiz client, you might need to send in a support ticket for a Squiz implementer to review further.