This issue has been created
 
 
Page Logs Application / cid:jira-generated-image-avatar-d955b6d3-5ab3-4365-beae-fe1d8e083e34 PAGELOGS-2 Open

Display the logs produced when saving a page, not only when rendering it

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-5dc2283c-adc1-40f8-8eb7-b9a248386d73 Charpentier Lucas created this issue on 07/Oct/26 16:21
 
Summary: Display the logs produced when saving a page, not only when rendering it
Issue Type: cid:jira-generated-image-avatar-d955b6d3-5ab3-4365-beae-fe1d8e083e34 Improvement
Assignee: Unassigned
Created: 07/Oct/26 16:21
Priority: cid:jira-generated-image-static-major-92575fcd-0bf8-4264-8dc8-05ec07173e33 Major
Reporter: Charpentier Lucas
Description:

The application only records the logs produced while a page is rendered: PageLogsEventListener starts capturing on the document.progress.render progress step and ignores everything else. Warnings and errors logged while a page is saved are therefore never shown to the user, and the only place to see them is the server log, which most users can't access.

A concrete case is XWIKI-16792: when a user saves a wiki macro whose ID is already used by another macro, the new macro overrides the existing one, or is hidden by it, depending on the registration level. This is the expected component override behavior, but the user gets no feedback at all, and since wiki macros are created through the generic object editor there is no dedicated UI where a warning could be displayed. As suggested on that issue, displaying the logs of the page save in the page UI would cover this case and similar ones, such as other wiki components or UI extensions.

Proposal

  • Also capture the logs produced while a document is saved, including the DocumentCreatedEvent and DocumentUpdatedEvent listeners, since this is where wiki macros and other wiki components get registered.
  • Display them in the page UI next to the rendering logs, clearly distinguished, so that the user sees them after saving.

Note

For the XWIKI-16792 case this is not enough on its own: DefaultWikiComponentManager#registerWikiComponent currently replaces an already registered component without logging anything, so platform would also need to log a warning when a wiki component overrides an existing one.