hi
i'm running into an odd issue with the nested-if recipe, and
wondering if there's a fix...
here's the deal:
let's say i have a page called Main.TestInclude with the following
set of nestedIfs:
(:if0 true:)
(:ifA true:)
(:if1 true:)
if0,ifA,if1 true
Monday, June 30, 2008, 12:56:58 AM, adam overton wrote:
I've just combined the GuiEdit recipe with the GuiButtons recipe.
- GuiEdit allows for more better-looking buttons to be added to
your 'edit' pages...
- GuiButtons allows for the (:guibuttons:) markup, so that you can
add buttons
however, if i then stick (:include UDP.TestInclude:) into Site.SiteFooter,
and then load any page on the site, it malfunctions and spits out onto the
page part of the conditional (i.e. it doesn't execute it all):
When PM decided to put the (:if0 ...:) as a div-like feature into core I
stopped
however, if i then stick (:include UDP.TestInclude:) into
Site.SiteFooter,
and then load any page on the site, it malfunctions and spits out onto
the
page part of the conditional (i.e. it doesn't execute it all):
OK, a different answer now that I've tested it. I put nested-if in my
Monday, June 30, 2008, 10:44:39 AM, Peter Melodye Bowers wrote:
This seems to suggest that
perhaps conditionals are evaluated before headers and footers are brought
in?
yes. GroupHeader and GroupFooter pages are included with standard
(:include ..:) markup, and (:include ..:) directives are
Monday, June 30, 2008, 10:44:39 AM, Peter Melodye Bowers wrote:
Perhaps if you change the 2nd argument of the nested-if to something later
like 'directives' or something like that it might work?
if using nested if markup try in config.php
Markup('include', 'nestedif',
yes. GroupHeader and GroupFooter pages are included with standard
(:include ..:) markup, and (:include ..:) directives are rendered
after (:if..:) directives (Markup('include', 'if', ... in
stdmarkup.php).
Conditional (:if ...:) markup does work in GroupHeader and GroupFooter
pages, BTW.
On Mon, Jun 30, 2008 at 12:48:23AM -0700, adam overton wrote:
hi
i'm running into an odd issue with the nested-if recipe, and wondering if
there's a fix...
here's the deal:
let's say i have a page called Main.TestInclude with the following set of
nestedIfs:
(:if0 true:)
Lookit:
http://universaleditbutton.org/Universal_Edit_Button
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Monday, June 30, 2008, 2:07:11 PM, Tegan Dowling wrote:
Lookit:
http://universaleditbutton.org/Universal_Edit_Button
see
http://www.pmwiki.org/wiki/Cookbook/UniversalEditButton
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
On Mon, Jun 30, 2008 at 01:44:41PM +0200, Peter Bowers wrote:
yes. GroupHeader and GroupFooter pages are included with standard
(:include ..:) markup, and (:include ..:) directives are rendered
after (:if..:) directives (Markup('include', 'if', ... in
stdmarkup.php).
Conditional (:if
On Mon, Jun 30, 2008 at 7:33 AM, Hans [EMAIL PROTECTED] wrote:
Monday, June 30, 2008, 2:07:11 PM, Tegan Dowling wrote:
Lookit:
http://universaleditbutton.org/Universal_Edit_Button
see
http://www.pmwiki.org/wiki/Cookbook/UniversalEditButton
Oh! Shoot -- sorry Hans; I should have looked
Sunday, June 29, 2008, 6:14:34 AM, Maria McKinley wrote:
Darn. So the problem is not the order they are called, unfortunately.
I am leary about upgrading Fox, because I am using foxblog, and last
time I tried to do anything with updating fox, it was a bit of a mess.
I think maybe I will try
Perhaps I'm doing something stupid, but I've tried lots of variations,
so this is possibly a bug.
My aim is to display the contents of a variable, with appropriate
headings, only when the variable is set. If the variable has a
single-line value, everything works perfectly, eg:
CODE:
(:ShopList:
Subject: Conditional markup with multi-line page variables
Perhaps I'm doing something stupid, but I've tried lots of variations,
so this is possibly a bug.
My aim is to display the contents of a variable, with appropriate
headings, only when the variable is set. If the variable has a
single-line
I've been using fox-comments for... about a day, so I've got a lot to learn
I'm trying placing the comments on a separate page, to make things
cleaner on the main-page for editing, and then including (in a
show-hide toggle section) them.
The display works fine, but delete does not.
Here is my
That works exactly as it should, but, if ShopList has a multi-line
value, I still get the correct output for my shopping list, but it is
preceded on the screen by the if statement, with ShopList expanded,
The (:if ...:) regex includes a [^\n]* when it is matching the condition
which excludes
That works perfectly, Peter. Thanks very much.
Andrew
2008/6/30 Peter Melodye Bowers [EMAIL PROTECTED]:
The (:if ...:) regex includes a [^\n]* when it is matching the condition
which excludes any newlines being part of your condition. I messed around
with how that regex might be changed
hey there
i just added the code to the page you listed
to try out the scenario that was giving me problems, you would then
need to add an include to the Site.SiteFooter page (which is password
protected):
(:include Main.HomePage:)
thanks!
adam
Could you try it at
Hi guys
thanks for the suggestions.
unfortunately none of them are solving my problem yet --
- adding directives or directives in the markup for nestedif just
makes the problem worse - the entire nestedif chain fails to load,
and just prints all of it as text on the screen, whereas in my
aha
i've just found the culprits --
i have my own versions of both
'filelist_sortable.php' and 'attachtable.php' enabled
when both are commented out, nestedif works as expected, even when
included from one page onto the Site.SiteFooter...
if either one of them is left enabled by
21 matches
Mail list logo
