Closed (fixed)
Project:
Drupal core
Version:
5.x-dev
Component:
profile.module
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
25 Dec 2006 at 22:46 UTC
Updated:
13 Jan 2007 at 08:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
dwwwhere's the patch? ;)
Comment #2
ChrisKennedy commentedBah
Comment #3
dwwyup, that works. the only problem is that core still displays your "profile" even without the profile.module enabled. in that case, we're also not loading the profile.css, so you get the default
<dt>stuff (no bold, indented info). maybe we should include profile.css in user_menu() when we know we're looking at a user page? something like the attached patch?Comment #4
ChrisKennedy commentedAh good point, I didn't think about that case. Updated patch works even with profile.module disabled.
Comment #5
dries commentedThat last patch doesn't cut it for me. It hardcodes a dependency between user.module and profile.module. If user module needs something that should be available when profile.module is disabled, that should be part of user.css not profile.css.
Comment #6
dwwgood point. ;) after further consideration (and a brief discussion in #drupal on IRC), here's what i've come up with:
this patch does that. we just move all the contents from profile.css into user.css, remove the part of profile.module that's including profile.css, and we're done. it's hard to roll a core patch that removes a file, so to actually apply this patch correctly, you need to:
thanks,
-derek
Comment #7
ChrisKennedy commentedEven better.
Comment #8
dries commentedCommitted to CVS HEAD. Thanks.
Comment #9
dwwwhoops, "//" isn't a valid .css comment. thanks to merlin for pointing it out.
Comment #10
dries commentedCommitted to CVS HEAD. Thanks.
Comment #11
(not verified) commented