Possibly a duplicate of this 6.x issue: http://drupal.org/node/478922
To recreate:
Create a piece of content with a link field using a relative path such as: inventory
Create a view using the link field and another field from the same piece of content, I am using an image field.
Exclude the link field from the display and set formatter to URL, as plain text.
With the second (in my case image) field check Output this field as a link and use the replacement pattern for the link [field_link] in my case.
The basepath for the link now appears to be doubled. My site is running from a drupal supdirectory so paths should come up as drupal/inventory in this case the path will appear as drupal//drupal/inventory but on any standard site I assume the double slashes would at least appear and break the link.
Comments
Comment #1
jamesrward commentedPer the note on the project page I upgraded to the dev version and the problem appears to persist.
Comment #2
dqdjamesrward, Thanks for trying both versions out as asked for on project page, as this helps us to file errors. Sadly I have to confirm that the code for views implementation doesn't look like views is fully integrated yet. But I have to work thru' it sequently, so I can't tell you now where to start or if it si a link issue really.
If you can point out more details or have any patch, I will play around with it to come closer. This would help me a lot, because in the moment I try to remove any old @ToDo's for a final 7.x-1.0.
Comment #3
jamesrward commentedI guess this is a question of behaviour. Should the URL, as plain text formatter provide anything other than the raw text that was entered into the url field? Do we need a formatter that is called Raw url text that provides just the url text? This would effectively be the same as using a text field in the content type except it would go through the url validation routines provided by link. In my case this is all I am after.
Comment #4
dqdjamestward, I've tried to reproduce the issue with no luck. Can you provide a step by step on link, views and drupal installation?
thanks.
Comment #5
dqdI'll close this issue due to inactivity for 12 years and upcoming EOL of Drupal 7 in January 2025. While the project version for Drupal 7 will keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. Thanks for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority to "Critical" here.