Source of modules.xliff - documentation

xxxxxxxxxx

<?xml version='1.0' encoding='UTF-8'?>

<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">

  <file source-language="en" target-language="nb-NO" datatype="plaintext" original="devel/modules.md">

    <body>

      <trans-unit id="12a4ad08" xml:space="preserve">

        <source>

# Modules</source>

      </trans-unit>

      <trans-unit id="f1b884d6" xml:space="preserve">

        <source>### What is a PHP frontend module?

-   A module is an entity with a unique ID, name, description, author, and other fields defined in it's manifest file, along with PHP, Javascript and other files located in a single directory inside the *modules* directory of your Zabbix frontend installation (for example, *zabbix/ui/modules*).

-   A module should conform to simple rules to guarantee correct operation.

-   A module must be installed (unpacked) and enabled in the frontend by the administrator.</source>

      </trans-unit>

      <trans-unit id="4e4bad2b" xml:space="preserve">

        <source>

### What a module can be used for

-   Adding new functionality via custom frontend sections;

-   Creating custom dashboard widget types (see [widget modules](/devel/modules/widgets));

-   Overriding or extending the existing functionality.</source>

      </trans-unit>

      <trans-unit id="064ddd80" xml:space="preserve">

        <source>

### What a module cannot be used for

-   Registering a new API method or modifying an existing one.</source>

      </trans-unit>

      <trans-unit id="bfe0360a" xml:space="preserve">

        <source>

### How modules work

-   An enabled module is launched on each HTTP request, before executing the action code.

-   The module will register new actions or redefine the existing ones.

-   The module will add new frontend sections and remove or redefine the existing ones.

-   The module will hook to frontend events like onBeforeAction and onTerminate, if needed.

-   The requested action is finally executed by running the action code - either the default one, or module-defined.</source>

      </trans-unit>

      <trans-unit id="7aea12f6" xml:space="preserve">

        <source>### Where to go next

Whether you prefer to learn by doing or read the guidelines first, these pages contain the information and steps required to build your own modules:

- [Step-by-step tutorials for writing your first module](/devel/modules/tutorials)

- [Module file structure](/devel/modules/file_structure)

- [Widget module specifics](/devel/modules/widgets)

- [Module examples to reuse](/devel/modules/examples)</source>

      </trans-unit>

    </body>

  </file>

</xliff>