@Free Articles,
You might very well know more than I do about Elgg, but ...
Be careful about simple hacks versus plugins. Next time there is an upgrade (and you really do have to keep your software current), all your hacks to Elgg core and the default plugins will get overwritten.
Plugins really are the way to go. And when you DO make a hack, the best way is using your own site-specific plugin.
That is a valid point Stephen, This particular hack could actually be turned into separate plugin but when you hack core plugins, make sure to keep a list of hacked ones and detailed instructions on what and where was hacked, it will save you headaches later.
I always try to extend/override any fuctionality in the Theme itself, so upgrading is much easier.
@free articles, the better way is to code it as plugin hook on registration action.
Sorry - I don't know anything about the twitter log in.
Thanks for the response Cash.
Who would know? Who installed/coded it on Community site? Who runs the site? who is the techie guy here? Brett?
Thanks.
The core devs admin the site as time allows. The twitterlogin plugin is in the elgg svn repository with the history here: http://trac.elgg.org/log/plugins/trunk/twitterlogin?action=stop_on_copy&mode=follow_copy&rev=6830&stop_rev=&limit=100
I don't know that the code in the repository is the same that is running on this site (I expect that it is not).
I know that in the move to a new server last week, email has not been configured yet so most or all email is being marked as junk. You should check your junk mail folder to see if that is the issue.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.