[pmwiki-users] writing paragraph style markup
Seth Cherney
sethcherney at yahoo.com
Wed Feb 6 04:22:53 CST 2008
I am trying to write a markup which will replace the default paragraph with one like <p class='mine'>
I have many custom markups which end at the line return, but do not know how to span a line return, I have many of them by necessity in the midle of paragraphs....
E.G:
Markup("scholium",'inline','/!s!(.*?)$/',"<span class='scholium'>$1</span>");
But getting that to wrap and be a p that replaces the standard one...
Thanks, Seth
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://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. Re: Anyone recognize these error messages? (Sandy)
2. Re: (DaveG)
3. Re: Admin password not recognized for FoxConfig (Hans)
4. Re: Admin password not recognized for FoxConfig (Hans)
5. Change the Page Does Not Exist page if not authorized (Sandy)
6. Re: Change the Page Does Not Exist page if not authorized
(Petko Yotov)
7. bilingual (nikos roussos)
8. Re: bilingual (Hans)
9. Re: bilingual (Hans)
10. Pre-fill author required field with login name on a
one-password-for-all wiki? (Benoit Dutilleul)
11. Re: Admin password not recognized for FoxConfig
(Peter & Melodye Bowers)
12. Re: bilingual (blues)
----------------------------------------------------------------------
Message: 1
Date: Tue, 05 Feb 2008 17:34:16 -0500
From: Sandy
Subject: Re: [pmwiki-users] Anyone recognize these error messages?
To: pmwiki-users at pmichaud.com
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
DaveG wrote:
> Tegan Dowling wrote:
> > "Warning: Cannot modify header information - headers already sent by
>> (output started at /home/justice4/public_html/test/pmwiki.php:281) in
>> /home/justice4/public_html/test/pmwiki.php on line 884".
>
>
>> RewriteEngine on
>> RewriteRule ^([A-Z].*) index.php?n=$1 [L,qsappend]
>> RewriteRule ^$ index.php [L,qsappend]
>>
>
> It looks like you have errors referring to pmwiki.php, whilst your
> .htaccess is redirecting to index.php. Did you simply rename pmwiki.php
> to index.php, or index.php does an include of pmwiki.php. If the later
> does index.php do anything else that would cause output? That'd be where
> I'd start.
>
> Also, I'm assuming this is a basic install with no cookbook? If not try
> disabling those to see if there might be some interference.
>
> ~ ~ Dave
Have you done anything non-standard with directories? Changing the path
in .htaccess usually means there are other paths to change as well.
Sandy
(Who absolutely hates getting into paths and redirects and rewriting.
Too many things to change all at once.)
------------------------------
Message: 2
Date: Tue, 05 Feb 2008 17:38:02 -0500
From: DaveG
Subject: Re: [pmwiki-users]
To: St?phane Heckel
Cc: pmwiki-users at pmichaud.com
Message-ID: <47A8E54A.6010408 at solidgone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
St?phane Heckel wrote:
> "Patrick R. Michaud" wrote :
>
HTML tag is generated by the skin, not by a PmWiki markup.<br>>> The default PmWiki skin (pub/skins/pmwiki/pmwiki.tmpl) uses:<br>>> <title>$WikiTitle | {$Group} / {$Title} $ActionTitle>> The
>
> Hi Patrick & Petko, thanks both
is not defined in the .tmpl file.> I use the Blix skin and
> I'm going to suggest this enhancement request to DaveG.
Thanks for the heads-up. I've added the problem to the Known Issues
list. Fix should be soon...
~ ~ Dave
------------------------------
Message: 3
Date: Tue, 5 Feb 2008 22:53:40 +0000
From: Hans
Subject: Re: [pmwiki-users] Admin password not recognized for
FoxConfig
To: Randy
Cc: pmwiki-users at pmichaud.com
Message-ID: <956699367.20080205225340 at softflow.co.uk>
Content-Type: text/plain; charset=us-ascii
Tuesday, February 5, 2008, 10:31:17 PM, Randy wrote:
> I have a suspicion about at least part of the email problem. You
> corrected Fox.php on 2008-01-22 to add handling of $ChangeSummary. I
> see that you didn't make any changes to foxdelete.php or foxedit.php.
> Today in testing the delete button I noticed that All Recent Changes
> is showing me "Post deleted", but the page history isn't. And the
> duplicate email notifications triggered by the deletion both contain
> the previous Summary ("item added"). I suspect foxdelete.php and
> foxedit.php need to be updated too.
okay, I added the same modification to foxdelete. see if that helps.
An update is uploaded:
http://www.pmwiki.org/wiki/Cookbook/FoxDelete
I also did a small change to Fox:
For foxaction=display with no target being set the output goes to the
current page. This was the case for 'add', but not for 'display'.
http://www.pmwiki.org/wiki/Cookbook/Fox
I have no idea about the admin password problem you are reporting,
and how it could relate to Fox.
~Hans
------------------------------
Message: 4
Date: Tue, 5 Feb 2008 22:57:25 +0000
From: Hans
Subject: Re: [pmwiki-users] Admin password not recognized for
FoxConfig
To: Randy
Cc: pmwiki-users at pmichaud.com
Message-ID: <753333588.20080205225725 at softflow.co.uk>
Content-Type: text/plain; charset=us-ascii
Tuesday, February 5, 2008, 10:53:40 PM, Hans wrote:
> I suspect foxdelete.php and foxedit.php need to be updated too.
PS: foxedit does not do any page saves, it just loads an edit form.
Let me know if the notify problem is cured or not with the change in
foxdelete.php
~Hans
------------------------------
Message: 5
Date: Tue, 05 Feb 2008 18:09:28 -0500
From: Sandy
Subject: [pmwiki-users] Change the Page Does Not Exist page if not
authorized
To: pmwiki-users at pmichaud.com
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Currently, if you go to a page that does not exist, and you are not
authorized to create one, it asks for a password before doing anything
else, without explaining why.
I would like the user to be told the page doesn't exist and get a link
to the Search page, as well being asked to log in.
I tried editing Site.PageNotFound, but the request for a password comes
up before that page.
Any ideas?
Thanks in advance,
Sandy
------------------------------
Message: 6
Date: Wed, 6 Feb 2008 00:18:53 +0100
From: Petko Yotov <5ko at 5ko.fr>
Subject: Re: [pmwiki-users] Change the Page Does Not Exist page if not
authorized
To: Sandy
Cc: pmwiki-users at pmichaud.com
Message-ID: <200802060018.53898.5ko at 5ko.fr>
Content-Type: text/plain; charset="iso-8859-1"
On Wednesday 06 February 2008, Sandy wrote:
> Currently, if you go to a page that does not exist, and you are not
> authorized to create one, it asks for a password before doing anything
> else, without explaining why.
>
> I would like the user to be told the page doesn't exist and get a link
> to the Search page, as well being asked to log in.
>
> I tried editing Site.PageNotFound, but the request for a password comes
> up before that page.
Edit the Site.AuthForm page too. Site.AuthForm is displayed when a user calls
a restricted page with ?action=edit. Site.PageNotFound is displayed when a
user calls the page without any action.
Thanks,
Petko
------------------------------
Message: 7
Date: Wed, 6 Feb 2008 02:32:29 +0200
From: nikos roussos
Subject: [pmwiki-users] bilingual
To: pmwiki-users at pmichaud.com
Message-ID: <20080206023229.0fbc679c at hellug.gr>
Content-Type: text/plain; charset=US-ASCII
what's the proper way to make a bilingual site with pmwiki using the same
skin?
------------------------------
Message: 8
Date: Wed, 6 Feb 2008 08:24:04 +0000
From: Hans
Subject: Re: [pmwiki-users] bilingual
To: nikos roussos
Cc: pmwiki-users at pmichaud.com
Message-ID: <1081998020.20080206082404 at softflow.co.uk>
Content-Type: text/plain; charset=us-ascii
Wednesday, February 6, 2008, 12:32:29 AM, nikos roussos wrote:
> what's the proper way to make a bilingual site with pmwiki using the same
> skin?
I recommend putting different language sections in each page, and have
one of them displayed, by user choice.
I tried http://www.pmwiki.org/wiki/Cookbook/MultiLanguage
which does exactly that, offering markup like
(:if userlang en:)
english text
(:if userlang gr:)
greek text
...
(:if:)
common text
but i had problem with that recipe, especially using th elanguage
conditional in the sidebar.
So i use http://www.pmwiki.org/wiki/Cookbook/ViewModes
instead. You get a (:if view ...:) conditional, a setview= action to
set a view cookie, and a {$View} page variable.
I redefined the $ViewList array, before including the script in
config.php, like
$ViewList, array(
'en' => 'en',
'de' => 'de',
'gr' => 'gr',
'it' => 'it',
));
and set a default:
$View = 'en';
Then in the pages i use
(:if view en:)
english text
(:if view de:)
deutscher Text
...
(:if:)
common text
In the sidebar, or header, I put links for setting the 'view'
(language):
[[{*$FullName}?setview=en| english]]
[[{*$FullName}?setview=de| deutsch]]
Actually instead of 'english', 'greek' etc text labels i use little
flag images to click on.
[[{*$FullName}?setview=en| Attach:Site/Site/flag-en.gif"english"]]
[[{*$FullName}?setview=de| Attach:Site/Site/flag-de.gif"deutsch"]]
That takes care for multi language content.
It is also possible to use a multi-language wiki interface for all the
action links etc.
I did that in config.php after the views.php is included with
if ($_COOKIE['view'] == 'de') {
XLPage('de','Site.XLDePageCookbook');
XLPage('de','Site.XLDeLocalPage');
XLPage('de','Site.XLDePage');
}
etc.
The default for pmwiki is english, so does not need to be specified.
The XL translation terms pages get loaded according to the cookie
setting.
A slight hitch is that on first page load the default language
interface will show, and only on subsequent page loads the cookie
setting will be taken into account. But this is for me a minor
inconveniance, and only affects the interface.
Hope this gives you some ideas!
~Hans
------------------------------
Message: 9
Date: Wed, 6 Feb 2008 08:48:05 +0000
From: Hans
Subject: Re: [pmwiki-users] bilingual
To: nikos roussos
Cc: pmwiki-users at pmichaud.com
Message-ID: <1824703034.20080206084805 at softflow.co.uk>
Content-Type: text/plain; charset=us-ascii
Wednesday, February 6, 2008, 8:24:04 AM, Hans wrote:
> $ViewList, array(
> 'en' => 'en',
> 'de' => 'de',
> 'gr' => 'gr',
> 'it' => 'it',
> ));
sorry, this should be:
$ViewList = array(
'en' => 'en',
'de' => 'de',
'gr' => 'gr',
'it' => 'it',
);
~Hans
------------------------------
Message: 10
Date: Wed, 6 Feb 2008 09:51:36 +0100
From: "Benoit Dutilleul"
Subject: [pmwiki-users] Pre-fill author required field with login name
on a one-password-for-all wiki?
To: "PmWiki Users"
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
Hi there,
One of my wikis is currently setup with a one-password-for-all (read and
edit) and $EnablePostAuthorRequired=1.
When users login on the wiki, they have to provide a login name (anything
they want) and the wiki password. If they attempt to edit a page, there is a
red warning message "An author name is required" displayed only the first
time they save an edit. I was wondering whether it is possible to have
pmwiki inherit that author name from the login name because this has caused
a bit of confusion with my users.
Kind regards,
Benoit
--
Wanderer, your footsteps are the road, and nothing more; wanderer, there is
no road, the road is made by walking. By walking one makes the road, and
upon glancing behind one sees the path that never will be trod again.
Wanderer, there is no road-- Only wakes upon the sea. -- Antonio Machado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/pmwiki-users/attachments/20080206/a5e298d9/attachment-0001.html
------------------------------
Message: 11
Date: Wed, 6 Feb 2008 10:21:37 +0100
From: "Peter & Melodye Bowers"
Subject: Re: [pmwiki-users] Admin password not recognized for
FoxConfig
To: "'PmWiki Users List'"
Cc: Peter Gmail Bowers
, SentN
Message-ID: <47244A56791D4D8A9FD12246F5302888 at plb>
Content-Type: text/plain; charset="us-ascii"
> I didn't realize that variables have to be set before a script is
> included. Some examples in PmWiki - for example SiteAnalyzer - show it
> the other way around. I guess some scripts don't care and others do.
> (To all recipe authors: it would help us PmWiki newbies if you mention
> loading order requirements wherever they exist.)
Is there a "standard" way to do this or even a "preferred" way? I can see
where certain implementations would make it harder or easier to allow
variable/option setting before/after the include line but probably many
times it's just happenstance -- maybe if there were a declared standard (or
preference) officially declared then all the "happenstances" would lean in
the same way...?
-Peter
------------------------------
Message: 12
Date: Wed, 06 Feb 2008 11:58:21 +0200
From: blues
Subject: Re: [pmwiki-users] bilingual
To: pmwiki-users at pmichaud.com
Message-ID:
Content-Type: text/plain; format=flowed; delsp=yes;
charset=iso-8859-15
On Wed, 06 Feb 2008 10:24:04 +0200, Hans wrote:
> Wednesday, February 6, 2008, 12:32:29 AM, nikos roussos wrote:
>> what's the proper way to make a bilingual site with pmwiki using the
>> same
>> skin?
>
> I recommend putting different language sections in each page, and have
> one of them displayed, by user choice.
>
> I tried http://www.pmwiki.org/wiki/Cookbook/MultiLanguage
> which does exactly that,
> [...cut...]
>
> but i had problem with that recipe, especially using th elanguage
> conditional in the sidebar.
the last MultiLanguage version should not have problems with
the sidebar anymore, unless you found something new. If so,
please tell me what problem you have.
> So i use http://www.pmwiki.org/wiki/Cookbook/ViewModes
> instead.
> [...cut...]
the MultiLanguage recipe offers some language-specific things that
ViewModes does not offer, for example:
- multi-language titles (also titled links work: [[MyPage|+]])
- multi-language pagelists (i.e. ability to search pages in a certain
language)
- automatic language selection links
- possibility to fall-back to a default language when the user selected
language does not exists
- etc...
blues
------------------------------
_______________________________________________
pmwiki-users mailing list
pmwiki-users at pmichaud.com
http://www.pmichaud.com/mailman/listinfo/pmwiki-users
End of pmwiki-users Digest, Vol 32, Issue 11
********************************************
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/pmwiki-users/attachments/20080206/14844350/attachment-0001.html
More information about the pmwiki-users
mailing list