[pmwiki-users] Still Problems with Auth Users and Groups

Boris Schwarz boris.schwarz at inode.at
Tue Nov 7 17:04:24 CST 2006


Hi,

My Goal is to define Groups and to tell pmwiki or AuthUser.php that users A
and B are members of Authentication group Management. 
Further on Members A and B and C and D are members of the Authentication
group Staff for example.

Eventually i would like to allow the Authentication group Management to edit
and read any group pages on my pmwiki.
On the other side though the groups staff should only be allowed to read
main.HomePage and all other pages with main.* but they are allowed to read
and edit staff.homepage and all other pages with staff.*. At the same time
though they should not be able to read or edit management.homepage and any
pages starting with management.*


PM was so kind to explain to me what you see below in quotations. My questin
back then was a little different so the @admin, @management etc. wont be
right but the authentication process/setup should be the same. I am though
not capable of following these instructions since i dont unerstand how to
define groups so authuser know which memebers are part or which group and
how can i tell authuser that group staff can only read main.* but not edit
with attributes?

"Assuming we're using AuthUser, let's call the three authorization groups
@admin, @management, and @staff.

To do item #1, set the following in local/config.php:

$DefaultPasswords['admin'] = '@admin';

The first line says that anyone in the @admin group can do everything on all
pages.  

For item #2, set:

$DefaultPasswords['read'] = array('@admin', '@management');

This says that the management group is allowed to read and edit any page.
However, we want to prevent management from editing whatever.homepage, so
use ?action=attr on whatever.homepage to set an edit password of '@admin'
(restricting editing of that page to admins).

For item #3, the $DefaultPasswords['read'] line above already says that
@staff is unable to read or edit any pages (because only @admin and
@management can read or edit).  However, we want @staff to be able to read
and edit main.homepage, so use ?action=attr on main.homepage to set a read
password and edit password of '@staff @management @admin'.  This says that
anyone in the @staff, @management, or @admin groups may read or edit the
page."

Pm

Did I misunderstand someting, is it actually possible to use authentication
groups and to include certain users and then allow these authentication
groups to either read edit or not to read or edit certain site groups like
main.hompage?

I would be happy if someone could help me im my state of confusion

Boris Schwarz

-----Ursprüngliche Nachricht-----
Von: pmwiki-users-bounces at pmichaud.com
[mailto:pmwiki-users-bounces at pmichaud.com] Im Auftrag von
pmwiki-users-request at pmichaud.com
Gesendet: Dienstag, 7. November 2006 22:47
An: pmwiki-users at pmichaud.com
Betreff: pmwiki-users Digest, Vol 17, Issue 25

Send pmwiki-users mailing list submissions to
	pmwiki-users at pmichaud.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.pmichaud.com/mailman/listinfo/pmwiki-users
or, via email, send a message with subject or body 'help' to
	pmwiki-users-request at pmichaud.com

You can reach the person managing the list at
	pmwiki-users-owner at pmichaud.com

When replying, please edit your Subject line so it is more specific than
"Re: Contents of pmwiki-users digest..."


Today's Topics:

   1. spammed page alert (Sandy)
   2. Re: get rid of group Main from url (JB)
   3. Re: spammed page alert (Neil Herber (nospam))
   4. Re: missing password form (Tegan Dowling)
   5. blocklist warning (Kevin Gabbert)
   6. Path to skins question (Hans)
   7. totalcounter error (dso)
   8. Re: Path to skins question (JB)
   9. Re: missing password form (Ben Stallings)
  10. Re: Path to skins question (Hans)
  11. Re: Any news about Blog feature? (Dominique Faure)
  12. html validation (dso)
  13. Icons attached to uploaded files...how to implement	the
      suggested solution? (Nicholas Buttle)


----------------------------------------------------------------------

Message: 1
Date: Tue, 07 Nov 2006 13:03:43 -0500
From: Sandy <sandy at onebit.ca>
Subject: [pmwiki-users] spammed page alert
To: pmwiki-users at pmichaud.com
Message-ID: <eiqhpt$nek$1 at sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Not confident enough to just delete the page and its reference from the
cookbook page. The correct page still exists but with capitals in the name.

Sandy

http://pmwiki.org/wiki/Cookbook/Wikifarmstepbystep




------------------------------

Message: 2
Date: Tue, 07 Nov 2006 12:05:31 -0600
From: JB <jbit at bitlink.com>
Subject: Re: [pmwiki-users] get rid of group Main from url
To: pmwiki-users at pmichaud.com
Message-ID: <4550CAEB.8060607 at bitlink.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

 > That's it.

Anno,  NO, That is not it.  What you posted does not work.
It only made it worse! The "Main." is still in the url and now it displays
"index.php" again!


Here is what works to remove "index.php" from the url

         # Eliminate "index.php" & "pmwiki.php" from URLs.
         $EnablePathInfo = 0;
         $ScriptUrl = "http://gnuzoo.org/stuffforsale/";

It changes my url from:
http://gnuzoo.org/stuffforsale/index.php?n=Main.OfficeTable

to:
http://gnuzoo.org/stuffforsale/?n=Main.OfficeTable

I want to try and make it look like:
http://gnuzoo.org/stuffforsale/?n=OfficeTable

   - get rid of the "Main.".



original quoted below
---------------

* Anno wrote, On 11/4/2006 10:20 AM:
> Step 1:
> create an index.php file in the same directory as pmiki.php containing
this:
> <? include_once ('pmwiki.php');
> 
> Step 2:
> 
> have this in your local/config.php file:
> 
> $ScriptUrl = 'http://gnuzoo.org/stuffforsale'; $PubDirUrl = 
> 'http://gnuzoo.org/stuffforsale/pub';
> 
> $PagePathFmt = array(
>        '{$Group}.$1',           # page in current group
>        '{$DefaultGroup}.$1',    # page in default group (Main)
>        '$1.$1',                 # group home page
>        '$1.{$DefaultName}',     # group home page
> );
> 
> $pagename = MakePageName('Main.HomePage', $pagename);
> 
> $FmtPV['$PageUrl'] = 'PUE(($group==$GLOBALS["DefaultGroup"])
>                              ? "$ScriptUrl?n=$name"
>                                : "$ScriptUrl?n=$group.$name")'; 
> $FmtP["!\\\$ScriptUrl?n=$DefaultGroup/!"] = '$ScriptUrl';
> 
> That's it.




------------------------------

Message: 3
Date: Tue, 07 Nov 2006 13:09:32 -0500
From: "Neil Herber (nospam)" <nospam at eton.ca>
Subject: Re: [pmwiki-users] spammed page alert
To: Sandy <sandy at onebit.ca>
Cc: pmwiki-users at pmichaud.com
Message-ID: <4550CBDC.10104 at eton.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Sandy wrote:
> Not confident enough to just delete the page and its reference from 
> the cookbook page. The correct page still exists but with capitals in the
name.
> 
> Sandy
> 
> http://pmwiki.org/wiki/Cookbook/Wikifarmstepbystep

Gone!

--
Neil Herber
Corporate info at http://www.eton.ca/



------------------------------

Message: 4
Date: Tue, 7 Nov 2006 12:11:44 -0600
From: "Tegan Dowling" <tmdowling at gmail.com>
Subject: Re: [pmwiki-users] missing password form
To: "Ben Stallings" <Ben at interdependentweb.com>
Cc: pmwiki-users at pmichaud.com
Message-ID:
	<5c8455a0611071011t24dbab22q1a82e959837bb8f8 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Make sure you haven't somehow lost wikilib.d/Site/AuthForm?

Paste in a fresh version?

On 11/7/06, Ben Stallings <Ben at interdependentweb.com> wrote:
> One of my PmWiki sites has stopped displaying the password form.  If you
> use an action that would require a password (such as ?action=edit), you
> get a blank page.  It's not using either AuthUser or UserAuth, but basic
> passwords only, defined in config.php.
>
> Check it out at http://franstallings.com/ .
>
> I've checked the config.php and the files in the scripts directory,
> comparing them to a working site running the same version (2.1.24), and
> can't find any differences -- the program files are identical.  I tried
> commenting out bits of config.php, and the only thing that changes the
> behavior is to comment out the definition of $DefaultPasswords['edit']
> ... and that only enables editing; commenting out the equivalent admin
> password doesn't enable ?action=attr.
>
> One difference I did find was that many files on the sick site were set
> to 644 (rw-r--r--) rather than 664 (rw-rw-r--), but changing this didn't
> help.  I even tried changing them to the Permissions of the Beast
> (rw-rw-rw-), but that did nothing but immanentize the eschaton,
> presumably. (obscure joke)
>
> The sick site is on a different server from my other sites, so I suppose
> some Apache setting could be different, but I don't know where to start
> diagnosing that.  It's been several months since I'm sure it was
> working, and I don't remember making any changes since then, but they
> could have made some changes on the server side without telling me.  Or
> I could have changed something and forgotten!
>
> Any ideas?  What have I overlooked?  Thanks in advance!  --Ben S.
>
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>



------------------------------

Message: 5
Date: Tue, 7 Nov 2006 10:26:02 -0800
From: "Kevin Gabbert" <whiskerville at gmail.com>
Subject: [pmwiki-users] blocklist warning
To: pmwiki-users at pmichaud.com
Message-ID:
	<deef9c660611071026i7daac711j2223020aabf96405 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

I'm using blocklist2 to keep certain words out of articles on my pmwiki, but
I dont like how it doesnt give the user any sort of warning when it blocks
them from saving a page due to a blocked word being present. Is there a way
to add some kind of warning message?

Thanks,

Kevin G.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
/pipermail/pmwiki-users/attachments/20061107/1e6223f1/attachment-0001.html 

------------------------------

Message: 6
Date: Tue, 7 Nov 2006 18:26:55 +0000
From: Hans <design5 at softflow.co.uk>
Subject: [pmwiki-users] Path to skins question
To: pmwiki-users at pmichaud.com
Message-ID: <1397076087.20061107182655 at softflow.co.uk>
Content-Type: text/plain; charset=us-ascii

Hi,

I thought I try and move in my farm setup pmwiki into a folder outside
public_html/, and have the fields and the skins inside it.
This works but no styling is applied.
I can't get pmwiki to see the skin folder.

How can I redefine the $SkinDirUrls array in farmconfig.php
to point to the skin directory?
Directory structure is this:
root/
  pmwiki/pmwiki.php
  public_html/
    farm/
      pub/
        skins/
        css/
        etc..
    fields/
      A-field
      etc..

I tried without success:
I declared $FarmPubDir in farmconfig.php:

$FarmPubDirUrl = 'http://example.com/farm/pub';

and tried without success ($FarmD is correct):

$SkinDirUrls = array(
       "./pub/skins/\$Skin"      => "$PubDirUrl/skins/\$Skin",
      "$FarmD/../public_html/farm/pub/skins/\$Skin" =>
"$FarmPubDirUrl/skins/\$Skin",
      );

How can I get the correct file path into the array?

-- 
Best regards,
 Hans




------------------------------

Message: 7
Date: Tue, 07 Nov 2006 11:32:28 -0700
From: dso <dso at moosoft.com>
Subject: [pmwiki-users] totalcounter error
To: pmwiki-users at pmichaud.com
Message-ID: <4550D13C.9010105 at moosoft.com>
Content-Type: text/plain; charset=ISO-8859-1

I occasionally get
Warning: Illegal offset type in
/usr/www/users/moosoft/www/cookbook/totalcounter.php on line 339

It seems pretty rare, but I was wondering if anyone else had this
problem and knew of a fix.  Thanks

Daniel




------------------------------

Message: 8
Date: Tue, 07 Nov 2006 12:57:11 -0600
From: JB <jbit at bitlink.com>
Subject: Re: [pmwiki-users] Path to skins question
To: pmwiki-users at pmichaud.com
Message-ID: <4550D707.7090100 at bitlink.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

* Hans wrote, On 11/7/2006 12:26 PM:
 > I thought I try and move in my farm setup pmwiki into a folder outside
 > public_html/, and have the fields and the skins inside it.
 > This works but no styling is applied.
 > I can't get pmwiki to see the skin folder.
 > How can I redefine the $SkinDirUrls array in farmconfig.php
 > to point to the skin directory?

Do not use "SkinDirUrls" - I think that is spelled wrong.
use "$SkinLibDirs".

Skin CSS and skin image files MUST be publicly available.
You can put the skin tmpl and skin php files anywhere.
This means that one skin can be comprised of 1 or 2
directories.

The $SkinLibDirs array index points to where the directory
is located in the file system.  The $SkinLibDirs array value
points to a url for the publicly accessible files.  They can
point to the same location, except the index is a file path
and the value is a url.

You can put skin css and images in one location and the
skin (tmpl and/or php) files into another location.

A skin is "found" when it finds a directory named for the skin
in the $SkinLibDirs array index.

It helps to looks at the PMWiki source code for function
SetSkin in file scripts/skins.php.




------------------------------

Message: 9
Date: Tue, 07 Nov 2006 13:07:01 -0600
From: Ben Stallings <Ben at InterdependentWeb.com>
Subject: Re: [pmwiki-users] missing password form
To: Tegan Dowling <tmdowling at gmail.com>
Cc: pmwiki-users at pmichaud.com
Message-ID: <4550D955.6080908 at InterdependentWeb.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Tegan Dowling wrote:
> Make sure you haven't somehow lost wikilib.d/Site/AuthForm?
> 
> Paste in a fresh version?

Whadda ya know!  I must have missed that one when I was comparing all 
the files.  Thanks, Tegan!!  I wonder how it got deleted... --Ben S.



------------------------------

Message: 10
Date: Tue, 7 Nov 2006 19:06:49 +0000
From: Hans <design5 at softflow.co.uk>
Subject: Re: [pmwiki-users] Path to skins question
To: JB <jbit at bitlink.com>
Cc: pmwiki-users at pmichaud.com
Message-ID: <1788266486.20061107190649 at softflow.co.uk>
Content-Type: text/plain; charset=us-ascii

Tuesday, November 7, 2006, 6:57:11 PM, JB wrote:

> Do not use "SkinDirUrls" - I think that is spelled wrong.
> use "$SkinLibDirs".

Sorry, I actually used  "$SkinLibDirs", not "$SkinDirUrls".
Just copied it into the email from an older defunct install.

> Skin CSS and skin image files MUST be publicly available.
> You can put the skin tmpl and skin php files anywhere.
> This means that one skin can be comprised of 1 or 2
> directories.

Yes, i tried this and it worked, splitting the skin into the php file
and into css and js files, and having the php in
pmwiki/pub/skins/$Skin. But I am not happy with this splitting, or
having the skins in two locations. I rather like to point the filepath
from th epmwiki/ directory to the public_html/farm/pub/skins/
directory, and I don't know how to write the right path syntax.

But I thank you for your detailed answer!


Hans




------------------------------

Message: 11
Date: Tue, 7 Nov 2006 21:34:18 +0100
From: "Dominique Faure" <dominique.faure at gmail.com>
Subject: Re: [pmwiki-users] Any news about Blog feature?
To: "David Spitzley" <dspitzle at wash.k12.mi.us>
Cc: pmwiki-users at pmichaud.com
Message-ID:
	<599dbcaf0611071234k50d02881u7c3ceb3bbe6e743d at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 11/7/06, David Spitzley <dspitzle at wash.k12.mi.us> wrote:
> I should note that I think I've got noted sci-fi author David Brin
interested in moving to a PmWiki blog sometime next spring, as long as the
feature is available by then.
>
>

Wouldn't this push PmWiki on the Uplift ladder?

:)
Dom



------------------------------

Message: 12
Date: Tue, 07 Nov 2006 13:56:24 -0700
From: dso <dso at moosoft.com>
Subject: [pmwiki-users] html validation
To: pmwiki-users at pmichaud.com
Message-ID: <4550F2F8.80400 at moosoft.com>
Content-Type: text/plain; charset=ISO-8859-1

I am trying to run my pmwiki through the HTML Validator and it is
complaining about a couple of things.

validator.w3.org

document type does not allow element "META" here
for each of keywords, description and link

end tag for element "SPAN" which is not open .

...R $1><SPAN class=\"abbr\" $1>$2</SPAN></ABBR>');

end tag for element "ABBR" which is not open .

...PAN class=\"abbr\" $1>$2</SPAN></ABBR>');

end tag for element "HEAD" which is not open .

    </head>

document type does not allow element "BODY" here .

    <body bgcolor="#ffffff">


Are these fixable?

Daniel



------------------------------

Message: 13
Date: Tue, 7 Nov 2006 13:46:44 -0800 (PST)
From: Nicholas Buttle <nicholas_buttle at yahoo.com>
Subject: [pmwiki-users] Icons attached to uploaded files...how to
	implement	the suggested solution?
To: pmwiki-users at pmichaud.com
Message-ID: <20061107214644.15575.qmail at web31009.mail.mud.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1

Hi,

Following my request for advice Anno posted this ->

Markup('attachicon', 'inline',
  '/Attach:(.*?)\\.(\\w{1,4})/',
'http://www.server.com/pub/icons/$2.png
Attach:$1.$2');

Replace http://www.server.com/pub/icons with the link
to your pub/icons 
directory

Get your icons from here:
http://www.stylegala.com/features/bulletmadness/

Rename them to be named like this:
pdf.png
xls.png
doc.png
.....
and place them in the icons directory.

<-

Where do I put this markup?  I need to have the icon
attached automatically when a user uploads say a .xls
or .doc file.  It's too much to expect them to inlcude
the above markup. Ideally they should use the PMWiki
standard upload procedure and the icon is magically
included on the page next to or instead of the link.

TIA

Nicholas




 
____________________________________________________________________________
________
Sponsored Link

Degrees online in as fast as 1 Yr - MBA, Bachelor's, Master's, Associate
Click now to apply http://yahoo.degrees.info



------------------------------

_______________________________________________
pmwiki-users mailing list
pmwiki-users at pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users


End of pmwiki-users Digest, Vol 17, Issue 25
********************************************





More information about the pmwiki-users mailing list