#76 new story type

Slash 1.1/2.0
closed-accepted
nobody
Stories (85)
1
2002-02-05
2001-10-02
shane
No

"indefinite" or something similar - meaning:

if the discussion::type=='indefinite' then
the Slash::DB::Static method in dailyStuff does
not, ever, set the type to 'archived' after the
var$archive_delay has passed.

what this gives you is perpetual sid's/threads.

an example of how it's used with 2.0 is:

http://www.bookiejoint.org/comments.pl?sid=chatter

Discussion

  • shane

    shane - 2001-10-02

    Logged In: YES
    user_id=52587

    <tf23> with discussion types, what is type='recycled'? is
    there a way to keep a particular sid open
    indefinitely?
    <tf23> (ie to make sure that said sid would never be marked
    as 'archived')
    <Cliff> Um.
    <Cliff> 'recycled' means "delete this discussion from the
    database".
    <Cliff> The only two other discussion types are "open" (can
    post) and "closed" (can read, not post)
    <Cliff> What EXACTLY are you trying to do?
    <tf23> something like this:
    http://www.bookiejoint.org/comments.pl?sid=chatter
    <tf23> one major thread for all to bicker in throughout the
    existance of the site
    <tf23> it works great with 2.0, but with 2.2 and the
    archiving to shtml back, rendering to shtml for anon
    users is fine, but i'd need to keep the sid open
    for posting forever.
    <Cliff> You'll have to hack either the code, or a task to
    keep such a thing open, TF.
    <Cliff> You can archive to .shtml and still keep a
    discussion in the DB in Fry, BTW>
    <Cliff> Just never set your discussions to 'recycled' and
    never set stories to 'delete'.
    <Cliff> s/discussions/discussions.type/
    <Cliff> s/stories/stories.writestatus/
    <tf23> so the system would automatically take a sid and
    archive to .shtml after {time period}. after that
    happens, the type is set to 'archived' and users
    can no longer post to it?
    <Cliff> The controlling variable is var$archive_delay.
    <Cliff> And the system sets the type to archived via a
    Slash::DB::Static method in dailyStuff
    <tf23> ok, so that's why you mentioned a task to routinely
    set the discussion type to 'open'.
    <Cliff> Once the type is set to archived (and here's a
    sticky point still under development, right now), then
    a handler would run and archive all stories so
    marked (final .shtml copy) and set the writestatus
    back to 'ok'.
    <Cliff> I guess what you COULD do is make it so that you
    have an "exclusion list" of SIDs. IDs in this list
    would simply not be closed.
    <Cliff> It's an easy hack, really.
    <Cliff> Slash::DB::Static::MySQL::archiveComments()
    <tf23> or an additional story type of 'alwaysopen' or
    something along that line of thinking
    <Cliff> Nope.
    <tf23> that the archiver would never archive
    <Cliff> Well, actually. Yes.
    <Cliff> You can do that.
    <Cliff> You'd need to modify the schema for both
    stories.writestatus and discussions.type
    <Cliff> Set the story from "ok" to "alwaysopen". Do the
    same for discussion, and it will never move from that
    state.
    <Cliff> No changes to code necessary, now that I look at it.
    <Cliff> Try it and let me know if something breaks.
    <tf23> ok, gonna copy all this and try it tonite once i get
    fry running on this dev box there

     
  • shane

    shane - 2001-10-04

    Logged In: YES
    user_id=52587

    this patches /fry/slash/sql/mysql/slashschema_create.sql
    so there's a new type in the schema.

     
  • shane

    shane - 2001-10-04

    patch for new story type (never ending) in schema

     
  • Rob Malda

    Rob Malda - 2002-02-05

    Logged In: YES
    user_id=288856

    Legitimate feature request. I hvae no need for this
    on Slashdot, but would consider patches.

     
  • Rob Malda

    Rob Malda - 2002-02-05
    • priority: 5 --> 1
    • status: open --> closed-accepted
     

Log in to post a comment.