phpwiki-talk

Re: [Phpwiki-talk] TOC headings - unique ID

[Micki K. <mic...@co...>]

ONe other addition: to exclude the comments from the 'main' page, but 
have them on the 'included' pages, just use a 'section=' in the 
IncludePage plugin. I don't think 'section=' is active in 
IncludeSiteMap, but that should be easy to explore...

Enjoy!
Micki

>For your application, make that 'h2'...
>
>Micki
>
>>Whit:
>>
>>I'd use IncludePage (for static includes) or IncludeSiteMap (for 
>>dynamic includes based on WikiBadges), and (HACK ALERT) change the 
>>'transclusion-title' in the stylesheet to an h1 heading. Then, 
>>insert a TOC and lock the main page. UnfoldSubPages should work 
>>similarly to IncludePage, with a defined list, not quite 'static' 
>>but not as dynamic as a 'WikiBadges' approach like IncludeSiteMap.
>>
>>Should give you a large chunk of the behavior for which you are 
>>searching - clickable headers that point back to the base pages, a 
>>locked 'book' page containing the includes, and a TOC that 
>>accommodates the huperlinking.
>>
>>What do you think? Am I missing something fundamental?
>>Micki
>>
>>At 8:07 PM -0800 3/6/04, php...@li... wrote:
>>>Message: 1
>>>Date: Sat, 6 Mar 2004 13:16:57 -0500
>>>From: Whit Blauvelt <wh...@tr...>
>>>To: php...@li...
>>>Subject: Re: [Phpwiki-talk] TOC headings - unique ID
>>>
>>>On Fri, Mar 05, 2004 at 08:33:30PM -0500, Micki Kaufman wrote:
>>>  > Absolutely - a unique ID in each anchor and href is critical, to
>>>  > differentiate form from function...
>>>
>>>While it's simple enough to add something either time-based on a fine-enough
>>>scale or sufficiently random in the TOC context, I've been puzzling on how
>>>to borrow the functionality being built for the TOC context to get the
>>>following effect: having each heading accompanied by an auto-generated link
>>>to a subpage (somewhat like the calendar plugin). The notion is that the
>>>main page remains owned by - and only editable by - the primary author(s),
>>>but the subpages are there for open comments on each of the subsections
>>>(with an option to display comments and sections side-by-side).
>>>
>>>The stumbling block with doing this is that, while the unique ID scheme that
>>>will be used in the TOC most probably will generate the IDs on-the-fly each
>>>time the page is generated, the unique ID scheme required for what I'm after
>>>would have to be stable so the subpage links could be consistent. To have it
>>>be stable all I can think of is to write the IDs into the page body on the
>>>first pass through - which seems a bit un-wiki-like and noisey. Is there a
>>>solution I'm overlooking?
>>>
>>>Thanks,
>>>Whit
>>

-- 

Micki
mailto:mic...@co...

RE: [Phpwiki-talk] Status of the UpLoad.php plugin?

[electron <ele...@mg...>]

You can use the GD library to check if a jpg is really a jpg.=20

The problem with the uploads plugin is usually that file is accessable =
right
away in uploads.

Say: http://www.wiki.org/uploads/hackme.php etc.

Paranoia solution is solved by sandboxing the new upload, running tests =
to
see what it is, and if it's strange put it aside for an admin to look =
at.

-Jtp


I've stopped 7,458 spam messages. You can too!
One month FREE spam protection at http://www.cloudmark.com/spamnetsig/}

-----Original Message-----
From: php...@li...
[mailto:php...@li...] On Behalf Of Whit =
Blauvelt
Sent: Sunday, March 07, 2004 2:04 PM
To: php...@li...
Subject: Re: [Phpwiki-talk] Status of the UpLoad.php plugin?

On Sun, Mar 07, 2004 at 01:45:24PM -0600, electron wrote:
> Since the upload plugin doesn't currently do any bounds checking, a
> malicious user can upload a hackme.php and do malicious things. I can =
come
> up with a fun list if you really want.

v 1.6 2004/02/27 (from the nightly a few days back) checks for =
disallowed
extensions including php. That's not enough to be really safe (for =
instance,
.php3 would work, and many servers recognize that). But it would be =
fairly
simply to change it instead to run a regex of _allowed_ extensions =
(i.e.,
jpg, jpeg, gif, zip ... whatever fits your purpose) and block everything
else. Then all you have to do is be sure there's no way a file with any =
of
your allowed extensions has any way of being executed, or included in
something that would render its contents so. YMMV. In other contexts =
I've
allowed signed-in users to upload via PHP for years, and locking it down =
to
the specific file types that make sense in the context and (as far as I
know) there have been no problems.

Whit


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] Status of the UpLoad.php plugin?

[Whit B. <wh...@tr...>]

On Sun, Mar 07, 2004 at 01:45:24PM -0600, electron wrote:
> Since the upload plugin doesn't currently do any bounds checking, a
> malicious user can upload a hackme.php and do malicious things. I can come
> up with a fun list if you really want.

v 1.6 2004/02/27 (from the nightly a few days back) checks for disallowed
extensions including php. That's not enough to be really safe (for instance,
.php3 would work, and many servers recognize that). But it would be fairly
simply to change it instead to run a regex of _allowed_ extensions (i.e.,
jpg, jpeg, gif, zip ... whatever fits your purpose) and block everything
else. Then all you have to do is be sure there's no way a file with any of
your allowed extensions has any way of being executed, or included in
something that would render its contents so. YMMV. In other contexts I've
allowed signed-in users to upload via PHP for years, and locking it down to
the specific file types that make sense in the context and (as far as I
know) there have been no problems.

Whit

RE: [Phpwiki-talk] Status of the UpLoad.php plugin?

[electron <ele...@mg...>]

Since the upload plugin doesn't currently do any bounds checking, a
malicious user can upload a hackme.php and do malicious things. I can =
come
up with a fun list if you really want.

Hence why the plugin is currently admin only :/

-Jtp

I've stopped 7,458 spam messages. You can too!
One month FREE spam protection at http://www.cloudmark.com/spamnetsig/}
-----Original Message-----
From: php...@li...
[mailto:php...@li...] On Behalf Of Robert =
Dodier
Sent: Sunday, March 07, 2004 1:24 PM
To: php...@li...
Subject: [Phpwiki-talk] Status of the UpLoad.php plugin?

Hello,

I set up a wiki for the Maxima project. Works great!
I just need to drum up more interest. 8^)

I'm considering enabling file uploads for general users.
I see that the UpLoad.php plugin script is enabled for the
administrator only by default. Is the script suitable for
general use (by disabling the administrator requirement),
or is there something fundamentally not OK about it?

Any comments you might have about UpLoad.php or file uploading
in general are very welcome.

regards,
Robert Dodier

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you're looking for faster
http://search.yahoo.com


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

[Phpwiki-talk] Status of the UpLoad.php plugin?

[Robert D. <rob...@ya...>]

Hello,

I set up a wiki for the Maxima project. Works great!
I just need to drum up more interest. 8^)

I'm considering enabling file uploads for general users.
I see that the UpLoad.php plugin script is enabled for the
administrator only by default. Is the script suitable for
general use (by disabling the administrator requirement),
or is there something fundamentally not OK about it?

Any comments you might have about UpLoad.php or file uploading
in general are very welcome.

regards,
Robert Dodier

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com

[Phpwiki-talk] excluding certain InitialCaps from being split

[Micki K. <mic...@co...>]

Hi folks - here's an idea - how about allowing list of words NOT to 
split (like product names, for example - WebCrossing, MacDraw, etc.)?

It would need to split other InitialCaps in the page name, but not 
the ones in the list...

Micki
-- 

Micki
mailto:mic...@co...

Re: [Phpwiki-talk] "Fatal Database Error"

[Tony L. <la...@is...>]

On Fri, 27 Feb 2004 01:12:22 +0100
Reini Urban <ru...@x-...> wrote:

> your page or link table is corrupt.
> Try to delete all pages with empty pagename AND all links to it.

By way of follow-up: 
It turns out there was just some characters on one page that didn't agree with something. deleting that text and saving (without touching the database) solved the problem. 


-- 
Tony Laszlo
irc://irc.freenode.net/issho
talking.to/blog

Re: [Phpwiki-talk] TOC headings - unique ID

[Micki K. <mic...@co...>]

For your application, make that 'h2'...

Micki

>Whit:
>
>I'd use IncludePage (for static includes) or IncludeSiteMap (for 
>dynamic includes based on WikiBadges), and (HACK ALERT) change the 
>'transclusion-title' in the stylesheet to an h1 heading. Then, 
>insert a TOC and lock the main page. UnfoldSubPages should work 
>similarly to IncludePage, with a defined list, not quite 'static' 
>but not as dynamic as a 'WikiBadges' approach like IncludeSiteMap.
>
>Should give you a large chunk of the behavior for which you are 
>searching - clickable headers that point back to the base pages, a 
>locked 'book' page containing the includes, and a TOC that 
>accommodates the huperlinking.
>
>What do you think? Am I missing something fundamental?
>Micki
>
>At 8:07 PM -0800 3/6/04, php...@li... wrote:
>>Message: 1
>>Date: Sat, 6 Mar 2004 13:16:57 -0500
>>From: Whit Blauvelt <wh...@tr...>
>>To: php...@li...
>>Subject: Re: [Phpwiki-talk] TOC headings - unique ID
>>
>>On Fri, Mar 05, 2004 at 08:33:30PM -0500, Micki Kaufman wrote:
>>  > Absolutely - a unique ID in each anchor and href is critical, to
>>  > differentiate form from function...
>>
>>While it's simple enough to add something either time-based on a fine-enough
>>scale or sufficiently random in the TOC context, I've been puzzling on how
>>to borrow the functionality being built for the TOC context to get the
>>following effect: having each heading accompanied by an auto-generated link
>>to a subpage (somewhat like the calendar plugin). The notion is that the
>>main page remains owned by - and only editable by - the primary author(s),
>>but the subpages are there for open comments on each of the subsections
>>(with an option to display comments and sections side-by-side).
>>
>>The stumbling block with doing this is that, while the unique ID scheme that
>>will be used in the TOC most probably will generate the IDs on-the-fly each
>>time the page is generated, the unique ID scheme required for what I'm after
>>would have to be stable so the subpage links could be consistent. To have it
>>be stable all I can think of is to write the IDs into the page body on the
>>first pass through - which seems a bit un-wiki-like and noisey. Is there a
>>solution I'm overlooking?
>>
>>Thanks,
>>Whit
>

-- 

Micki
mailto:mic...@co...

Re: [Phpwiki-talk] TOC headings - unique ID

[Micki K. <mic...@co...>]

Whit:

I'd use IncludePage (for static includes) or IncludeSiteMap (for 
dynamic includes based on WikiBadges), and (HACK ALERT) change the 
'transclusion-title' in the stylesheet to an h1 heading. Then, insert 
a TOC and lock the main page. UnfoldSubPages should work similarly to 
IncludePage, with a defined list, not quite 'static' but not as 
dynamic as a 'WikiBadges' approach like IncludeSiteMap.

Should give you a large chunk of the behavior for which you are 
searching - clickable headers that point back to the base pages, a 
locked 'book' page containing the includes, and a TOC that 
accommodates the huperlinking.

What do you think? Am I missing something fundamental?
Micki

At 8:07 PM -0800 3/6/04, php...@li... wrote:
>Message: 1
>Date: Sat, 6 Mar 2004 13:16:57 -0500
>From: Whit Blauvelt <wh...@tr...>
>To: php...@li...
>Subject: Re: [Phpwiki-talk] TOC headings - unique ID
>
>On Fri, Mar 05, 2004 at 08:33:30PM -0500, Micki Kaufman wrote:
>>  Absolutely - a unique ID in each anchor and href is critical, to
>>  differentiate form from function...
>
>While it's simple enough to add something either time-based on a fine-enough
>scale or sufficiently random in the TOC context, I've been puzzling on how
>to borrow the functionality being built for the TOC context to get the
>following effect: having each heading accompanied by an auto-generated link
>to a subpage (somewhat like the calendar plugin). The notion is that the
>main page remains owned by - and only editable by - the primary author(s),
>but the subpages are there for open comments on each of the subsections
>(with an option to display comments and sections side-by-side).
>
>The stumbling block with doing this is that, while the unique ID scheme that
>will be used in the TOC most probably will generate the IDs on-the-fly each
>time the page is generated, the unique ID scheme required for what I'm after
>would have to be stable so the subpage links could be consistent. To have it
>be stable all I can think of is to write the IDs into the page body on the
>first pass through - which seems a bit un-wiki-like and noisey. Is there a
>solution I'm overlooking?
>
>Thanks,
>Whit


-- 

Micki
mailto:mic...@co...

Re: [Phpwiki-talk] regex modification

[Micki K. <mic...@co...>]

Worked like a charm, and did no harm!

Can't ask for more than that. Thanks John!

Reini, Steve, Jeff, et. al: any idea whether this patch is 
appropriate to commit to the code base? Any disadvantages to this mod 
from others?

Micki

>Message: 3
>Date: Wed, 3 Mar 2004 22:44:26 +0000
>To: php...@li...
>From: John Kershaw <li...@ke...>
>Subject: Re: [Phpwiki-talk] regex modification
>
>At 3:17 pm -0500 3/3/04, Micki Kaufman wrote:
>  >We need a run of capital letters to be treated as a word, EXCEPT the
>  >last of the capital letters... like this:
>  >
>  >ABCProductInfo  should become  ABC Product Info
>  >
>  >right now, it becomes ABCProduct Info
>
>Caveat: I'm still using 1.3.2. Your mileage may vary.
>
>I wanted the same thing for pages like this:
>http://www.through-the-maze.org.uk/pages/BTCVConservationVolunteers
>
>and made the following changes to my lib/stdlib.php file:
>
>/*
>          // This splits the single-letter words 'I' and 'A' from any
>following capitalized words.
>          $RE[] = '/(?: |^)([AI])([[:upper:]])/';
>*/
>          // Space before last capital in a run of caps: PCCMeeting ->
>PCC Meeting
>          $RE[] = '/([[:upper:]]+)([[:upper:]][[:lower:]])/';
>
>ie I commented out the first one and added in the second one.
>
>John.


-- 

Micki
mailto:mic...@co...

Re: [Phpwiki-talk] TOC headings - unique ID

[Whit B. <wh...@tr...>]

On Fri, Mar 05, 2004 at 08:33:30PM -0500, Micki Kaufman wrote:
> Absolutely - a unique ID in each anchor and href is critical, to 
> differentiate form from function...

While it's simple enough to add something either time-based on a fine-enough
scale or sufficiently random in the TOC context, I've been puzzling on how
to borrow the functionality being built for the TOC context to get the
following effect: having each heading accompanied by an auto-generated link
to a subpage (somewhat like the calendar plugin). The notion is that the
main page remains owned by - and only editable by - the primary author(s),
but the subpages are there for open comments on each of the subsections
(with an option to display comments and sections side-by-side).

The stumbling block with doing this is that, while the unique ID scheme that
will be used in the TOC most probably will generate the IDs on-the-fly each
time the page is generated, the unique ID scheme required for what I'm after
would have to be stable so the subpage links could be consistent. To have it
be stable all I can think of is to write the IDs into the page body on the
first pass through - which seems a bit un-wiki-like and noisey. Is there a
solution I'm overlooking?

Thanks,
Whit

[Phpwiki-talk] Sitemap or backlinks?

[Electrawn <ele...@el...>]

Trying to produce behavior of just listing all subpages inside the main =
page
rather than unfold them all

Like: Verb List/A
      Verb List/B
      Verb List/Special  =20

Etc

Unfoldsubpages, sitemap, backlinks, likepages are ways to do it it =
seems.
Doc is poor and is giving me a headache, so I toss it to the list :/

-Jtp
     =20

I've stopped 7,449 spam messages. You can too!
One month FREE spam protection at www.cloudmark.com

[Phpwiki-talk] TOC headings - unique ID

[Micki K. <mic...@co...>]

Absolutely - a unique ID in each anchor and href is critical, to 
differentiate form from function...

Rocking Job, Folks!

Micki

At 8:05 PM -0800 3/4/04, php...@li... wrote:
>From: Joby Walker <joby@u.washington.edu>
>To: Whit Blauvelt <wh...@tr...>
>CC: Reini Urban <ru...@x-...>, php...@li...
>Subject: Re: [Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings)
>
>Nice catch.
>
>This could be resolved by appending an (invisible) index number to every TOC
>link/anchor.
>
>jbw
>
>Whit Blauvelt wrote:
>
>>  On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote:
>>
>>>I fixed now CreateToc to link to the headers and
>>>optionally link back to the TOC.
>>
>>
>>  Nice addition.
>>
>>  One thing the current scheme misses is when two different headings have the
>>  same subheading. So if you have a page with sections like:
>>
>>    Category One
>>      Examples
>>
>>    Categore Two
>>      Examples
>>
>>  - the two Examples subcategories try to set up links to the headers like:
>>
>>  <li><a href="InPage#Categoryx20.1" class="named-wiki" 
>>title="InPage">Category 1</a></li>
>>  <li><a href="InPage#Examples" class="named-wiki" 
>>title="InPage">Examples</a></li>
>>  <li><a href="InPage#Categoryx20.2" class="named-wiki" 
>>title="InPage">Category 2</a></li>
>>  <li><a href="InPage#Examples" class="named-wiki" 
>>title="InPage">Examples</a></li>
>>
>>  which both assigns the same link to two locations, but throws an error:
>>
>>  PHP Warnings
>>
>>  lib/plugin/CreateToc.php (In template 'browse') (In template 
>>'savepage') (In template 'body') (In template 'html'):77: 
>>Notice[1024]: Heading <h3> Examples </h3> not found
>>
>>  Whit


-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] WikiText++ ?

[Dan F <dfr...@cs...>]

I'd like to be able to put together some Wiki-ish text in a plug-in, 
pass it to something (class or function), and have it render as the 
output of the plug-in. So, for example, in the run method of FooPlugin.php:

  $str = <<<EOD
  This is *bold*.
  Show [ a backlinks button without homepage | 
phpwiki:ResearchPaper?action=BackLinks&exclude=HomePage ]
  <?plugin-form FuzzyPages ?>
  Here is a WikiWordLink.
  EOD;

  return new WikiText($str);


Now this almost works, but the active elements (buttons, plug-ins, 
wiki-links) don't get rendered as active buttons or plug-ins. They 
render as plaintext.

I feel as if this should exist, because some entity has to do it while 
displaying a page.

Suggestions?

Dan

Re: [Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings)

[Reini U. <ru...@x-...>]

Joby Walker schrieb:
> Nice catch.
> This could be resolved by appending an (invisible) index number to every 
> TOC link/anchor.

yes, CreateToc is not quite stable enough.
I'll have more time on sunday for this and more.

> Whit Blauvelt wrote:
>> On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote:
>>
>>> I fixed now CreateToc to link to the headers and
>>> optionally link back to the TOC.
>>
>>
>>
>> Nice addition.
>>
>> One thing the current scheme misses is when two different headings 
>> have the
>> same subheading. So if you have a page with sections like:
>>
>>   Category One
>>     Examples
>>
>>   Categore Two
>>     Examples
>>
>> - the two Examples subcategories try to set up links to the headers like:
>>
>> <li><a href="InPage#Categoryx20.1" class="named-wiki" 
>> title="InPage">Category 1</a></li>
>> <li><a href="InPage#Examples" class="named-wiki" 
>> title="InPage">Examples</a></li>
>> <li><a href="InPage#Categoryx20.2" class="named-wiki" 
>> title="InPage">Category 2</a></li>
>> <li><a href="InPage#Examples" class="named-wiki" 
>> title="InPage">Examples</a></li>
>>
>> which both assigns the same link to two locations, but throws an error:
>>
>> PHP Warnings
>>
>> lib/plugin/CreateToc.php (In template 'browse') (In template 
>> 'savepage') (In template 'body') (In template 'html'):77: 
>> Notice[1024]: Heading <h3> Examples </h3> not found
>>
>> Whit
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: IBM Linux Tutorials
>> Free Linux tutorial presented by Daniel Robbins, President and CEO of
>> GenToo technologies. Learn everything from fundamentals to system
>> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>> _______________________________________________
>> Phpwiki-talk mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
> 
> 


-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

[Phpwiki-talk] um....

[Chris L. <cla...@hb...>]

not sure you want to serve this up:


http://chattyfig.figleaf.com/flashcoders-wiki/index.php?XMLNitro

doing some research on XMLNitro when I found that.

[Phpwiki-talk] WikiBlog in nightly doesn't always save comment right

[Whit B. <wh...@tr...>]

Pressing "Add a Comment" ends up working like an edit button for the page -
brings up the page being commented on in editing mode rather than adding the
comment anywhere. 

This is with the main page (InPage) being commented having as content:

<?plugin WikiBlog mode=add?>

[/Comments]

and /Comments having:

<?plugin WikiBlog page=InPage mode=show?>

- which is what is suggested in the plugin:

 * To have comments show up on a separate page:
 * On TopPage, use
 *   <?plugin WikiBlog mode=add?>
 * Create TopPage/Comments with:
 *   <?plugin WikiBlog page=TopPage mode=show?>

Playing with it some more, sometimes it does work correctly, sometimes it
doesn't. Can't pin down what's different between the two. Doing without the
separate /Comments page seems to not make the difference.

Whit

Re: [Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings)

[Joby W. <joby@u.washington.edu>]

Nice catch.

This could be resolved by appending an (invisible) index number to every TOC 
link/anchor.

jbw

Whit Blauvelt wrote:

> On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote:
> 
>>I fixed now CreateToc to link to the headers and
>>optionally link back to the TOC.
> 
> 
> Nice addition.
> 
> One thing the current scheme misses is when two different headings have the
> same subheading. So if you have a page with sections like:
> 
>   Category One
>     Examples
> 
>   Categore Two
>     Examples
> 
> - the two Examples subcategories try to set up links to the headers like:
> 
> <li><a href="InPage#Categoryx20.1" class="named-wiki" title="InPage">Category 1</a></li>
> <li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li>
> <li><a href="InPage#Categoryx20.2" class="named-wiki" title="InPage">Category 2</a></li>
> <li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li>
> 
> which both assigns the same link to two locations, but throws an error:
> 
> PHP Warnings
> 
> lib/plugin/CreateToc.php (In template 'browse') (In template 'savepage') (In template 'body') (In template 'html'):77: Notice[1024]: Heading <h3> Examples </h3> not found
> 
> Whit
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Phpwiki-talk mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

Re: [Phpwiki-talk] Re: feature idea - TOC (de facto IncludeHeadings)

[Whit B. <wh...@tr...>]

On Tue, Mar 02, 2004 at 07:24:12PM +0100, Reini Urban wrote:
> I fixed now CreateToc to link to the headers and
> optionally link back to the TOC.

Nice addition.

One thing the current scheme misses is when two different headings have the
same subheading. So if you have a page with sections like:

  Category One
    Examples

  Categore Two
    Examples

- the two Examples subcategories try to set up links to the headers like:

<li><a href="InPage#Categoryx20.1" class="named-wiki" title="InPage">Category 1</a></li>
<li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li>
<li><a href="InPage#Categoryx20.2" class="named-wiki" title="InPage">Category 2</a></li>
<li><a href="InPage#Examples" class="named-wiki" title="InPage">Examples</a></li>

which both assigns the same link to two locations, but throws an error:

PHP Warnings

lib/plugin/CreateToc.php (In template 'browse') (In template 'savepage') (In template 'body') (In template 'html'):77: Notice[1024]: Heading <h3> Examples </h3> not found

Whit

Re: [Phpwiki-talk] Doxygen docs on PhpWiki

[Whit B. <wh...@tr...>]

On Thu, Mar 04, 2004 at 12:42:36AM -0500, Steve Wainstead wrote:

> http://phpwiki.sf.net/docs/

Nice. Thanks.

Whit

RE : [Phpwiki-talk] Doxygen docs on PhpWiki

[<jw...@fi...>]

Hello,

Doxygen has been our choice in my company to document the source code of =
our
php project. I leads to usable documentation.

One cool thing is also the windows doxygen parser : you can localy =
create
documentation out of a directory without having to install a whole lot =
of
scripts on the server.

It would be a great step forward for phpwiki I think.

Please post on the list when the choice for a documentation standard is
made.

J=E9r=F4me

-----Message d'origine-----
De=A0: php...@li...
[mailto:php...@li...] De la part de Steve
Wainstead
Envoy=E9=A0: jeudi 4 mars 2004 06:43
=C0=A0: 'php...@li...'
Objet=A0: [Phpwiki-talk] Doxygen docs on PhpWiki

I've been playing with Doxygen at work, and thought I'd try it on the=20
project to see what kind of documentation it makes. Drupal has some=20
really nice documentation made with Doxygen. Let me know what you=20
think:

http://phpwiki.sf.net/docs/

~swain



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Phpwiki-talk mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwiki-talk

[Phpwiki-talk] Doxygen docs on PhpWiki

[Steve W. <sw...@pa...>]

I've been playing with Doxygen at work, and thought I'd try it on the 
project to see what kind of documentation it makes. Drupal has some 
really nice documentation made with Doxygen. Let me know what you 
think:

http://phpwiki.sf.net/docs/

~swain

Re: [Phpwiki-talk] regex modification

[John K. <li...@ke...>]

At 3:17 pm -0500 3/3/04, Micki Kaufman wrote:
>We need a run of capital letters to be treated as a word, EXCEPT the 
>last of the capital letters... like this:
>
>ABCProductInfo  should become  ABC Product Info
>
>right now, it becomes ABCProduct Info

Caveat: I'm still using 1.3.2. Your mileage may vary.

I wanted the same thing for pages like this:
http://www.through-the-maze.org.uk/pages/BTCVConservationVolunteers

and made the following changes to my lib/stdlib.php file:

/*
         // This splits the single-letter words 'I' and 'A' from any 
following capitalized words.
         $RE[] = '/(?: |^)([AI])([[:upper:]])/';
*/
         // Space before last capital in a run of caps: PCCMeeting -> 
PCC Meeting
         $RE[] = '/([[:upper:]]+)([[:upper:]][[:lower:]])/';

ie I commented out the first one and added in the second one.

John.

[Phpwiki-talk] regex modification

[Micki K. <mic...@co...>]

Hi folks!

Need to make a modification to the WikiName regex.

We need a run of capital letters to be treated as a word, EXCEPT the 
last of the capital letters... like this:

ABCProductInfo  should become  ABC Product Info

right now, it becomes ABCProduct Info

Thanks for any insight the gurus on this list can offer.

Micki
-- 

Micki
mailto:mic...@co...

[Phpwiki-talk] Last-modified header for ZIP Dump

[Oliver B. <ob...@de...>]

Hello All,

for automated backups via Wget etc., wouldn't it be nice to have a 
"Last-modified" header with either the date of the last modification 
of the database or the last page edit?

Otherwise Wget will download the ZIP Dump always even if there was no 
change...

Oliver