OK, I've got to the nub of the problem.

Basically, it's like this : when the news module asks for the Url to be generated by the friendly url provider, it provides two basic pieces of information : the Tab and the required path.

The required path looks like default.aspx?tabid=xxx&newsid=yyy.  This is what generates the right path, including the news id parameters.  The Tab, however, that is passed in is for the home page.

The Url Master module expects that the Tab passed in is for the destination page, not the source page - which is why the Urls come out looking like they do.

I'm attempting to work out who is right and who is wrong here, but that's going to take some time to work through, and will require a new version from either Philipp or me.

In the meantime, I think the best thign for you to do is to manually craft up your Urls by manually constructing your template.  You could do this by putting in a url like this:

<a href="/case-studies/newsId/[newsId].aspx">Read More...</a> instead of the [DETAILLINKURL] token.

I installed it with the version you sent me, then watched every call that came into the friendly url provider.  The one that came in for the newsid/1/ call used the source tab rather than the destination tab.  It originates from the [DESTINATIONLINKURL] token in the 'FirstItem' template.

Hi folks,

any progresss in this issue?

I am experiencing the same problem with Ventrian's News Articles Archives.
When a module instance is placed on the page where the main module resides, all is fine, but when News Articles Archives is e.g. placed on the home page it does not work, because the links created are directing to the home page.

Example:
This is how the links should be, when the NA Archives is placed on the Home page
http://www.wolfsbau.de/NewsundBlogs/articleType/AuthorView/authorID/309/joe.aspx

This is how the links effectively are (not working) when the NA Archives is placed on the Home page
http://www.wolfsbau.de/Home/articleType/AuthorView/authorID/309/joe.aspx

Hope this helps to work the problem out.

Cheers,
Joe

P.S.: Did i mention that this is quite an urgent problem, as it hurts all my production sites