Should to produce node alias or use internal relative url's (node/xy)?

The decision to use absolute url's was made because a drupal administrator can make changes to pathauto settings and rebuild the URL alias table, breaking links. (Drupal.org uses absoute node references frequently for the same reason, I believe.)

Unless you can explain how it is not dangerous to use url aliases when those aliases may change, I'd like to call this Not A Bug and propose people use http://drupal.org/project/pathfilter as GiorgosK suggested.

Sorry but I'm using
Pathauto 6.x-2.x-dev
TinyMCE Node Picker 6.x-2.0-beta4
Non-Root Site: My Drupal installation is in server root subfolder, like www.mydomain.org/dev
and Node Picker insert links as their alias!
Whats up? It should insert internal relative path like "node/xy", isn't it?
Thanks!

not absolute but relative path, sorry!

I'm sorry but you have to explain exactly what you mean.

I think it should use the internal link in format node/nid instead of the alias!
When I select a node now, it's always taking the alias, as soon as the alias changes, the link will no longer work!

----------------------------
JGO | http://www.e2s.be
----------------------------

JGO: I understand that can be a problem. A better solution would be to allow integration with some kind of input filter that translates [link:node/nid] (for example) tokens to real paths on node load. To use the node/nid path is in my opinion not an option as that would produce "content duplication" that would hurt google ranking.

JGO: You could achieve the requested behavior by modifying the nodepicker_nodes view.

indeed, I just discovered that.
It works ok now! :)

Creating now an "internal:node/[nid]" link and using the path filter module. Works great these 2 modules together!

----------------------------
JGO | http://www.e2s.be
----------------------------

Superb. Do you think further support for integration with Path filter is necessary?

Not really I think atm, maybe you could give the user some options to create this with the configuration when path filter is detected.
But for me now I know the solution, it's easy enough though.

I'm marking this as closed. The original poster has not provided further details and a solution for integration with Path filter has been suggested.

Sorry blixxxa for reviving this issue, but can you be kind to elaborate further on how to go about doing this:

"You could achieve the requested behavior by modifying the nodepicker_nodes view."

My goal is the same as the rest, instead of inserting the alias, I would like to insert just "node/xx", so that I don't have to update the link each time the alias is changed. I'm using Global Redirect to direct all node/xxx requests to their correct aliases so there is no need to worry about Google penalizing duplicate links.

Sorry blixxxa for reviving this issue, but can you be kind to elaborate further on how to go about doing this:

"You could achieve the requested behavior by modifying the nodepicker_nodes view."

My goal is the same as the rest, instead of inserting the alias, I would like to insert just "node/xx", so that I don't have to update the link each time the alias is changed. I'm using Global Redirect to direct all node/xxx requests to their correct aliases so there is no need to worry about Google penalizing duplicate links.

P/s: Sorry for the double posting too. I meant to change the status of this issue to active in the second time.

In the README.txt file, under the headline "How to integrate with Pathfilter", there is a link to a forum post describing how to set it up to have your links
"node/xxx" instead of the path alias.

Maybe I should set up a handbook page for this module.

Thanks blixxxa! The problem is solved!