Nikolai, thanks again. So you're saying that the administrator created when installing Elgg (me) is automatically given a user profile page like every other user who registers? So, how is he able to stop other users from becoming administrators themselves when they register and from accessing certain privileges/pages/events/functions etc? I am having a tough time wrapping my head around how the platform works. Thanks again for your time.

I won't make a tutorial here, you can always ask a more specific question here.

As for administrator privileges, everything is controlled through the user entity menu (3 vertical dots)

With 'Developer tools'  plugin activated, you can examine all the metadata and attributes of any entity via 'Entity explorer' tool.

You can also use 'Login as' feature.

Sorry to have upset you. I will just move on. Thanks

Because PHP 7.4 is End-Of-Life and it is no longer supported. See https://www.php.net/supported-versions

When a PHP version is no longer supported why should we support it. It exposes your installation to potential security risks nobody is going to fix.

Also we might use newer features of PHP which aren't available in older versions. We're only a small team of volunteers and supporting the main version of Elgg is already a lot of work. Making a version for older PHP versions is just not doable.

Any real reason?  Hard to believe it is ever supported, given the fact there is no money in it, it was once on store shelves, now it's a free drag download.  There is no reason to feel motivated, I wonder if the programmers and site runners are paid.

I may agree 5 would be totally off, 

The bad habit of theirs to remove good things and then place in something vulnerable is also plaguing 

Nearly two years ago

This was discussion about community Ui not about plugins.

This is reminiscent of my concern about plugins.  Besides, aren't all mods plugins? Shouldn't all mods be plugins?

What plugins are you talking about?

All important plugins are supported by the few developers who are on Elgg.

The rest of the unsupported plugins have either lost their relevance or are not needed by users.

If the developer abandoned the project, why would anyone work on it?

iionly wrote a good post about this problem, please search the community for similar whiny discussions ("Elgg is dying ... blah blah blah")

If you can't find the plugins you need here, look for them in the repositories on GitHub or somewhere else.

We created a channel in Telegram, where we regularly posted information about the release of all plugins from all sources, both paid and free.

P.S. Why do you call plugins "mods"? There are no mods in Elgg, only plugins.

I call plugins 'mods' because they're modules in the 'mod' directory, along with many core functions.  I thought that it would be sensible for all functions that operate as modules to be modular.  Your response is disheartening, especially as such a cold dismissal of a reasonable suggestion from a long-time elgg enthusiast.  My suggestion is good-natured and well-intentioned.  It's not whiny.  But it does disincline me from contributing back to an uninviting, insular community who seems to not want my contribution.

I call plugins 'mods' because they're modules in the 'mod' directory, along with many core functions.  I thought that it would be sensible for all functions that operate as modules to be modular.

"All important plugins are supported by the few developers who are on Elgg. The rest of the unsupported plugins have either lost their relevance or are not needed by users." ignores both the example that I provided and the need that I expressed.  I wish you wouldn't be so dismissive in the face of direct evidence to the contrary.

Your response is disheartening, especially as such a cold dismissal of a reasonable suggestion from a long-time elgg enthusiast.  My suggestion is good-natured and well-intentioned.  It's not whiny.  But it does disincline me from contributing back to an uninviting, insular community who seems to not want my contribution.