PmWiki-Devel Google Group

Re: [pmwiki-devel] PmWiki as Markup Service - is this a security hole?

xraysmalev...@gmail.com (michael paulukonis) — Fri, 17 May 2013 14:39:52 UT

I neglected to thank you for the help (summer 2012!).
I haven't done further work on the project, but have been using it, and
hope to extend it further this year.

cheers!

-Michael Paulukonis
[link]
<[link]>Interference Patterns (a
blog)<[link]>

Re: [pmwiki-devel] Question about Reorder function in PITS.php on pmwiki.org

as...@aslandata.com (David Sovinski) — Thu, 09 May 2013 15:04:15 UT

So that's what happened!
I just checked and...
Without realizing it, I have been using a 2005 version of PITS.php on my
.com site
I have the correct version on my machine but uploaded the old one
accidentally when I created my .com site.

Now we'll have to decide if we want to update pits-0.24.php so that

Re: [pmwiki-devel] Question about Reorder function in PITS.php on pmwiki.org

5...@5ko.fr (Petko Yotov) — Thu, 09 May 2013 14:39:03 UT

It is using the PITS.php file which is attached at the beginning of the
Cookbook:PITS recipe, the priority2 markup expression is defined at the end
of it. Here is a direct link to the file, the one in use is the same:

[link]

The pmwiki.org PITS uses the markup (:pits2list:) and not (:pitslist:) and

[pmwiki-devel] Question about Reorder function in PITS.php on pmwiki.org

as...@aslandata.com (David Sovinski) — Thu, 09 May 2013 13:03:19 UT

[link]
I copied the code from the above page to my site for implementation of
the PITS recipe.
Everything worked EXCEPT parts of Reorder

If I Reordered on a field that begins with an alpha character it
Reorders correctly
examples: name (Version), category, summary

Re: [pmwiki-devel] Is EnablePathInfo required for action=$PageUrl in forms?

pbow...@pobox.com (Peter Bowers) — Wed, 08 May 2013 20:21:56 UT

It doesn't get any clearer than that!

I will try over the next couple of days to look through the various pages
documenting forms and see if there is a good place to include this new (to
me, at least) information about $EnablePathInfo.

Thanks, as always, for your conscientious and knowledgeable and extremely

Re: [pmwiki-devel] Is EnablePathInfo required for action=$PageUrl in forms?

5...@5ko.fr (Petko Yotov) — Wed, 08 May 2013 18:58:51 UT

The third method is "post".

Anyways, I have reviewed the standard specifications here:

[link]
[link]

and it appears that when you use the "get" method, the browser opens a URL

Re: [pmwiki-devel] Is EnablePathInfo required for action=$PageUrl in forms?

pbow...@pobox.com (Peter Bowers) — Wed, 08 May 2013 16:11:31 UT

Sorry, that was unhelpful to leave it in the working rather than the
non-working state. I have now commented out the $EnablePathInfo.

On the first one (${PageUrl}, get) it does *not* work.

On the second one (${PageUrl}, post) it *does* work.

On the third one (${ScriptUrl?n={$FullName}, get) it *does* work.

Re: [pmwiki-devel] Is EnablePathInfo required for action=$PageUrl in forms?

5...@5ko.fr (Petko Yotov) — Wed, 08 May 2013 15:42:25 UT

This page works for me as expected - I added a form with method=post, and
another form with action={$ScriptUrl}?n={$FullNa me}. Both work, and the
latter should behave exactly like when $EnablePathInfo is not set.

When I submit the forms, I land on the same page.

Note that the very first form action in the page is not correct, there is no

Re: [pmwiki-devel] Is EnablePathInfo required for action=$PageUrl in forms?

pbow...@pobox.com (Peter Bowers) — Wed, 08 May 2013 15:04:43 UT

Thank you for correctly interpreting my overly abbreviated typing... :-)

So is there something else going on in my configuration that makes it so
without $EnablePathInfo it goes to my default page?

(Example: [link] -- I think I've left
it with $EnablePathInfo=1 right now...)

Re: [pmwiki-devel] Is EnablePathInfo required for action=$PageUrl in forms?

5...@5ko.fr (Petko Yotov) — Wed, 08 May 2013 14:53:54 UT

You probably mean (:input form:) not (:form:), and later {$PageUrl} not
$PageUrl.

No, it is not required, but if the script which is receiving the posted form
expects a $_POST['n'] or $_GET['n'] variable instead of $_REQUEST['n'] or
simply $pagename, you may need to add to the form

(:input hidden n {*$FullName}:)

[pmwiki-devel] Is EnablePathInfo required for action=$PageUrl in forms?

pbow...@pobox.com (Peter Bowers) — Wed, 08 May 2013 13:26:04 UT

Is it required to have $EnablePathInfo=1 set in order to use

(:form action=$PageUrl:)

???

If so, is there a more generic way of specifying that the current page
receives the action that will work regardless of the setting of this
variable?

I'm familiar with using the hidden input field named "n" set to the value

Re: [pmwiki-devel] Attempting to get pits-0.23.php operational

as...@aslandata.com (David Sovinski) — Sat, 04 May 2013 22:57:46 UT

Peter

The test site for solving the generic PITS script problems may be found at:
[link]
The Write and Upload passwords are "BugMe" without the quotes
------------------------------ ------------------------------ ------------------------------ ---------

[pmwiki-devel] Attempting to get pits-0.23.php operational

as...@aslandata.com (David Sovinski) — Fri, 03 May 2013 22:13:17 UT

Is there anyone interested in helping me troubleshoot (read fix) the
generic pits-0.23.php recipe?
Found at [link]

I have found three bugs one of which I have fixed.
The other two bugs may simply be the scope of the variable definitions

When working properly it will allow many Issue Tracking Systems to

Re: [pmwiki-devel] serving a part of a page by AJAX

5...@5ko.fr (Petko Yotov) — Thu, 02 May 2013 08:18:01 UT

Don't pass the $out variable in the function call, instead get it from the
global $FmtV['$PageText'] variable.
So, have something like this:
...
$HandleBrowseFmt = array('function:PrintJSON()');
...
print json_encode($GLOBALS['FmtV'][' $PageText']);
# or global $FmtV; print json_encode($FmtV['$PageText'] );

[pmwiki-devel] serving a part of a page by AJAX

pbow...@pobox.com (Peter Bowers) — Thu, 02 May 2013 07:25:32 UT

I am putting together a web-site where the help is served in a jsquery-ui
dialog populated by AJAX. Up until now I've coded the help in HTML and
just put it directly in PHP variables. As the site matures the
documentation is growing rapidly and maintaining it in HTML is getting a
bit onerous -- it would be great if I could maintain the docs in pmwiki.