Christophe David a écrit :
I'd like to second this. The recipe installation is by now very
programmer-style, adding a include line, setting some config variables,
writing some php in a new file...It's all not difficult but not user
friendly for non-programmer admins.
What about a
On Sun, Feb 24, 2008 at 07:19:48AM +, imoc wrote:
some thing with a cookbook list, with check boxes
when installing several cookbooks, the process is quite cumbersome and
annoying, and a such script should be quite simple (however I'm not
able do do it myself)
I'd like to
On Sat, Feb 23, 2008 at 11:29:37AM +, Hans wrote:
Saturday, February 23, 2008, 12:28:28 AM, Patrick R. Michaud wrote:
The ability to change the cauthor attribute could be done through
?action=attr, but thus far I've been a little reluctant to have
non-password attributes in the
Sunday, February 24, 2008, 3:55:48 PM, Patrick R. Michaud wrote:
## not tested, but gives the general idea
function SetPageCreator($pagename, $page, $new) {
global $EnablePost, $Author;
if ($EnablePost) SDV($new['cauthor'], $Author);
unshift($EditFunctions, 'SetPageCreator');
Patrick R. Michaud wrote:
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be cases where this would be
okay, but in the general case I
Sunday, February 24, 2008, 3:55:48 PM, Patrick R. Michaud wrote:
## not tested, but gives the general idea
function SetPageCreator($pagename, $page, $new) {
global $EnablePost, $Author;
if ($EnablePost) SDV($new['cauthor'], $Author);
unshift($EditFunctions, 'SetPageCreator');
I added this as a new recipe PageCreator:
http://www.pmwiki.org/wiki/Cookbook/PageCreator
~Hans
___
pmwiki-users mailing list
pmwiki-users@pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
Patrick R. Michaud a écrit :
The problem with using a web-based interface to install cookbook
recipes automatically is that it requires write permission to
the cookbook/ directory. That's a security risk we haven't
wanted to take yet.
This is especially an issue since basically anyone can
Sunday, February 24, 2008, 6:18:53 PM, Hans wrote:
The SetPageCreator function sets cauthor everytime new when the page
is saved, not just when the page is saved the first time.
I think this will do it:
the 'author' attribute does not exist before the first page save:
# set page creator
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be cases where this would be
okay, but in the general case I think it's too big a
On Sun, Feb 24, 2008 at 11:19:19PM +0100, Christophe David wrote:
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be cases where
On Sun, Feb 24, 2008 at 11:52:05AM -0500, DaveG wrote:
Patrick R. Michaud wrote:
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be
could even be a sh script, to be done by the admin, not an online
administration tools.
- not everyone is using unix
- not everyone using unix has command-line access
WikiSh has most capabilities to do this currently except for the actual
download from pmwiki.org. It's a way to give unix
Jan Erik Moström wrote:
I want to set up a issue tracker on personal site. I looked at
the cookbook and found three recipes PITS, JITS and Yeats ...
should I use one of these (recommendations?) or should I do it
in some other way?
It depends on your requirements.
I made a _really_ simple
14 matches
Mail list logo
