In some cases it is wanted that you can change complete tree structures, so I don't think we should remove the option that people can freely attach structures.
Surely, I was only talking about cutting that branch of the tree that starts with the article being edited. This would leave all (sensible ...

Hello again!
Since the 'approveComment' feature now has an event hook, can you use that one to migrate your comment? I figure you only need approved comments in the mirrored blogs, so at that place you'd have the entry/comment ID available, and we wouldn't need to add a new hook to after the ...

It is now impossible to make an entry a child of itself, but one can still make it a child of a child, grandchild etc. With the current database structure, there will have to be a non-trivial query to determine all offspring. Alternatively, when the list of possible parents is created for the edit ...

When editing a comment, it is possible to make it the child of one of its own offspring. It's stupid to do, but the involved comments then disappear until parenthood is set again.

If you merge blogs, the IDs of comments shouldn't matter at all, so you could just insert the entries using the auto-increment assigned key using the existing savecomment hook?
They matter as soon as there are comments on comments: when I know that a new comment is a reply to number 10 in the ...

Have you thought about using MySQL replication setup instead?
As it's about merging several blogs, IDs have to be changed, so a mere replication wouldn't suffice.

So it should only go the 'backend_publish' route in case an article is newly published (or re-published after setting it to 'Draft ...

You're right about the underscore, I forgot that one can define a prefix to those tables' names, which in your case apparently is "serendipity_". When I wrote "serendipity.authors", though, the part in front of the dot meant the database name. Combined with your complete table name, that would ...

Hi, thanks for faithfully replying to everbody! I am trying to move several blogs' articles into another blog 'in real-time'. Aggregating feeds is too inefficient, as is using a frequent cron job to duplicate things, so I am writing a plugin that mirrors any database changes (article creation ...

In whichever database you pointed Serendipity to during installation, there is a table called "authors" with a column "password" for each author. The passwords are encrypted, but you can simply set a different value. In the same software that you used to create the database required for Serendipity ...

Hi, when trying to process comments in a plugin, I found that the existing hook frontend_saveComment is positioned before the actual database entry is made, making it lack information on the inserted comment's ID. Simply guessing that it is the latest comment's ID plus one could be wrong in case ...