This issue has been migrated from Redmine: https://dev.icinga.com/issues/10881
Created by tgelf on 2015-12-17 16:45:27 +00:00
The iframe module basically consists of two lines of code, plus brackets and a namespace/class/function-definition. Is there anything that hinders us from making this part of our default functionality? Currently most users are confused, as they have no Idea what this module is all about. Iframes, ok. And then?
2016-02-09 12:37:53 +00:00 by aklimov 7fe71f7
2016-02-09 12:39:44 +00:00 by aklimov 86834c4
2016-02-09 12:54:56 +00:00 by aklimov 8958873
2016-02-09 12:58:07 +00:00 by aklimov 1abd1d2
Updated by jmeyer on 2016-02-09 12:06:28 +00:00
While you're working on this, please also fix the index action's view script which is missing the usual html structure. (tabs and content)
Updated by mfriedrich on 2016-02-14 15:11:13 +00:00
This change broke the rpm builds on build.icinga.org as the spec file tries to copy the iframe module. Please verify that next time.
I've fixed that with 1fcbe87 because I was preparing the vagrant boxes for the upcoming icinga camps. Mainly incorporating the change of moving the iframe module into the main framework.