-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
River items use an extension-less module (Trac #3404) #3404
Comments
ewinslow wrote on 41395952-02-27 During the creation of my facebook theme, I found that most river views in bundled plugins manually insert some html:
This kind of coding pattern is crying out for a template view that any river entry can use. I found it was much cleaner to do something like this:
The template view then takes care of the layout of the river entry, so themes only have to override one view to get a consistent change across the board. That's really what I'm looking for -- there's no reason that themes should have to "know" so much about all the different content plugins out there. |
cash wrote on 41415450-09-06 This needs to be done soon if we're going to do it for 1.8 as plugin authors are starting to update plugins. |
Milestone changed to |
cash wrote on 41436282-10-17 See #35 for some great progress on this |
Original ticket http://trac.elgg.org/ticket/3404 on 41320618-12-30 by ewinslow, assigned to ewinslow.
Elgg version: Github Master
Two options:
I checked facebook, twitter, github, buzz, all seem to incorporate these aspects, plus or minus.
The text was updated successfully, but these errors were encountered: