[geeklog-devel] Geeklog Topics

[Tom]

Okay I have committed the parent topic and session changes. New installs and
upgrades have been tested in mysql but not mssql or pgsql. There are also a
few functions that I still need to comment, and I will be depreciation a few
topic functions in lib-common and moving them to lib-topic. The topic
functions may also change slightly still as I work on adding 

- allowing a story to have multiple topics (plus everything else that is
connected to stories and topics)
- allowing stories to be inherited by parent topics
- allowing a staticpage to be displayed in multiple topics (instead of just
all topics)

As I said before, my next step will be finishing work on the blocks and
getting them to be inherited by topics. Once this is finished I will commit
this work and then start on the story stuff 

Please let me know if you find any bugs related to this commit.

Thanks

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom
Sent: October-07-11 3:19 PM
To: 'Geeklog Development'
Subject: [geeklog-devel] Geeklog Topics

Okay,

I am going to be checking in the Geeklog Sessions update and part of the
Topic update soon (next week sometime) so more testing can be done since I
might have missed something. I also want to make sure everyone agrees with
how the security, etc. works.

The session changes include the ability to track anonymous users, and the
who's online block now uses a column in the session table to track online
versus offline users.

The topic updates includes the ability to add a topic as a child to another
topic. New fields in the Topic admin form include parent topic, hidden and
inherit. New rules have been added to this form so admin's shouldn't be able
to have the parent topic of a topic be the child (or grandchild, etc.) of
the same topic. You also shouldn't be able to make your topic be a child of
a topic you do not have access to. 

Admins are going to have to keep an eye on what topics are hidden and what
security is set. If you remove read access for anonymous from the top topic
then anonymous users will not have access to that topic only. They still
would have access to child topics if their security allowed it (though these
will not be displayed in the topics block since the path is broken). At some
point we could add a checkbox to the Access Rights section to allow
permissions to be set for child topics as well if checked and the topic was
saved.

The Topics block has been updated. It now shows the tree structure of the
topics. Topics have several properties that affect them being displayed in
this block. These are Security, if it is Hidden, and if it is a Topic for a
different language. How it works is if the visitor doesn't have access to
the child topic, or if it is hidden or in another language then it is not
displayed. If it is not displayed then none of its child topics are
displayed (even if the visitor would have access to the topic)

Right now stories display in their topic but are not inherited (and no
stories in multiple topics yet)

Next up I will be working on getting the blocks from a child topic to be
inherited by a parent topic when viewed.

So once I have committed these changes and if you have a few moments I could
use some people to just double check that the topics work as advertised.

Thanks

Tom



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