Hello,
just to let you know in case you experience irregularities:
In UserAuth2 versions prior and including 2.0-stable4 there is
"inappropriate code" that interferes in the engine-used variable
$ScriptUrl. This leads to bad links in the admin tool (and potentially
pmwiki-wide), once the admin to
On Sat, May 26, 2007 16:06, Patrick R. Michaud wrote:
> In fact, this brings up a larger question of what to do with the
> Site.* group in general... should we change the PmWiki default so that
> viewing pages in the Site group is restricted to admins? There
> are three options that I see:
>
>
> O
> > By the way, there is one more action that would ideally complement the
> > "import"... ;-) Guess what ? action=export. This would take the
> > content of the page and copy it as text in an "export" directory.
> If you consider using action=source for that, the feature is already
> available
Sivakatirswami wrote:
> Aloha, Patrick:
>
> Thanks for including this in the core.
>
> 1) I upgraded 2) went to Site.AuthList 3) All we we are **
> everywhere. 4) click to login 5) enter the "topmost" password that I
> have set for the site... in farmconfig.php
>
> $DefaultPasswords['admin
Aloha, Patrick:
Thanks for including this in the core.
1) I upgraded
2) went to Site.AuthList
3) All we we are ** everywhere.
4) click to login
5) enter the "topmost" password that I have set for the site... in
farmconfig.php
$DefaultPasswords['admin'] ='$1$px1OwiFE* (etc)
instead of
On Sat, May 26, 2007 at 09:06:42AM -0500, Patrick R. Michaud wrote:
> Option 2: Leave the Site.* group open as it is now, but lock
> certain pages that should generally be restricted to admins.
> This would include:
>
> Site.InterMap
> Site.AuthUser
> Site.AuthList
> Site.Approved
On 5/27/07, Christophe David <[EMAIL PROTECTED]> wrote:
[...]
> By the way, there is one more action that would ideally complement the
> "import"... ;-) Guess what ? action=export. This would take the
> content of the page and copy it as text in an "export" directory.
>
> I have many pages that
I use FireBug to analyze page speeds... on every switch to a new wiki
page on our side we see the
layout-fixflow.css
and sometimes
layout-main.css
are taking huge times... and it does not appear that these are being
cached from one page to the next. why is PMwiki downloading it again
each
I have in my local/config.php these lines:
## Let Author = AuthId
if (@$AuthId) $Author = $AuthId;
This means that Author gets value equal to the login name if the visitor
logs in using
some authentification script
- AuthUser ... core script
- UserAuth2 ... cookbook recipe
- Zap login ... cookbo
> > May I suggest to add one more configuration variable to specify a
> > maximum script running time or a maximum number of files to import in
> > one run ?
>
> Sure, we can do that. But note the caveat below...
>
> > This way, the first request could import a first batch of files
> > without rea
On Sat, May 26, 2007 at 11:08:36PM +0200, Christophe David wrote:
> However, when you have **many** files to import (as when you have one
> page per record in an "emulated database", your often reach the server
> timeout when importing.
>
> May I suggest to add one more configuration variable to s
> This already exists in import.php, as $ImportFilePattern (no 's').
I am using the new import feature extensively now, and it works great.
However, when you have **many** files to import (as when you have one
page per record in an "emulated database", your often reach the server
timeout when imp
Just a quick heads-up to anyone who's tried to access zapsite.org today
for ZAP downloads or documentation... Dan's domain name expired without
his knowledge, but I gave him a call and he's renewing it now, so it
should be back up soon.
It was kind of fun to talk on the phone with someone I've
I've just released pmwiki-2.2.0-beta52, available from
http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.0-beta52.tgz
http://www.pmwiki.org/pub/pmwiki/pmwiki-2.2.0-beta52.zip
svn://pmwiki.org/pmwiki/tags/latest
The major change to this version is the addition of a Site.AuthList
page, which
On Sat, May 26, 2007 at 12:40:23AM +0200, Tobias Thelen wrote:
> Is it possible to display/determine from which PageStore resp.
> WikiLibDir a page was read? I found no straight-forward way to do so.
> (maybe I didn't notice..)
>
> A relatively simple solution to make us happy would be e.g. sett
Hi,
If you edit sidebar
http://www.belovedparrot.com/index.php?n=Site.SideBar?action=edit
you can move the links where you want. I keep having to create a pagelist
on Site.Site to remember what each component is called
Dave
Original Message:
-
From: Marguerite Floyd [EMAIL PROT
I really like the Barthelme skin, but the action bar (view, edit,
history, etc.) is at the bottom of the side bar. I'd like it at the
top of the editable page -- www.belovedparrot.com
I've checked the pmwiki.org site and I could have sworn I'd seen how
to do this, but I can't find it now.
Should
On 5/26/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
On Sat, May 26, 2007 at 02:06:05PM +0200, [EMAIL PROTECTED]:
> On Fri, 25 May 2007, Patrick R. Michaud wrote:
> >>Also, who has read access to these new passwd variables? Shouldn't
> >>they be set to those with attr permissions, or are th
Why not have a Site.ReadPage and/or Site.OpenPage that lists the pages
that can be read and/or opened without admin rights?
Conversely, one might have a Site.LockedPage or Site.AdminPages, which
would be a list of pages to be locked except to admins.
Presumably, these sorts of pages would be
Patrick R. Michaud wrote:
> At the moment I'm leaning heavily towards option 2. Any comments
> or thoughts from others?
option 3 could be let for the next major update :()
and a page with click boxes to choose the page permissions could ease
the work a lot
jdd
--
http://www.dodin.net
http://
> Option 2: Leave the Site.* group open as it is now, but lock
> certain pages that should generally be restricted to admins.
> This would include:
>
> Site.InterMap
> Site.AuthUser
> Site.AuthList
> Site.ApprovedUrls
> Site.Blocklist
> Site.NotifyList
>
> This approach
On Sat, May 26, 2007 at 02:06:05PM +0200, [EMAIL PROTECTED] wrote:
> On Fri, 25 May 2007, Patrick R. Michaud wrote:
> >>Also, who has read access to these new passwd variables? Shouldn't
> >>they be set to those with attr permissions, or are they...
> >
> >The default is to require attr permissions
On Fri, 25 May 2007, Patrick R. Michaud wrote:
http://www.pmwiki.org/wiki/Test/AuthList2
Questions and suggestions welcomed. After getting an initial
round of feedback I will see about publishing this as a
recipe, if not actually placing it into the core somewhere.
Also, who has read access
Hello,
I have a wiki with my classroom where every student has to introduce an author
name before saving a page ($EnablePostAuthorRequired=1). If I use a ZAP form
which appends the content of the form fields in a file, it doesn't work because
an Author name was not introduced to modify the page. I
Thanks, Hans, that works perfectly for me too!
Philippe
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
25 matches
Mail list logo
