Thanks for the reply.<br>
Hans, I wonder if you should post your detailed reply on <a href="http://pmwiki.org">pmwiki.org</a>?<br>
<br>
<br><br><div class="gmail_quote">On Dec 18, 2007 2:21 PM, Hans <<a href="mailto:design5@softflow.co.uk">design5@softflow.co.uk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Tuesday, December 18, 2007, 5:21:36 PM, Matt Strauser wrote:<br><br>> Was {$Name} replaced with {*$FullName}<br><br>> As in:<br>> [[{$Name}?action=edit | Edit ]]<br><br>> changed to:<br><br>
> [[{*$FullName}?action=edit | $[Edit] ]]<br><br><br>> Could someone point me to a page at <a href="http://pmwiki.org" target="_blank">pmwiki.org</a> that discusses this?<br><br></div>See PmWiki/ReleaseNotes about 2.2.0
beta.<br>I quote:<br><br>* Page variables and page links inside of (:include:) pages are now<br>treated as relative to the included page, instead of the currently<br>browsed page. In short, the idea is that links and page variables
<br>should be evaluated with respect to the page in which they are<br>written, as opposed to the page in which they appear. This seems to be<br>more in line with what authors expect. There are a number of important<br>ramifications of this change:
<br><br>* We now have a new {*$var} form of page variable, which always refers<br>to "the currently displayed page". Pages such as Site.PageActions and<br>Site.EditForm that are designed to work on "the currently browsed
<br>page" should generally switch to using {*$FullName} instead of<br>{$FullName}.<br><br>* The $EnableRelativePageLinks and $EnableRelativePageVars settings<br>control the treatment of links and page variables in included pages.
<br>However, to minimize disruption to existing sites,<br>$EnableRelativePageVars defaults to disabled. This will give existing<br>sites an opportunity to convert any absolute {$var} references to be<br>{*$var} instead.<br>
<br>* Eventually $EnableRelativePageVars will be enabled by default, so we<br>highly recommend setting $EnableRelativePageVars = 1; in<br>local/config.php to see how a site will react to the new<br>interpretation. Administrators should especially check any customized
<br>versions of the following:<br>Site.PageActions<br>Site.EditForm<br>Site.PageNotFound<br>SideBar pages with ?action= links for the current page<br>$GroupHeaderFmt, $GroupFooterFmt<br>Page lists that refer to the current group or page, etc in sidebars,
<br>headers, and footers<br><br>* The (:include:) directive now has a basepage= option whereby an<br>author can explicitly specify the page upon which relative links and<br>page variables should be based. If no basepage= option is specified,
<br>the included page is assumed to be the base.<br><font color="#888888"><br><br>Hans<br><br></font></blockquote></div><br>