Core 4.0.8 jsonquery.php 404 not found

[mobrien03]

Reference: Nagios Support Forum post 32973 for details.

Issue
The initial screen of jsonquery.html prompts the user to select from one of the 3 GGI's: Archive, Object or Status. Selecting either one can produce a screen with their selection, and ONLY the "SEND QUERY" button for a period of time -- that is, the background processing to obtain the object data and update the screen with further selection Options can be delayed -- for several seconds, perhaps up to 10 seconds. Yet, the "SEND QUERY" button is live the entire time, and a user not familiar with the application can press "SEND QUERY" prematurely, and receive an error jsonquery.php 404 not found.

Our Nagios Core systems are not very large: we have 130+ hosts, with ~5600 services on a decent sized multi-cpu Linux server. However, there can be sufficient lag of several seconds (as described above) to present the user with a screen that leads them to believe the next step is to hit "SEND QUERY" without knowing further selection options will eventually be painted on the screen.

Suggestion: Gray out the "SEND QUERY" button until the background processing has filled any list boxes, and the user has made at least some selection from the new options.

[mobrien03]

I should also note, that while the title does indicate the issue is with Core 4.0.8, in attempts to fix this, I upgraded our Test system to 4.1.0rc1 and the issue still existed. I then backed off to 4.0.8 again, and as described in the Nagios Support Forum post 32973, I kinda stumbled onto what the real issue was.