I place all my theming templates in a subfolder in my theme directory. It would be great if the code could search for the template in subdirectories in the theme folder.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | print_template_folder.patch | 1.32 KB | eugenmayer |
| #8 | print_template_folder.patch | 1.25 KB | eugenmayer |
| #6 | print_template_folder.patch | 1.25 KB | eugenmayer |
| #5 | print_template_folder.patch | 1.25 KB | eugenmayer |
Comments
Comment #1
jcnventuraYes it would.. I will add this to the list of 'nice things to have'.
Comment #2
hefox commented#358838: Let print use the theme-api : using preprocess methods / placing of templates are the core-needs to cover with this
that would fix this
Comment #3
surgeonbor commentedThis module really needs to use the core theming tools. It's more important than just "nice to have."
Comment #4
eugenmayer commentedGuys stop claiming only - help implementing! Looking at the issue queue its just like "i want this - do it".
What about starting to help? This module is huge and actually needs some polishing or even more, but with this size .. its not capable to do be done alone.
Comment #5
eugenmayer commentedAttached a patch. Actually halfs the size of the code needed for scanning the patchs while adding full theme-api support. That means nodes are searched in every registered template path, that means in the current theme, then subtheme and every module using the theme_regestry to place its folder for scanning ( usual approach for modules to get involved with templates ).
Comment #6
eugenmayer commentedWell that last patch was garbage..i must be sleeping sorry
Comment #7
dawehnerCould we rename $value to $filename? This makes more sense for me.
we still call this function multiple times. its still not needed. yes this was in before, but why not fix it now.
could you please remove the whitespace errors/tabs in the code. This would be cool
Powered by Dreditor.
Comment #8
eugenmayer commentedDamn. attached the wrong patch above..
Comment #9
eugenmayer commentedsorry...just too confused. Finally the patch with the ideas of daniel
Comment #10
eugenmayer commentedi implemented it from bottom up, this patch should not be needed if this gets used http://drupal.org/node/358838#comment-3052810
Comment #11
kitsol commentedAfflicted for my bad English, do I seek to make print the documents with the topic by defect but impossible and not easy to know or put the code above? In which repertory. Help me Thanksi
Comment #12
jcnventuraIndeed, as EugenMayer said, this is invalidated by the (so much better) patch in #358838: Let print use the theme-api : using preprocess methods / placing of templates are the core-needs to cover with this