Override Node erases "Authored by" information
| Project: | Override Node Options |
| Version: | 6.x-1.9 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
I'm trying to use this module to allow users to change the "Publishing options": "Published" and "Promoted to front page" for their own content. While this works in itself, every time a user now edits his own content and saves it again, the "authored by" information becomes erased and is then displayed by Drupal as "Anonymous".
I've verified that this is indeed cause by "Override Node": If I disable this module, the "authored by" information is not erased when a user updates one of his nodes.
I also found a workaround: if I additionally give users the permission to "override blog authored by option", the "authored by" information is not erased.
A similar problem happens with "authored on", if the user has permission to change it. I noticed that when hitting "Preview", the "authored on" information becomes erased (blank).
#1
Thanks I will look into it and try to get a new release out ASAP.
#2
I can confirm this issue.
I wrote a patch for it. It checks whether $node->override_authored_by is set.
#3
#4
committed
#5
I'm not sure this is fixed. Installing 6.x-1.7 actually caused this problem to start for me. Since the April 7 dev release, anyone that I've given "override [nodetype] authored by option" permission to is having their posts saved as Anonymous by default, even though anonymous users can't create content on the site.
Hoping someone else can confirm the problem.
Correction: I originally marked this as 6.x-dev, but in fact the version is 6.x-1.7.
#6
#7
ok, I see the issue. I'll look into it.
Should just need a simple 'if' statement somewhere.
#8
Fixed in Version 6.x-1.8
#9
Should I re-open this issue or create a new one? I installed 1.8 last night from 1.4 (I think 1.4), and I am having this same issue. It doesn't appear to be fixed yet...
The ONLY option I have turned on, is "override post publish" (post being the content type I have setup)
Any ideas?
#10
Yep, this is not fixed. I can confirm this bug. I think I'll downgrade for now, to... 1.6?
#11
No point in downgrading: 1.6 was the version I originally reported the bug against.
#12
I was using this module for a while, and the bug came for me in a recent version. I only hope this gets fixed fast though.
#13
This bug does not appear to be limited to the "Authored by" information. Also the "authored on" information seems to be reset to the current date and time. The solution for me was to roll-back to 1.4
#14
ok, I had it working, so can we clarify the bug and I'll go back and check
Authored by field
- When the user does not have the "Override authored by" permission it gets set to Anonymous rather than their username (and on preview?).
- When the user does have the "Override authored by" permission it doesn't save the overridden value or their username (and on preview?)
Authored on field
- When the user does have the "Override authored on" permission it doesn't save the overridden value (and on preview?).
I'll try to take a look today, if you can feed back with specific bugs (from the list above, or not) that would be great, and patches would be better.
Thanks
#15
I hope this is all fixed in version 6.x-1.9
#16
i think that it should leave the 'created' ($node->created) value unaltered on save if "authored on" is hidden.
with 6.x-1.9 i get that parameter overwritten every time i save the node so created becomes => changed.
#17
I'm using 6.x-1.9 and I can confirm #16.
I changed line #259 from
$node->created = !empty($node->override_authored_on) ? strtotime($node->override_authored_on) : time();to
if (!empty($node->override_authored_on)) $node->created = strtotime($node->override_authored_on);#18
Please see follwing patch which is for fine for us when using 6.x-1.9
#19
Tom,
Thanks for the patch.
I hope to test it this week, and will then commit. If anyone else could test this would be great.
#20
Last posted patch works fine! Thank you, Tom Freudenberg!
#21
sub - sounds like my search for this may be easy once the commit is made - thanks to all for sorting this - one thing off the list - back to the list
#22
I have the same problem as #16 and the patch in #18 fixes it for me.
#23
Committed to branch DRUPAL-6--1.
#24
Automatically closed -- issue fixed for 2 weeks with no activity.