Posted by axle_foley00 on June 2, 2008 at 7:24pm
| Project: | RelatedContent |
| Version: | 6.x-1.0 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hello,
I'm using both the Related Content module and Simplenews module together to pull articles from my Drupal site and send out via a E-mail Newsletter. Unfortunately, when the message arrives to the recipient via email the links (ie. Title and Read more) do not contain the domain name, but rather only the absolute path from the Drupal Root folder. (e.g. instead of http://www.example.com/node/123 it gives /node/123).
I did see the following post, http://drupal.org/node/43815 and tried what it said, however it doesn't affect the Related Content nodes being added.
Is there any way to get the nodes to show use the full URL?
Comments
#1
I'm interested by a solution too ... It's a very nice combination (simplenews and related content) but if we can't send absolute urls in the newsletter ... there are no interests ...
#2
I got this working by simply edition the node.tpl.php for teasers and making sure that the template file output full urls with domain. RelatedContent isn't doing anything about the urls, it's just passing the through as is in the preformatted teaser.
#3
Could you post your code so others don't have to figure it out from scratch?
> RelatedContent isn't doing anything about the url
Changing to a feature request that RC does "do something", perhaps an option in the config screen: "Output full URLs for emailing"
#4
I'm also having this problem with 6.x-1.0 beta 1.
How do i get node.tpl.php to output full URLs?
#5
This has been fixed in latest version of D6. You can turn absolute links on per content type in the settings of relatedcontent. (screenshot).
#6
#7
Automatically closed -- issue fixed for 2 weeks with no activity.
#8
This doesn't work for me, I've selected yes under Create absolute links but it doesn't work it still sends the newsletters with relative URLs, any ideas?
#9
Actually it was a problem using content template but i've fixed it now.