Hi folks,
After several months of struggling with a painful server, Birmingham Perl Mongers have now bought hosting for our various projects. I've started setting up the box, and now would seem to be a good time to upgrade OpenGuides too.
However, the current installation is running 0.49 and as I'd like to use the latest OG code, 0.60. Is there a conversion script to migrate the database between the two? It's currently running under postgresql, and can remain so, or move to MySQL if anyone has a conversion script for that.
Following up Kake's post about a SpamDetection module. This closely follows how things work on the current Birmingham site, with the hacked version of the code I made. However, rather than one SpamDetection module, I'd like to see the ability to have several, so that it allows people to plug'n'play with a variety of detection modules. Much in the same way that most email spam engines work.
In addition the Birmingham OpenGuides has a rollback feature, which allows an admin to rollback to a specific version, rather than deleting nodes one by one. I haven't seen this as a feature, is it something that would be useful? I don't have the time to patch anything right now, but I could look at this during July.
And finally, how painful is the template and CSS migration likely to be? There looks to be a lot of new templates in the latest release!
Cheers, Barbie.
On Mon 21 May 2007, Barbie barbie@missbarbell.co.uk wrote:
After several months of struggling with a painful server, Birmingham Perl Mongers have now bought hosting for our various projects. I've started setting up the box, and now would seem to be a good time to upgrade OpenGuides too.
Hurrah!
However, the current installation is running 0.49 and as I'd like to use the latest OG code, 0.60. Is there a conversion script to migrate the database between the two? It's currently running under postgresql, and can remain so, or move to MySQL if anyone has a conversion script for that.
I upgraded Vegan Oxford from an oldish version, and it Just Worked - it converted the database schema when I did "perl Build install".
Following up Kake's post about a SpamDetection module. This closely follows how things work on the current Birmingham site, with the hacked version of the code I made. However, rather than one SpamDetection module, I'd like to see the ability to have several, so that it allows people to plug'n'play with a variety of detection modules. Much in the same way that most email spam engines work.
The idea is that what I've done is completely pluggable - it'd be easy to write a module that would call several other modules in order to make its decision.
In addition the Birmingham OpenGuides has a rollback feature, which allows an admin to rollback to a specific version, rather than deleting nodes one by one. I haven't seen this as a feature, is it something that would be useful? I don't have the time to patch anything right now, but I could look at this during July.
I don't think we have that - and I think it would be very useful!
And finally, how painful is the template and CSS migration likely to be? There looks to be a lot of new templates in the latest release!
Many of the new templates come from splitting out sections of the older, more monolithic/complicated templates. I'm happy to help with CSS munging where necessary, having spent quite some time playing with various OpenGuides designs recently.
Kake
On Mon, May 21, 2007 at 06:07:09PM +0100, Kake L Pugh wrote:
On Mon 21 May 2007, Barbie barbie@missbarbell.co.uk wrote:
Hurrah!
Indeed :)
I upgraded Vegan Oxford from an oldish version, and it Just Worked - it converted the database schema when I did "perl Build install".
Well I'll keep my fingers crossed it all goes smoothly for BrumOG too :)
The idea is that what I've done is completely pluggable - it'd be easy to write a module that would call several other modules in order to make its decision.
Would you be able to remove a module by actually deleting it and for everything still to work? Or probably more appropriate, add a new plugin simply by copying it into the appropriate directory? I use Module::Pluggable for autodetection with other things and it just works (tm) :) It saves a lot of configuration.
In addition the Birmingham OpenGuides has a rollback feature ..
I don't think we have that - and I think it would be very useful!
Okay I'll have a look at the new code when I get the chance and send a patch.
Many of the new templates come from splitting out sections of the older, more monolithic/complicated templates. I'm happy to help with CSS munging where necessary, having spent quite some time playing with various OpenGuides designs recently.
Cool. I'm glad you've moved towards a CSS way of presentation, it makes playing with skins alot easier :)
Well I plan to try and copy everything over during this week, and will let you know how I get on.
Cheers, Barbie.
On Mon, 21 May 2007, Barbie wrote:
However, the current installation is running 0.49 and as I'd like to use the latest OG code, 0.60. Is there a conversion script to migrate the database between the two? It's currently running under postgresql, and can remain so, or move to MySQL if anyone has a conversion script for that.
The wiki toolkit migration script should do all of this for you, when you upgrade wiki toolkit (before you do your openguides upgrade)
In addition the Birmingham OpenGuides has a rollback feature, which allows an admin to rollback to a specific version, rather than deleting nodes one by one. I haven't seen this as a feature, is it something that would be useful? I don't have the time to patch anything right now, but I could look at this during July.
In the new admin interface, there is an option to revert all the changes made by someone, which will often allow you to zap a spam run
Nick
On Mon 21 May 2007, Barbie barbie@missbarbell.co.uk wrote:
Would you be able to remove a module by actually deleting it and for everything still to work? Or probably more appropriate, add a new plugin simply by copying it into the appropriate directory? I use Module::Pluggable for autodetection with other things and it just works (tm) :) It saves a lot of configuration.
I think the answer to this one is to write a module that uses Module::Pluggable, and then put that module in your config file. I'd offer to do this for you, but I'm not familiar with Module::Pluggable, so it might be quicker for someone else to.
Okay I'll have a look at the new code when I get the chance and send a patch.
Yay, thank you!
Well I plan to try and copy everything over during this week, and will let you know how I get on.
Good luck; let us know if there's any problem you think we can help with.
Kake
On Thu, May 24, 2007 at 02:46:19PM +0100, Barbie wrote:
On Tue, May 22, 2007 at 11:09:57AM +0100, Nick Burch wrote:
The wiki toolkit migration script should do all of this for you, when you upgrade wiki toolkit (before you do your openguides upgrade)
I think you've misunderstood the nature of this upgrade. I'm *not* upgrading the machine BrumOG is currently on, I'm installing a brand new installation of OG on a new machine, and have an SQL file resulting from a postgresql dump that I want to be able to import, and for it all to just work ;)
Hence why I was asking for a conversion script that would amend the inserts to ensure all the field names were correct and anything new was populated with default values.
It shouldn't matter. If you restore the database dump, then run wiki-toolkit-setupdb (from the new distribution) on the database, it'll upgrade the db schema for you.
Dominic.
On Tue, May 22, 2007 at 11:09:57AM +0100, Nick Burch wrote:
The wiki toolkit migration script should do all of this for you, when you upgrade wiki toolkit (before you do your openguides upgrade)
I think you've misunderstood the nature of this upgrade. I'm *not* upgrading the machine BrumOG is currently on, I'm installing a brand new installation of OG on a new machine, and have an SQL file resulting from a postgresql dump that I want to be able to import, and for it all to just work ;)
Hence why I was asking for a conversion script that would amend the inserts to ensure all the field names were correct and anything new was populated with default values.
In the new admin interface, there is an option to revert all the changes made by someone, which will often allow you to zap a spam run
That isn't the same as a rollback. While it's been useful when there have been spam attacks, it's also useful to rollback when inappropriate content is posted, when deleteing everything by a single person is not what you want. I may have misunderstood this, but until I've got it up and running and seen it for myself, I suspect a rollback work along side this.
Cheers, Barbie.
On Thu, May 24, 2007 at 02:42:50PM +0100, Dominic Hargreaves wrote:
It shouldn't matter. If you restore the database dump, then run wiki-toolkit-setupdb (from the new distribution) on the database, it'll upgrade the db schema for you.
Excellent :)
Following this it may be worth including this in the site FAQ. While this list is really responsive and helpful, it really deserves to get written down somewhere.
Cheers, Barbie.
On Thu 24 May 2007, Barbie barbie@missbarbell.co.uk wrote:
Following this it may be worth including this in the site FAQ. While this list is really responsive and helpful, it really deserves to get written down somewhere.
Have added it to http://dev.openguides.org/cgi-bin/trac.fcgi/wiki/FAQ
Thanks!
Kake
openguides-dev@lists.openguides.org
-
Barbie -
Dominic Hargreaves -
Kake L Pugh -
Nick Burch