Hmmm. If you know PHP, look at the section in portal/htdocs/wiki/InfoBody.ihtml labeled '/* print links from it which lead nowhere */'. You can put that in a loop over all topic names to get every (the list will probably contain duplicates) undefined WikiWords. An all-topics loop is used in portal/export.php3, under the line 'if( $response == "[all]" )'. You'll have to do a little variable renaming, if you copy & paste. You'll also need to fetch `linksfrom' via the wikiQuery for the $linksfrom variable used later in the InfoBody.ihtml fragment.
If you don't know PHP, let me know; I'll try to get to it tonight.
-jQuinn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This feature will be in the next version of PhpWiki (http://sourceforge.net/pm/task.php?func=detailtask&project_task_id=25840&group_id=6121&group_project_id=7691).
thanks for asking!
~swain
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can get by with only a handful of commands with CVS. Part of the barrier is learning how a version control system works; and once you've learned one, you've pretty much learned them all since the concepts are the same. I was dismayed by this when I finished college and went to work in the real world; versioning systems are absolutely essential to *any* software project. If one is not in use, there will certainly be disaster.
Sourceforge has a few simple documents on setting up and using CVS and there are a lot of good web sites to help out:
I am working with a wiki and it would be valuable for me to find all the undefined wiki words and put them in a list.
What would I have to do in order to find all of these wikiwords that have not yet been defined?
Hmmm. If you know PHP, look at the section in portal/htdocs/wiki/InfoBody.ihtml labeled '/* print links from it which lead nowhere */'. You can put that in a loop over all topic names to get every (the list will probably contain duplicates) undefined WikiWords. An all-topics loop is used in portal/export.php3, under the line 'if( $response == "[all]" )'. You'll have to do a little variable renaming, if you copy & paste. You'll also need to fetch `linksfrom' via the wikiQuery for the $linksfrom variable used later in the InfoBody.ihtml fragment.
If you don't know PHP, let me know; I'll try to get to it tonight.
-jQuinn
Oh, sh!t. I misread the email; the above advice is for sfWiki, not phpwiki.
Sorry!! My apologies.
-jQuinn
This feature will be in the next version of PhpWiki (http://sourceforge.net/pm/task.php?func=detailtask&project_task_id=25840&group_id=6121&group_project_id=7691).
thanks for asking!
~swain
Take a look at
http://www.benbun.co.uk/wiki/index.php?pagename=MissingPages
is this the kind oif thing you are refering to ?.
Yes, that's exactly what we're after here. Did you use the wikilinks table to calculate this page?
~swain
Yes I did, if you want the code let me know.
I would help with the PHPWiki development but I don't know anything about CVS.
You can get by with only a handful of commands with CVS. Part of the barrier is learning how a version control system works; and once you've learned one, you've pretty much learned them all since the concepts are the same. I was dismayed by this when I finished college and went to work in the real world; versioning systems are absolutely essential to *any* software project. If one is not in use, there will certainly be disaster.
Sourceforge has a few simple documents on setting up and using CVS and there are a lot of good web sites to help out:
http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/
http://www.delorie.com/gnu/docs/cvs/cvs_toc.html
http://cvsbook.red-bean.com/
In the meantime you could send me files as attachments, if you wouldn't mind.
cheers!
~swain
~swain