websitemaster at cogeco.net
Mon Oct 3 12:25:32 EDT 2011
That sounds fine with me. I don't think we need a RC2.
>> We also need to get the plugin authors on board to test their plugins
Most plugin authors who use blocks "the old way" should be able to switch
them to dynamic with few problems (use the updated polls or calendar code
as example) and still retain all the functionality of a regular PHP Block.
We should discourage Plugin authors from accessing the blocks table directly
(or any Core table).
The multiple topics and child topics stuff I am working on shouldn't require
any changes by plugin authors.
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: October-03-11 11:20 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] 1.8.1
> You probably noticed but I have added 2 censor bug reports (one with a
Okay, so the two censoring bugs #1392 and #1393 are fixed. I think we should
push the follow-up bug #1395 to 1.9.0 and think about releasing 1.8.1 real
Does anyone think we need an rc2?
I'd rather see us move on to 1.9.0 now. We also need to get the plugin
authors on board to test their plugins with 1.9.0 (remember that we have
"nightly" tarballs) so that plugins can be updated for the topic/blocks
changes and tested with MySQLi (which is more picky than the old MySQL API -
I've had a few issues with older plugins .).
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel