If you are updating to a new version, delete the minScript folder inside your extensions folder and repeat steps 1-2 from the installation instructions.

The following list informs about changes which could break compatibility with older versions:

  • 2.1
    • Removed ExtMinScript::$minScriptRuntimePath. The runtime path will be chosen automatically.
    • ExtMinScript::minScriptGetPath() method visibility was changed to "protected".
    • ExtMinScript::$minScriptController was renamed to $minScriptControllerId.
    • ExtMinScriptController::$minScriptComponent was renamed to $minScriptComponentId and does not contain the minScript component instance anymore.
    • Removed ExtMinScript::minScriptInitDir().
  • 2.0
    • Complete rewrite. The old methods/configuration won't work anymore. Please read the guide on how to configure and use minScript 2.0
  • 1.1.0
    • ExtMinScript::$controllerID has been removed. The minScript controller ID will now be detected automatically.
    • ExtMinScript::generateUrl() and ExtMinScript::generateScriptMap() have been modified in this version. ExtMinScript::generateScriptMap() needs to have an array/string passed as parameter, calling the method without parameter won't work anymore. See Usage for more information.


Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.