id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,difficulty 2829,"Extending ""view"" vs. ""view/extend""",ewinslow,,"It seems that we have a pattern of inserting a view/extend view if we want some view to be extendable. The reason is that a lot of views are like so: {{{ --- page/elements/head --- }}} So there's no way, unless you specifically insert a new (non-existent view) to just add something to the end of head without it being outside the head. Have we thought about doing this instead?: {{{ --- page/shells/default --- echo elgg_view('page/elements/head'); ... }}} This also allows people to insert html at the beginning of the view. Either way, I think we need to decide on a consistent way to go, because IIRC we don't do this consistently: 1. put the wrapper html in the view itself and require an explicit view/extend in order for people to insert content inside 2. The view does not contain its wrapper and this allows plugins to extend both from the top and bottom without any extra views being introduced. This encourages separation b/w container and content. E.g., the page/shells/default provides the container (shell), the page/elements/footer provides the content, agnostic of whether elgg-inner is present or not. An argument against 2 would be that some views absolutely require a view/extend view (such as the login form) anyways, so we wouldn't be able to achieve consistency.",Defect,new,normal,Long Term Discussion,Core,1.7,minor,,,brett@…,