ways to make the ticker work

Documentation is not so clear

the ticketboo ONLY SHOWS nodes NOTHING else
but it has different ways of picking these nodes

1) specifying node ids (nodes have to have teasers otherwise nothing displays)
2) specifying content type i.e. story (those nodes have to have a valid teaser otherwise nothing displays)
3) specifying term ids is used to find nodes assigned to those tids (if those ids have no nodes assigned or their teasers are empty nothing displays)

hope this helps

support tickets can never be critical this is not a paid support forum !!

yes i agree with Giorgosk,

the ticketboo ONLY SHOWS nodes NOTHING else
but it has different ways of picking these nodes

you need a node id value to put in a textarea selection node
block configure.

for alternatif. maybe you can install pathauto module, actually this is for URL aliases management, but for me it's really helpfull to find the nodes id value from my content easily by this module.

after you install the pathauto module you go to administer >> site buiding >> URL aliases
and then you will see the node id from your content. you get the node id value and then put it on in your ticker1 block configure node selection.

i have also modified the .module.
so when the content scrolling in block it will be show the strong title link and body
from the default code line 217

$ret .= '<div id="ticketyboo_'.$delta.'_'.$i.'" class="ticketyboo_teaser" style="'.$item_style.'">';
$ret .= $node->teaser;
$ret .= '</div>';

to be

 $ret .= '<div id="ticketyboo_'.$delta.'_'.$i.'" class="ticketyboo_teaser" style="'.$item_style.'">';
			$link =  l("<b>".$node->title."</b>", "node/".$node->nid, array('attributes' => array('title'=>$node->title), 'absolute' => TRUE, 'html' => TRUE));		
$ret .= $link; 
$ret .= $node->teaser;
 $ret .= '</div>';    

i hope this usefull

Thanks nubiebanget, I used your sugested change and it does exactly what I want.

I started off listing 5 nodes by node number, it scrolls 3 of them and shows blank for the other 2, I cannot find any significant difference between the nodes in question, the are all of the same node type etc. Does any-one have an idea why this is?

Solution found: When the nodes are listed in the block configuration, the list must start and end with a comma.

ie. it must look something like this:

, 951, 891, 874, 873, 872,

rather than like this:

951, 891, 874, 873, 872

The second example does not display the first and last nodes listed.