Don't miss out Virtual Happy Hour this Friday (April 26).

Try our conversational search powered by Generative AI!

Wrong page url in conversion path report

Found in

Release 7.5 CMO

Created

Dec 06, 2013

Updated

Feb 03, 2014

Area

Falcon/CMO/Campaign Monitor

State

Closed, Fixed and Tested


Steps to reproduce

  1. Install EPiServer 7.5 CMO on site with Alloy templates
  2. Create a campaign that includes Alloy Track or Alloy Meet or Alloy Plan pages
  3. Create a Conversion path with any of those pages and save campaign
  4. Open campaing Report page
  5. Open Conversion Path tab in the report
  6. Click on Show details link in order to see the conversion path details
  7. Click on Alloy Track (or Alloy Meet or Alloy Plan) page

OBSERVED: Error page is displayed (see below)
EXPECTED: The page should be displayed on a site

NOTE: Reproducable only on WebForms. Works fine on MVC site.

Page could not be loaded

The link you specified does not work. This may either be the result of temporary maintenance or an incorrect link.

Detailed error information (authorized by permissions to functions)

Error occured 12/5/2013 11:38:09 PM
User IP 10.99.11.141
User Agent Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36
Url http://10.99.11.196:17000/Views/Pages/ProductPageTemplate.aspx?id=13&epslanguage=en
Referer http://10.99.11.196:17000/EPiServer/CMO/CMConversionReport.aspx?campaignid=1

ContentData Cast. The requested type EPiServer.Templates.Alloy.Models.Pages.ProductPage is not compatible with Castle.Proxies.StartPageProxy

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.InvalidCastException: ContentData Cast. The requested type EPiServer.Templates.Alloy.Models.Pages.ProductPage is not compatible with Castle.Proxies.StartPageProxy

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 

[InvalidCastException: ContentData Cast. The requested type EPiServer.Templates.Alloy.Models.Pages.ProductPage is not compatible with Castle.Proxies.StartPageProxy]
   EPiServer.Core.ContentDataExtensions.Cast(ContentData content) +234
   EPiServer.Templates.Alloy.Views.Pages.ProductPageTemplate.OnLoad(EventArgs e) +53
   System.Web.UI.Control.LoadRecursive() +71
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178