Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
theme system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Oct 2014 at 12:56 UTC
Updated:
12 Nov 2014 at 23:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
derheap commentedRemoved classes and ids.
Copied the template to classy/templates/taxonomy.
There are some lines of CSS in the module, but they seem to be needed by the taxonomy overview form, so I left them alone.
Comment #2
derheap commentedComment #6
davidhernandezI don't think we need to comment that there are no classes by default.
Also, the blank line is not needed on line 30 before the div where the term id is removed.
Comment #7
derheap commentedMade the changes according to #6.
And we have to keep the attributes on the div (
<div{{ attributes}}>).Otherwise RDF-Support (and maybe other modules) break.
Comment #8
davidhernandezThe templates should go into the root of the templates folder, not a subfolder.
Comment #9
derheap commentedOK. Moved to the template to the root template folder.
Tagging cssbanana, as there are some lines of css, which might be needed for admin.
We should investigate in a followup.
Comment #10
mortendk commentedComment #11
xen commentedComment #12
xen commentedNew template file is properly used.
Comment #13
xen commentedComment #14
davidhernandezI'm universally setting all the phase 2 issues back to needs review, because we're missing some things. Please double-check if any removed classes are being used in javascript. It is best to test the affected template using Stark to make sure nothing is broken.
Comment #15
mortendk commentedno .js is effecting the taxonomy terms templates.
Comment #16
alexpottThis fix is also applicable to the template being copying to classy. Let's keep them in sync.
Apart from that I can confirm the the classes added here are not used in any css or js.
Comment #17
derheap commentedOK, I will fix in the classy template too.
Can I remove the css classes, as they are not used?
Comment #18
alexpottI don't think we should be removing the classes. But I'll leave that to the likes of @davidhernandez, @john_albin or @mortendk to make the call.
Comment #19
davidhernandez@derheap, are you referring to the classes in the Classy copy of the template? If so, no, those classes stay. The only classes that would get removed are in the template kept in the taxonomy module.
Comment #20
derheap commentedFixed classy template according to #16.
@davidhernandez
Yes, I was over ambitious. I left them in.
Comment #21
mortendk commentedlooks good to me. and yes we fist begin to hammer on classes when they are in classy
Comment #22
alexpottCommitted 0ba69d7 and pushed to 8.0.x. Thanks!
This normal task was committed due the fact the banana consensus received per approval wrt to #2350615: [policy, no patch] What changes can be accepted during the Drupal 8 beta phase?
Comment #24
dcrocks commentedWhy wasn't taxonomy-term.html.twig placed in the 'templates' sub-directory of classy, as the others were?
Comment #25
davidhernandezThere shouldn't be any templates going into subdirectories. We will address that later. See #2349559: [meta] Discuss the organization of subfolders in Classy
Comment #26
davidhernandezOh I see. That went into the root. That's a problem. We need a quick fix.
Comment #27
mortendk commentedquickfix moving the taxonomy-term.html.twig into /templates
Comment #28
mortendk commented*sigh* lets try again with the correct file
Comment #29
lauriiiComment #30
alexpottI'm no longer committing on-issue followups since there cause issue management problems. For example, this is now a bug and not a task. Please open a new issue to do the move.
Comment #31
lauriii