Doesn't works with "CCK Blocks Module" and "nodeID block-view"

CCK Blocks is doing things at a field level, so outside of the scope of the module. It piggybacks the entity view modes for field formatting info only, (afaik)

Is your block set up to use the teaser view and to show links? If so, send me an export and I can take a look. Otherwise, it to is outside of the scope of the module.

The read more is only a concept for the teaser view, but I could look at making this configurable to look at other view modes as well. As soon as you move to a non node view mode then this module is not the right module for the task.

Done!

Any entity that supports entity_url() and entity_label() is now supported. Only shows up if there are more than just a small core group of unsupported modes: default, full, search_index, and token (or similar)

Also allows customisations of the link, similar to Read More Link, but probably less featured to that module (bar minimal set of features were added, about 10 or so)

Checkout the latest dev version to try this out (on a dev server or live with backup - just in case)

I guess I wasn't clear enough in #1.

That module specifically displays individual fields from the node using field level hooks, and this module helps at the entity level. They do not play together.

The same goes for views. A field display uses fields, not view modes, so this module can not work there either.

I guess the easiest way to think of this is that the entity (aka node) is a game station (XBox) and the fields are the game disks, and this module is the memory card. Using field displays is similar to taking the disk out of the machine to show your friends, which makes the memory card useless. To get use of of the card, you have to be playing the game itself, in the machine.

(Apparently it takes 15min to explain this topic, rather than a random 2 minute analogy off the top of my head)

When creating the view, use settings similar to this:

Of the display settings, only teasers work by default. If you added additional view modes, then these could be used. The titles are views module internal db listings and full display is disabled in this module as this view mode is the one that you compare to, so full always equals full. Fields do not work.

i.e. I'm talking about this bit.

And yes, I looked at the export you supplied, this was fields based, so it does not work. And yes, I tried the above example and it worked perfectly with the module :)