Plugin Management

Hi, I previously used another cms called Xoops, this was a very good cms very easy to use etc.

What xoops has which I think Elgg needs is the ability to order the plugins by number rather than pushing up and down which is the current elgg method.

The idea is the lower the number next to the plugin higher the priority of loading that plugin this could speed up plugin management.

The other thing that xoops did was place uninstalled modules below the installed ones, or in Elgg it would be enabled and disabled.

 

There was also a tick system for the modules so you could activate multiple modules at the same time, if you want to do this with elgg you have two options all or one at a time.

  • @Kiwi-Chris, This is a good idea.

    I would like to add:

    - plugin naming: This is now just by chance, every plugin developer creates his own name, Version naming is likewise ambiguous. Have every plugin developer register a name before it is uploaded. Attach version after name in a decimal notation fashion.

    - plugin loading: Presently it works but demands a lot of manual steps.  Having a centralised repository a adminstrator function would make plugin loading a breeze. This should include proper version control (does it fit the version of core elgg?

    - plugin language loading: At present it is easier to do the translation on the spot than searching for the translation file. A Function to fetch language files for all plugins loaded would really enhance elgg in the multilingual field.

  • For me, the most immediate improvement I would like to see to the plugin system would be to make it easier to reorder and activate/deactivate selections of plugins. I can see the benefits of the other suggestions here, but could live without them in the short-to-medium turn.

    A method for easily recovering from the white screen of death would be good too :-)

Feedback and Planning

Feedback and Planning

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