Invalid view console in ZM_WEB_HOMEVIEW does not exist

Current Development version likely to have breaking changes
Post Reply
zemerdon
Posts: 15
Joined: Wed Dec 01, 2021 2:23 pm

Invalid view console in ZM_WEB_HOMEVIEW does not exist

Post by zemerdon »

Went from 1.36.33 to 1.37.37

Keep getting...

/12/23, 2:10:23 PM GMT+10 web_php 1114 WAR Invalid view console in ZM_WEB_HOMEVIEW does not exist at /var/www/html/skins/classic/views/console.php /usr/share/zoneminder/www/includes/functions.php 2457

any ideas please?
User avatar
makers_mark
Posts: 18
Joined: Sun Jul 05, 2020 7:23 pm

Re: Invalid view console in ZM_WEB_HOMEVIEW does not exist

Post by makers_mark »

Is your DocumentRoot incorrect in the apache config?
Try commenting out this line (with a '#'):

Code: Select all

DocumentRoot /var/www/html
And add this line:

Code: Select all

DocumentRoot /usr/share/zoneminder/www
Restart Apache
Pjoms
Posts: 12
Joined: Fri Jan 14, 2022 12:05 pm

Re: Invalid view console in ZM_WEB_HOMEVIEW does not exist

Post by Pjoms »

zemerdon wrote: Sun Mar 12, 2023 4:12 am Went from 1.36.33 to 1.37.37

Keep getting...
Did you solve this?
I experience the same issue after upgrading from 1.37.2x to 1.37.37.

I´m not able to find either "DocumentRoot /var/www/html" or "DocumentRoot /usr/share/zoneminder/www" in any Apache config-files, but there is a line in the Zoneminder config-file under Apache that contains "/usr/share/zoneminder/www"

Beside all the errors in the Zoneminder log, I am not experience any other obvious issues.
zemerdon
Posts: 15
Joined: Wed Dec 01, 2021 2:23 pm

Re: Invalid view console in ZM_WEB_HOMEVIEW does not exist

Post by zemerdon »

Didn't solve, went back to 1.36.33 and works perfectly.
User avatar
iconnor
Posts: 2879
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Invalid view console in ZM_WEB_HOMEVIEW does not exist

Post by iconnor »

In 1.36.33 values for homeview were ?view=console I think... but in 1.37 It wuold just be console, and we specifically check for valid values. This code will be going into 1.36.34 as well as it is actually a security vulnerability.
Post Reply