<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7233.28">
<TITLE>RE: [pmwiki-users] Handling of PageNotFound situations - also automatic Category pages</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2> Well, this will not really help for misspellers,<BR>
they will still click on the link won't they? Then<BR>
what?<BR>
<BR>
If we jump forward to the idea discussed being<BR>
discussed the blog thread, we are talking about not<BR>
just creating the Category page, but using it as a<BR>
trail page and appending new pages in the Category<BR>
to it automatically. <BR>
<BR>
After thinking about this scenario a bit, I asked<BR>
myself: what happens when a user edits the Category<BR>
page Foo and deletes the entry for page Group.A which<BR>
is in the Category Foo? Is page Group.A still in<BR>
Category Foo? What if a user adds page Group.B to the<BR>
trail on Category.Foo page, but Group.B does not have<BR>
a Category Foo link on it? Is Group.B in the Category<BR>
or not?<BR>
<BR>
Now I am a little uncomfortable with the idea that<BR>
one page can update another page, but if we go so far<BR>
as to make a link to a Category Foo from Group.A<BR>
automatically put an entry on the Category.Foo page,<BR>
why not go all the way and make an entry Category.Foo<BR>
page, say Group.B put itself as a link to the Category<BR>
page on Group.B page? Go full ahead and create a<BR>
"symbiotic" update between the two groups of pages,<BR>
deletes included, pages in Categories and entries on<BR>
Category pages would automatically stay in sync. This<BR>
would provide a complete Category solution where one<BR>
never has to update data in more than one place but it<BR>
CAN be done from either place, where ever one happens<BR>
to find oneself!<BR>
<BR>
Scary, and more details such as where appends on<BR>
pages would go would need to be worked out, but it<BR>
sure would be usefull,<BR>
<BR>
-Martin<BR>
<BR>
-----Original Message-----<BR>
From: pmwiki-users-bounces@pmichaud.com on behalf of H. Fox<BR>
Sent: Wed 1/11/2006 9:46 PM<BR>
To: Hans<BR>
Cc: Pmwiki-users@pmichaud.com<BR>
Subject: Re: [pmwiki-users] Handling of PageNotFound situations<BR>
<BR>
On 1/10/06, Hans <design@softflow.co.uk> wrote:<BR>
> 1. Creating a new category page by creating a link alone. Clicking the<BR>
> ne wcategory link will take you to the newly created and saved<BR>
> category page, saving the step of having to save it.<BR>
<BR>
I like this idea, except the category page should be created on the<BR>
first visit, not by the mere act of creating a link.<BR>
<BR>
At minimum there should be some kind of limit to the number of new<BR>
blank pages that can be created by saving a page with links to<BR>
non-existent category pages. Otherwise pasting in 200 category links<BR>
creates 200 pages...<BR>
<BR>
Requiring an author to click the link doesn't seem like too much to<BR>
ask, especially in an open-wiki environment. Save the page => See the<BR>
' ? ' => Click... Done.<BR>
<BR>
Remember too, some people are [[!mispellers]]. :-)<BR>
<BR>
Hagan<BR>
<BR>
_______________________________________________<BR>
pmwiki-users mailing list<BR>
pmwiki-users@pmichaud.com<BR>
<A HREF="http://host.pmichaud.com/mailman/listinfo/pmwiki-users">http://host.pmichaud.com/mailman/listinfo/pmwiki-users</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>