1. Configure/navigate one template (e.g. items) in tab A via the suburl: zabbix.php?action=trigger.list&context=template... .
2. Configure/navigate one template (e.g. triggers) in tab B via the suburl: zabbix.php?action=trigger.list&context=template... .
3. Go back to tab B and press the "back button".
4. Observe how tab B now takes you to some configuration page of the template you were working on in tab A. You end up showing the e.g. triggers of host in tab A instead of B as expected.
I know it's FOSS and that the code base originates from an era and paradigm where PHP was the easiest solution (though PHP still quite bad), but this is quite amateurish even for a legacy/artifact from that time.
There's no way to bug report without registering, so doing a forum post instead. You're welcome.
2. Configure/navigate one template (e.g. triggers) in tab B via the suburl: zabbix.php?action=trigger.list&context=template... .
3. Go back to tab B and press the "back button".
4. Observe how tab B now takes you to some configuration page of the template you were working on in tab A. You end up showing the e.g. triggers of host in tab A instead of B as expected.
I know it's FOSS and that the code base originates from an era and paradigm where PHP was the easiest solution (though PHP still quite bad), but this is quite amateurish even for a legacy/artifact from that time.
There's no way to bug report without registering, so doing a forum post instead. You're welcome.
Comment