Hi!
I'd use ob_Start() before calling updertEntry, so you can even store this debug output somewhere, and then discard it.
I saw that you set the rightpublish session var. You should keep track of the original content, and reset it after the update. Else, anyone with a sesssion would be able to publish entries after that.
Also, in the setpuDB routine I would remove the backticks ` so that the code is compatible for SQLite and PostgreSQL. In the end, merging the code into the trackbacks-event plugin would also be a great addition? In that case, its update routine would need some kind of hidden configuration value, and if that does not exist, the plugin would need to create the missing database table.
generateDelayed() should IMHO only inclkude the trackback library, if at least one tracbkack is to be sent, to save some space. otherwise the lib would be included on every page request. Plus, you might want to add a simple random(1, 10) function and only execute the check when that number is 1 - so the overhead of this SQL query would only occur about once every 10 page requests, which should still be sufficient and much less on the performance impact side.
The basic idea of this is very nice, and should work perfectly! MAny thanks for working on this!
REgards,
Garvin