- current implication for blogs is that if a blog is set as the home page its posts are then all rooted (e.g. if a blog at
/blog is set as the home page then it's available at / and a post at, say, /my-post instead of /blog/my-post). There should
maybe be a setting to alter the paths of the posts but (1) that's a pain at the moment, (2) hacking the URL by removing
the post slug would result in a 404 instead of redirecting to /, the path of the blog - we don't handle redirects of that
nature - and (3) the ability to root a blog in this manner *has* been requested by some.
--HG--
branch : dev
- previously if the page wasn't immediately published (saved as draft or scheduled for later publishing) it still overrode the home page setting and the home page subsequently became a nice 404 page
--HG--
branch : dev
Related to #16496 which was already fixed a w/ another bug a little earlier but a double '/' appears when the app is not in a vdir.
work item: 16496
--HG--
branch : dev
This lets unique display actions, like Blog/Item, do their own thing. In the case of the blog, its posts are once again showing up on the home page.
The routing problem (where the home page'd item still is seen as having its own path) still needs to be fixed so the item on the home page can't be hit at different URLs (and so something like paging works on the home page)
work item: 16720
--HG--
branch : dev
- content directories no opt-in to static files only.
- module web.configs no longer need to explicitly exclude cshtml, etc, paths.
--HG--
branch : dev
If lambda takes an argument, it is dynamic, and is an uninitialized shape of the named type
ShapeHelper and IShapeHelperFactory are obsolete - IShapeFactory itself is now dynamic
--HG--
branch : dev
ContentShapeResult.Apply calls through the context.FindPlacement to acquire placement location
DefaultContentDisplay component wires the FindPlacement onto the ShapeDescriptor.Placement
ShapeDescriptor.Placement func contains the chained per-theme rule stack for part shape placement
Next up - simple Placement.txt parser to convert rules into Placement chain
--HG--
branch : composition
- Includes changing display-related implementations (drivers & views) to work with shapes
- Editor implementations still on the old template model
- Orchard.Blogs is currently using a different display type instead of specifying alterations (for Blog and BlogPost)
--HG--
branch : dev
