Loading...

All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).

Ticket #249 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Wrong url's in enterprise solution

Reported by: andreas.nicolaisen@… Owned by: oyvind@…
Priority: blocker Component: Newsletter
Keywords: Cc:

Description (last modified by simon@…) (diff)

The problem is as follows:

We have an enterprise-solution with three sites. Say www.firstsite.com, www.secondsite.com, www.thirdsite.com.
We then have a newsletter belonging to www.firstsite.com (living under this startpage). The newsletter contains url's pointing to pages on www.firstsite.com.
ie http://www.firstsite.com/about/. These urls are added with a LinkItemCollection, and is written out in the newsletter with the following code:

<asp:Repeater runat="server" ID="uxFooterMenu" >
<HeaderTemplate><tr><td style="padding:0 0 5px 14px;"></HeaderTemplate>
<ItemTemplate>
<a style="color:#008aaf;" href="<%# ((LinkItem)Container.DataItem).GetMappedHref() %>">
<%# ((LinkItem)Container.DataItem).Text ?? ((LinkItem)Container.DataItem).Title %>
</a>      
</ItemTemplate>
<FooterTemplate></td></tr></FooterTemplate>
</asp:Repeater>

If I choose to preview the newsletter, all the links are ok. If I send a test via the test functionality in the module, all is ok.

But, if I send the newsletter to a mailinglist, all the links are suddenly changed, and can appear like http://www.secondsite.com/about/. (Which is a link that do not exist)

I have also tried adding a property on the newsletterpage "BaseUrl" to force the correct baseurl as documented in the revision 600 by Steve without luck.

Change History

comment:1 Changed 6 years ago by simon@…

  • Description modified (diff)

(Just formatting for easier reading - hint)

comment:2 Changed 6 years ago by permagne@…

  • Status changed from new to closed
  • Resolution set to fixed

Closing ticket as this has been fixed in changeset:2077 and changeset:2078.

Note: See HelpUser/Tickets for help on using tickets.