Which your Elgg version?

v3.3.9

Check your PM

I did what you suggested originally and then I read there was a caveat to that methodology due to long term maintenance.

What would be the problem? If you override the views in your own plugin (and NOT change the core views) the only problem I can see if we patch something in a view you won't get it.

Since this rarely happens for the core views (mainly in major builds) I don't think this will be a problem.

Just out of interest, is there a performance implication in either of the solutions?

Hooks add a (tiny) bit of extra execution and therefor performance costs (but it's very very small), overruling the view doesn't add additional execution so no penalty

Thanks again, Jerome. I'll do as you suggest.

I'll have to find another use for those hooks :)

I'll have to find another use for those hooks

hint: menu items ;)

Welcome back!

Look at our apps for inspiration: 1, 2, 3, 4, 5

Thanks. I have been spending a couple days doing everything I can the vanilla way and will chime in if I run into something new. A lot of the features that I added to 1.8 are part of 3.x.