메뉴
Use when writing, reading, or debugging SPIP logs — spip_log(), journal(), log constants, log file location, gravité levels, or log rotation. For SPIP 4.1+.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
| name | spip-logs |
| description | Use when writing, reading, or debugging SPIP logs — spip_log(), journal(), log constants, log file location, gravité levels, or log rotation. For SPIP 4.1+. |
SPIP has two distinct logging entry points:
spip_log() — writes to rotating text files in tmp/log/; for developer/debug tracesjournal() — event log API; in core it writes to tmp/log/journal.log via spip_log(), and a plugin can override it (via charger_fonction('journal', 'inc')) to store entries in DB and display them| Term | Meaning |
|---|---|
| gravité | Severity level of a log entry (_LOG_DEBUG, _LOG_INFO, …) |
| journal | Site event log; minimal in core (a dedicated log file), extensible by plugins |
| tmp/log/ | Directory that holds rotating .log files written by spip_log() |
| _LOG_FILTRE_GRAVITE | Constant that acts as a threshold: only messages with gravité ≤ this value are written |
spip_log(mixed $message = null, string|int $name = null): void
$name form | Meaning | Example |
|---|---|---|
'type' | Log file prefix, gravité defaults to _LOG_INFO | 'monplugin' → tmp/log/monplugin.log |
| int | Gravité, file defaults to spip.log | _LOG_ERREUR |
'type.' . niveau | Both at once | 'monplugin.' . _LOG_DEBUG |
$message accepts any value — non-strings are dumped with print_r() automatically.
| Constant | Value | Written by default? | Use for |
|---|---|---|---|
_LOG_HS | 0 | yes | System down / unrecoverable |
_LOG_ALERTE_ROUGE | 1 | yes | Red alert |
_LOG_CRITIQUE | 2 | yes | Critical error |
_LOG_ERREUR | 3 | yes | Recoverable error |
_LOG_AVERTISSEMENT | 4 | yes | Warning |
_LOG_INFO_IMPORTANTE | 5 | yes | Important info |
_LOG_INFO | 6 | no | Normal info — default gravité of a spip_log() call |
_LOG_DEBUG | 7 | no | Debug trace |
Default threshold (_LOG_FILTRE_GRAVITE) = _LOG_INFO_IMPORTANTE (5). Messages with a gravité value greater than the threshold are silently discarded — so a plain spip_log($msg, 'monplugin') (gravité _LOG_INFO = 6) writes nothing until the threshold is raised in config/mes_options.php.
// Info — requires _LOG_FILTRE_GRAVITE >= _LOG_INFO to be written
spip_log('Plugin activated for id_article=' . $id_article, 'monplugin');
// Important info — written with the default threshold
spip_log('Import finished', 'monplugin.' . _LOG_INFO_IMPORTANTE);
// Warning — something unexpected but non-blocking
spip_log('Empty result from external API', 'monplugin.' . _LOG_AVERTISSEMENT);
// Error — an operation failed
spip_log('sql_insert failed: ' . $msg, 'monplugin.' . _LOG_ERREUR);
// Debug — only written when _LOG_FILTRE_GRAVITE >= _LOG_DEBUG
spip_log(['query' => $query, 'result' => $result], 'monplugin.' . _LOG_DEBUG);
journal(string $phrase, array $opt = []): void
Records a site event. The core implementation (inc_journal_dist() in ecrire/inc/journal.php) is minimal: it appends the $opt values to the phrase (' :: ' . join(', ', $opt)) and calls spip_log($phrase, 'journal') — so entries land in tmp/log/journal.log. There is no fixed option schema and no DB storage in core; a plugin can override inc_journal (loaded via charger_fonction('journal', 'inc')) to store entries in base and provide display/selection tools.
// Log a content publication event
journal(
_T('monplugin:log_article_publie', ['titre' => $titre]),
['id_article' => $id_article, 'statut' => 'publie']
);
| Goal | Read |
|---|---|
| Write a developer/debug trace | references/spip-log.md |
| Configure gravité levels and log threshold | references/spip-log.md |
| Understand log file naming and rotation | references/spip-log.md |
Enable _LOG_DEBUG messages in dev | references/spip-log.md |
Record a site event with journal() | references/journal.md |
Store/display journal entries beyond tmp/log/journal.log | references/journal.md (plugin override) |
| Debug a plugin with SPIP's native debug tools | references/debug.md |
Understand _LOG_FILTRE_GRAVITE override | references/spip-log.md |
references/spip-log.md → choose the right gravitéreferences/spip-log.md → pick a $type name scoped to the plugin (e.g. 'monplugin')references/spip-log.md → enable debug output in dev via _LOG_FILTRE_GRAVITEreferences/journal.md → call journal() with a phrase and optional context arrayreferences/journal.md → read tmp/log/journal.log (or a plugin's storage if inc_journal is overridden)references/debug.md → use spip_log() + ?var_mode=debug for request-level tracesreferences/spip-log.md → tail tmp/log/ to read output in real timeecrire/inc/utils.php → spip_log() and journal() entry pointsecrire/inc/log.php → inc_log_dist(), the actual file writer (naming, rotation, line format)ecrire/inc/journal.php → inc_journal_dist(), the core journal implementationecrire/inc_version.php → _LOG_* constants and _LOG_FILTRE_GRAVITE defaultSOC 직업 분류 기준
Use for SPIP translation/i18n work — creating, editing, or auditing language files (lang/prefix_XX.php, lang/paquet-prefix_XX.php), naming keys, adding translations, using _T() / <:module:key:>, or debugging missing/untranslated strings.
Use when developing a SPIP plugin (paquet.xml present, _pipelines.php, spip_* table references in PHP) or when the user asks about plugin architecture, pipelines, hooks, or the SPIP PHP/SQL API. SPIP 4.1+. Not for template/squelettes work — use the spip-squelettes skill for that.
Use when creating, reviewing, or debugging SPIP CVT forms — canonical HTML wrappers, field/global errors, `charger`/`verifier`/`traiter`/`identifier`, or when deciding whether Saisies or Verifier are appropriate.
Guides automated testing of SPIP plugins and squelettes using PHPUnit — the standard test tool for SPIP. Covers the full self-contained setup (composer, spip-cli), unit tests with lightweight mocks, and integration tests against a real SPIP instance. Use whenever the user wants to test, verify, or validate a SPIP plugin or squelette — even if they don't mention PHPUnit — including questions like "how do I test my plugin", "I want to make sure my filtre works", or "how do I write tests for my autorisation / CVT form /
Use for any SPIP template question — BOUCLE loops, balises, critères, filtres, INCLURE, pagination, image filters, recursive trees, AJAX reloads. Covers public squelettes and plugin squelettes (espace privé, modèles). Trigger even when the user doesn't say "squelette". Not for PHP hooks/pipelines → use spip-plugins.
