Try https://elgg.org/plugins/1939447/releases/1939448/download

You might want to read http://learn.elgg.org/en/stable/admin/plugins.html. And you can also look at the other sections in the docs to find other topics that might help you to get over the initial helplessness of not knowing how to do things with Elgg.

If you have other questions not answered in the docs (or not already answered in exisiting discussion topics), you can of course ask here on the site.

Exception at time 1501358326.

Check the server error log to find out what causes the error. You must to do it.

how do I clear the cache manually?

Delete system_cache and views_simplecache folders from data directory.

Console:

$ rm -fR system_cache

$ rm -fR views_simplecache

Hello guys nice discussion on how to move elgg forward..
I would love to ask some questions based on this discussion... Thanks

Question 1:
"because there are superior suites, like Laravel"
Is laravel better than elgg?..cos I do brag about elgg being better than laravel with my friends.

Question 2:
" Elgg is great for testing ideas and working with small budgets"
Is elgg no longer suitable or great for building large communities or enterprise startup communities?

1) Laravel comes barebones, so Elgg wins in terms of how much functionality you can get out of it by installing a bunch of plugins. Laravel wins in terms of its architecture and mindset that allows you to build high class large scale apps. Testability of Laravel apps is much higher, so I think it beats Elgg in terms of long-term maintenance and growth burden. But in reality Elgg can be a Laravel app, ultimately Laravel is a set of tools, so we could throw away all the wheels that Elgg has reinvented and use Laravel as a foundation. Once I am more comfortable with Laravel I'd like to try and put Elgg on top of it.
2) Sure you can. It depends on your needs. We still use Elgg a lot, but Laravel might be more suitable for custom projects. The amount of work that goes into customising Elgg, dealing with third-party plugins, corky UI, expensive database queries sometime outweighs the effort that would go into building a Laravel app from scratch.

I appreciate the Elgg cheerleading and putting thought into this!

I think we have to consider what unique value Elgg brings to the table, and whether or not we would be better off in a world where Elgg were a set of APIs/features within another ecosystem. To attract devs a system must have either a great developer experience (Laravel/Symfony) or an undeniably rich featureset (Drupal) or community (WordPress). Elgg is lacking all three.

Drupal is really Elgg's big sister, built with the same everything-is-hookable/plugins-working-together spirit, and already has so many CMS features Elgg users want: Web-configurable Views, Panels, Paragraphs, Rules, Taxonomy, roles, workflows. For entities: custom ordering, URL paths, revisions, translations. And Elgg could benefit from its fragment caching, CDN support, and efficient DB structures.

But that cost: Drupal's APIs and coding conventions are arguably worse than Elgg's (some notable exceptions, like forms) and it's a behemoth out of the box.

The big features of Laravel I think are its docs, and Laracasts. I think Symfony can do all the same, but I feel like I'd do more digging. Symfony 4 is around the corner. As we stew on this it'll be interesting to see what changes in the Symfony world.