Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Short answer is that both items (blog and mvc player) are fighting over the path portion of your URL. They both expect they own the path into bit to do routing.</p> <p>Example: <code>/en/Blog</code> <code>/2011/11/29/Chamonix-To-Courmayeur-Skiing-Day-Trips</code></p> <p>The /en/Blog portion is routing you to the page hosting your blog, while the rest is path info that is passed along to any functions you may have hosted on the page. Since the path is "one thing" there is no distinction whether this string is intended for the blog function or the MVC Player function. This is what is creating the confusion.</p> <p>Provided you wish to leave the blog as is you can work around this issue in two ways:</p> <ol> <li>Move the feature you have in MVC Player to another function provider, like Razor Functions</li> <li>Change the MVC Player so it does not pass the path info along to you MVC controller. </li> </ol> <p>The second workaround can be done quick and dirty by editing <code>~/App_Code/Composite/AspNet/MvcPlayer/Player.cs</code> and commenting out this line (line 57)</p> <pre><code>Path = PathInfo; </code></pre> <p>Before you do this note that this would impact all your running instances of MvcPlayer.</p> <p>To create a new alternative MvcPlayer which does not rely on routing (leaving the original one intact) do this: </p> <ol> <li>Copy <code>Player.cs</code> to <code>NoRoutePlayer.cs</code> (and rename the class accordingly) and make the above mentioned change there (comment out line 57).</li> <li>Then register this new function in Composite C1 by going to Functions | C# Functions | Composite | AspNet | MvcPlayer and add a node here, using the existing Render element as inspiration. Just set the 'Type' name to NoRoutePlayer.</li> </ol> <p>With that change you will have a Player function and a NonRoutingPlayer function and you can then use the latter to run your MVC controller, and everyone should get along just fine :)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload