Problems with contexts / search page / paint layouts


(Acallaghan) #1

Hi,


For a new site we have created a new context (Chinese) and created a new base url: http://xxxxx/cn and set Chinese as the default context for this url.



On the Details screen of our standard page assets I have edited asset names / asset short names for default and Chinese contexts.



On our home page we have a Standard page & nested search page configured to list assets with a metadata field ('HomeFeature') set to the value of 'Yes'.



This works fine and prints our Standard pages configured via the metadata field to be HomeFeatures.



The Type Format\Default Format of the Search page contains the following:



%asset_contents_paint_xxxx% (xxxx is the asset id of our desired paint layout for our featured pages)



This works fine.



The xxxx paint layout has the following under Type Formats\Default Format for the default context:



%asset_short_name%



For the Chinese context I change this to:



%asset_attribute_short_name^context:Chinese%



As soon as I do this the Chinese context version of the page prints the correct Chinese language short name.



However on the Default context version of the page it is no longer the asset's short name that is printed but the parent's short name (in this case the web-site itself) is printed.



If I change the paint layouts default context to %asset_name% instead of %asset_short_name% this then fixes the default context version of the page however the Chinese version of the page no longer prints the short names at all / or it displays the asset's parent name (I have seen both cases occur)!



Apart from this contexts in menus and page content appear to work fine.



I'm thinking:


  • there is some incompatibility with the above setup and contexts?
  • I have really missed something obvious?
  • search has an issue with contexts? (I have re-indexed the site but it makes no difference)



    We are running v3.28.4



    Any ideas?

(Acallaghan) #2

When one of the contexts is broken if I make ANY change to the paint layout problem context (even just adding white space) this fixes the issue for that context but as above breaks the other one.


(Acallaghan) #3

I can't figure out what is causing the problems with the above configuration and using asset name / short name in paint layout so have created a 'Feature Title' metadata field to use instead. This works fine. So maybe a bug with the previous setup?


(Anthony Barnes) #4

This does sound like a bug, could you post it in our bug tracker: http://bugs.matrix.squiz.net. I could be wrong, but it would be best to get a developer to test.


A possible workaround might be trying %globals_asset_short_name% instead of the %asset_short_name%. It appears that the keyword is getting confused so that might correct it.