OpenGuides-Dev January 2005

openguides-dev@lists.openguides.org

12 participants
26 discussions

[OpenGuides-Dev] Re: [OpenGuides-London] Validating categories
by IvorW 09 Jan '05

09 Jan '05

Cross-posted from OG London to OG Dev ----- Original Message ----- From: "Andrew Black" <andrew3(a)black1.org.uk> To: "Discussion of the Open Guide to London." <openguides-london(a)openguides.org> Sent: 09 January 2005 09:57 Subject: [OpenGuides-London] Validating categories > > Thanks Kake for deleting the categories that were duplicates. > > I would find it useful if the edit screen gave you a chance to view > existing categories. This would help encourage reuse of existing ones > rather than create duplicates (library/ies or Wi-Fi / WiFi ). > On a similar topic. I would like to see "*Comment about your changes:" > as a mandatory field (unless you have selected minor tidying). It is > terribly easy to save a change forgetting to add the comment.* I did moot the idea of a select dropdown and add/remove buttons for the categories and locales, on the edit page. These are the kind of thinks that look and work better in (Java|Ecma)script though, which might be bad for browser compatibility. What do others think?

2 1

[OpenGuides-Dev] Wishlist: custom metadata fields
by Earle Martin 05 Jan '05

05 Jan '05

https://rt.cpan.org/NoAuth/Bug.html?id=9380 Thoughts? -- Earle Martin http://downlode.org/ http://purl.oclc.org/net/earlemartin/

4 3

RE: [OpenGuides-Dev] Dealing with wiki spam
by IvorW 04 Jan '05

04 Jan '05

Just having a braindump on this hot topic. 1. We should look to improving the user login side of OG/CW. Currently, you just go into the "preferences" page and set your ID to whatever you want. If we have a password associated with the ID, this will hopefully prevent impersonation and other suchlike abuses. OK so the form may be sending the password in clear text, but the paranoid could always wrap the login page in https. The authenticated values result in a session cookie, much as happens with the preferences at present. It's probably best if the cookie does not hold much - just a session ID: index into a session table with a foreign key on a user table to retrieve preferences server side. Secondly, the first password should be emailed to a valid email address. This also enables use of a "forgotten password" link or button on the login page. An alternative to this would be manual "vouching" for new user requests. More work for the admins, but less work for the developers possibly. 2. Ideally we want OpenGuides to stay wiki, i.e. allow anonymous contributors. But, there's no reason why it needs to be a WorldWideWiki, open to Chinese and Russian spammers. We could restrict the anonymous login from anywhere but the same country as the guide is located in, decoding the country from the IP address (I'm sure there's a module or three that does this). Of course we still want genuine contributors to add content from abroad - but they can always register and log in :). My £0.02th Ivor.

1 0

[OpenGuides-Dev] Plucene support for Debian packages
by Dominic Hargreaves 04 Jan '05

04 Jan '05

[non-Debianites may switch off here]. I've uploaded to Plucene (and deps) packages to my repository, so you can now run OpenGuides with Plucene on Debian. I have also built new openguides packages with some minor changes to accommodate this. Some caveats: - libplucene-perl depends on perl 5.8.4, so you can't use this on woody yet. It *may* be possible to work around this, but I didn't bother as a first stab. - The built-in default (not the supplied config file) for whether to use plucene has changed to match upstream. So in the unlikely event that your configuration file has no mention of whether to use plucene, and you install the new openguides package without having libplucene-perl installed, your guide will be broken unless you add back a "use_plucene=0" option to your configuration file. This will almost certainly not affect anyone. To enable plucene support: - apt-get update - apt-get install libplucene-perl - apt-get install openguides - Edit your wiki.conf(s) so that use_plucene is 1 - For each guide, as www-data change into the CGI directory (eg /usr/lib/cgi-bin/openguides for the default) and run perl /usr/share/doc/openguides/examples/reindex.pl (note that this was broken in 0.46-1,2; upgrade to 0.46-3 first). - Test! I would like to upload Plucene and deps to Debian before long so it would be good to get preliminary testing here. Cheers, Dominic.

3 3

[OpenGuides-Dev] Text formatting help
by Earle Martin 02 Jan '05

02 Jan '05

New, tidier: http://openguides.org/page/text_formatting Associated wishlist item: https://rt.cpan.org/NoAuth/Bug.html?id=9117 -- Earle Martin http://downlode.org/ http://purl.oclc.org/net/earlemartin/

2 2

[OpenGuides-Dev] Charset support improvement
by Dominic Hargreaves 02 Jan '05

02 Jan '05

One of the recurring themes with using OpenGuides is that it doesn't do a particularly good or consistent job of allowing people to use charsets other than iso-8859-1. I've made a page on the wiki: http://openguides.org/dev/?node=Character%20Sets which hopefully sets out what problems there are and how to solve them. Please hack on that wiki page with additions and corrections, and/or make comments on list. Once we have a clear plan of how to proceed we'll need someone to implement it, too :) If you are regularly dealing with non iso-8859-1 charsets at the moment, then your input is especially valuable here. Cheers, Dominic.

3 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

OpenGuides-Dev January 2005