Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
watchdog.module
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Apr 2006 at 14:29 UTC
Updated:
15 Jul 2007 at 21:18 UTC
Jump to comment: Most recent file
Comments
Comment #1
Stefan Nagtegaal commentedI don't think this is the right way todo. IMO it would be far better to wrap every page in a div with a unique id, rather than doing it this way for ever element.
Maybe we could discuss this here so we (I?) can/could prepare a patch for drupal once HEAD is open for development again..
Steef
Comment #2
simeSounds fine by me. I just wanted to put it out there while the hack was fresh in my mind. :-)
Comment #3
Tobias Maier commentedI hate it that we give everything an id
wouldnt be a class enough?
Comment #4
Stefan Nagtegaal commentedClasses should be anough if the page content will be wrapped in a div with a unique id. but why do you hate the usage of id's?
Steef
Comment #5
Tobias Maier commentedfor example you create a dashboard-site and put in for example two aggregator-pages or two profile listings...
and what do you have?
an id-conflict
this is followed by my second most hated problem: hardcoded html
I think that ids should only be used if reallyreallyreally necessary (maybe javascripts need it - but i'm no js-coder so i dont really know)
and directly in themes and not in modules or in drupal core
Comment #6
simeThat's an interesting case you present, I hadn't thought about that possibility.
Comment #7
sime.... except when would you have two watchdog tables for the one site? :-/
Comment #8
keith.smith commentedNeeds rerolling to accommodate 6.x watchdog/dblog changes, at the very least.
Comment #9
simePatch rerolled.
I again considered the request for a classed div, but I don't see this being necessary. There is only one table on this page. You'd have to write your own page to gain multiple tables and then you'd obviously add your classes there.
Comment #10
simeComment #11
dmitrig01 commentedthis works and well too
Comment #12
webchickSmall coding style error.
Comment #13
meba commentedseems ok
Comment #14
gábor hojtsyComitted, thanks!
Comment #15
gábor hojtsyComment #16
(not verified) commented