phpwiki-talk

[Phpwiki-talk] rollout of 1.1.6

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

I'd like to roll out 1.1.6 soon, and put it up live on Sourceforge. Any
comments? I think the theme-ability is a big thing and worthy of a
freshmeat posting alone.

People keep trying to use new features on sourceforge (that's a 1.03 wiki)
and I'd like to give them the ability to try things like the new linking
scheme and such.

sw

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] rollout of 1.1.6

[Arno H. <aho...@in...>]

Hi,

 > I'd like to roll out 1.1.6 soon, and put it up live on Sourceforge. Any
 > comments? I think the theme-ability is a big thing and worthy of a
 > freshmeat posting alone.

I'd like to see the following going into 1.1.6
(this shouldn't be too much work and can be done within two, three days):

- incorporate pageviewer.php3 into the regular wiki setup (via placeholder)
  e.g. at the bottom of the page: (last updated 1 Mar 2000 [more info])
  the "more info" link leads to the pageviewer of that particular page
  (placeholder e.g. ###INFOURL###?###PAGEURL###)
  (note: pageviewer itself should use the MESSAGE template)

- add the ability to dump the contents of a wiki into files like in /pgsrc
- add the ability to dump from 1.0.x and 1.1.y wikis to 1.1.6 format.
  (in both cases the reload could be done by simply putting the result 
  into /pgsrc and starting over again. In 1.1.6, we may or may not
  lose additional information like version number, last modified, ...

- resolve the LostUpdate-bug when editing a copy of the page where
  (version_wiki - version_copy) != 1

- resolve the EditCopy link appearance -- maybe we don't need the
  ###IFCOPY### placeholder at all - I don't like that placeholder.

- implement the new db schema in mySQL (only tables wiki & archive).
  (my task)


1.1.5 was announced on freshmeat 10 days ago.
I guess it doesn't hurt if 1.1.6 takes some more days.

/Arno

Re: [Phpwiki-talk] rollout of 1.1.6

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

On Tue, 20 Jun 2000, Arno Hollosi wrote:

> - incorporate pageviewer.php3 into the regular wiki setup (via placeholder)
>   e.g. at the bottom of the page: (last updated 1 Mar 2000 [more info])
>   the "more info" link leads to the pageviewer of that particular page
>   (placeholder e.g. ###INFOURL###?###PAGEURL###)
>   (note: pageviewer itself should use the MESSAGE template)

Interesting; when I started writing pageviewer.php3 I only wanted a
debugging tool for developers... I didn't think about making it available
to end users.

It should be renamed then to wiki_pagestructure.php3 or something similar
for consistency.

> 
> - add the ability to dump the contents of a wiki into files like in /pgsrc
> - add the ability to dump from 1.0.x and 1.1.y wikis to 1.1.6 format.
>   (in both cases the reload could be done by simply putting the result 
>   into /pgsrc and starting over again. In 1.1.6, we may or may not
>   lose additional information like version number, last modified, ...

Yes, was thinking about this last night. The algorithm would be:

* in a DBM-based Wiki, call dump.php3.
* Choose between saving the page source only (like the files in pgsrc/),
or as serialized data structures (preserving all page information).
* Dump the pages
* Edit wiki_config.php3, switching databases
* call load.php3 to load pages; choose whether they are page source or
serialized hashes in files
* load the database, checking for each file whether it has all 8
attributes (lastmodified, refs, created, version, etc) and add defaults if
they are not there
* go have coffee and relax


> - resolve the LostUpdate-bug when editing a copy of the page where
>   (version_wiki - version_copy) != 1

ok

> - resolve the EditCopy link appearance -- maybe we don't need the
>   ###IFCOPY### placeholder at all - I don't like that placeholder.

ok, this is in TODO

> - implement the new db schema in mySQL (only tables wiki & archive).
>   (my task)

Question: (I think I already emailed you on this) what do you think about
making the schema for the ARCHIVE table the same as for WIKI? I think this
might save us some code writing since InsertPage and RetrievePage can work
on both tables.

> 
> 1.1.5 was announced on freshmeat 10 days ago.
> I guess it doesn't hurt if 1.1.6 takes some more days.

Seems longer ago than that! :-)

sw


...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] rollout of 1.1.6

[Arno H. <aho...@in...>]

 > > - add the ability to dump the contents of a wiki into files like in /pgsrc
 > > - add the ability to dump from 1.0.x and 1.1.y wikis to 1.1.6 format.

 > * in a DBM-based Wiki, call dump.php3.

can be in a mysql or pgsql wiki as well - I don't see any problems
here. Just call RetreivePage and store it in a file.

 > * Choose between saving the page source only (like the files in pgsrc/),
 > or as serialized data structures (preserving all page information).

How about having the page source in files like /pgsrc and one additional file
that contains serialized data structures (in the 1.1.6 format)?

 > * call load.php3 to load pages; choose whether they are page source or
 > serialized hashes in files

No need to create a new file - just instruct wiki_setupwiki.php3 to
look for that additonal file and read in the serialized data and fill
the newly created structures not with defaults but with values from
that file.

 > * load the database, checking for each file whether it has all 8
 > attributes (lastmodified, refs, created, version, etc) and add defaults if
 > they are not there

 > * go have coffee and relax

Nice idea - we should add this to the README :o)

On a side note: the file names have to be escaped in some way.
The new naming scheme allows arbitrary characters and some
filesystems don't allow that. Know of any good escaping scheme,
short of naming the files 1,2,3,4,5,6, ....
(I thought of something like using a special character, say ','
and escape any odd characters with their decimal value, e.g.
the name "you \\don't// hear, do you?" would be saved as
"you ,92,,92,don,39,t,47,,47, hear,44, do you,63,"
I guess you can see why this might not be a good solution)

 > what do you think about
 > making the schema for the ARCHIVE table the same as for WIKI?

No problem. As you say: it saves code. It's always better to
have easy manageable code.

/Arno

Re: [Phpwiki-talk] rollout of 1.1.6

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

On Wed, 21 Jun 2000, Arno Hollosi wrote:

>  > * in a DBM-based Wiki, call dump.php3.
> 
> can be in a mysql or pgsql wiki as well - I don't see any problems

Yes, this was just an example. It would port any database to any database.

I think in the long run it would be used the most for DBM -> RDBMS though
(as people upgrade their installations);  DBM files are a great way to
start off, and for small Wikis they are sufficient, but as traffic rises
you really want the stability and efficiency of a SQL database. 

> How about having the page source in files like /pgsrc and one additional file
> that contains serialized data structures (in the 1.1.6 format)?

That would be even simpler... I'll only have to write one dump.php3 file
:-)

> On a side note: the file names have to be escaped in some way.
> The new naming scheme allows arbitrary characters and some
> filesystems don't allow that. Know of any good escaping scheme,
> short of naming the files 1,2,3,4,5,6, ....

Would rawurlencode() work?

> (I thought of something like using a special character, say ','
> and escape any odd characters with their decimal value, e.g.
> the name "you \\don't// hear, do you?" would be saved as
> "you ,92,,92,don,39,t,47,,47, hear,44, do you,63,"
> I guess you can see why this might not be a good solution)

There's probably no clean solution to this. Anyways people should
StickWithTheNamingConvention :-)

sw

...............................ooo0000ooo.................................
   Hear FM quality freeform radio through the Internet: http://wcsb.org/
                     home page: www.wcsb.org/~swain 

Re: [Phpwiki-talk] rollout of 1.1.6

[Arno H. <aho...@in...>]

Hi again,

ok, I just fixed some more bugs.

- FullSearch now works again (updated to new datastructure)
  note: might not work with pgsql - please check

- fixed those two bugs regarding EditCopy link and EditCopy version
  control.

Together with my previous changes I've included what I wanted.
You may roll out 1.1.6 any time you like to.

Could you please proof-read the README for templates?

Thanks
/Arno

ps. going to bed now (2am :o) - I'm leaving for a long weekend.
I will be able to check my email, but can't do any coding or verification.