Hi there,
I am wondering if it would be possible to make a modification such that the date of a post (the colored bubble with the date in it) is located directly left of the topic in the list of posts on the front page. Just as it is if one is viewing a node directly.
I tried to look around in the theme files to see if I could figure out where the code is that generates the location of the date, but not sure if I found the right spot. Would it be possible for you to point if out for me, and I'll have a try myself to see if I can adjust it the way I would like.
If its not possible I will be using the theme anyways. This is just a minor detail. I would like to thank you for your work with this theme. It is really comprehensive!
Best regards,
Andreas
Comment | File | Size | Author |
---|---|---|---|
#8 | node.tpl_.php_.txt | 6 KB | Matt B |
Comments
Comment #1
Danny EnglanderHi, That's probably a good idea, the theme would have a more uniform look anyway. I'll see what I can do, I had a quick look and I'd probably need to restructure the way node.tpl.php is laid out. I'm not sure when I'll have time for this but hopefully within the next week or so.
Comment #2
AndreasT CreditAttribution: AndreasT commentedHi there,
Looking forward to it. Thanks for you efforts!
// Andreas
Comment #3
anbela CreditAttribution: anbela commented...
Comment #4
AndreasT CreditAttribution: AndreasT commentedHi there, have You had any chance to look into this topic since last time?
Comment #5
Danny EnglanderI've not had much time to work on this, I'll see if I can get to it within the next few weeks.
Comment #6
AndreasT CreditAttribution: AndreasT commentedHi, ok, looking forward to it :)
Comment #7
AndreasT CreditAttribution: AndreasT commentedbump
Comment #8
Matt BUpdated node.tpl.php file attached (goes in /sites/all/themes/bamboo/templates/) - remove the /txt from the file name.
I would create a patch, but I've made other modifications as well... might need some css tweaks as well...
Comment #11
Danny EnglanderI ended coming up with a fairly trivial solution to this that had the least impact on the existing code base. The fix is in both 1.x and 2.x dev.