wouldn't this be complex. we shouldn't bring any new features if it's not realy necessary, will just add to maintenance cost.
how about making it mandatory for landing page to be anon if user make any page anon. that is, you can't make any page anon before making landing anon. UX team what do you think? On Tue, Oct 20, 2015 at 6:15 PM, Nipuna Chandradasa <nipu...@wso2.com> wrote: > Hi team, > > There was a problem which came up during the discussion about anonymous > view in dashboard server. > > Discussion was about restricting the user creating an anonymous page > without making the landing page (Home page) of the dashboard anonymous. > > But this way user always have to make the landing page anonymous in order > to make the other pages anonymous even user does not want to make the > landing page anonymous. > > So what we came up with was to add an option to define landing pages for > anonymous state and the default state of the dashboard. So there will be > two landing pages when it comes to a anonymous dashboard. One landing page > is for anonymous state and other landing page for default state. > > Appreciate any suggestions and comments on this. > > Thank you. > -- > Nipuna Marcus > *Software Engineer* > WSO2 Inc. > http://wso2.com/ - "lean . enterprise . middleware" > Mobile : +94 (0) 713 667906 > nipu...@wso2.com > -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : m...@wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
