Extension GUI

This feature was born as pet project in our development team. The goal was to beautify current extension management process, by adding separate admin page, instead of single text-area input describing class extend information.

Separate Extension page

There is new page for extensions, including list, overview, setting and dragable module dependency sections.


Extension list


This list is created after module directory scan and includes all found folder names (not nested), if extension metadata (will be described lates) file is found in directory, wee see nice titles, otherwise just a folder name is visible.

Installed shop modules


This section nicely represents structure of well known modules array, but this time you can use drag & drop to change module dependency chains and see disabled modules.

Extension overview


This section is for Activating or Deactivating selected extension and showing additional information from extension meta-data:

  • Title
  • Description
  • Author
  • Version
  • Picture

If extension did not provide meta-data information, it must be provided by user once to enable module activation/deactivation feature.


The module in my shop is deactivated “automatically” without an obvious reason? Or is there even a dedicated mechanism for automatic deactivation if certain conditions are met?

There is a mechanism implemented: in case the shop detects that some file of the module (which should be existing) is missing it deactivates the module automatically. In this case, a record in exception.log should appear.

There are neither any files missing nor is there an entry in the exception log.

You could try to go to admin modules tab: if a class is registered but file is missign you should get a warning message about that.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *