Upgrading from old versions
The Wiki::Toolkit database schema changed some time around 0.69/0.70, so if you're upgrading from versions earlier than this, you'll need to upgrade your database too. The way to do this is to run wiki-toolkit-setupdb from the new distribution and point it at your existing database; it will upgrade it for you. (As with any database munging, it's wise to take a backup first, just in case.)
If you receive this message:
Search::InvertedIndex::add_index() - Unable to locate the existing 'ie_first_index_enum' value. Database may be corrupt. at /usr/share/perl5/CGI/Wiki/Search/SII.pm line 127
Delete the index files (/var/lib/openguides/indexes/default/ in the Debian packages) and run examples/reindex.pl from the distribution (/usr/share/doc/openguides/examples/reindex.pl in the Debian packages) in the same directory as wiki.conf.
This will rebuild the indexes from scratch. Search::InvertedIndex? indexes do this occasionally, and it is recommended that you use Plucene instead.
Distance calculations and ellipsoids
wiki.conf contains an option to use British National Grid, Irish National Grid or a Universal Transverse Mercator (UTM) for distance calculations and storage of coordinates. UTM is recommended for sites covering areas outside Britain and Ireland.
A further option, if using UTM, is the ellipsoid to use. An elipsoid estimates the (non-spherical) shape of the globe and is used to calculate distances while taking the curvature of the earth into account. See: http://www.vterrain.org/Projections/ Kake gives an explanation in this post.
The ellipsoid you use can be any of those mentioned in the readme for GEO::Coordinates::UTM. International is recommended.
In practical terms, you don't need to really worry about this overly. This list post includes some calculations that show the error between different UTM ellipsoids isn't great enough to cause real problems.
This presentation explains the issues, and the Perl modules in use, for you: Ivor's Geo Talk Slides
<i>Can someone explain what a locale is meant to do in Openguides - what sort of area is it meant to cover. Specifically I have seen a couple of entries with Locale = "Southwark" that I don't consider to be within Southwark. I assume that it is not meant to cover the London Borough of that name.</i>
For me, a locale is the answer to the question "where is foo?" So for example if someone said "Where is Manna?" I'd say "Primrose Hill", and so that's its locale. If someone said "Where is the Crabtree Tavern?" I'd answer "Well, it's sort of on the border of Hammersmith and Fulham", so it's in both locales.
If something's down as being in Southwark but you know Southwark well and you disagree, then you're probably right and the locale was added by someone who doesn't know the area very well - sort of the "South of the river is all the same place" syndrome.
<i>I'm wondering if anyone has developed, or is working on, an authentication module for OpenGuide?.</i>
Put something like this in .htaccess in the same directory as the wiki.cgi:
<Limit POST> Order deny,allow Deny from all AuthType Basic AuthName "Username: " AuthUserFile /home/kake/.htpasswd-openguides require valid-user satisfy any </Limit>
All the edit forms are POST. I think there is a POST search form as well, but this really needs changing to GET - there's no reason for search results not to be linkable to, and a search doesn't change data. Um, hack that in your version pending a fix in the distro. I wouldn't normally recommend that, but you seem to be in dire straits, and it's a bugfix which will go in at some point.
(Dom suggests instead limiting with
They won't get the auth request until after they've submitted the edit form though. I think (but have not tested this) that you can get around this by making a little login.cgi that's protected by the same htpasswd file and adding a link to this somewhere.
That really is a bit of a hack, but it might do.