[pmwiki-users] Re: pmwiki-users Digest, Vol 3, Issue 14

Rene Visco rvisco at csdr-cde.ca.gov
Fri Sep 2 13:26:37 CDT 2005


Hi,

Regarding the links to Microsoft Word files using Intermap links work  
great, however for Mac clients, it doesn't work.

Here's the email from IT director:

Ok, first go to:
 
http://www.schubert-it.com/pluginword/
 
and download and install the plug-in.
 
Make sure Distributions is mounted. Restart Safari and go to this  
address:
 
file:///Volumes/Distributions/Public/Instruction/testword.doc
 
I don’t like this solution for two reasons: it requires an installation  
of the plug-in, and it requires that the volume be mounted. But it is  
another step in the right direction!
 
Erik

If I copy and paste the file location in Safari, it worked.

I updated the localmap.txt file and use the file location.  The links  
just won't enable the downloading of the doc file.

The top one is for PC version and it worked.  The last two lines are  
for Mac clients.

Instruction     file://csdrsrv03/Distributions/Public/Instruction/
Mac             file:///Volumes/Distributions/Public/Instruction/
MacX		afp:///Volumes/Distributions/Public/Instruction/

Instruction:testwiki.txt  - worked in PC, but not in Mac
Instruction:testword.doc - worked in PC but not in Mac
Mac:testwiki.txt - Not working
Mac:testword.doc - Not working
MacX:testword.doc - Not working

Any ideas/feedback would be helpful!

Rene V.

On Sep 2, 2005, at 10:53 AM, pmwiki-users-request at pmichaud.com wrote:

> Send pmwiki-users mailing list submissions to
> 	pmwiki-users at pmichaud.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://host.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. Re: Method to selectively include template markup	based on
>       auth level (Patrick R. Michaud)
>    2. Re: Method to selectively include template markup	based on
>       auth level (H. Fox)
>    3. Re: Method to selectively include template markup	based on
>       auth level (Patrick R. Michaud)
>    4. Re: New skin: Lens (Christian Schlatter)
>    5. Re: UserAuth (Waylan Limberg)
>    6. Re: UserAuth (Patrick R. Michaud)
>    7. Re: New skin: Lens (Patrick R. Michaud)
>    8. Re: Re: Camel Case by Default . . . (Neil Herber)
>    9. Re: Dynamic Wiki Trails Recipe (Patrick R. Michaud)
>   10. Re: Re: Camel Case by Default . . . (Ben Wilson)
>   11. Re: Method to selectively include template markup	based on
>       auth level (Waylan Limberg)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 2 Sep 2005 12:09:23 -0500
> From: "Patrick R. Michaud" <pmichaud at pobox.com>
> Subject: Re: [pmwiki-users] Method to selectively include template
> 	markup	based on auth level
> To: Mr Wappy <mrwappy at yahoo.co.uk>
> Cc: pmwiki-users at pmichaud.com
> Message-ID: <20050902170923.GP31300 at host.pmichaud.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Sep 02, 2005 at 05:53:04PM +0100, Mr Wappy wrote:
>> I have been using a skin which has tabs for view,
>> edit, attr etc which are displayed all the time.  I
>> have been trying to determine how I could selectively
>> display them based on the current users permissions.
>
> The PmWiki 2 default skin does this for its tabs.  For example, see
>
>     http://www.pmwiki.org/wiki/PmWiki/PmWiki
>     http://www.pmwiki.org/wiki/Main/WikiSandbox
>
> and notice that the "Attach" link appears only where upload permissions
> are enabled.
>
> This is all handled from the Site.PageActions page, which has
> something like the following (simplified here for clarity):
>
>     * %item class=browse% [[{$FullName} | View]]
>     * %item class=edit% [[{$FullName}?action=edit | Edit]]
>     * %item class=history% [[{$FullName}?action=diff | History]]
>     (:if auth upload:)
>     * %item class=upload% [[{$FullName}?action=upload | Attach]]
>     (:if:)
>     * %item class=print% [[{$FullName}?action=print | Print]]
>
> Notice that the (:if ...:) causes the "Attach" link to be displayed
> only if the visitor is currently authorized to upload attachments.
> In the skin template, we simply do:
>
>     <!--wiki:$SiteGroup.PageActions-->
>
> which includes the above page, and then use CSS to style the list
> into tabs.
>
> More generally, one could use:
>
>     (:if auth read:)
>     * %item class=browse% [[{$FullName} | View]]
>     (:if auth edit:)
>     * %item class=edit% [[{$FullName}?action=edit | Edit]]
>     * %item class=history% [[{$FullName}?action=diff | History]]
>     (:if auth upload:)
>     * %item class=upload% [[{$FullName}?action=upload | Attach]]
>     (:if auth read:)
>     * %item class=print% [[{$FullName}?action=print | Print]]
>     (:ifend:)
>
> to display only those actions for which the visitor has authorization.
>
> The "class=xyz" items above make it possible to style the "active tab"
> based on the current action, as seen in
>
>     http://www.pmwiki.org/wiki/Test/Tabs .
>
> The magic that makes this per-action highlight happen is in the
> local customization file:
>
>   $HTMLStylesFmt[] =
>     " #wikicmds li.$action
>        { background-color:white; border-bottom:1px solid white; } ";
>
> which styles the list item corresponding to $action with a
> different background color from the other items.  (Obviously
> more complex styling could be done here.)
>
> Pm
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 2 Sep 2005 10:10:54 -0700
> From: "H. Fox" <haganfox at users.sourceforge.net>
> Subject: Re: [pmwiki-users] Method to selectively include template
> 	markup	based on auth level
> To: pmwiki-users at pmichaud.com
> Message-ID: <2966e8a505090210104b2ba658 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 9/2/05, Mr Wappy <mrwappy at yahoo.co.uk> wrote:
>> but it's not clear to me how I can either
>> i) conditionally include this function within the
>> syntax provided within a template
>> or
>> ii) identify programmatically, within my function that
>> I have placed in config.php, the auth level of the
>> current user.
>>
>> Can anybody provide some more information that would
>> help me with this task?
>
> Related question: How do I do the equivalent of
>
>      (:if auth read:)
>      (:if auth edit:)
>      (:if auth attr:)
>      (:if auth admin:)
>
> in skin.php?
>
> Hagan
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 2 Sep 2005 12:20:06 -0500
> From: "Patrick R. Michaud" <pmichaud at pobox.com>
> Subject: Re: [pmwiki-users] Method to selectively include template
> 	markup	based on auth level
> To: "H. Fox" <haganfox at users.sourceforge.net>
> Cc: pmwiki-users at pmichaud.com
> Message-ID: <20050902172006.GQ31300 at host.pmichaud.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Sep 02, 2005 at 10:10:54AM -0700, H. Fox wrote:
>>> Can anybody provide some more information that would
>>> help me with this task?
>>
>> Related question: How do I do the equivalent of
>>
>>      (:if auth read:)
>>      (:if auth edit:)
>>      (:if auth attr:)
>>      (:if auth admin:)
>>
>> in skin.php?
>
> $page = RetrieveAuthPage($pagename, 'read', false, READPAGE_CURRENT);
> if ($page['=auth']['read']) /* visitor has read permission */
> if ($page['=auth']['edit']) /* visitor has edit permission */
> if ($page['=auth']['attr']) /* visitor has attr permission */
> if ($page['=auth']['admin']) /* visitor has admin permission */
>
> Pm
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 02 Sep 2005 19:31:15 +0200
> From: Christian Schlatter <ch at schlatter.net>
> Subject: Re: [pmwiki-users] New skin: Lens
> To: Pmwiki-Users <pmwiki-users at pmichaud.com>
> Message-ID: <43188C63.2000302 at schlatter.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Patrick R. Michaud wrote:
>> ...
>> But potentially another way to do things is to add another variable:
>>
>>    $Skin = 'lens';
>>    $Theme = 'sample';
>>
>> and then the skin.php file can use the $Theme variable to decide
>> what subdirectory of lens/ to use to pick and choose things from.
>> (If $Theme isn't set, the skin.php could choose a default.)
>> Inside of a skin template, one can do things like
>> $SkinDirUrl/$Theme/whatever.css to get to theme-specific files for
>> the skin.
>
> The Gallery2 developer team just decided to get rid of the distinction
> between skin and theme since it mainly introduced a lot of confusion.
> They also divided the css files into theme specific (fonts, colors,  
> etc)
> and template specific (placement, widths, etc) ones. At the end, the
> whole templating/theming system got too complex.
>
> IMHO, it would be "dangerous" to introduce even a $Theme variable only.
>
> -ChristianS
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 2 Sep 2005 13:33:49 -0400
> From: Waylan Limberg <waylan at gmail.com>
> Subject: Re: [pmwiki-users] UserAuth
> To: pmwiki-users at pmichaud.com
> Message-ID: <e5d795bb0509021033340bd104 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
>> There is a new template directive that allows defining PmWiki markup  
>> in
>> the template. As an example, you could use
>>
>> <!--markup:(:if auth edit:)[[Edit this page ->
>> {$Name}?action=edit]](:if:)-->
>>
>
> Very cool. Where is this documented? I've never seen it before.
>
>
> --  
> ----
> Waylan Limberg
> waylan at gmail.com
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 2 Sep 2005 12:35:01 -0500
> From: "Patrick R. Michaud" <pmichaud at pobox.com>
> Subject: Re: [pmwiki-users] UserAuth
> To: Waylan Limberg <waylan at gmail.com>
> Cc: pmwiki-users at pmichaud.com
> Message-ID: <20050902173500.GS31300 at host.pmichaud.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Sep 02, 2005 at 01:33:49PM -0400, Waylan Limberg wrote:
>>> There is a new template directive that allows defining PmWiki markup  
>>> in
>>> the template. As an example, you could use
>>>
>>> <!--markup:(:if auth edit:)[[Edit this page ->
>>> {$Name}?action=edit]](:if:)-->
>>>
>>
>> Very cool. Where is this documented? I've never seen it before.
>
> http://www.pmwiki.org/wiki/PmWiki/SkinTemplates
>
> Pm
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 2 Sep 2005 12:42:03 -0500
> From: "Patrick R. Michaud" <pmichaud at pobox.com>
> Subject: Re: [pmwiki-users] New skin: Lens
> To: Christian Schlatter <ch at schlatter.net>
> Cc: Pmwiki-Users <pmwiki-users at pmichaud.com>
> Message-ID: <20050902174203.GA20961 at host.pmichaud.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Sep 02, 2005 at 07:31:15PM +0200, Christian Schlatter wrote:
>> Patrick R. Michaud wrote:
>>> ...
>>> But potentially another way to do things is to add another variable:
>>>
>>>   $Skin = 'lens';
>>>   $Theme = 'sample';
>>
>> The Gallery2 developer team just decided to get rid of the distinction
>> between skin and theme since it mainly introduced a lot of confusion.
>> ...
>> IMHO, it would be "dangerous" to introduce even a $Theme variable  
>> only.
>
> Ah, this sounds like very good advice based on experience.
> Then I'd say to fall back to trying something along the lines of
>
>     $Skin = 'lens/sample';
>
> That *should* work, and if it doesn't we'll make it work.
>
> Many thanks,
>
> Pm
>
>
>
> ------------------------------
>
> Message: 8
> Date: Fri, 02 Sep 2005 13:49:06 -0400
> From: Neil Herber <nospam at eton.ca>
> Subject: Re: [pmwiki-users] Re: Camel Case by Default . . .
> To: dausha at gmail.com,pmwiki-users at pmichaud.com
> Message-ID: <6.2.1.2.0.20050902132204.01f41b10 at pop3mail.eton.ca>
> Content-Type: text/plain; charset="us-ascii"; format=flowed
>
> At 2005-09-02  08:10 AM -0500, Ben Wilson is rumored to have said:
>> We're supposed to be documenting PmWiki for its 2.0 release, not  
>> asking
>> for nitnoid changes to look more like another wiki. PmWiki is hands  
>> down
>> the best wiki product I've used or evaluated. I tell people that I've  
>> been
>> using it since July 26, 2004. Yes, it was such a breath of fresh  
>> air--even
>> then--that I made a point of remembering the date. (It does not hurt  
>> that
>> my wedding anniversary is the next day.)
>>
>> Please, let's stop asking for these changes until we finish the
>> documentation. I want the 'beta' moniker removed. :-)
>
> Unless I am sadly mistaken, version 2.0.0 has been released and the  
> "beta"
> suffix is gone. ;-)
>
> The discussion about CamelCase linking was sparked by a comment from Pm
> himself. He mused that he would liked to have made CamelCase linking  
> off by
> default. It is not a new feature request.
>
> My nitnoid response that I would like to see CamelCase off by default  
> is
> based on my personal experience. I find it much more aggravating to  
> disable
> individual links (via backtick) than to enable links I really want via
> [[brackets]]. Besides, someone wanting to make an [[explicit link]]  
> via a
> phrase that is not CamelCase has to learn the brackets code (or use the
> edit button).
>
>
> Neil
>
> Neil Herber
> Corporate info at http://www.eton.ca/
> Eton Systems, 15 Pinepoint Drive, Nepean, ON, Canada K2H 6B1
> Tel: (613) 829-4668
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Fri, 2 Sep 2005 12:51:07 -0500
> From: "Patrick R. Michaud" <pmichaud at pobox.com>
> Subject: Re: [pmwiki-users] Dynamic Wiki Trails Recipe
> To: "Fick, Martin" <fick at fgm.com>
> Cc: PmWiki <pmwiki-users at pmichaud.com>
> Message-ID: <20050902175107.GB20961 at host.pmichaud.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Sep 01, 2005 at 10:29:11PM -0400, Fick, Martin wrote:
>>
>>    That does not seem to work, I get the following:
>>
>>    Fatal error: Cannot redeclare readtrail() (previously declared in
>>    local/urltrails.php:29) in scripts/trails.php on line 37
>
> PmWiki's trails code can be turned off by setting $EnableWikiTrails=0;
> in the urltrails.php script.  That's probably a bit more than what
> you're wanting to do, however.
>
> More likely I'll see about fixing the trail code in the core
> so that any ?trail= or other options can still be processed by the
> core code.
>
> Pm
>
>
>
> ------------------------------
>
> Message: 10
> Date: Fri, 2 Sep 2005 12:52:39 -0500
> From: Ben Wilson <dausha at gmail.com>
> Subject: Re: [pmwiki-users] Re: Camel Case by Default . . .
> To: Neil Herber <nospam at eton.ca>
> Cc: pmwiki-users at pmichaud.com
> Message-ID: <cc60970505090210525739b603 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Yes, I have been humbled. :-( I had not been keeping up on my list  
> reading
> and reacted before I had enough information. I did not notice the
> 2.0release--that's how behind on my reading I'd been. I'll blame it on
> Law
> School.
>
> Ben
>
> On 9/2/05, Neil Herber <nospam at eton.ca> wrote:
>>
>> At 2005-09-02 08:10 AM -0500, Ben Wilson is rumored to have said:
>>> We're supposed to be documenting PmWiki for its 2.0 release, not  
>>> asking
>>> for nitnoid changes to look more like another wiki. PmWiki is hands  
>>> down
>>> the best wiki product I've used or evaluated. I tell people that I've
>> been
>>> using it since July 26, 2004. Yes, it was such a breath of fresh
>> air--even
>>> then--that I made a point of remembering the date. (It does not hurt  
>>> that
>>> my wedding anniversary is the next day.)
>>>
>>> Please, let's stop asking for these changes until we finish the
>>> documentation. I want the 'beta' moniker removed. :-)
>>
>> Unless I am sadly mistaken, version 2.0.0 has been released and the  
>> "beta"
>> suffix is gone. ;-)
>>
>> The discussion about CamelCase linking was sparked by a comment from  
>> Pm
>> himself. He mused that he would liked to have made CamelCase linking  
>> off
>> by
>> default. It is not a new feature request.
>>
>> My nitnoid response that I would like to see CamelCase off by default  
>> is
>> based on my personal experience. I find it much more aggravating to
>> disable
>> individual links (via backtick) than to enable links I really want via
>> [[brackets]]. Besides, someone wanting to make an [[explicit link]]  
>> via a
>> phrase that is not CamelCase has to learn the brackets code (or use  
>> the
>> edit button).
>>
>>
>> Neil
>>
>> Neil Herber
>> Corporate info at http://www.eton.ca/
>> Eton Systems, 15 Pinepoint Drive, Nepean, ON, Canada K2H 6B1
>> Tel: (613) 829-4668
>>
>>
>
>
> --  
> Ben Wilson
> " Mundus vult decipi, ergo decipiatur"
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:  
> /pipermail/pmwiki-users/attachments/20050902/9463ad69/attachment 
> -0001.html
>
> ------------------------------
>
> Message: 11
> Date: Fri, 2 Sep 2005 13:53:00 -0400
> From: Waylan Limberg <waylan at gmail.com>
> Subject: Re: [pmwiki-users] Method to selectively include template
> 	markup	based on auth level
> To: "Patrick R. Michaud" <pmichaud at pobox.com>
> Cc: Mr Wappy <mrwappy at yahoo.co.uk>, pmwiki-users at pmichaud.com
> Message-ID: <e5d795bb050902105364c06cc6 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
>> Notice that the (:if ...:) causes the "Attach" link to be displayed
>> only if the visitor is currently authorized to upload attachments.
>> In the skin template, we simply do:
>>
>>     <!--wiki:$SiteGroup.PageActions-->
>>
>> which includes the above page, and then use CSS to style the list
>> into tabs.
>>
>> More generally, one could use:
>>
>>     (:if auth read:)
>>     * %item class=browse% [[{$FullName} | View]]
>>     (:if auth edit:)
>>     * %item class=edit% [[{$FullName}?action=edit | Edit]]
>>     * %item class=history% [[{$FullName}?action=diff | History]]
>>     (:if auth upload:)
>>     * %item class=upload% [[{$FullName}?action=upload | Attach]]
>>     (:if auth read:)
>>     * %item class=print% [[{$FullName}?action=print | Print]]
>>     (:ifend:)
>>
>
> All this Site.PageActions stuff is nice. Would have saved me a little
> trouble the past couple days. I have not come acrossed anything about
> it in the wiki. It this documented anywhere?
>
>
> -- 
> ----
> Waylan Limberg
> waylan at gmail.com
>
>
>
> ------------------------------
>
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://host.pmichaud.com/mailman/listinfo/pmwiki-users
>
>
> End of pmwiki-users Digest, Vol 3, Issue 14
> *******************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 18307 bytes
Desc: not available
Url : /pipermail/pmwiki-users/attachments/20050902/5ffbb8e6/attachment.bin 


More information about the pmwiki-users mailing list