Do not execute trackbacks for entries in the future

This commit is contained in:
Garvin Hicking 2008-08-03 11:40:51 +00:00
parent 6c112ff3d2
commit fdfcdeb56d
2 changed files with 7 additions and 2 deletions

View File

@ -3,6 +3,11 @@
Version 1.4 ()
------------------------------------------------------------------------
* Trackbacks are no longer sent when an entry shall be published
in the future. You can force them by editing and re-saving an
entry, once it is published. TODO: A plugin/cronjob to automatically
execute those trackbacks? (garvinhicking)
* Allow 'sequence' widget to enable/disable each config item,
if the property "checkable" is added to the introspect method.
(garvinhicking)

View File

@ -1299,7 +1299,7 @@ function serendipity_updertEntry($entry) {
serendipity_purgeEntry($entry['id'], $entry['timestamp']);
if (!serendipity_db_bool($entry['isdraft'])) {
if (!serendipity_db_bool($entry['isdraft']) && $entry['timestamp'] <= serendipity_serverOffsetHour()) {
// When saving an entry, first all references need to be gathered. But trackbacks to them
// shall only be send at the end of the execution flow. However, certain plugins depend on
// the existance of handled references. Thus we store the current references at this point,
@ -1316,7 +1316,7 @@ function serendipity_updertEntry($entry) {
serendipity_plugin_api::hook_event('backend_save', $entry, $newEntry);
}
if (!serendipity_db_bool($entry['isdraft'])) {
if (!serendipity_db_bool($entry['isdraft']) && $entry['timestamp'] <= serendipity_serverOffsetHour()) {
// Now that plugins are executed, we go ahead into the Temple of Doom and send possibly failing trackbacks.
// First, original list of references is restored (inside the function call)
serendipity_handle_references($entry['id'], $serendipity['blogTitle'], $drafted_entry['title'], $drafted_entry['body'] . $drafted_entry['extended'], false);