read more link on custom content does not show
mrgoltra - May 7, 2007 - 19:38
| Project: | Read More link (Drupal 6 and earlier) |
| Version: | 6.x-3.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
Good Day,
Module works great but does not work on custom content type (CCK). I created a custom content page and one of those fields is a text field to enter a message about 100 rows. Is there a away to have the read more link show up in the field?
Read more also does not show on teaser or custom content. I have tried several suggestion on forum but no good. Any help is very much appreciated.
TIA,
Mark
#1
I have a similar problem.
We create our own teaser block via cck. If we leave the template for the teaser alone, we get the "read more" link. But that's only because it pulls in the beginning of the "body" text as well as the "teaser" text.
If we edit the template so it will only show the teaser, not part of the body, we lose the read more link. We can add it in via the template, but its value is FALSE, which means it won't show in the teasers.
How do we go about getting an automatic link to the full text of the node, the way the title already does. A lot of site visitors don't understand they need to click the title and need some kind of obvious "read more" link.
#2
Anyone have any idea?
I know using cck to create the teaser is fairly common.
How are others fixing it so it only shows the teaser (not part of the body) and gives the "read more" link?
#3
Here's a solution I found that works if you're using contemplate. Add this into your teaser's template:
<br class="clear" /><span class="readmore">» <a href="node/<?php print $nid ?>" title="Full event details">Read more</span></p>
Of course you can change around the text as you'd like. I like mine with just a simple » Read more
Others like theirs to look different.
This doesn't solve the problem of the teaser and node not working together to see that the teaser should link to the node. But using the template, it forces it to do so.
#4
Same here. Most of our nodes are 'normal' (type = blog post) but some are a 'podcast' CCK type we created. The 'read more' suffix shows up fine on the teasers for the blog post content, but not on the teasers for the newly created content type.
To be clear, the teasers for the podcast content type appear as they should on the homepage and elsewhere ... it's just the "read more" that is not there.
#5
another issue that I marked as adupe of this, #120307: New content type
#6
The Read More module works only with the node's default teaser. Custom solutions for teasers like CCK cannot be easily implemented.
As new features will not be added to 5.x, I'll switch this to 6.x for possible development. (Of course, 6.x's much-improved teaser functionality eliminates most of the need for supporting custom teasers.)
#7
Marking as a duplicate of #297010: Inline placement of read more link in teaser with CCK fields.