Closed (fixed)
Project:
Lost & found issues
Component:
Twig templates conversion (front-end branch)
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
25 Oct 2012 at 19:42 UTC
Updated:
31 Dec 2012 at 16:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
artofeclipse commentedComment #2
vlad.dancerWorks fine! Thx!
Comment #3
podarok#1 commited / pushed to front-end
Thanks!
Comment #4
c4rl commentedDon't we need to remove theme_filter_admin_overview from filter.admin.inc?
Comment #5
c4rl commentedNevermind, I didn't realize that Drupal breaks if we remove these since only one theme is using Twig as of now.
Comment #7
artofeclipse commentedre-implements to reflect the new changes on table theme.
Comment #8
joelpittet@artofeclipse the table stuff I did shouldn't have broke this, it should work with and without twig just the same as before. I like the intent to help out the Attribute stuff but the way you had it before was closer to what it should be, IMO.
You should be able to call theme('table', $variables['table']) from this preprocess function or from twig itself instead of having to directly call the preprocess and include in the twig file. Someone was telling me they prefer to have theme() in a twig file vs the include.
I will see why this is breaking in the mean time but just wanted to get you on a slightly better path in the meantime:)
Comment #9
joelpittetFormats doesn't seem to be getting 'configure' and 'disable' anymore as separate elements & columns due to that little popdown operations thing from views. It's just a 'operations' key now.
becomes
and remove
, 'colspan' => 2from the Operations header.Comment #10
artofeclipse commentedThanks for this, but as I recall jenlampton said it should be something like this #1830192: Convert theme_taxonomy_overview_terms to twig. and I didn't have the time to catch up with the new changes and the discussion that happens on the this initiative. anyway thanks for directing me :)
Comment #11
joelpittetAh yeah so your splitting out the variables for the template is good way to go. Just the operations thing and no more {% include %}
The reference I was to lazy to find the first post...
http://drupal.org/node/1848116
Comment #12
artofeclipse commentedfixed in this patch :)
Comment #13
joelpittetLooks good! thanks artofeclipse.
Comment #14
steveoliver commentedI'll finish this up.
Comment #15
steveoliver commentedI'll commit this if someone else wants to give it another look.
Comment #16
steveoliver commentedThis issue link may not be appropriate. I'm not sure I understand what issue we want to reference, but it seemed to me we were talking about calling theme() from within templates, so th
ise template could call theme('table').form...children...same diff. I don't think there was supposed to be a 'pager', though. See theme_filter_admin_overview().
EDIT: s/this/the template/
Comment #17
joelpittetCleaner, looks good. A bit arbitrary what things we pass to the twig templates and what we don't.
themetable! ftw:) ... well probably not but it sounds like a word. Oh man it's late.
Comment #18
steveoliver commentedLooks good -- tested to make sure we didn't break anything for non-Stark themes. Seven looks great.
Committed in 6d65b6b6b.
Comment #19
steveoliver commented@todo: Make this table responsive?