:)

I got it coded so it only displays for the user and administrators :D

I think you misunderstood me, or perhaps I was not clear.

I know where the options for the hack are located. However, there does not appear to be a way to say NO ONE should be able to delete (or only superadministrators). The same for preventing anyone from seeing the feedback entry's username. I might be overlooking it, but pressing <ctrl-click> on the selected entry will clear it from the box, but it will not save that way. There is no 'NONE' choice, either.

I see - and yes, thats correct. I dont see any point in a no-one option.

At the very least the site administartors should have the power. Superadministrators are not a option in any standard permissions, they are just an ACP oddity.

If you really want a no-one option then simply ceate a dummy usergroup called no one, and only assign it the option(s).

I see your point of view. The flip side is not making so easy for people to make mistakes. Admins already have the power within the admin control panel whereupon it becomes a very conscious decision to delete feedback. Also, inline moderation would typically require an admin to reenter their password (presuming option is enabled), but not in this case.

Thank you for the suggestion regarding the dummy usergroup. This is a good option for the client assuming it becomes a requirement. I also discovered an easier method to make deletions harder via examining the code: Set the delete timeout option to zero. This removes the button (as opposed to allowing for an indefinite period for deletions).

Nice mod, works on 4.1.2. Only blip is that it knocks the 'conversation' tab off the end of the profile page. Thanks Paul, installed and rated.

Installed, will go nicely with your other mod. Yours are always high quality, so I never fret about using 'em :)

With PHP 5.3.6 and vB 4.1.13 getting error:

I have no such error on my test forum (which is also PHP 5.3.6 and vB 4.1.3).

Hi Paul,

Thank you for your reply.
Yesterday I've upgraded two of our servers to php 5.3.6 and the messages appeared.
No problem with php 5.2.17 on other server.
Maybe it's vB bug. Not sure...

P.S.
Forgot to tell you that you should add:
in config.php to see this message

Yep, got it - a php 5.3 issue. Update released.