Hi,

I would like to allow a select group of editors, rather than the site administrator, to validate reviews. I guess that Links SQL can't do this out of the box so I'm quite happy to write a bit of custom PHP.

I'm happy not to bother sending email to the person who posted the review.

So, 2 questions:

1. To validate a review, is it simply a case of changing Review_Validated from No to Yes in the Reviews table, or do I need to do anything else?

2. To delete a review, can I just delete the relevant row from the Reviews table or are there any other things that I need to update?

Thanks!

Rob

Allowing editors to validate reviews has been asked for more than a year ago:

http://www.gossamer-threads.com/...i?post=232189#232189

A bit disappointed this hasn't made it into any upgrades yet. It's one of the biggest holes in the current review system. If you think about it, it just doesn't make sense. You surely would expect to receive more reviews than links (many to one) and still the bulk of the work is left with the administrator(s).

It also diminishes from the ability to truly assign "ownership" of a section/category to an editor and make them feel responsible and accountable for it.

Safe swoops
Sangiro

BUMP.

I want to allow my editors to validate reviews, as well... I'm with sangiro - it's ridiculous this hasn't been included in the current review system yet.

Anyone official want to answer Rob's questions? I might just hand-code this myself, too... Either that or just validate all reviews on submission and only allow registered users to submit reviews.

Thanks!

Seems I was the last person to reply to that thread, and asked for a discussion of it. I haven't seen any, maybe I missed it.

I've been pulling most management features out into HTML, away from the central management area. Partly, because it seems to make more sense, and partly because there are "too many cooks" in the central mix to do it otherwise.

To allow an editor to update reviews, is not difficult. If I remember correctly, just pick the editor permissions, and display all unvalidated reviews, with a link to the link. It's not a complicated thing, I don't think. It requires a logged in user, and taking the "editor" link down one level. eg: when you click the "editors" button, rather than getting the java controls, you get the editors_home.html page, and the various features are linked to from there.

The problem I have, is no input on what people needed/wanted on it, and no site to test it out on, since none of our sites generate any practical amount of review traffic.

I hesitate to make changes to anything in the core system, especially the admin area, since none of those changes would be portable. Additionally, I have not had time to go over the changes in the 2.2 links version.

Like GT and Alex with the release of Links SQL 2.0, there is a _lot_ of stuff that has to go on behind the scenes to make it happen. Ripple changes in logic, rewriting routines to handle more generic cases, development of special-case handlers, etc.


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.

I'm just implementing the final touches to a LinksSQL set-up and I was looking to see how to let editors work on sifting through the reviews for their categories.
My set-up may not be close enough to the average usage of LinksSQL, in effect it will be the editors that post links and detailed links. Visitors can suggest links and editors will look them up and post if decided appropriate.
From what I understand enabling theme to sift through reviews is not yet possible but I agree with the previous posts in that editors should be able to / if not be responsible for reviews concerning their categories.

Even though I am not familiar enough yet with LinkSQL I can say through experience with large european content management web sites and directories that a web site would usually be very big before you had separate people managing content for specific areas.
It would be unusual to have Person A posting and creating content for Area 1 and then having Person B or the webmaster deciding whether content referring to content and maybe even criticizing content in Area 1 was posted or not.
In content management systems a work-flow may often exist to allow the Person A to refer it to another person higher up for legal issues etc.

There obviously isn't a perfect solution for all cases but I do feel that the admin already has a sufficient work load and also that in my opinion it shouldn't really be the admin deciding whether a review is relevant and it could be pretty bad in the context of the link reviewed.

John
Significant Media