Closed (fixed)
Project:
Drupal core
Version:
x.y.z
Component:
comment.module
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Dec 2005 at 13:13 UTC
Updated:
2 Jun 2006 at 15:15 UTC
as I split up the comment megapatch, I feel that this is a duplicate, since i remember dries commenting on this issue somewhere. will mark as such if i find the other bug.
| Comment | File | Size | Author |
|---|---|---|---|
| comment.user.patch | 453 bytes | Wesley Tanaka |
Comments
Comment #1
Wesley Tanaka commentedI marked http://drupal.org/node/40566 as a duplicate of this bug.
Comment #2
killes@www.drop.org commentedI amnot convinced we need this patch. Storing the default will only bloat the database and will make changing the default not take an effect.
Comment #3
killes@www.drop.org commentedno way critical.
Comment #4
Wesley Tanaka commentedThe problem is that a "0" value gets (or got -- I haven't looked at this for a long time now) interpreted in two different ways.
In some cases it means "use the site's default setting".
In other cases, it means COMMENT_MODE_FLAT_COLLAPSED or COMMENT_ORDER_NEWEST_FIRST.
Newly registered users are getting sort and mode set to 0 without this patch, and that gets interpreted in the second fashion, even if the site default is set to something else.
Comment #5
Wesley Tanaka commentedI'm not sure what "bloat the database" means. Usually a "2" or a "3" takes up the same amount of space as a "0".
Comment #6
Wesley Tanaka commentedfixed as of comment.module revision 1.455
Comment #7
Wesley Tanaka commentedComment #8
(not verified) commented