Hey,
I tried searching to find out if anyone else has had similar problems, but I couldnt find anything.

Basically, the <--break--> tag does not work with flexinode nodes, nor does it wrap the teaser at the value specified in admin/settings/node/

I have a node type called news, which is basically just a single textarea, and the title, but in /node and other views, it stop sthe text after the first or second line and presents the 'read more' link, ignoring the <--break--> delimiter entirely.

Is there any way to specify the cut point for the teaser on flexinode nodes?

Comments

darius’s picture

Status: Active » Closed (duplicate)

See the discussion at http://drupal.org/node/22788

Darius

igy-1’s picture

Status: Closed (duplicate) » Closed (fixed)

Ah, guess it's all taken care of then :)

Tried that code snippet and it didnt quite work, i've come up with another workaround though.
thanks

steffen’s picture

Status: Closed (fixed) » Active

This request should not have been closed, as this is a problem that goes way deeper into Drupal than simply cutting off the teaser. This problem also renders Excerpt, Superteaser, etc. modules unusable for Flexinode users.

Any way of making this compatible with Excerpt or Superteaser? As it is, Flexinode simply inserts the whole node into the teaser field, not matter what you chose.

mjs2020’s picture

I'm having exactly the same problem as steffen and it is giving me big problems with the taxonomy_menu module! Ho do I get control of the teaser?

mjs2020’s picture

Hi,
My problem was working with the taxonomy_menu module which was rendering the node list putting the whole node content for each node instead of the teaser due to the fact that flexinode stores the whole content into the teaser field in the database. I only have one content type created with flexinode so if you have more I suppose you should apply this to each type.
I also needed a separate filed for teaser input because the teaser could be different from content of the article. It's actually more like a summary of the article in my case.
I somewhat solved the problem and am posting some info that could hopefully help others get around this problem before flexiblock is fixed (i tried looking at the code but I'm a php newbie so I couldn't fix it... sorry!)
This requires you are using a phptemplate as your theme engine.

This is what I did:
- I created a flexiblock textarea named "short description" for my content type and then edited the node-flexinode-1.tpl.php
- At the beginnig of the file there should be something like:

if ($page == 0) {
....
}

- I removed what was inside and put my own design:

<div id="title"><?php print $title ?></div>
<div id="teaser"><?php print $node->flexinode_4 ?></div>

- flexinode_4 is my "short description" field I created, check the number in your specific case.
- then just before the closing bracket "}" i put in:
return;
So now the block looks like this:

<?php if ($page == 0) { ?>
<div id="title"><?php print $title ?></div>
<div id="teaser"><?php print $node->flexinode_4 ?></div>
<?php return; } ?>

You can obviously include more info and more themeing, it's up to you!
hope this is helpful for someone, feel free to give feedback if you have any

mjs2020

bryan kennedy’s picture

Does the patch submitted here (Textarea teaser not using node_teaser) address any of these issues? I am not familiar with the accessory modules that are mentioned in this post.

samc’s picture

Status: Active » Closed (duplicate)

Think so... Once that patch is applied we'll have real teasers, with node_teaser() from core doing all the hard work for flexinode.

http://drupal.org/node/47805