[pmwiki-users] SectionEdit cookbook : How to avoid "Section Edit " labels on printed page?

[Philippe Boeraeve]

Something annoying is that if I print my page, the "Section Edit" labels appear
on the printed page. Is there any means to change the CSS or something else to
avoid that? I have never changed any CSS, thus please could you give me all the
instruction if it is the way to solve the problem. Thanks, Philippe.


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Footnotes and Endnotes?

[Stirling Westrup]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Currently I'm using MarkupExtensions when I want to add footnotes to an
article. For simple things its adequate, but today I found myself wanting a
much more powerful footnoting recipe (where, for example, the text of the
footnote could be stored on a different page). I could swear I remembered
folks talking on this forum about creating such a thing, but I don't remember
any details.

A quick search for 'footnotes' and 'endnotes' on PmWiki didn't find me
anything relevant. Is there such a more-advanced recipe, or will I have to
construct my own?

- --
Stirling Westrup -- Visionary, Technology Analyst, Researcher, Software
Engineer, IT Generalist

LinkedIn Profile: https://www.linkedin.com/e/fpf/77228

Website:   http://www.pooq.com
Tech Blog: http://technaut.livejournal.com
Business Blog: http://willcodeforfood.livejournal.com
- --
Spread the word: Its all a HOAX, memes don't exist!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGU8un5dZZEoPlyIURAuC8AJ9nrii/0TAza90gox+vAVzqB5B79ACbBvon
Fezyg1hVEdrGroTBdTj7xOA=
=WoJn
-END PGP SIGNATURE-

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Wed, May 23, 2007 at 12:14:01AM +0200, Petko Yotov wrote:
> On Tuesday 22 May 2007 23:33, Patrick R. Michaud wrote:
> > Also, it would help to know which you think is more important:
> >
> >- getting an "import feature" to work
> >- getting pagelist to work properly with HTML caching
> >
> Oh, certainly (2) will benefit immediately to more sites, even those that do 
> not "import" externally generated pages.

I did some more testing on HTML caching, and here's what I found...

First, there's nothing about (:pagelist:) that causes HTML caching to
not work.  It works fine.

However, the $EnableDrafts capability was always disabling the HTML cache,
as well as any recipes that happen to call the CondAuth() function.

I've now fixed this in pmwiki-2.2.0-beta50, just released.  

An example page with HTML caching enabled is at
http://www.pmwiki.org/wiki/Test/HTMLCache .  On this page you can try
different markups (including pagelist) and see the resulting
effect on caching.  For long pagelists, it's pretty dramatic.

If the stopwatch at the bottom of the page says something like 
"HandleBrowse: caching page", then that means that PmWiki is 
saving the page's HTML in the cache.  If the stopwatch
says "HandleBrowse: using cached copy", that means that it is
using the cached copy of the page instead of rendering it again.

One can also look at the HTML source -- if it contains the string
"" then you know that the HTML was coming from the cache
as opposed to being rendered.

Questions, comments welcome.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] PmForm

[Patrick R. Michaud]

On Tue, May 22, 2007 at 09:46:30PM -0400, Scott Connard wrote:
> Patrick,
> 
> I know it's a wee bit against normal policy, but can you post a  
> PmForm page that contains your current settings for the PmForm group  
> (i.e., PmForm.php)?  I realize that the file may change and you may  
> forget to update the wiki page, but I won't complain often.

For the time being I've decided to move the PmForm demonstration
and documentation pages into a separate wiki from the normal pmwiki.org
set.  I think this will make it easier to create a variety of
PmForm demonstrations as separate wikigroups without cluttering the
main pmwiki.org site, especially as we're fleshing things out in
PmForm.  Once the demos are a bit more stable, and/or we know where
things are headed, we can see about merging it into the main site.

So, the new pmform site is at http://www.pmwiki.org/pmform/ .

In particular, the configuration files I'm using for that site
are all available at http://www.pmwiki.org/pmform/local/ .
But as you'll see, there's not a whole lot there -- just a few
entries into the $PmForm array.  Most of the "configuration"
takes place in the templates for the code.

Questions welcomed.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] PresenceAwareness and PresenceAwarenessLight Recipes.

[IchBin]

I am interested in using PresenceAwarenessLight or maybe the 
PresenceAwareness recipe. On their recipe pages they both say they are 
based off of the UserAuth recipe. Does this mean that I need the 
UserAuth recipe. I am running UserAuth2. Does anyone know if there would 
be a problem have UserAuth2 and try to run either PresenceAwarenessLight 
or PresenceAwareness recipes. I just did not want to have to do it by 
trial and error.

-- 
Thanks in Advance...   http://weconsulting.org
IchBin, Philadelphia, Pa, USA  http://ichbinquotations.weconsulting.org
__
'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor, Regular Guy (1952-)




___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] 2 things / password problems & registration

[IchBin]

Marguerite Floyd wrote:
> I've looked and read everything I could find looking for an answer.  I
> had the site set to require my password (admin password) for anything.
>  Tonight I tried to release that requirement so I could work on some
> pages.  I've commented (#) and uncommented everything in the config
> file related to my admin password.  I can view the home page just
> fine, but when I click on a new item on the sidebar so I can edit it,
> it demands a password.  I enter my admin password, and the password
> box comes back.  I haven't created any other password, so I have no
> idea what it's looking for.  (using v 2.45; latest upload)
> 
> What am I doing wrong and where can I find the answer?
> 
> Also, I'd like people who want to contribute and/or edit material to
> register -- name, user name, etc., but I can't find anything like that
> in the Cookbook.  Maybe I'm looking at it wrong but I want some way to
> identify folks who work with content.  Just in case . . .
> 
> the site is www.belovedparrot.com
> 
> Thanks -- and I'll probably bug y'all again -- but I do try to find
> the answer in all the archives first.

First Question: When you copied the sample-config.php to your local as 
config.php You can just uncomment the predefined one for admin. Should 
only ask for a password one time during your terminal session.

# $DefaultPasswords['admin'] = crypt('secret');

You may want to use a different password and encrypt it first and put 
the encrypted where the password would be in this format:

$DefaultPasswords['admin'] ='$1$dC/.io..$CTtqn4N8TSAm68FQBEKdZ.';

To encrypt you can look here("Encrypting passwords in config.php"):
http://www.pmwiki.org/wiki/PmWiki/PasswordsAdmin


Second question: There are a few recipes that will do what you want for 
accounts and password. Say ZAP, UserAuth with PresenceAwareness and 
others. I am using UserAuth2.

And just by chance I was just going to ask here if anybody knows if 
PresenceAwareness  works with UserAuth2. But I will open a new thread 
for that question.

-- 
Thanks in Advance...   http://weconsulting.org
IchBin, Philadelphia, Pa, USA http://ichbinquotations.weconsulting.org
__
'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor, Regular Guy (1952-)




___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] PmForm

[Scott Connard]

Patrick,

I know it's a wee bit against normal policy, but can you post a  
PmForm page that contains your current settings for the PmForm group  
(i.e., PmForm.php)?  I realize that the file may change and you may  
forget to update the wiki page, but I won't complain often.

I've started playing with it a bit and I figured that I'd have a  
better chance if I could see the config info.  It would save me from  
waiting until the documentation is complete.

Thanks,
Scott Connard.


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] 2 things / password problems & registration

[Marguerite Floyd]

I've looked and read everything I could find looking for an answer.  I
had the site set to require my password (admin password) for anything.
 Tonight I tried to release that requirement so I could work on some
pages.  I've commented (#) and uncommented everything in the config
file related to my admin password.  I can view the home page just
fine, but when I click on a new item on the sidebar so I can edit it,
it demands a password.  I enter my admin password, and the password
box comes back.  I haven't created any other password, so I have no
idea what it's looking for.  (using v 2.45; latest upload)

What am I doing wrong and where can I find the answer?

Also, I'd like people who want to contribute and/or edit material to
register -- name, user name, etc., but I can't find anything like that
in the Cookbook.  Maybe I'm looking at it wrong but I want some way to
identify folks who work with content.  Just in case . . .

the site is www.belovedparrot.com

Thanks -- and I'll probably bug y'all again -- but I do try to find
the answer in all the archives first.

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Kathryn Andersen]

On Tue, May 22, 2007 at 02:33:40PM -0500, Patrick R. Michaud wrote:
> On Tue, May 22, 2007 at 09:27:17PM +0200, Christophe David wrote:
[snip -- import feature]
> > I don't want to push you, but if you could tell me how many nights I
> > still have to sleep before seeing it ;-)
> 
> Could happen tonight (small probability), could be several days before
> I can get to it.  I have a lot of stuff on my plate at the moment.
> 
> But if I get a lot of "me too" requests for this feature, its 
> priority goes up accordingly.  :-)  And it'll undoubtedly be a
> recipe, not a core feature.

Me too!  I have some stuff that I put on my personal wiki that I wrote a
script for, which calls pywe in order to put it there -- it would be nicer
and simpler if I could just put things in an import directory, and let
PmWiki take care of them.

A question, though: what if the page one is importing already exists in
the wiki?  Would it simply overwrite it, or would it be treated as a
conflict?

But I agree that HTML caching is probably beneficial to more people.

Kathryn Andersen
-- 
 _--_|\ | Kathryn Andersen  
/  \| 
\_.--.*/| GenFicCrit mailing list 
  v | 
| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |   -> Earth -> Sol -> Milky Way Galaxy -> Universe

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Petko Yotov]

On Tuesday 22 May 2007 23:33, Patrick R. Michaud wrote:
> Also, it would help to know which you think is more important:
>
>- getting an "import feature" to work
>- getting pagelist to work properly with HTML caching
>
Oh, certainly (2) will benefit immediately to more sites, even those that do 
not "import" externally generated pages.

Thanks,
Petko


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Mike Bishop]

On Tue, May 22, 2007 at 04:33:06PM -0500, Patrick R. Michaud wrote:
> On Tue, May 22, 2007 at 02:33:40PM -0500, Patrick R. Michaud wrote:
> > On Tue, May 22, 2007 at 09:27:17PM +0200, Christophe David wrote:
> > > I don't want to push you, but if you could tell me how many nights I
> > > still have to sleep before seeing it ;-)
> > 
> > Could happen tonight (small probability), could be several days before
> > I can get to it.  I have a lot of stuff on my plate at the moment.
> 
> Also, it would help to know which you think is more important:
> 
>- getting an "import feature" to work
>- getting pagelist to work properly with HTML caching
> 
> :-)
> 
> Pm
> 

 Hmm‐‐I think (2) would have a wider application ...

Rgds,
--
Mike Bishop 
Willow, Alaska

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Tue, May 22, 2007 at 02:33:40PM -0500, Patrick R. Michaud wrote:
> On Tue, May 22, 2007 at 09:27:17PM +0200, Christophe David wrote:
> > I don't want to push you, but if you could tell me how many nights I
> > still have to sleep before seeing it ;-)
> 
> Could happen tonight (small probability), could be several days before
> I can get to it.  I have a lot of stuff on my plate at the moment.

Also, it would help to know which you think is more important:

   - getting an "import feature" to work
   - getting pagelist to work properly with HTML caching

:-)

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Skins and wikilib.d

[Patrick R. Michaud]

On Tue, May 22, 2007 at 01:13:50PM -0400, DaveG wrote:
> 
> According to this http://pmwiki.com/wiki/Cookbook/SkinGuidelines#pages, 
> skins can have their own wikilib.d directories. This seems to be a great 
> place to store wiki specific pages, etc. 

Out of curiosity, what do you mean by "wiki specific pages"?

> Question is how do I *add* my skin wikilib.d to the default list? 
> I'm not sure I understand the sample code on the page. 
> 
> ## Add a custom page storage location for the
> ## custom Edit Form and a Preferences page.
> global $WikiLibDirs;
> $PageStorePath = dirname(__FILE__)."/wikilib.d/{\$FullName}";
> $where = count($WikiLibDirs);
> if ($where>1) $where--;
> array_splice($WikiLibDirs, $where, 0,
>   array(new PageStore($PageStorePath)));

I'll try and explain it.  We want to create a new PageStore
object for the skin's wikilib.d/, and place it _just before_ the
last PageStore in the $WikiLibDirs.

Normally the above code goes into the skin's skin.php file,
so __FILE__ returns the location of the skin.php file.  
It follows then that dirname(__FILE__) is the directory
of the skin itself, and to that we add "/wikilib.d/{\$FullName}"
to get the specification for page files held in the skin's
wikilib.d/ subdirectory.

Once we know where the page files are at, we now want
to splice it as the second-to-last entry in $WikiLibDirs.
The last entry of $WikiLibDirs is nearly always the
farm's wikilib.d/ directory; we want the skin's wikilib.d/
to appear just before that so that page files provided by the
skin get precedence.

The "if ($where>1) $where--;" statement is guarding against
the possibility that there's only one directory in $WikiLibDirs,
which would likely be wiki.d/ .  We don't want the skin's
wikilib.d/ to get priority over locally edited pages.

Hope this helps.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Tue, May 22, 2007 at 11:44:43AM -0800, Mike Bishop wrote:
> On Tue, May 22, 2007 at 02:33:40PM -0500, Patrick R. Michaud wrote:
> > But if I get a lot of "me too" requests for this feature, its 
> > priority goes up accordingly.  :-)  And it'll undoubtedly be a
> 
>  Okay, I’ll add a "me too" (but it’s not urgent).
> 
>  I ftp a number of pages each month (minutes, financials,
>  recurring calendar events generated locally) and sometimes
>  the site pagelists are not quite what I expect.
> 
>  In rare cases I use "pywe" for complex content where I need
>  a better editor, but since I prefer to test locally before
>  updating the live site(s), ftp is the better way to go for
>  me.

>  Question:  should this be done automatically by PmWiki, or
>  by explicit command (or both|either)?

I think both options make sense (and should be available).

Also, come to think of it, the import directory should be
able to read PmWiki-formatted page files as well as raw text.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Test

[Petko Yotov]

On Tuesday 22 May 2007 18:07, Adaram wrote:
> Am I suppose to receive a mail from the mailing list when I send a mail to
> the mailing list?
> I guess I will see when I send this
> Sorry for spamming everyone while I try and figure this stuff out.

You can select to recieve your own messages or not to, as well as many other 
preferences at the page 
http://www.pmichaud.com/mailman/options/pmwiki-users .

Thanks,
Petko


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Test

[Adaram]

Thank you!  Glad to see you got this.  I have set that option correctly, but
funnily enough, I have not yet received a single one of the messages I have
sent.  Maybe I will get this one!

On 22/05/07, Petko Yotov <[EMAIL PROTECTED]> wrote:


On Tuesday 22 May 2007 18:07, Adaram wrote:
> Am I suppose to receive a mail from the mailing list when I send a mail
to
> the mailing list?
> I guess I will see when I send this
> Sorry for spamming everyone while I try and figure this stuff out.

You can select to recieve your own messages or not to, as well as many
other
preferences at the page
http://www.pmichaud.com/mailman/options/pmwiki-users .

Thanks,
Petko


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] includexml recipe questions

[Dominique Faure]

On 5/22/07, Jean-Fabrice [gmail] <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In the includexml.php recipe someone (or maybe Dominique), add the
> following test in order to solve issue with UrlApprovals  :
> if (strrpos($f, 'action=approvesites') !== false) return Keep($f);
>
> Shouldn't it be (using strpos instead of strrpos) :
> if (strpos($f, 'action=approvesites') !== false) return Keep($f);
>
> ??
>
> I have an other question on this recipe :
> I protected my attachments using $EnableDirectDownload = 0, thus
> ending in Attach:file converted to ?action=download&upname=file
>
> (:includexml xml=Attach:somefile.xml xsl=somestylesheet.xsl:)
> internally generates URL links for the Attach statement (using the
> MakeLink function), then gets the appropriate files using
> file_get_contents. The issue is that the ampersand in
> ?action=download&upname=file is converted by MakeLink to
> ?action=download&upname=file. Raw passed to file_get_contents,
> this ends with a 404 not found.
>
> JF
>

Well, this recipe initially written more or less as a proof of concept
really needs some housekeeping and I've desperately not enough time
for this now, but it's put near the top of the to-do stack ;)

Dominique

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Mike Bishop]

On Tue, May 22, 2007 at 02:33:40PM -0500, Patrick R. Michaud wrote:
< snip>
> 
> But if I get a lot of "me too" requests for this feature, its 
> priority goes up accordingly.  :-)  And it'll undoubtedly be a
> recipe, not a core feature.
> 
> Pm

 Okay, I’ll add a "me too" (but it’s not urgent).

 I ftp a number of pages each month (minutes, financials,
 recurring calendar events generated locally) and sometimes
 the site pagelists are not quite what I expect.

 In rare cases I use "pywe" for complex content where I need
 a better editor, but since I prefer to test locally before
 updating the live site(s), ftp is the better way to go for
 me.

 Question:  should this be done automatically by PmWiki, or
 by explicit command (or both|either)?


Rgds,
--
Mike Bishop 
Willow, Alaska

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Patrick R. Michaud]

On Tue, May 22, 2007 at 03:34:38PM -0400, Ben Wilson wrote:
> On 5/22/07, Vince Admin Account <[EMAIL PROTECTED]> wrote:
> >Patrick, please don't end there. Tell us what should be done.
> >Is it $x="a2007W19" or ...
> >Thanks
> 
> $FmtPV = "'a2007W19'"; # Note, there are single quotes inside the
> double quotes.  That allows PmWiki to evaluate the string as, er, a
> string.

Oh, right, yes.  I didn't completely understand Vince's comment.

If wanting to create a page variable that is a constant string, 
then use the format Ben just gave (except that $FmtPV needs an index):

$FmtPV['$SomeVar'] = "'a2007W19'";

Pm


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Patrick R. Michaud]

On Tue, May 22, 2007 at 02:53:42PM -0400, Vince Admin Account wrote:
> 
> On May 22, 2007, at 2:47 PM, Patrick R. Michaud wrote:
> 
> >On Tue, May 22, 2007 at 01:05:08PM -0400, Ben Wilson wrote:
> >>On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> >>>For example, in PHP I can write:
> >>>
> >>>   $x = a2007W19;
> >>>
> >>>PHP automaticaly treats the bareword string as though I had written:
> >>>
> >>>   $x = 'a2007W19';
> >
> >I should also note that even though PHP _allows_ a programmer
> >to write bareword strings in this way, doing so is considered
> >very bad (and potentially unsafe) programming practice.
>
> Patrick, please don't end there. Tell us what should be done.
> Is it $x="a2007W19" or ...

Oh.  In general one should use single quotes instead of 
bareword strings:

$x = a2007W19;# bad
$x = 'a2007W19';  # good

The same goes for constant string indexes inside of arrays:

$a = $x[color];   # bad
$a = $x['color']; # good

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Ben Wilson]

On 5/22/07, Vince Admin Account <[EMAIL PROTECTED]> wrote:
> Patrick, please don't end there. Tell us what should be done.
> Is it $x="a2007W19" or ...
> Thanks

$FmtPV = "'a2007W19'"; # Note, there are single quotes inside the
double quotes.  That allows PmWiki to evaluate the string as, er, a
string.

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Tue, May 22, 2007 at 09:27:17PM +0200, Christophe David wrote:
> Speaking for myself, I prefer the import feature quickly and possibly
> some small delay sometimes that having to wait until an elegant
> background solution can be found.

Doing things in the background isn't a really a problem -- PmWiki
already backgrounds a number of tasks (for example, rebuilding 
.pageindex, sending out mail notifications via NotifyList, etc.).
This is just another one of those.

> >If we remove the restriction of renaming the file, then the
> >import/ directory doesn't need to be writable at all.  
> 
> Indeed, but is it worth the trouble of having to manage which file
> have already been processed, etc?  

Oh that's no problem -- once we've decided to check for imports,
we just process those files that have timestamps newer than
.lastimport .

> And the external programs creating the files need write access too.

Yes, but if they're running under a task such as cron(1),
that's already been taken care of.

> I don't want to push you, but if you could tell me how many nights I
> still have to sleep before seeing it ;-)

Could happen tonight (small probability), could be several days before
I can get to it.  I have a lot of stuff on my plate at the moment.

But if I get a lot of "me too" requests for this feature, its 
priority goes up accordingly.  :-)  And it'll undoubtedly be a
recipe, not a core feature.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Christophe David]

> It could also check the timestamp of the import directory itself,
> to perhaps detect the import more quickly.  So then we'd have both,
> a check every n minutes, and a check whenever the import/ directory
> obviously changed somehow.

Indeed.


> We'd probably need to do the actual conversion as a background
> task after handing the visitor's request, otherwise some unlucky
> visitor could have a long wait as PmWiki performs the import
> (especially if there are a lot of files, or if any of them
> are particularly long).

If it can be done, yes of course.  But if the process runs quite
often, there should not be so many pages to process and the extra
delay for the unlucky visitor should not be that long.
Speaking for myself, I prefer the import feature quickly and possibly
some small delay sometimes that having to wait until an elegant
background solution can be found.

> - to take all files in the import directory that have a name that
> meets the PmWiki naming conventions and to use their content as if a
> user had typed it in the PmWiki edit form
> What authorship should it use in this case?  I guess this would
> need to be set as a configuration variable.

Ideally. By default "import" or something like that.

>> - then the imported file could be renamed (,imported012345678 for example).
> If we remove the restriction of renaming the file, then the
> import/ directory doesn't need to be writable at all.  Or
> perhaps we leave renaming of import files as a configuration
> option.

Indeed, but is it worth the trouble of having to manage which file
have already been processed, etc?  And the external programs creating
the files need write access too.
Same comment as above: nice to have, but I prefer a fast
implementation without it than waiting for the import feature.

> Thanks!

Thank YOU !  ;-)

I don't want to push you, but if you could tell me how many nights I
still have to sleep before seeing it ;-)

What a great feature it will be ;-)  Think of all the applications,
scripts and system logs that now require system access to be read and
that would be readable from PmWiki with all its features !  Same for
automatically generated reports of all kinds...

---

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Ben Wilson]

On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
[...]
> Using $NameISOWeek={*$NameISOWeek} will end up being
> far more efficient than the if= conditional anyway, so I
> strongly recommend that approach (which doesn't depend on
> being able to parse 2007W21 as a date, since it's just a
> simple string comparison).

This works. It would probably have been easier to resolve if I managed
to properly describe my goals.

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Adaram]

I can't seem to make my own direct posts work.  Sorry to muddle this thread,
but I wanted to test to see if this would actually go to the list or
not...my others have not.  Sorry again and thanks for your patience with me.


On 22/05/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:


On Tue, May 22, 2007 at 01:07:26PM -0400, Ben Wilson wrote:
> On 5/22/07, Ben Wilson <[EMAIL PROTECTED]> wrote:
> > Does anybody have a suggestion on how to capture a pagelist items
> > within a date range? For example, I want to list all journal pages
> > occurring this week (by page name "Journal-2007-05-21").
>
> I should clarify that I'm looking for a dynamic answer, so I can say
> something like:
>
> (:pagelist occurring=2007W21:)

(:pagelist if="date monday-7days..monday {=$Name}" :)

If this were executed today (2007-05-22, tuesday) then this
would list all of the pages from 2007-05-21 through 2007-05-28
(inclusive).

Unfortunately, on Monday 2007-05-28 itself it would end up
showing the pages of the previous week instead of the next week,
which is probably not what you want.  I haven't thought of a clean
way around this yet.

I can see about adding the ISO week notation if you like.
Then the pagelist command would be

(:pagelist if="date {(ftime %GW%V)} {=$Name}" :)

which would get all pages that have dates in the current week
(where a new "current week" starts each Monday).

We can also add a "thisweek" shortcut for the above, so that
it becomes

(:pagelist if="date thisweek {=$Name}" :)

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Patrick R. Michaud]

On Tue, May 22, 2007 at 02:59:12PM -0400, Ben Wilson wrote:
> >On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> >> > Hmm. Is this available now? I upgraded the site using subversion
> >> > (Exported revision 2062), but the above does not work. 
> >>
> >> The exact code I have in the local/Test.NameISOWeek.php file on
> >> pmwiki.org is:
> >>
> >>>> $FmtPV['$NameISOWeek'] =
> >>   "strftime('%GW%V', array_shift(DRange(\$name)))";
> >>
> >
> >(:pagelist if="date {$NameISOWeek} {=$Name}" :)
> 
> (:pagelist $NameISOWeek={Summary-2007-05-19$NameISOWeek} :)
> 
> The above works, but not (:pagelist if="date {$NameISOWeek} {=$Name}"
> :). I'm assuming there is nothing I must do to activate the "if"
> feature in pagelist.

The "if=" feature is in the trunk, but not the ability for the
'date' conditional to parse ISO week dates.  That's what I meant
(but wasn't explicit) when saying

The ability to parse a name like Summary-2007W21 as a date is 
dependent on me adding the code to the date parsing routine 
that can understand ISO week specifications.

Using $NameISOWeek={*$NameISOWeek} will end up being
far more efficient than the if= conditional anyway, so I
strongly recommend that approach (which doesn't depend on
being able to parse 2007W21 as a date, since it's just a
simple string comparison).

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Tue, May 22, 2007 at 06:09:17PM +0200, Christophe David wrote:
> >One way that we could improve things here would be to provide
> >an avenue whereby an external application could create a plain
> >text file somewhere, and then issue a command to PmWiki telling
> >it to update the page with the contents of the text file.  
> >[...]
> >Of course, the tricky part in this is managing the files in the
> >directory.  
> 
> This would be extremely useful.
> 
> At first glance, I would suggest
> 
> - to define an "import" directory
> - to create a file .lastimport (like .lastmod)

Oh, .lastimport is an excellent idea.  I should've thought of that.

> - to let Pmwiki check every time it runs if .lastimport is 
>   older than n minutes

It could also check the timestamp of the import directory itself,
to perhaps detect the import more quickly.  So then we'd have both,
a check every n minutes, and a check whenever the import/ directory
obviously changed somehow.

We'd probably need to do the actual conversion as a background
task after handing the visitor's request, otherwise some unlucky
visitor could have a long wait as PmWiki performs the import
(especially if there are a lot of files, or if any of them
are particularly long).

> - to take all files in the import directory that have a name that
> meets the PmWiki naming conventions and to use their content as if a
> user had typed it in the PmWiki edit form

What authorship should it use in this case?  I guess this would
need to be set as a configuration variable.

> - then the imported file could be renamed (,imported012345678 for example).

If we remove the restriction of renaming the file, then the 
import/ directory doesn't need to be writable at all.  Or
perhaps we leave renaming of import files as a configuration
option.

Thanks!

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Ben Wilson]

On 5/22/07, Ben Wilson <[EMAIL PROTECTED]> wrote:
> On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> [...]
> > > Hmm. Is this available now? I upgraded the site using subversion
> > > (Exported revision 2062), but the above does not work. This appears to
> > > be the trunk revision. I believe what you have scratches the itch
> > > perfectly.
> >
> > The exact code I have in the local/Test.NameISOWeek.php file on
> > pmwiki.org is:
> >
> >> $FmtPV['$NameISOWeek'] =
> >   "strftime('%GW%V', array_shift(DRange(\$name)))";
> >
> > It's working on pmwiki.org, so I'm not sure why it wouldn't
> > be working on your site.  If you just put {2007-05-22$NameISOWeek}
> > into a page, what do you end up getting, if anything?
>
> I get _everything_. What you offer works, but the page list lists all pages:
>
> (:pagelist if="date {$NameISOWeek} {=$Name}" :)

(:pagelist $NameISOWeek={Summary-2007-05-19$NameISOWeek} :)

The above works, but not (:pagelist if="date {$NameISOWeek} {=$Name}"
:). I'm assuming there is nothing I must do to activate the "if"
feature in pagelist.


-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Ben Wilson]

On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
[...]
> > Hmm. Is this available now? I upgraded the site using subversion
> > (Exported revision 2062), but the above does not work. This appears to
> > be the trunk revision. I believe what you have scratches the itch
> > perfectly.
>
> The exact code I have in the local/Test.NameISOWeek.php file on
> pmwiki.org is:
>
>$FmtPV['$NameISOWeek'] =
>   "strftime('%GW%V', array_shift(DRange(\$name)))";
>
> It's working on pmwiki.org, so I'm not sure why it wouldn't
> be working on your site.  If you just put {2007-05-22$NameISOWeek}
> into a page, what do you end up getting, if anything?

I get _everything_. What you offer works, but the page list lists all pages:

(:pagelist if="date {$NameISOWeek} {=$Name}" :)

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Vince Admin Account]

On May 22, 2007, at 2:47 PM, Patrick R. Michaud wrote:

> On Tue, May 22, 2007 at 01:05:08PM -0400, Ben Wilson wrote:
>> On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
>>>
>>> In the case where you had
>>>
>>>$FmtPV['$YearWeek'] = 'a2007W19';
>>>
>>> when PHP evaluates "a2007W19" it sees it as a "bareword string"
>>> and automatically treats it as a string.  For example, in PHP I
>>> can write:
>>>
>>>$x = a2007W19;
>>>
>>> PHP automaticaly treats the bareword string as though I had written:
>>>
>>>$x = 'a2007W19';
>
> I should also note that even though PHP _allows_ a programmer
> to write bareword strings in this way, doing so is considered
> very bad (and potentially unsafe) programming practice.
>
> Pm
Patrick, please don't end there. Tell us what should be done.
Is it $x="a2007W19" or ...
Thanks


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Patrick R. Michaud]

On Tue, May 22, 2007 at 02:35:38PM -0400, Ben Wilson wrote:
> On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> [...]
> >> However, I want to have a page (Summary-2007W21) list all journal
> >> entries for that week. Each week, there will be a new summary page. In
> >> six months, a visitor should be able to visit Summary-2007W21 and see
> >> the same pages as they would this week.
> >
> >Okay, then
> >
> >(:pagelist if="date {(ftime %GW%V {*$Name})} {=$Name}" :)
> >
> >which returns all of the pages where the name is in the same
> >week as that of the current page.
> 
> Spot on!
> 
> [...]
> >
> >Even simpler would be to make it a page variable instead of a
> >page text variable:
> >
> >$FmtPV['$NameISOWeek'] =
> >  "strftime('%GW%V', array_shift(DRange(\$name)))";
> > ...
> >
> >See, as an example, http://www.pmwiki.org/wiki/Test/NameISOWeek .
> 
> Hmm. Is this available now? I upgraded the site using subversion
> (Exported revision 2062), but the above does not work. This appears to
> be the trunk revision. I believe what you have scratches the itch
> perfectly.

The exact code I have in the local/Test.NameISOWeek.php file on
pmwiki.org is:

  http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Patrick R. Michaud]

On Tue, May 22, 2007 at 01:05:08PM -0400, Ben Wilson wrote:
> On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> >
> >In the case where you had
> >
> >$FmtPV['$YearWeek'] = 'a2007W19';
> >
> >when PHP evaluates "a2007W19" it sees it as a "bareword string"
> >and automatically treats it as a string.  For example, in PHP I
> >can write:
> >
> >$x = a2007W19;
> >
> >PHP automaticaly treats the bareword string as though I had written:
> >
> >$x = 'a2007W19';

I should also note that even though PHP _allows_ a programmer
to write bareword strings in this way, doing so is considered
very bad (and potentially unsafe) programming practice.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Ben Wilson]

On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
[...]
> > However, I want to have a page (Summary-2007W21) list all journal
> > entries for that week. Each week, there will be a new summary page. In
> > six months, a visitor should be able to visit Summary-2007W21 and see
> > the same pages as they would this week.
>
> Okay, then
>
> (:pagelist if="date {(ftime %GW%V {*$Name})} {=$Name}" :)
>
> which returns all of the pages where the name is in the same
> week as that of the current page.

Spot on!

[...]
>
> Even simpler would be to make it a page variable instead of a
> page text variable:
>
> $FmtPV['$NameISOWeek'] =
>   "strftime('%GW%V', array_shift(DRange(\$name)))";
>
> Then {$NameISOWeek} returns the ISO week corresponding to the page's name,
> for any page.  Then you can do pagelist of pages in the current ISO week
> with:
>
> # all pages in the current week
> (:pagelist $NameISOWeek="{(ftime %GW%V)}" :)
>
> And to get all of the pages in the same week as the current
> page (e.g., Summary-2007W21 [1]):
>
> (:pagelist $NameISOWeek={*$NameISOWeek} :)
>
> This would even work if the Summary page has a "normal" date in its
> name instead of a week date -- for example, all of the names below
> would evaluate to the same value of $NameISOWeek (i.e., "2007W21"):
>
> Summary-2007-05-24
> Summary-20070521
> Summary-20070527-XYZ
>
> See, as an example, http://www.pmwiki.org/wiki/Test/NameISOWeek .

Hmm. Is this available now? I upgraded the site using subversion
(Exported revision 2062), but the above does not work. This appears to
be the trunk revision. I believe what you have scratches the itch
perfectly.

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Patrick R. Michaud]

On Tue, May 22, 2007 at 01:59:47PM -0400, Ben Wilson wrote:
> On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> >On Tue, May 22, 2007 at 01:07:26PM -0400, Ben Wilson wrote:
> >> On 5/22/07, Ben Wilson <[EMAIL PROTECTED]> wrote:
> >> > Does anybody have a suggestion on how to capture a pagelist items
> >> > within a date range? For example, I want to list all journal pages
> >> > occurring this week (by page name "Journal-2007-05-21").
> >>
> >> (:pagelist occurring=2007W21:)
> >I can see about adding the ISO week notation if you like.
> 
> I am using the ISO week, so that would be helpful.
> 
> >We can also add a "thisweek" shortcut for the above, so that
> >it becomes
> >
> >(:pagelist if="date thisweek {=$Name}" :)
> 
> However, I want to have a page (Summary-2007W21) list all journal
> entries for that week. Each week, there will be a new summary page. In
> six months, a visitor should be able to visit Summary-2007W21 and see
> the same pages as they would this week.

Okay, then

(:pagelist if="date {(ftime %GW%V {*$Name})} {=$Name}" :)

which returns all of the pages where the name is in the same
week as that of the current page.

> I've thought of using pagelist mapping to (:Week:2007W21:).[1]
> However, that necessitates that the page author embed the PTV, which
> may be asking a bit much. 

Even simpler would be to make it a page variable instead of a
page text variable:

$FmtPV['$NameISOWeek'] = 
  "strftime('%GW%V', array_shift(DRange(\$name)))";

Then {$NameISOWeek} returns the ISO week corresponding to the page's name,
for any page.  Then you can do pagelist of pages in the current ISO week
with:

# all pages in the current week
(:pagelist $NameISOWeek="{(ftime %GW%V)}" :)

And to get all of the pages in the same week as the current
page (e.g., Summary-2007W21 [1]):

(:pagelist $NameISOWeek={*$NameISOWeek} :)

This would even work if the Summary page has a "normal" date in its
name instead of a week date -- for example, all of the names below 
would evaluate to the same value of $NameISOWeek (i.e., "2007W21"):

Summary-2007-05-24
Summary-20070521
Summary-20070527-XYZ

See, as an example, http://www.pmwiki.org/wiki/Test/NameISOWeek .

Pm

[1] The ability to parse a name like Summary-2007W21 as a date is 
dependent on me adding the code to the date parsing routine 
that can understand ISO week specifications.


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Ben Wilson]

On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Tue, May 22, 2007 at 01:07:26PM -0400, Ben Wilson wrote:
> > On 5/22/07, Ben Wilson <[EMAIL PROTECTED]> wrote:
> > > Does anybody have a suggestion on how to capture a pagelist items
> > > within a date range? For example, I want to list all journal pages
> > > occurring this week (by page name "Journal-2007-05-21").
> >
> > I should clarify that I'm looking for a dynamic answer, so I can say
> > something like:
> >
> > (:pagelist occurring=2007W21:)
> I can see about adding the ISO week notation if you like.

I am using the ISO week, so that would be helpful.

> We can also add a "thisweek" shortcut for the above, so that
> it becomes
>
> (:pagelist if="date thisweek {=$Name}" :)

However, I want to have a page (Summary-2007W21) list all journal
entries for that week. Each week, there will be a new summary page. In
six months, a visitor should be able to visit Summary-2007W21 and see
the same pages as they would this week.

I've thought of using pagelist mapping to (:Week:2007W21:).[1]
However, that necessitates that the page author embed the PTV, which
may be asking a bit much. Maybe I can ROSPattern the template so the
value is stored when the page is saved.

Hmm. I may have to put together a recipe that breaks the pagename into
the prefix/date (Summary-2007W21 into array(Summary, 2007W21)) then
feeds the date into a pagelist. Then, it becomes a question of
creating each week's summary page on Mondays, which is easily enough
done.

[1]:  (:pagelist $:Week=2007W21:)


-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[DaveG]

That's the one -- guess it didn't help then :)


On Tue, 22 May 2007 13:24:53 -0400, "Ben Wilson" <[EMAIL PROTECTED]> wrote:
> On 5/22/07, DaveG <[EMAIL PROTECTED]> wrote:
>>
>> There was a thread on this a while back, with Pm providing a number of
> examples. I seem to recall that the '*' was used as a wildcard.
> [...]
> 
> Are you referring to the May 1 thread that included the following
> artifact?
> 
> http://www.pmwiki.com/wiki/Test/PageListIf
> 
> Ben Wilson
> 
> 


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Patrick R. Michaud]

On Tue, May 22, 2007 at 01:07:26PM -0400, Ben Wilson wrote:
> On 5/22/07, Ben Wilson <[EMAIL PROTECTED]> wrote:
> > Does anybody have a suggestion on how to capture a pagelist items
> > within a date range? For example, I want to list all journal pages
> > occurring this week (by page name "Journal-2007-05-21").
> 
> I should clarify that I'm looking for a dynamic answer, so I can say
> something like:
> 
> (:pagelist occurring=2007W21:)

(:pagelist if="date monday-7days..monday {=$Name}" :)

If this were executed today (2007-05-22, tuesday) then this
would list all of the pages from 2007-05-21 through 2007-05-28
(inclusive).

Unfortunately, on Monday 2007-05-28 itself it would end up 
showing the pages of the previous week instead of the next week, 
which is probably not what you want.  I haven't thought of a clean
way around this yet.

I can see about adding the ISO week notation if you like.
Then the pagelist command would be

(:pagelist if="date {(ftime %GW%V)} {=$Name}" :)

which would get all pages that have dates in the current week
(where a new "current week" starts each Monday).

We can also add a "thisweek" shortcut for the above, so that
it becomes

(:pagelist if="date thisweek {=$Name}" :)

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Ben Wilson]

On 5/22/07, DaveG <[EMAIL PROTECTED]> wrote:
>
> There was a thread on this a while back, with Pm providing a number of 
> examples. I seem to recall that the '*' was used as a wildcard.
[...]

Are you referring to the May 1 thread that included the following artifact?

http://www.pmwiki.com/wiki/Test/PageListIf

Ben Wilson

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[DaveG]

There was a thread on this a while back, with Pm providing a number of 
examples. I seem to recall that the '*' was used as a wildcard.

On Tue, 22 May 2007 13:07:26 -0400, "Ben Wilson" <[EMAIL PROTECTED]> wrote:
> On 5/22/07, Ben Wilson <[EMAIL PROTECTED]> wrote:
>> Does anybody have a suggestion on how to capture a pagelist items
>> within a date range? For example, I want to list all journal pages
>> occurring this week (by page name "Journal-2007-05-21").
> 
> I should clarify that I'm looking for a dynamic answer, so I can say
> something like:
> 
> (:pagelist occurring=2007W21:)
> 
> --
> Ben Wilson
> "Words are the only thing which will last forever" Churchill
> 
> ___
> pmwiki-users mailing list
> pmwiki-users@pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Skins and wikilib.d

[DaveG]

According to this http://pmwiki.com/wiki/Cookbook/SkinGuidelines#pages, skins 
can have their own wikilib.d directories. This seems to be a great place to 
store wiki specific pages, etc. Question is how do I *add* my skin wikilib.d to 
the default list? I'm not sure I understand the sample code on the page. 

## Add a custom page storage location for the
## custom Edit Form and a Preferences page.
global $WikiLibDirs;
$PageStorePath = dirname(__FILE__)."/wikilib.d/{\$FullName}";
$where = count($WikiLibDirs);
if ($where>1) $where--;
array_splice($WikiLibDirs, $where, 0,
  array(new PageStore($PageStorePath)));


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Capture all pages within date range.

[Ben Wilson]

On 5/22/07, Ben Wilson <[EMAIL PROTECTED]> wrote:
> Does anybody have a suggestion on how to capture a pagelist items
> within a date range? For example, I want to list all journal pages
> occurring this week (by page name "Journal-2007-05-21").

I should clarify that I'm looking for a dynamic answer, so I can say
something like:

(:pagelist occurring=2007W21:)

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Ben Wilson]

So, the problem is my own misunderstanding of PHP. I appreciate the insight. :-)

Regards,
Ben

On 5/22/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Tue, May 22, 2007 at 11:15:33AM -0400, Ben Wilson wrote:
> > On 5/22/07, Stirling Westrup <[EMAIL PROTECTED]> wrote:
> > > Ben Wilson wrote:
> > > > I am setting $FmtPV with the following value: '2007W19'; This is how I
> > > > set it, outside of any function, but in a recipe.
> > > >
> > > > $FmtPV['$YearWeek'] = '2007W19';
> > >
> > > This won't work. The contents of $FmtPV are run through eval. That
> > > means it has to be a valid PHP expression. 2007W19 isn't one.
> >
> > Thanks. But then why does it not fail otherwise?
>
> In the case where you had
>
> $FmtPV['$YearWeek'] = 'a2007W19';
>
> when PHP evaluates "a2007W19" it sees it as a "bareword string"
> and automatically treats it as a string.  For example, in PHP I
> can write:
>
> $x = a2007W19;
>
> PHP automaticaly treats the bareword string as though I had written:
>
> $x = 'a2007W19';
>
> But with
>
> $FmtPV['$YearWeek'] = '2007W19';
> $FmtPV['$YearWeek'] = 'Test-2007W19';
>
> PHP ends up evaluating the constants as though we had written
>
> $x = 2007W19;  # $x = 2007 'W19';
> $x = Test-2007W19; # $x = 'Test' - 2007 'W19'
>
> and gets confused at the W19 part, because it sees a bareword
> string where it was expecting an operator of some sort.
>
> Pm
>


-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Capture all pages within date range.

[Ben Wilson]

Does anybody have a suggestion on how to capture a pagelist items
within a date range? For example, I want to list all journal pages
occurring this week (by page name "Journal-2007-05-21").

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Christophe David]

> One way that we could improve things here would be to provide
> an avenue whereby an external application could create a plain
> text file somewhere, and then issue a command to PmWiki telling
> it to update the page with the contents of the text file.  Then
> PmWiki could handle generating all of the meta information it
> needs (targets=, invalidating caches, updating indexes, etc.).

> Of course, the tricky part in this is managing the files in the
> directory.  For example, after PmWiki has finished converting
> a text file in the load directory into a page, should it eliminate
> the original text file?  Or should it leave it there, but somehow
> keep a marker of which files it has processed?  Or what other
> options would there be?


This would be extremely useful.

At first glance, I would suggest

- to define an "import" directory
- to create a file .lastimport (like .lastmod)
- to let Pmwiki check every time it runs if .lastimport is older than n minutes
- to take all files in the import directory that have a name that
meets the PmWiki naming conventions and to use their content as if a
user had typed it in the PmWiki edit form
- then the imported file could be renamed (,imported012345678 for example).

I guess that would not ne too complicated to do and would really make
life easier.

I am more than willing to do whatever testing you need to have this
implemented !

Thanks a lot !

Christophe

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Test

[Adaram]

Am I suppose to receive a mail from the mailing list when I send a mail to
the mailing list?
I guess I will see when I send this
Sorry for spamming everyone while I try and figure this stuff out.
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Patrick R. Michaud]

On Tue, May 22, 2007 at 11:15:33AM -0400, Ben Wilson wrote:
> On 5/22/07, Stirling Westrup <[EMAIL PROTECTED]> wrote:
> > Ben Wilson wrote:
> > > I am setting $FmtPV with the following value: '2007W19'; This is how I
> > > set it, outside of any function, but in a recipe.
> > >
> > > $FmtPV['$YearWeek'] = '2007W19';
> >
> > This won't work. The contents of $FmtPV are run through eval. That 
> > means it has to be a valid PHP expression. 2007W19 isn't one. 
>
> Thanks. But then why does it not fail otherwise?

In the case where you had

$FmtPV['$YearWeek'] = 'a2007W19';

when PHP evaluates "a2007W19" it sees it as a "bareword string"
and automatically treats it as a string.  For example, in PHP I
can write:

$x = a2007W19;

PHP automaticaly treats the bareword string as though I had written:

$x = 'a2007W19';

But with

$FmtPV['$YearWeek'] = '2007W19';
$FmtPV['$YearWeek'] = 'Test-2007W19';

PHP ends up evaluating the constants as though we had written

$x = 2007W19;  # $x = 2007 'W19';
$x = Test-2007W19; # $x = 'Test' - 2007 'W19'

and gets confused at the W19 part, because it sees a bareword
string where it was expecting an operator of some sort.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] zap "consecutive numbering" comments

[The Editor]

On 5/22/07, noskule <[EMAIL PROTECTED]> wrote:
> hi list/dan
>
> I wondering if there is a way to "consecutive numbering" numbering
> comments, ie comment-1, comment-2, comment-3. What I'm doing now is save
> datapages like this:
>
>(:zap datapage="{*$Group}.{*$Name}-Issue-+" note:)
> so far I undersand the + gives a timestamp number

That's the purpose of the threading.  Try using # instead of + (must
be the last character of a page name.  To get it to start at something
beside 1000, reset $ZAPthreadstart in your config file.

> And a question: If it somehow would work, what's happen if a Issue gets
> deleted.

The pages will not be renumbered. There will be a gap in the sequence.
The next one will get added on to the end, + 1 of course.

> thanks for any hints

Cheers,
Dan

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Ben Wilson]

Thanks. But then why does it not fail otherwise?

On 5/22/07, Stirling Westrup <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ben Wilson wrote:
> > I am setting $FmtPV with the following value: '2007W19'; This is how I
> > set it, outside of any function, but in a recipe.
> >
> > $FmtPV['$YearWeek'] = '2007W19';
>
> This won't work. The contents of $FmtPV are run through eval. That means it
> has to be a valid PHP expression. 2007W19 isn't one. You need to do something
> like this:
>
>  $FmtPV['$YearWeek'] = '"2007W19"';
>
> Because "2007W19" *is* a valid expression. If you need to use the value of a
> (non-global) variable, you'd do it like this:
>
>
>  $FmtPV['$YearWeek'] = '"'.$MyVariable.'"';
>
> If $MyVariable contains a string with quotes though, things get a bit messier.
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.3 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGUwT05dZZEoPlyIURAl0pAJ97sphEtX6YXzyg4JWKGrstgGOy4gCeMAZW
> 0/MidNKzn/20AA4xzSzTo1M=
> =geB3
> -END PGP SIGNATURE-
>


-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Ralph Zeller]

On 05/22/07 09am, Patrick R. Michaud wrote:
> On Tue, May 22, 2007 at 08:40:27AM -0500, Patrick R. Michaud wrote:
> > If yes, then the problem is that PmWiki can't 
> > see that a page has been created by an external program, and 
> > therefore doesn't realize that the pagelist cache it's already
> > created is invalid.
> 
> One way that we could improve things here would be to provide
> an avenue whereby an external application could create a plain
> text file somewhere, and then issue a command to PmWiki telling
> it to update the page with the contents of the text file.  Then
> PmWiki could handle generating all of the meta information it
> needs (targets=, invalidating caches, updating indexes, etc.).
> 
> Suppose we have a "load directory" where external applications
> place the text content they want added to PmWiki.  Then, when
> PmWiki is told (or detects) that there are new pages to be
> converted, it just does the conversion.
> 
> Of course, the tricky part in this is managing the files in the
> directory.  For example, after PmWiki has finished converting
> a text file in the load directory into a page, should it eliminate
> the original text file?  Or should it leave it there, but somehow
> keep a marker of which files it has processed?  Or what other
> options would there be?
> 
> Pm

Being able to search external pages would be a really nice feature.  It
would be even better if there was a table to define filters for files
with extensions like .htm, .doc, .pdf, .xls, etc.  In other words,
provide a means for PmWiki to create the text file when the other
application can't do it automatically.  That way, I wouldn't need an
external search engine to find those types of files on my wiki.

It would also be nice to be able to search external pages that start
with "http://someserver";.  Could the "load directory" include an array
of local directories, and some URLs, too?

Ralph

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Problem with $FmtPV;

[Stirling Westrup]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ben Wilson wrote:
> I am setting $FmtPV with the following value: '2007W19'; This is how I
> set it, outside of any function, but in a recipe.
> 
> $FmtPV['$YearWeek'] = '2007W19';

This won't work. The contents of $FmtPV are run through eval. That means it
has to be a valid PHP expression. 2007W19 isn't one. You need to do something
like this:

 $FmtPV['$YearWeek'] = '"2007W19"';

Because "2007W19" *is* a valid expression. If you need to use the value of a
(non-global) variable, you'd do it like this:


 $FmtPV['$YearWeek'] = '"'.$MyVariable.'"';

If $MyVariable contains a string with quotes though, things get a bit messier.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGUwT05dZZEoPlyIURAl0pAJ97sphEtX6YXzyg4JWKGrstgGOy4gCeMAZW
0/MidNKzn/20AA4xzSzTo1M=
=geB3
-END PGP SIGNATURE-

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Calendar that handles recurring events

[apastuszak]

Is there a calendar recipe out there that candle daily recurring events?  I 
looked at pmcalendar, but it does not seem to handle recurring events.

Andy

Sent via BlackBerry from Cingular Wireless  


___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Problem with $FmtPV;

[Ben Wilson]

I am setting $FmtPV with the following value: '2007W19'; This is how I
set it, outside of any function, but in a recipe.

$FmtPV['$YearWeek'] = '2007W19';

On the page, the variable is not set. If I set the variable to
'a2007W19', the variable is displayed. If I put a hyphen in the
variable, the variable is not set. (e.g. This-2007W19). This problem
remained even though I disabled all configuration on the site and set
the value via local/farmconfig.php (i.e., 'a2007W19' displays, but not
'2007W19');

This occurred via an older beta of 2.2, but I upgraded to the latest
release and the problem remained.

I was able to trace the problem to pmwiki.php:716. The conditional
works, but the eval fails.

 eval("return ({$FmtPV[$var]});");

Again:

'a2007W19' passes
'2007W19' fails
'a-2007W19' fails

-- 
Ben Wilson
"Words are the only thing which will last forever" Churchill

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Tue, May 22, 2007 at 08:40:27AM -0500, Patrick R. Michaud wrote:
> If yes, then the problem is that PmWiki can't 
> see that a page has been created by an external program, and 
> therefore doesn't realize that the pagelist cache it's already
> created is invalid.

One way that we could improve things here would be to provide
an avenue whereby an external application could create a plain
text file somewhere, and then issue a command to PmWiki telling
it to update the page with the contents of the text file.  Then
PmWiki could handle generating all of the meta information it
needs (targets=, invalidating caches, updating indexes, etc.).

Suppose we have a "load directory" where external applications
place the text content they want added to PmWiki.  Then, when
PmWiki is told (or detects) that there are new pages to be
converted, it just does the conversion.

Of course, the tricky part in this is managing the files in the
directory.  For example, after PmWiki has finished converting
a text file in the load directory into a page, should it eliminate
the original text file?  Or should it leave it there, but somehow
keep a marker of which files it has processed?  Or what other
options would there be?

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Tue, May 22, 2007 at 03:40:00PM +0200, Christophe David wrote:
> >Could you please explain how (:pagelist:) works internally in order to
> >take the neccessary steps to get externally generated pages listed ?
> >Are the caching options related somehow ?
> 
> In particular, PmWiki does not seem to cache the "expanded pagelists"
> despite caching (pages and pagelist) is enabled.
> 
> As most of the processing time is spent on "rendering" the page and
> not on the identification of the pages to list, it would be very
> useful to have the full resulting page cached.
> 
> Can something be done to make it happen ?

I have it on my "to do" list to figure out why the output of
pagelist isn't being cached by the html cache.  However, note
that if the page contains any of the non-cacheable elements
I mentioned earlier, then it really cannot be reliably cached.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Test and Question

[Adaram]

Hello.  I am having a really tough time getting our new wiki to take
advantage of the various security options.  In fact, there seems to be no
security at all.  I am a complete newbie at this stuff, so I am shocked I
even got it installed correctly.  In a perfect world, I would be able to
enable security to work in conjunction with this "recipe/addon"
http://www.pmwiki.org/wiki/Cookbook/AuthPhpBB2.

I have followed the steps in the setup for this...tried several times,
actually, but still no luck.  If you know the address of my wiki, you have
complete freedom to edit, etc.  So there must be something simple I am
missing.

Any thoughts?

Thanks in advance
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] Is 'RightBar' the right name?

[Stirling Westrup]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tegan Dowling wrote:

> OR have a LeftBar and RightBar but have NO fixed contents in either one, 
> and instead populate each only via "includes", and name the includables for
> their functions - GroupMenu, LinksMenu, ToolsMenu, etc.

That is more-or-less what I plan to do. The thing is, standard markup has a
(:nosidebar:) directive, so I need to decide which bar that affects. I can
easily make it be either one.

In either case, I still have the interesting problem of defaults. I'll
probably have the left sidebar default to including Site.Sidebar, as that's
quite common, so should the right sidebar include Site.Altbar, or what? Maybe
it should just default to not being there?



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGUvMp5dZZEoPlyIURAogXAJ0ccSsVTJCYtDNTfE5WYEHj7tPLzQCgpvN6
zOjVUjReGtTVL9BoWY5591E=
=6kMw
-END PGP SIGNATURE-

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Patrick R. Michaud]

On Tue, May 22, 2007 at 02:55:29PM +0200, Christophe David wrote:
> I am using beta 49, and have wiki pages created dynamically from
> external applications (say "Group1.Name1", Group1.Name2, etc.), and a
> simple (:pagelist group=Group1:) fails to list them.
> 
> Deleting .pageindex does not help.
> 
> When creating a page with PmWIki in Group1, pagelist sees it.
> 
> Could you please explain how (:pagelist:) works internally in order to
> take the neccessary steps to get externally generated pages listed ?

That's a pretty large question... pagelist is by far the largest
subsystem within PmWiki, and undoubtedly the most complex.  The
basic algorithm is straightforward -- simply loop through all of
the available pages and filter out any that don't match whatever
criteria are presented.  It's the speed optimizations such as
indexing and caching that add complexity and dependencies.

> Are the caching options related somehow ?

Yes.  In this case I suspect it's not the .pageindex that is the 
culprit but the pagelist cache.  (A simple group=Group1 query 
doesn't use .pageindex at all.)  So, are you running with pagelist 
caching enabled?  If yes, then the problem is that PmWiki can't 
see that a page has been created by an external program, and 
therefore doesn't realize that the pagelist cache it's already
created is invalid.

PmWiki keeps a file (normally "wiki.d/.lastmod") that indicates
the time of last modification to any pages on the site.  The
various caches in PmWiki then use this to determine when something
has changed and thus invalidate the cache.

So, whenever your external program creates a new page, it
probably needs to update the ".lastmod" file as well.  This
can be as simple as

touch wiki.d/.lastmod

The contents of the .lastmod file don't matter -- PmWiki just
uses the file's "last modified" timestamp.

Pm

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Christophe David]

> I am using beta 49, and have wiki pages created dynamically from
> external applications (say "Group1.Name1", Group1.Name2, etc.), and a
> simple (:pagelist group=Group1:) fails to list them.
> Deleting .pageindex does not help.
> When creating a page with PmWIki in Group1, pagelist sees it.

Part of the problem was due to the fact that the file name of the wiki
page must start with an uppercase to be seen by pagelist.  This is
important to know when generating pages with external applications.

> Could you please explain how (:pagelist:) works internally in order to
> take the neccessary steps to get externally generated pages listed ?
> Are the caching options related somehow ?

In particular, PmWiki does not seem to cache the "expanded pagelists"
despite caching (pages and pagelist) is enabled.

As most of the processing time is spent on "rendering" the page and
not on the identification of the pages to list, it would be very
useful to have the full resulting page cached.

Can something be done to make it happen ?

Christophe

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] pagelists link= with pages generated externally

[Christophe David]

> Oh, I think I might have misread the original.  There are two
> steps needed for indexing:  first, the page file needs to
> have an appropriate target= value (this normally occurs when
> the page is saved); second, the target= values go into the
> .pageindex file.
>
> I was thinking that a reindexall action would need to
> handle both phases... but if we just want to have the
> .pageindex file rebuild, that could probably be done
> fairly easily.

I am using beta 49, and have wiki pages created dynamically from
external applications (say "Group1.Name1", Group1.Name2, etc.), and a
simple (:pagelist group=Group1:) fails to list them.

Deleting .pageindex does not help.

When creating a page with PmWIki in Group1, pagelist sees it.

Could you please explain how (:pagelist:) works internally in order to
take the neccessary steps to get externally generated pages listed ?

Are the caching options related somehow ?

Thank you in anticipation.

Christophe

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] [pmwiki-devel] Is 'RightBar' the right name?

[Tegan Dowling]

On 5/22/07, Stirling Westrup <[EMAIL PROTECTED]> wrote:


I'm working on a skin for a project and its going to have both a sidebar
and
an (optional) rightbar. I'm not sure that 'rightbar' is what I should be
referring to it as though. One of the configuration options is going to be
to
switch the contents of the left and right sidebars, so the 'sidebar' will
be
on the right, and the 'rightbar' will end up on the left, thus
demonstrating
the problem with the name.

I've been thinking of using 'altbar' or 'altsidebar' or some other name
for
the sidebar that will (by default) show up on the right side. Does anyone
else
have any suggestions?



Maybe name them for their intended uses?  NavBar, ToolsBar, LinksBar, etc.
OR have a LeftBar and RightBar but have NO fixed contents in either one, and
instead populate each only via "includes", and name the includables for
their functions - GroupMenu, LinksMenu, ToolsMenu, etc.
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] zap "consecutive numbering" comments

[noskule]

hi list/dan

I wondering if there is a way to "consecutive numbering" numbering
comments, ie comment-1, comment-2, comment-3. What I'm doing now is save
datapages like this:

(:zap datapage="{*$Group}.{*$Name}-Issue-+" note:)
so far I undersand the + gives a timestamp number

And a question: If it somehow would work, what's happen if a Issue gets
deleted.

thanks for any hints
nos

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] Test if user or not online...

[The Editor]

I'm thinking of setting up a documentation system that shows a simple
version of some documentation if they are viewing a page offline, and
a different view with additional links if they are online. Is there
some way to setup a conditional that tells whether someone has
internet access?

something like URL_exists( ) or something?

Cheers,
Dan

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] IncludeXML does not include the xml source

[Jean-Fabrice [gmail]]

> thanks for your advice. Now I got the error message "XML data not found". 
> Maybe the XML- and XSL-files are at the wrong place. Where do I have to put 
> them?

if you use xml=Attach:stdplan.xml, the stdplan.xml should be attached
to the same page where  (:includexml...:) stands.

Also, take a look at my last message on the mailing list, since, I got
some issues with includexml (mainly depends if you activated
$EnableDirectDownload or not) and with a typo in the includexml.php
code (which make use of strrpos instead of strpos)

JF

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] includexml recipe questions

[Jean-Fabrice [gmail]]

Hi,

In the includexml.php recipe someone (or maybe Dominique), add the
following test in order to solve issue with UrlApprovals  :
if (strrpos($f, 'action=approvesites') !== false) return Keep($f);

Shouldn't it be (using strpos instead of strrpos) :
if (strpos($f, 'action=approvesites') !== false) return Keep($f);

??

I have an other question on this recipe :
I protected my attachments using $EnableDirectDownload = 0, thus
ending in Attach:file converted to ?action=download&upname=file

(:includexml xml=Attach:somefile.xml xsl=somestylesheet.xsl:)
internally generates URL links for the Attach statement (using the
MakeLink function), then gets the appropriate files using
file_get_contents. The issue is that the ampersand in
?action=download&upname=file is converted by MakeLink to
?action=download&upname=file. Raw passed to file_get_contents,
this ends with a 404 not found.

JF

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Re: [pmwiki-users] IncludeXML does not include the xml source

[Jean-Fabrice [gmail]]

2007/5/21, Boris Mitschke <[EMAIL PROTECTED]>:
> The Sourcecode of the mainpage looks like this:
>
> (:includexml xml=stdplan.xml xsl=stdplan.xsl:)

I don't know if it's related, but here is the code I would use :
(:includexml xml=Attach:stdplan.xml xsl=Attach:stdplan.xls:)
Having take care to upload your stdplan.xml and stdplan.xls on the page

'xml' and 'xsl' parameters take either an url or a PmWiki 'Attach'
markup as parameter

hope that help
JF

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] logbook and session.bug_compat_42 error

[Bernhard Schroetter]

Hi there,

I have a wiki (Version 2.2.0-beta49) using some recipes (utf-8,
totalcounter.php, fplauth.php, XSiteInfo.php, recipecheck.php,
refcount.php, authuser, perGroupSubDirectory, German XLPage) running
without having problems, but if I try to enable logbook (following the
instructions on , without using
AJAX) I always get warnings like:

| Warning: Unknown: Your script possibly relies on a session side-effect
| which existed until PHP 4.2.3. Please be advised that the session
| extension does not consider global variables as a source of data, unless
| register_globals is enabled. You can disable this functionality and this
| warning by setting session.bug_compat_42 or session.bug_compat_warn to
| off, respectively. in Unknown on line 0

and, if I edit a page:

| Warning: session_write_close() [function.session-write-close]: Your
| script possibly relies on a session side-effect which existed until PHP
| 4.2.3. Please be advised that the session extension does not consider
| global variables as a source of data, unless register_globals is
| enabled. You can disable this functionality and this warning by setting
| session.bug_compat_42 or session.bug_compat_warn to off, respectively.
| in D:\Webserver\xampplite\htdocs\bioparadeis\wiki\pmwiki.php on line 487
| 
| 
| Warning: Cannot modify header information - headers already sent by
| (output started at 
D:\Webserver\xampplite\htdocs\bioparadeis\wiki\pmwiki.php:487)
| in D:\Webserver\xampplite\htdocs\bioparadeis\wiki\pmwiki.php on line
| 1032

On my local Webserver (xampp: Apache/2.2.4 (Win32) DAV/2 mod_ssl/2.2.4
OpenSSL/0.9.8e mod_autoindex_color PHP/5.2.1) I can turn register_globals
On and everything is working without any warning, unfortunately on the
webserver register_globals is unchangeable set to Off.

Any ideas?

TIA,
berni

___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

[pmwiki-users] per group css problem

[Ryan O'Toole]

Dear List,

I'm using a custom skin with additional CSS added per group in
$PubDirUrl/css/GroupName.css, but my template isn't picking up the
additional styles. I've followed all the instructions on this page:
http://pmwiki.com/wiki/PmWiki/PerGroupCustomizations to no avail. Is there
something more I need to do, or can someone point me to a potential bug in
my process?

Thanks
Ryan
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users