Hi all,
Time to get some of this approval/moderation stuff tested by people other than me..

In case you don't have a clue what I'm on about, tye started some changes to the Approval system a while back, which mostly involve internal changes, namely getting rid of using the link table to 'link' nodes to sections and/or the frontpage. (tye, feel free to add anything/correct me). I've picked this up and have been adjusting/adding to/improving it (hopefully) to a point where we can start using it in production.

I'm inviting anyone with a login on the test server to have a look, and test out the functionality. In theory, the overall result should work as before, on the surface. What needs testing:

• Moderation Nodelet - replaces the Approval Nodelet, also the 'removelinks' part of the editors nodelet
• Node Status - nodelet, check that it reflects the correct status
• The Monastery Gates - should show nodes frontpages by the moderation nodelet
• Seekers of Perl Wisdom - and other sections, show approved nodes (or all if showunapproved is on), approve nodes if level > 5

Changes in detail:

• moderation nodelet - make work, mostly
• node status - nodelet, use isapprove
• newapprove - make work, adapt
• isapprove - ..
• approvalhistory - table that holds the history of all approval actions
• approvalstatus - table that holds the current/last status of each approved/fp'd node (no entry means unapproved)
• newcachedlistapproved - complete rewrite of cachedlistapproved, to use new tables etc
• Monastery Gates/Section pages - use newcachedlistapproved
• moderatelist default outer container - use newapprove opcode
• cachedinfo table - made key unique
• listapproved settings - added daysOnFrontPage, updateInterval

Some of the section pages are not yet converted, and the approve code is still producing entries in the link table. These will be fixed soon.

I'd appreciate if people would point out any other areas that are using the 'listapproved'/'approval' type code, that I've otherwise missed. (I've already noted that several section-similar pages, such as Editor Requests, SQL Query list, need another htmlcode, which doesnt use approval (since their entries arent/cant be approved.)

Many thanks to tye for starting this in the first place.

C.

PS: Note that this is by no means the end of the changes coming, once this has proven itself, I'll get on to the showing of history, and similar for considerations..

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, 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:
	&		&
	<		&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.