Closed (fixed)
Project:
Recipe
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Jul 2011 at 21:28 UTC
Updated:
16 Jul 2013 at 13:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
vadzen commentedI have the same issue.
Comment #2
taps7734 commentedSame Issue here.
Subscribing to this thread to see a fix.
Comment #3
taps7734 commentedQuick fix for this in current 7.x-1.x-dev.....
In recipe.module, I copied the code from lines 846-850
and added them to the section right above it so that it now looks like
Now it adds the description title and text in my node teasers.
Comment #4
efiniste commentedThanks Taps7734, that little snippet just worked for me too.
Steve
Comment #5
doitDave commentedSubscribed, needs fixing in the release. IMO this is a bug report, because to a new site builder it would appear clearly that a teaser is possible. So I hope you won't mind my changing the category. (Correct it if you feel different.) Thx!
Comment #6
jvandervort commentedNote this is not a full support for a trimmed teaser description, but it will add a full length description. Also if you want to turn off the description to return to the current functionality, the admin/structure/types/manage/recipe/display/teaser does work to turn it off. Also since this adds a theme function, you'll need to clear your caches.
Comment #8
jvandervort commentedTrying again.
Comment #9
jvandervort commentedComment #10
jvandervort commentedComment #12
jvandervort commentedComment #13
jvandervort commented#10: add-desc-to-teaser-1219260-1.patch queued for re-testing.
Comment #14
dcam commentedI'm a little worried about the recipe descriptions suddenly appearing in the teasers if someone decides to update the module. I guess since it's configurable via the Fields UI then maybe it's not a big deal. Maybe inconveniencing some sites is better than others not having the ability to include the description in teasers at all. What do you think?
Comment #15
jvandervort commentedSome impact, yes, but not too much. Overall I think the good outweighs the risk since we are moving toward the Drupal default. Of course if sites have really long descriptions and use current name-only front page list they will get a much longer display. We also can leave it in dev for a while. Folks upgrading to dev expect little changes like this.
Comment #16
dcam commentedEverything looks good to me. I added a quick test.
Comment #17
dcam commentedComment #18
doitDave commentedWhat #15 says. (Re-)establishing expected behaviour is no evil. And then, there is the famous "releaase notes" field. A site builder not reading what he is updating to is not in the position to complain about surprise effects. Fullstop. :-)
Comment #19
jvandervort commentedCommitted.