[geeklog-devel] Geeklog 2.0.0 Schedule
websitemaster at cogeco.net
Wed Mar 28 15:29:19 EDT 2012
Yeah same here. One of the problems with these 2 issues is how far do we
want to go?
Do we design something completely new and more elegant (as stated in some of
the feedback on the issues) which would take time or do we go for a simpler
solution to solve the issue while keeping compatibility with older plugins
(but not necessarily strict compliance).
If we did decide to do something I would be probably for the second option
especially if it has a remote chance to be in 2.0.0 (feature creep here we
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan
Sent: March-26-12 10:04 AM
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Geeklog 2.0.0 Schedule
Quoting Tom <websitemaster at cogeco.net>:
> A quick update in regards to the Geeklog 2.0 release. We are
> approaching the end of March and still have things to work on. I know
> everyone is pretty busy so let's bump the RC to mid-end of April.
> Rouslan has been working on the new theme and it has been coming along
> nicely. For those of you who haven't seen it yet it is available in
> the repository and is currently called newpro.
> Here are the list of items (besides the theme) I think we should
> finish before we release Geeklog 2.0.0 RC 1:
> Name the new Theme - Ideas?
> Changing "Remember Me For" does not update cookie timeout
> Update Page Navigation with link elements
> The part of the page navigator should do markup by a list.
> Failure when trying to report sitemap.xml write error (I am not sure
> if this happens on a Windows system since I have not seen it before)
> If anyone has and additions or comments let us know.
I think that this bug needs to be fixed for 2.0.0 I keep stumbling into
it while working on the theme and can never find a proper workaround for
this. Others have had their issues with it as well. One example is the
CSS layout and another one are the breadcrumbs, which should be generated in
the header, but we don't know if there will be any when generating the
header. Then they may be created in a few different places on the page since
they are rendered with the articale (or static page, or whatever), but they
really must be fixed in a particular position to be effective.
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel