Quote from: zolee1 at Oct 29, 2006, 07:42 PM
I, however noticed that the weblink function uses a 302 (permanently moved) redirect. Modx being an SEO friendly CMS, I would suggest to change this to 301 redirect. Search engines don’t like 302s, so this might trigger a negative effect in ranking.
This is fixed in the latest 0.9.5 release candidates; they are returning 301 as they should now.
Quote from: PaulGregory at Oct 29, 2006, 08:08 PM
However, I am confused as to what is going on with weblinks. If I understand correctly, you added functionality to use numbers instead of names so that you can have easily documents referenced in the tree twice. Then Wayfinder came along and ignored this. Now you have another hack that saves names instead of numbers (but with the benefit of being able to click and pick pages).
Is this new hack in 0.9.5, and should it be?
Wayfinder is handling the detection for the 0.9.5 release, so interpreting web links by directly reading the content is at the moment, the responsibility of each component that uses it. This will change, as in the future, the content of a web link will be able to process any kind of tag; but I don’t want to introduce an interim change and confuse users more with that already planned. I’d rather wait until we do have a central point of code which handles this responsibility; i.e. post-0.9.5.
Quote from: Cassiel at Nov 09, 2006, 02:56 PM
Now that we can set more attributes (like the target) on 0.9.5, weblinks are more useful! I was wondering if there is a way to get/use the external URL (for external weblinks of course) directly. I’ve read we can already do that already but only in Wayfinder.
In case I wasn’t clear enough, I have a weblink pointing to an external URL ’http://www.mozilla.org/’ which id is 15. If I use [~15~] in a document I’ll get an internal MODx URL ’/index.php?id=15’. How do I get the external URL directly? I know that the internal URL will trigger a redirection, but as far as I’ve read here, it’s not so SE friendly.
Or is it time to write my very first own snippet? 
You can use a snippet for now to do this, you basically just need to see if the content of the web link is
numeric an integer, and if so apply the makeUrl() API function to it.
In the near future there will be ways to easily differentiate web links that are 301’s and should show the content parsed into a URL when used as an [~id~] tag, and those that should send 302’s or simply forward to another pages content using the web links internal URL when interpreted. And it will be easy to define other custom web link types if the need should arise, without changing anything in the core code.
MODX Staff
