Path in the Gestor modulos/variables/
This screen edits each module's configuration variables. Its selector chooses a modulos record, while the configuracao library builds editing cards from variaveis records in the current language.
How to use
Open variables/ and choose a module in the searchable selector; the URL then carries that module's id parameter. Edit, add, or remove variables in the cards and save. The route and flow are the same in pt-br and en. The selector excludes the bibliotecas group.
Technical reference
The controller's only main case is variables, with the alteracoes interface. AJAX opcao returns only an empty payload and Ok status. configuracao_administracao() builds the fields; configuracao_administracao_salvar() compares submitted values with rows by modulo and language, updates or inserts them, deletes omitted rows, and increments the modulos record's version and modification date when values change. The JSON defines no specific widget, template, hook, or hooks.api.
The module JSON points its main table to modulos because the screen also displays metadata for the selected module. The actual values live in variaveis: id_variaveis, language, modulo, id, MEDIUMTEXT valor, tipo, grupo, and descricao in the initial migration. Library types include string, text, bool, number, quantidade, dinheiro, css, js, html, editor-texto, and date types.
Confirmed limitations
See also
Tailwind panel controls
The type selector also works in entry boxes cloned after loading. Cloning requires rebuilding the control instance; values and keys remain resource data.
Shared conventions: Administrative interface.