[geeklog-devtalk] Re: Geeklog 1.3.10 Modifications for consideration

[Jeff Hare]

Hi Guys,

    I've been mulling this over for a few months to give me a chance to
experiment with how the auto-expire/archive to topic might work.

I implemented this to evaluate the concept on my site, but since it changes
the db tables slightly, I don't plan to keep it as implemented.   I don't want
to support customized tables on my site... :)

Just for some background, here's why I agree that this behavior would
be very helpful.

Since I use GL to manage a club website, what I find very frequently is
that we have major events or announcements that need to be "front and center"
on the home page, but should show up beginning on some date, and then go
away once the event is over.

Before, I managed this by assigning a start date, and then have to remember
to go uncheck the "show on home page" option to get it off the page and back
into the topic only.   It's hard for me to explain/train other story moderators
to do all this when most are not all that technical.

As for deleting them, I can certainly see why this is useful, because some
events or announcements will never make sense again.   While it's easy to
go in and delete them,  it's still work that needs to be done, and it would be
nice to be able to program this at posting time.

If there's anything I can do to assist here, let me know.

BTW, GL is fantastic.  I'm quite pleased with the GL2 coding and architecture
I've seen so far.   Nice job.

-Jeff Hare
Sr. Member Consulting Staff
Cadence Design, Inc.


At 10:43 AM 4/19/2004, you wrote:

>I think it would be great to see this functionality incorporated into the

>core, Blaine.  I have a couple of thoughts after reading your e-mail.

>

>1) It would be really nice to activate and deactivate this functionality

>through a config.php flag.  There are always users on the forums who don't

>want their story editors to become bloated with options they never use.

>Providing a flag would be an easy way to remedy this without forcing users

>to hack template files.

>

>2) Is an auto-delete option really a good idea?  I can see people

>accidentally deleting content with no good way of getting it back.  This

>seems dangerous.  It's generally good practice in CMSes to never delete

>content, anyway.  I think it might be better to force the site admin to

>create an archive topic that is hidden to most users and then archive

>everything they would normally want to delete into that topic.

>

>3) There have been requests for two types of archiving.  First, people

>have said they would like to archive content off of the frontpage.  Also,

>some users have wanted to archive content from one topic to another (like

>from a What's New topic to a more specific topic).  Does your modification

>do both of these?  If not, it would be nice to add that for 1.3.10.

>

>- Turias

>

>

> > I would like the following modifications considered to be included in the

> > nex release and am posting to get any feedback.

> >

> > Modification 1:

> >   Extend the Story Editor to also be able to auto-expire article content

> >   Stories can be optionally moved to a "Archive" topic or deleted

> >   Site configureable "archive" topic

> >   Able to setup a Archive themed template for stories as well

> >

> >   See attached image of the modified story editor

> >

> > Modification 2:

> >    Extend the Block Editor to be able to specify Start and End Dates for

> > blocks to show

> >

> >

> > Blaine

>

>_______________________________________________

>geeklog-devtalk mailing list

>geeklog-devtalk at lists.geeklog.net

>http://lists.geeklog.net/listinfo/geeklog-devtalk