modelo.php library

Path in the Gestor bibliotecas/modelo.php

modelo.php is the Gestor's template library. Everything Conn2Flow renders on the server goes through it: pages, layouts, components and widget responses are HTML strings where code replaces markers with values and cuts, repeats or removes blocks. There is no template engine, AST or automatic escaping — only plain string functions.

The library is loaded during the Gestor bootstrap and registers its version in $_GESTOR['biblioteca-modelo'] (currently 1.1.0).

The two kinds of marker

The functions enforce no format: they look for exactly the string they receive. The block comment convention is followed by core modules and widgets.

Replacing variables

When the variable is not found, the template comes back unchanged; there is no error or warning.

modelo_var_troca() and modelo_var_troca_tudo() also accept an associative array instead of $var. Each key is used literally as the marker; no # is added, despite what the function's docblock says:

$html = modelo_var_troca_tudo($html, [
    '#titulo#' => $titulo,
    '#url#'    => $url,
]);

modelo_var_troca_tudo() uses str_ireplace() on purpose. The old preg_replace() version treated $19 inside the value as a group reference and corrupted prices such as $19.97.

Working with blocks

The repetition ("cell") pattern

This is how core modules build lists on the server: extract the block as a template, leave a marker in its place, and insert each row before the marker.

$cel_nome = 'linha';
// 1. Keep the template and leave a marker where the block was.
$cel = modelo_tag_val($_GESTOR['pagina'], '<!-- '.$cel_nome.' < -->', '<!-- '.$cel_nome.' > -->');
$_GESTOR['pagina'] = modelo_tag_in($_GESTOR['pagina'], '<!-- '.$cel_nome.' < -->', '<!-- '.$cel_nome.' > -->', '<!-- '.$cel_nome.' -->');
// 2. For each record, fill a copy and insert it before the marker (order is preserved).
foreach ($registros as $r) {
    $linha = modelo_var_troca_tudo($cel, '#nome#', htmlspecialchars($r['nome']));
    $_GESTOR['pagina'] = modelo_var_in($_GESTOR['pagina'], '<!-- '.$cel_nome.' -->', $linha);
}
// 3. Remove the marker.
$_GESTOR['pagina'] = modelo_var_troca($_GESTOR['pagina'], '<!-- '.$cel_nome.' -->', '');

The same pair of functions handles conditional blocks: modelo_tag_del() drops the section when the condition is false — for example, the publisher module does this with its templates-todos-linkados-msg messages.

Legacy functions

• modelo_abrir($modelo_local) reads a file and removes the development block <!--!#del#(#!--> … <!--!#del#)#!-->. It has no callers in the core: templates live in the database and in resources/, not in files read at runtime. It also removes only the first block.

• modelo_input_in($modelo, $in, $out, $valor) calls paginaTrocaVarValor(), which does not exist in the core. Calling it is a fatal error. It has no callers; do not use it.

See also

• Menus module — a widget that uses <!-- item < --> blocks with its own rules.

• How to write documentation

Functions

modelo_input_in(string $modelo, string $name_input_in, string $name_input_out, string $valor): string

modelo_var_troca(string $modelo, string|array $var, string $valor = null): string

modelo_var_troca_fim(string $modelo, string $var, string $valor): string

modelo_var_troca_tudo(string $modelo, string|array $var, string $valor = null): string

modelo_var_in(string $modelo, string $var, string $valor): string

modelo_tag_val(string $modelo, string $tag_in, string $tag_out): string

modelo_tag_in(string $modelo, string $tag_in, string $tag_out, string $valor): string

modelo_tag_del(string $modelo, string $tag_in, string $tag_out): string

modelo_tag_troca_val(string $modelo, string $tag_in, string $tag_out, string $valor): string

modelo_abrir(string $modelo_local): string