A recent change to the node module (see http://drupal.org/node/view/6140) has broken 'read more' links in flexinodes . Attached patch fixes the problem.

Great work by the way.

CommentFileSizeAuthor
#6 read_more_forced2.patch992 bytesAnonymous (not verified)
#4 read_more_forced.patch659 bytesAnonymous (not verified)
#3 read_more.patch608 bytesAnonymous (not verified)
#1 drupal_4517 bytesAnonymous (not verified)
drupal_3517 bytesAnonymous (not verified)

Comments

Anonymous’s picture

StatusFileSize
new517 bytes

Sorry, patch didn't attach properly, so here it is...

jonbob’s picture

Doesn't this patch end up filtering multiple times? I'll look into it some more...

Anonymous’s picture

StatusFileSize
new608 bytes

I've attached a revised patch which doesn't filter multiple times.

Anonymous’s picture

StatusFileSize
new659 bytes

Following on from the previous post...

Are flexinodes supposed to always have a 'read more' link (see lines 520-521 in the 4.4.0 version of the module) or is based solely on the description field?

If they are supposed to always have a 'read more' link, the attached patch is replacement for the previous one with and additional line which forces a 'read more' link.

jonbob’s picture

Assigned: Unassigned » jonbob

The forced "read more" link is a band-aid for the problem that without forced links, if the teaser matches the description, there is no way to get to the additional defined fields. The correct long-term solution is probably to have some system for customizing how teasers are generated from all the fields, not just the description fields. I will look at the submitted patch.

Anonymous’s picture

StatusFileSize
new992 bytes

Sorry, previous patch wasn't filtering the node's description, attached patch does...

killes@www.drop.org’s picture

Applied.

Anonymous’s picture