Now, with that little bit of embarrassment for not catching that sooner out of the way , I'm still somewhat confused.
Isn't the purpose of a wild card item (home/product/*/*) to allow for me to have a "single" presentation detail defined, my (*) page. And then the
item resolved from the url will be used as the datasource for the "page"? Yes, Volodymyr, i realize now that's NOT how your module is designed to work..
And the more I think about that in my head the more I realize resolving the MVC Page Item args.Result was NEVER going to function the way that I was thinking..
My goal was two-fold.
1 - have a shared content repo for all products,
2 - have a common presentation for all products, HOWEVER, the common presentation details
may differ from site to site / function... For example, if I wanted to provide an "embed" link for my products, the presentation details would be watered down and contain less (or even different) components.
Site A Home
- * (Product ID)
- * (Product Name) <-- Has Presentation Details Defined to display products one way
Site B Home
- * (Product ID)
- * (Product Name) <-- Has Presentation Details Defined to display products a different way
- Product A <-- Just data no presentation details
- Product B <-- just data no presentation details
This seems to fit within the mold of wildcard items, but i'm no longer certain that a different approach would not be better.
First, let me start by saying, thanks again to Volodymyr and Paul for your responses. Paul, i'd like to go back and say, for Item #2, my wildcard item (*), has presentation details, BUT the individual items, did not... Once I set presentation details for the items within my shared content folder, things started to work..