This is a list where we can put everything in that we think that is wrong today ind D6
if theres a spot where you know the answer - then please add a link to it
The idea is that we collect all the stuff and create its as issues not just to bitch & moan
The big Bitch list of Whats wrong with Theming in Drupal 6
- To many class definitions from core - CSS/HTML markup is too verbose in general
*Hard to set a dynamic class to a block
-wheres that element at? - hard to backtrack to where an element is created from
Answer:
I would think that devel module's theme developer stuff would REALLY help with this. It's a great tool.
* why do we have a pseudo php template language in phptemplate?
we shuld just keep basic php:
if(foo == "bar"){
}else{
}
we are not that dumb ;)
Menu
* hard to add ad a class/id to a menu element
* hard to add a menu direct in the page.tpl
its a pain to get all the elements from a menu fx for a dropdown menu
* pain to split $menu and add remove elements
* $primary & secondary links? lets
$content
* Split $content
* cck
its a pain to get the $node->content['field_FOO']['#XXX'];
and even find the names it would be nice with a dump of all the fields, instead of walking through krumo($node)
Answer:
it's always $node->content['field_name']['#value']. If you'd like to explore via krumo easier just krumo($node->content) and that should be a nicer list.
* seperate the field order from the backend order in different instances (teser, node, frontpage ...)
* $content in both page.tpl & node.tpl
* pain to split $links and add remove elements
* pain to get taxonomy terms for a single vocabulary
* $picture? #fail should be called $user_picture
Note: According to the CCK (drupal 6) and fields (drupal 7) developers you can use $FIELD_NAME_rendered to get to the information right now.
Answer:
That's a great point can you post that to [#382870]
* only 2 instances
* in node.tpl.php, it is very hard to figure out where the node is being rendered (in a block? in a view? which one?). This sucks when you want the same node to display differently in different places.
* $var for a node.tpl
classes
* class="title" huh ?
* a class that cant be argumented for should not be there
* impossibleto know if a class is importent for a module to funtion - we should have a
*css from modules demands for a ton of overwrites
* system css is a pain in the ass
** system.css mixes "sensible defaults" for things like list margins and inline links with absolutely essential rules for collapsible fieldsets, drag-and-drop UI elements.
* control the load order of $styles
- order of css in styles
- in a sub sub theme the parents css is loader AFTER the kids css :(
forms
* a pain in the ass... unleass you really understands the form api
something like theming the login form should be easy to do ... and not lile it is today - wheres its totally impossible unless you end up writing custom php stuff ...