[geeklog-devel] 1.3.10 to do list

[Blaine Lang]

I have just submitted to CVS the changes to support the Story Archive
Feature.
I updated the themes, mysql update script and associated docs.

Dirk, I need to add one fix. I have used Javascript to disable the extra
fields in the story editor "Edit" screen if this option is disabled. The
default is for this option to be disabled unless toggled on per story. It's
a nice touch but I may have to disable it or find a quick way to leave these
new fields enabled if JS is disabled in the browser. Just about everyone has
JS enabled don't they :)

This is a topic for another day but maybe we assume JS is enabled for
Admin's and start to use JS to improve the UI.
I'd love to see a nice Tab'ed interface for some of these large admin pages.

If the user has not set the new $_CONF parm - then even if the arvhive
feature is enabled for a story and the expiry time is reached, the story
will not be effected.
$_CONF['archivetopic']          = 'archive';   // Topic ID to Auto-Archived
topics after expire date

Blaine
----- Original Message ----- 
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Sent: Monday, July 26, 2004 12:57 PM
Subject: Re: [geeklog-devel] 1.3.10 to do list


I would like to add the Story Archive and can do so this week.
- Option to set a date where the story will be moved to a "defined" archive
topic or delete automatically.
- It's also possible to use a new set of template files for the archive
topic

I also have a similar feature for Blocks - where you can set the show until
time then it gets disabled.

Another item I have is a change to the advanced search results. I just need
to complete a bit more testing on that one.
I will aim for this week as well to get that in.

Blaine
----- Original Message ----- 
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Sent: Monday, July 26, 2004 11:58 AM
Subject: [geeklog-devel] 1.3.10 to do list


Okay, I think I have pretty much implemented everything that I wanted to
go into 1.3.10. Now it's on to the usual stuff (bug fixes, documentation
and language file updates, testing, ...).

Not sure if I'll have a go at the Admin Toolbox we've talked about or
leave it for the next version. I may give it a try if I have a mood swing
or something ...

Then there are a few other open issues:

Inclusion of the SpamX plugin - what's the status here? We probably need
a new plugin API function so that plugins can filter or reject comments
before they will be saved. Also, a method to make it easier to package
plugins with Geeklog would be nice, e.g. by making the install script
read the SQL for the plugin from some predefined directory (if we do
that, it also needs to be able to handle plugin updates).

Vinny, you wanted to do some work on the comment bar. What's the status /
plan here?

PDF: Currently, the PDF-related files all produce XHTML, which is
inconsistent with the rest of Geeklog which produces plain ol' HTML. From
the documentation, the PDF add-on doesn't understand XHTML either (but
only HTML 3.2), so I don't see the need for this. Tony? Anything else
that needs to be done on the PDF support?

A few features have been mentioned in the past as being possibly ready to
go into the next release. Most notably spell checking and archiving of
old stories. Tony, Blaine - any updates?

Anything else?

bye, Dirk


-- 
http://www.haun-online.de/
http://www.tinyweb.de/

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel