On Sat, Jul 19, 2014 at 10:02 AM, Glen Mazza <glen.ma...@gmail.com> wrote:
> Hi Dave, I don't understand the use case of "navbar", and it doesn't seem > to work today anyway. I took one of my templates, "_header", and marked it > navbar-able. So my navbar menu indeed changed from: > > Front Page > Weblog > Login > > to > > Front Page > Weblog > _header > Login > > Even without logging in, "_header" is viewable to the world now. Question: > What is the use case for mass-broadcasting Velocity templates to your blog > readership? Why would anyone want that? If it's to facilitate tweaking of > templates, that can be done by keeping the template in a separate browser > tab while hitting refresh on the tab displaying the blog. And we already > have a "design: template page" menu item getting them one click away from > template modifications anyway. > The use case is "add a new page to my blog site with content defined by a template but without me having to edit every that includes the page menu." > Regardless, it doesn't work anyway, it hyperlinks to this URL: > https://web-gmazza.rhcloud.com/blog/page/ which just returns a 404. So > this would need to get fixed, but I don't see this an itch that anyone will > need to scratch. Further, it seems to have lost its semantic meaning in > 5.1, in the past _header would have pointed to a single template, but now > that multi-renditions are available, which one should it point to? > It should point to the page URL and if it is a dual theme, the rendition will be chosen based on device type, mobile or not. > Do you still want to retain this functionality in 5.1, even if it > presently doesn't work? Otherwise, what I can do is have > WeblogTemplate.isNavBar() hardcoded to always return false, so it won't > break anyone's templates, it just will never render, and remove isNavBar > from the data model and the UI screen. > I want to fix this before we ship 5.1. - Dave
