wiki functionality in DITA.xml.org

[Greg Rundlett <greg.rundlett@oasis-open.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Carol,

I worked on the code for dita.xml.org enabling wiki functionality.
When you edit any 'collaborative story' content, you can use double
bracket syntax to create new 'collaborative story' content
automatically.  In short, DITA.xml.org has wiki support.

I setup submission guidelines in
http://dita.xml.org/admin/node/configure/types/storycollab (that you
may want to wordsmith), and set the default permissions such that
users can normally just skip right over them and enter the content.
The permission setup is now enhanced through the "node privacy by
role" module giving authors extra control over who can edit their
content.  The system is configured so that regular authenticated users
can contribute wiki pages.  (Did you want anonymous users to be able
to add wiki pages?)  Editors can override wiki articles (by locking them).

Shutting off camelcase is not a feature that is exposed in the 4.6
code.  So, I looked at the 4.7 code but there are a large number of
changes between 4.6 and 4.7.  So, I ended up just writing a hack to
intentionally turn off CamelCase words like McDonalds.

I will be working on Taxonomy the next chance I get (next Tuesday?)

The rest of this message is more technical (for my own reference if
nothing else).  Read on if interested.

I discovered that the site was actually running the incorrect version
of freelinking (installed by Moshe).  He unwittingly installed the 4.5
version rather than the 4.6 version because 4.5 was labelled
incorrectly as "the latest" on the Drupal site.  However, after
assessing the changes or conflicts that might have been introduced,
there were actually no significant changes in the freelinking code
between versions 4.5 and 4.6 which  would have caused it to work
improperly.  Put another way, 4.6 only included a couple bug-fixes and
some additional help content, but no major code changes.

The issues I found were:

~   1. the wrong version of freelinking was installed
~   2. the node_privacy_by_role module was not installed,
~   3. the url_filter module (optional) was not installed.
~   4. the configuration needed to account for these modules
~   5. permissions on the files needed to be set

To install and configure, I basically had to enable new modules
first.  The modules are enabled at http://dita.xml.org/admin/modules.
Because the "node privacy by role" module has special database
requirements and Drupal 4.6 does not have module
activation/deactivation event trigger hooks, there is an extra
settings page to run the appropriate database scripts (through a
simple form) http://dita.xml.org/admin/settings/node_privacy_byrole

Next, you have to configure settings for each module. The freelinking
module settings are set at http://dita.xml.org/admin/settings/freelinking

Then, I administered the filters.  The filters are administered at
http://dita.xml.org/admin/filters/3/list

I logged onto the webserver machine and reset file ownership at the
command-line so that all contents of the module directory on disk are
owned by the webserver user to avoid any write or execute conflicts.


I also ran the cron.php script to update the search index (it was
already 93% indexed by you).  It failed to parse the RSS feed  "/Cover
Pages/: / 110 Connection timed out" / You can access this settings
page at http://dita.xml.org/admin/settings/search

I will ask Steve to add cron.php to the system cron facility so you
never have to do it again...it will happen automatically every day at
1am EST.

- --
Gregory S. Rundlett
Manager
Technology Services
OASIS
"Advancing E-Business Standards Since 1993"
http://www.oasis-open.org
(978) 667-5115 x 205
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD/AuIzdIuXNTVHCgRAmbdAJ9wdz0QUAV2txv3oejy7HuuQCPMOwCgh3ac
elnCTFFMmSrFYo2gs9F+1qA=
=qBLA
-----END PGP SIGNATURE-----