Serendipity Forums

Hi

is there a way to forbid the editing and deleting of an user's own posts? The users should be allowed to create new ones, but it is neccessary that existing ones cannot be changed or removed.

I thought about removing the edit and delete links in the template, but there might be a more elegant solution.

any help would be appreciated

Hi!

You could do that by creating a custom PHP plugin, that checks if an item is being edited, and denies access. You can hook into the corresponding backend_display and other event hooks to check the item.

Serendipity itself does not restrict that, because in a blog environment its highly unusuall that an entry owner should not be able to edit his entries.

Best regards,
Garvin

hi,

is there a howto how to create such plugins?

some example code would be extremley helpful

Hi!

There is some documentation on www.s9y.org, and many things can be done by just looking at existing plugins.

The 'serendipity_event_entrycheck' plugin (available via spartacus) already goes into a similar direction, you can look that up for an example

Best regards,
Garvin

thank you, i'll have a look

i have yet another question: how is it possible to cancel an event?

so i just have to hook into the update / delete event and cancel it...

I don't think it's possible to cancel a hook once it's started.

I think you'll need to change the event_data instead.

soylentgreen wrote:thank you, i'll have a look

Please send me a note when you finish the plugin, I would use it as well, due to the same problem.

Filip

judebert wrote:I don't think it's possible to cancel a hook once it's started.

I think you'll need to change the event_data instead.

the hook api tells the following

http://s9y.org/116.html wrote: backend_delete_entry - Called when deleting an entry. Input data: Entry data

would be setting the entry data's id to an invalid number an appropriate way to prevent the entry from being deleted? or should the entry data set to null?

Hi!

If you search the code for 'backend_delete_entry' you'll see that the hook gets executed with $id as $eventData before the DELETE SQL statements are set.

Thus, setting $id to "-1" or "0" would make all the DELETE statements not delete matching rows.

So, the answer is: Yes.

Best regards,
Garvin

i have completed the plugin, if anyone is interested i can upload it or send it

I'd love to see it!

here's the code

comments are welcome

please note that the plugin still allows to enter the editing / deleting screens, since i could not figure out a way to prevent that