Mods as Plugins

I realize that a lot of work goes into the development and refinement of the elgg version package; however, the age and staleness of Plugins makes it seem like the product itself is not actively maintained.  I would really like to be able to update single mods without a wholesale elgg upgrade.  For example, I want to simply update CKEditor.  The current version of elgg does have the updated version of this tool; unfortunately, the CKEditor plugin is currently more than 15 years (5,544 days) old.  Not only is this inconvenient for many developers (myself included), I think that it sends the wrong message to those looking to adapt this fantastic elgg product.

Please consider modularizing all core mods as plugins to assist iterative deployment.

Thank you

  • No one will update plugins except those who developed them. Or it should be done by enthusiasts.

    This is not a problem for the core developers. The guys are already doing a lot of work to keep Elgg running.

  • Nearly two years ago, you @Shcherbin, Nikolai, posted 'Elgg Community Future' in this discussion forum bemoaning that, "The current Elgg community core and UI are outdated Elgg community is still on Elgg 2. This puts off many new visitors. It reminds as if we stopped in 2012."

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

    Are we conceding that it is impossible that elgg could be a Joomla or a Drupal?

  • 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.

Feedback and Planning

Feedback and Planning

Discussions about the past, present, and future of Elgg and this community site.