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

[Blaine Lang]

Turias, thanks for the feedback.


> 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.


Sure, it could be setup in the config.php  OR .. we could add the option to
the topic editor so it could be enabled online at the topic level.

2) The auto-delete was really a delete. This was requested by the client. I
can understand the concern but can also see that sites that are not
traditional blogs but are business or content driven sites are looking for
ways to have the site more auto managing. A busy site that has content that
really is date sensitive such as sale related items.  It could be a config
option but we already have functions such as deleting a topic can be
accidently done and you delete all content in that topic. A good reason for
backups.

The archive topic may normally be a hidden topic.

3) Auto move from one topic to another topic - other then the default
"Archive" topic was not one of the features I had added.
    This would require having a target topic per story.

   Disabling the "Show on Frontpage" instead of archiving or deleting could
be another option. Not currently there but could be added.

Blaine

----- Original Message ----- 
From: "Turias" <geeklog at sebastiancelis.com>
To: <geeklog-devtalk at lists.geeklog.net>
Sent: Monday, April 19, 2004 10:43 AM
Subject: [geeklog-devtalk] Re: Geeklog 1.3.10 Modifications for
consideration



> 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