Hi all
I'm using global keywords in a nested content area in my design. This works fine when viewing the page normally, but when opening the page in simple edit mode (we are on EES/Edit+ v1.4.2) the global keywords do not get replaced. Other keywords do get replaced, as do url replacements of the form './?a='. Only seems to affect the globals. Is there some caveat that the global keywords are not available in simple edit?
I'll try explain, the following is in my parse file:
and in my customisation I point it to a Standard Page asset that has this content:
<!-- TD from nested content %globals_asset_assetid% %globals_asset_status_description% %asset_assetid% %asset_status_description% -->
At later stages I can print this area using this line:
and it replaces all those keywords when the page is rendered normally, looks like this:
However, if the PRINT statement is in the EES Design area (see code below) then when opening the asset in edit mode only the '%asset_' keywords are replaced. The globals are not replaced but appear in the rendered code literally.
<MySource_AREA id_name="exit_area" design_area="exit" print="no"></MySource_AREA>
<MySource_AREA id_name="nested_EES_code" design_area="nest_content" print="no" />
<MySource_AREA id_name="my_nested_stuff" design_area="nest_content" print="no" />
<MySource_AREA id_name="simple_edit_EES" design_area="show_if">
<MySource_SET name="condition" value="simple_edit_mode" />
<MySource_THEN>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
<title>Loading Edit+ ...</title>
<MySource_PRINT id_name="nested_EES_code" />
<MySource_PRINT id_name="my_nested_stuff" /><!-- this line here -->
When page is opened in edit mode, the line indicated above renders as this:
<!-- TD from nested content %globals_asset_assetid% %globals_asset_status_description% 123221 Under Construction -->
I know that I can get most (if not all) this info using design print statements rather than keyword replacements, but there's cleaner modularity if I can put it into nested content, and in this case means I can easily turn my EES plugins on/off using a design customisation.