Can you post the xml? It's *extremely* odd to have either of those two modules in a situation where they have no parents. Much less both in one view.
And by the way 'parent' just means - the `` tag that the ViewRedirector is nested immediately inside. When a module has no parents it means it's right at the top, right under the `` tag.
In fact, I suspect that something weird is going on, like there are parents there but they've been rendered into layoutPanels that don't exist in that template (search.html vs dashboard.html usually) . Can you post the XML of the view?
UPDATE:
To back up a second, aside from the obvious way of giving RowNumbers no children and giving ViewRedirector no parents, you can also get this error message if somehow the corresponding parent or child modules' layoutPanels get somehow obliterated. Thus although the XML looks fine, the ViewRedirector and RowNumbers modules end up being sort of 'orphaned' or 'de-child-ed' respectively.
I took a look at the search app's views in 4.3, and 1) some views give the ViewRedirector it's own layoutPanel (all the dashboard views and only the dashboard views it seems) 2) Also the 'flashtimeline view, aka the default search UI, gives the RowNumbers module a layoutPanel of resultsOptions. The upstream modules of the ViewRedirectors in the (1) cases, are rendered into "splSearchControls-inline" layoutPanel and the downstream modules in the (2) cases are rendered into "resultsAreaLeft".
So.. it sounds crazy, but the best theory here is that something, possibly some fancy app, has taken it upon itself to override both the dashboard.html template and the search.html template, without realizing that this could damage functionality in other apps. They have destroyed the 'splSearchControls-inline' layoutPanel in the search.html template, and destroyed the resultsAreaLeft layoutPanel in the search.html template.
What I would do is search $SPLUNK_HOME/etc/apps for any files called search.html and dashboard.html. And send everything over to Splunk Support for them to look into this. Whatever it is, it's such a crazy problem that I'm pretty confident it'll be easy to fix.
↧