Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??


The idea now is to make a generic "Create New Forum" capability. Not only would this be useful for things like group-private fora, but we'd eventually want to convert the existing sections to the new scheme.

First and foremost, stop using distinction of nodetypes to define fora (i.e., "sections"). Instead, go to a prototype-like (i.e., Self-like) scheme, where a forum is defined by a root node. a super-root node, as it were. (Let's call it the "base" node.) An ordinary root post would be a note, whose parent is itself (or nil), but whose root is the forum base. All of the forum base nodes would be of the same (proposed new) type; they simply differ in content. The title of one could be "Seekers of Perl Wisdom", for example.

Of course, such a change would have far-ranging implications. Super Search, for example, would be drastically impacted. But changes would, almost universally, be for the simpler.

We also wouldn't need to create a superdoc as the "landing page" for each section. :-)

I believe we should have group-private fora, for pmdev, janitors, gods, so that we can get discussions away from the wikis. That by itself would be enough of a win.

So maybe we start by creating the "generic" forum scheme only for use for these known desired fora.

The new nodetype should have a field (NULL-able) which refers to an accessrule. Actually, two: one for defining who can create a root post in the forum, and another for controlling who can read/write replies. We'd have to have a form (in a superdoc) where the properties of the new forum would be specified. The two access rules (root and reply control) could be pick lists, populated with the extant usergroups and accessrules.

 s/ $NODE->{root}{type}{title} / $NODE->{root}{root}{title} /
What is the sound of Windows? Is it not the sound of a wall upon which people have smashed their heads... all the way through?

In reply to Re: Create new [pmdev]-only section "Pmdev Discussion" by jdporter
in thread Create new [pmdev]-only section "Pmdev Discussion" by jdporter

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others chilling in the Monastery: (4)
    As of 2020-05-27 13:26 GMT
    Find Nodes?
      Voting Booth?
      If programming languages were movie genres, Perl would be:

      Results (155 votes). Check out past polls.