If you are here by mistake, you may feel free to
No member, no entry hereunder. |
Once you longin the admin page successfully, you can edit your message-board as below.
|
If you are here to hack the site, please don't. And if you can inform the administrator any security hole you've found,
Thank you! $warn Articles to be reviewed. |
:
: |
$data{'name'} ($posted) $data{'title'} check to DELETE
Please note, "$dall" deletes all the articles from the data base and the MessageBoard. If everything is ok, please click "$aok" and do not quit arbitrary. |
Temporary while a board master is working on the administrative page, a guest can not post an article to the board. And if the administrative work is interrupted, a guest can not write an article on the board 30 minutes. The duration can be changed from basic set up $lfexp. Have it long enough for the admin work but not too long. Make it clear that a board master goes to the administrative page only after he has determined the articles to be deleted - so that the admin work can be done quick. Further, even if he finds everything is ok, he better not quit the operation arbitrarily. Click "$aok" (the default is "All OK" but you can change it). Otherwise temp.dat which is used to block new messages will be left there 30 minutes.
If a board master sees the message "The lock file temp.dat has been created...", most probably somebody is writing on Board. It wouldn't take minutes. If he tries the admin page again or reloads it, the board master will see the lock file gone (and a new message is added on the board).
If a board master has interrupted the admin operation within last 30 minutes, he would see "The lock file temp.dat has been created..." message too. He can just ignore it.
Other possibility is a server malfunction, mostly due work overload. Or someone tried to hack the site recently. If you suspect something goes seriously wrong, see the access log (if you can see it) or talk to the server administrator. If frequent work overloads, you want to upgrade the server. If hacking, you may see the culprit's IP address, at least, and then you can trace back who did it.