Previewing an issue shows bogus date

confirmed again on drupal.org, and a local 4.7 test site. to reproduce, you must do two things:

1. have your theme configured to display post info on issues
2. attempt to preview an issue submitted by a user without "administer nodes" permissions.

i'm hoping that my patch for #29105 will fix this, too, but i don't have time to test it right now. i'll report back later once i have a chance to look closer.

drat: this is a separate issue. my other patch doesn't help this. the reason is that in this case, we're dealing with the original issue (which is a first-class node), not the issue followups (which are these weird quasi-comments that are neither comments nor nodes). my patch in that other issue fixes the quasi-comment previewing, but this bug remains. i think i know why: we're probably just not setting the creation date stuff at the right place. probably won't be too hard to fix. i'll work on it when i get the chance (probably not in the next few days, unfortunately).

I can confirm this issue here on drupal.org too (I see January 1, 1970 - 01:00), where the 5.x version is presumably in use.

local testing with the latest version of the module, i can't repro this. please reopen if necessary.

This still happens on d.o (for me at least). However, I'm guessing this is related to http://drupal.org/node/175743 which appears to have been fixed recently for Drupal 6 and is not a bug specific to project issue tracking.

@aclight: duplicate means this exact bug was already reported earlier. in this case, there might be a similar bug in core (so it seems, given a quick skim of that other issue), but this particular bug in project_issue needs its own patch to be fixed. moving this back to active, so we can fix it.

@hunmonk: i bet you're testing as a user with 'administer nodes' perms. try again using the d.o testing profile, submit an issue as the "auth1" user, and preview it. i clearly see the bug (though I haven't updated my local workspace in a week, and I see you've been busy). ;)

@dww: i have been able to reproduce the problem now, but it i can repro for any node type.

this is not a project issue problem. the bug is in node module, specifically in node_object_prepare(). reading http://drupal.org/node/175743, this issue rightly classified as a duplicate IMO.