You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We just upgraded from version 1.1.2
This happens in cacti 1.2.28 but probably also other versions are affected.
During re-activation of the plugin, the following warnings appeared:
2024-11-29 11:24:07 - PLUGIN WARNING: Registering Realm for Plugin reportit and Filenames view.php,charts.php is ambiguous. Using first matching Realm. Contact the plugin owner to resolve this issue.
2024-11-29 11:24:10 - PLUGIN WARNING: Registering Realm for Plugin reportit and Filenames reports.php,view.php is ambiguous. Using first matching Realm. Contact the plugin owner to resolve this issue.
Maybe as a result of this, we have problems with some pages only showing a blank page.
For example:
Console -> Management -> ReportIt
we click on the wrench icon of an existing report
this takes us to the page /cacti/plugins/reportit/reports.php
but the page content is blank
To Reproduce
remove files from 1.1.2 and copy + activate reportit 2.0
obeserve realm warnings in cacti.log
click wrench icon of a report in the list
Expected behavior
there should be no warnings, pages should have content
Plugin (please complete the following information):
Version: 2.0 (development branch [this could be cleaned up by tagging it as v2.0])
Source: github
Identifer: last commit was 04360b6 (installed develop/HEAD from today, 2024-11-29)
The text was updated successfully, but these errors were encountered:
Describe the bug
We just upgraded from version 1.1.2
This happens in cacti 1.2.28 but probably also other versions are affected.
During re-activation of the plugin, the following warnings appeared:
Maybe as a result of this, we have problems with some pages only showing a blank page.
For example:
To Reproduce
Expected behavior
there should be no warnings, pages should have content
Plugin (please complete the following information):
The text was updated successfully, but these errors were encountered: