I don't see changes in tables, the nid is always 0.
I have made a test in forward.module at line 707
if ($nid == '') {
$nid = 0;
$returnurl = '';
}
I try $nid=15; and the change is applied in the table ...
The problem is that $nid is empty ! automatically you assign 0 and tables are updated with nid =0 ...
Somebody has the same problem?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | printscreen of forward_log table | 41.51 KB | pixelpreview@gmail.com |
| #1 | forward blocks, always 0 ... | 10.25 KB | pixelpreview@gmail.com |
Comments
Comment #1
pixelpreview@gmail.com commentedwebmaster for dynasite.be - dynasite.ma
Comment #2
dantw commentedI'm having the same problem that forwarding a content article (blog, story, etc) while recording a 'SENT' type in the forward_log table, the corresponding inserted nid was always 0. As a result, the 'Most Emailed' and 'Most Forwarded' blocks are pretty much useless. I have Drupal 5.10 running on IIS6.
Would appreciate any advice. Thanks.
Comment #3
windhamdavid commentedsame problem :)
Comment #4
windhamdavid commentedreplaced
if ($nid == '') {
$nid = 0;
$returnurl = '';
}
with
$arg1=arg(1);
if (is_numeric ($arg1)) {
$nid=$arg1;
}
else {
$nid = 0;
}
$returnurl = '';
Comment #5
pixelpreview@gmail.com commentedperfect for forward module but not for clicktroughs blocks enbaled with forward module. I have the same problem no table update when I click in the mail and when the forward_tracker function is called.
yes it's the same problem no nid ... here
at line 342 and line 355 if nid != 0
same changes to make like the forward function above
perhaps a problem with url rewriting ...
to retrieve the nid in arguments
I change this :
by
and that's work.
because the link in email is for example http://lwww.site.com/forward/emailref/node/10
it's the arg(3) to retrieve the nid
if you have an another idea ?
Comment #6
seanrLooks like no release had been made for 5.x-1.17 (though if you were using 5.x-dev, that'd work fine). I've made the new release now; please update to that. Sorry for the confusion.
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.