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... ;)
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:
Option
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
As far as I understand, PmWiki does all it can to disable local
caching by the client browser, as the pages are exptected to change
at any time.
$PageListCacheDir = 'work.d';
$PageCacheDir = 'work.d';
Now that we have page caching and pagelist caching available, is this
approach still the
I've done a massive rewrite of Cluster (partly based on Feral's code,
with improvements of my own).
http://www.pmwiki.org/wiki/Cookbook/Cluster
Major things of note:
* some features are not compatible with earlier versions; of most note,
(:breadcrumb:) and (:clustergrouptitle:) directives have
Patrick,
I've been doing some work with parameters to include files (an
excellent feature) and I'm wondering if you might consider adding a
markup expression for strpos() or some variant of it so that we can
see if a string occurs in a parameter string. My needs are simply to
evaluate if
On Sun, May 27, 2007 at 09:50:34AM +0200, Christophe David wrote:
As far as I understand, PmWiki does all it can to disable local
caching by the client browser, as the pages are exptected to change
at any time.
$PageListCacheDir = 'work.d';
$PageCacheDir = 'work.d';
Now that we have
On Sun, May 27, 2007 at 08:28:32AM +0200, Christophe David 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.
If you consider using
A simple answer might be to simply extend ?action=source so that
it not only returns a copy of the source to the browser, but
optionally exports a copy of the text to an export directory
somewhere.
This would be perfect indeed: action=export could run the same code as
action=source and save
Scott Connard writes:
I've been doing some work with parameters to include files (an
excellent feature) and I'm wondering if you might consider adding a
markup expression for strpos() or some variant of it so that we can
see if a string occurs in a parameter string.
My needs are
On 5/27/07, Patrick R. Michaud [EMAIL PROTECTED] wrote:
Scott Connard writes:
I've been doing some work with parameters to include files (an
excellent feature) and I'm wondering if you might consider adding a
markup expression for strpos() or some variant of it so that we can
see if a
Hello...
(I believe) I have followed the instructions on the various pages to set up
extra wikis and set them up as part of a farm. My home wiki works
perfectly, but all I can do on the additional wiki is view the home page,
sidebar and my footnotes are being applied. _Any_ link I choose on
On Sun, May 27, 2007 at 11:22:33AM -0400, Bob Koon wrote:
Hello...
(I believe) I have followed the instructions on the various pages to set
up extra wikis and set them up as part of a farm. My home wiki works
perfectly, but all I can do on the additional wiki is view
On Sun, May 27, 2007 at 10:19:46AM +1000, Kathryn Andersen wrote:
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:
Hi...
I already had this in the local config (but with instead of '). Changing
the quotes doesn't change its behavior. This existed in the config because
I ripped it from the home config as part of the clean URLs recipe, so the
local config also has:
$EnablePathInfo = 1;
(I don't know if
$EnableIMSCaching = 1;
PmWiki then uses the If-Modified-Since request header to
(smartly) manage the browser's cache also.
Great, thank you.
The subject of caching and the retaled variables would definitely
deserve their own page in the documentation ;-)
---
Hi...
I sorted out the problem by removing the following lines from the extra
wiki's config file:
$EnablePathInfo = 1;
$ScriptUrl = http://anothersubdomainwiki.mydomain.com;;
It has the long (ugly) URLs which is a shame but I'll take that over it not
working. :)
-- Bob
-Original
On Sat, 26 May 2007, Patrick R. Michaud wrote:
So, PmWiki will come distributed with a Site.AuthList page by default.
That leaves the question of whether viewing Site.AuthList should be open
or restricted to admins by default.
In fact, this brings up a larger question of what to do with the
Before I get myself too confused . . . am I correct that I need to set
up a database first and then install the code for a stand-alone code?
What I'm trying to do is set up a registration page for user
information and the assign them a password.
The last batch of code at
On 5/27/07, Marguerite Floyd [EMAIL PROTECTED] wrote:
Before I get myself too confused . . . am I correct that I need to set
up a database first and then install the code for a stand-alone code?
What I'm trying to do is set up a registration page for user
information and the assign them a
On Sun, May 27, 2007 at 09:34:13AM -0500, Patrick R. Michaud wrote:
?action=source would seem to work pretty well for this.
A simple answer might be to simply extend ?action=source so that
it not only returns a copy of the source to the browser, but
optionally exports a copy of the text to
After entering the permision items in the box 'Permissions granted by' I
get the following report
UserAuth II Administration
Settings could not be saved. Please contact the system administrator.
Back to UserAuth main page.
The same happens if I add a user. There I get the error message
Settings
Is there a way of recording *with the file* the Author who deleted the
page?
With one wiki that I administer, I had the DeleteAction recipe because
I thought it would be more convenient, but I then found that people
would (accidentally) delete files and I had no way of determining
who did it. So
I put the htpassword.php in the cookbook file, and I pasted in the
local/config file.
Nothing happened. Then I put (:htpasswdform:) in my Login page, where
it shows up as (:htpasswdform:) I guess I'm not understanding the
directions.
Do I need to create a file called htpasswdform and stick it
Marguerite Floyd wrote:
I put the htpassword.php in the cookbook file, and I pasted in the
local/config file.
Nothing happened. Then I put (:htpasswdform:) in my Login page, where
it shows up as (:htpasswdform:) I guess I'm not understanding the
directions.
Do I need to create a file
Is it too late to beg for a change to the syntax for markup expressions?
My problem is this - I use a lot of mathematics in some pages, and
render it using ASCIIMathML
(http://www1.chapman.edu/~jipsen/asciimath.html). The new syntax for
markup expressions completely breaks this because the
26 matches
Mail list logo
