[dw-free] Don't backdate community posts when importing
[commit: http://hg.dwscoalition.org/dw-free/rev/906a190f66f5]
Don't backdate community posts when importing
We use the backdate option so that posts you import don't flood your reading
page. It turns out that this is unnecessary for community posts because we
manually set the logtime/rlogtime to an old value. This means we can turn
off backdate and we won't flood the reading pages.
Patch by
mark.
Files modified:
Don't backdate community posts when importing
We use the backdate option so that posts you import don't flood your reading
page. It turns out that this is unnecessary for community posts because we
manually set the logtime/rlogtime to an old value. This means we can turn
off backdate and we won't flood the reading pages.
Patch by
Files modified:
- cgi-bin/DW/Worker/ContentImporter/Local/Entries.pm
--------------------------------------------------------------------------------
diff -r 40848a3f33dc -r 906a190f66f5 cgi-bin/DW/Worker/ContentImporter/Local/Entries.pm
--- a/cgi-bin/DW/Worker/ContentImporter/Local/Entries.pm Tue Mar 13 19:02:58 2012 +0000
+++ b/cgi-bin/DW/Worker/ContentImporter/Local/Entries.pm Tue Mar 13 20:07:54 2012 +0000
@@ -132,8 +132,12 @@
};
# Overwrite these here in case we're importing from an imported journal (hey, it could happen)
- $proto{prop_opt_backdated} = '1';
$proto{prop_import_source} = $evt->{key};
+ if ( defined $posteru ) {
+ delete $proto{prop_opt_backdated};
+ } else {
+ $proto{prop_opt_backdated} = 1;
+ }
my %res;
LJ::do_request(
--------------------------------------------------------------------------------
