Any tricks for seeing the DRI doc of a POST'd parameterized page such
as:
:8080/dome-xmlui-webapp/search
Clearly sticking /DRI in the URL doesn't net a DRI representation of
the actual displayed search page. I'm trying to dig around and make
some changes to templates being used to
Like that one too. I recommended to him to save the previous page
and change the POST to a GET, then he'd have an address in the
browser that he could insert XML or DRI into to his hearts content.
Yours arrives at the same end.
On Jan 9, 2008, at 11:16 AM, Scott Phillips wrote:
Sands,
Does anyone have a trick for determining which templates process a
Manakin page? For instance, how do I determine what file/template to
modify/override if I want, say, the item page to change?
I'm looking for more of a general way of working here, not just that
specific page's templates.
Ok Scott,
So if I'm seeing things clearly, the only way to target a page *(e.g.
the front page of the site)* or a group of pages (e.g. all item
pages) is to control where the theme applies by specifying the URL
pattern in the theme configuration, unless a particular type of
metadata only
Sands,
That is generally the best option, however it's not your only option.
One at least one theme we have done we've split out the document
template so that it checks the page your on and based upon that may do
something special. Basically the document template consists of a
series of
That is generally the best option, however it's not your only option.
One at least one theme we have done we've split out the document
template so that it checks the page your on and based upon that may do
something special.
I've done this. I set up a currentpage variable as follows, to save
Things are simpler with XSL 2.0 where you can just use regular
expressions to match anything relatively painlessly. But with XSL 1.0
you can use the build in string manipulation functions for some help
Well, the specific use-case for $currentpage was a bit different...
xsl:template
7 matches
Mail list logo
