Notice: CMSB v2.65 Beta (Mar 31, 2015)

Also, we made some small changes to the config files: .htaccess, .user.ini, and php.ini to help detect which config files are loading.  We'd like to show this in the admin menu in future versions.

We've tested them on a few servers without issue, but if you do get any errors with any of those files, just remove the settings at the bottom of each file under "Identify loaded config files" and then post to let us know.  

The settings look like this:

.htaccess
  php_value highlight.html '#000000; CMSB_CONFIG_HTACCESS'
  php_value date.default_latitude '11.1111 CMSB_CONFIG_HTACCESS'

.user.ini
  highlight.string       = '#DD0000; CMSB_CONFIG_USER_INI'
  date.default_longitude = '33.3333 CMSB_CONFIG_USER_INI'

php.ini
<IfModule mod_php5.c>
  php_value highlight.html '#000000; CMSB_CONFIG_HTACCESS'
  php_value date.default_latitude '11.1111 CMSB_CONFIG_HTACCESS'
</IfModule>



Thanks!

Hi Dave

I performed a fresh install of Beta v2.65 this morning and encountered an unnecessary error being logged.

E_NOTICE: Undefined index: QUERY_STRING

xxxxxxxxxxxxxxxxxxxxx\lib\common.php (line 108)

xxxxxxxxxxxxxxxxx/admin.php

You could just suppress it I suppose but I'm not a big fan of suppressing errors.

Line 108: if (sha1($_SERVER['QUERY_STRING']) == '3831b0376dab413292f03dd30523e749bdd3279e') {

A suggestion:

if (isset($_SERVER['QUERY_STRING']) && sha1($_SERVER['QUERY_STRING']) == '3831b0376dab413292f03dd30523e749bdd3279e') {

Thanks Glen!

That's really useful.  We generally don't check for QUERY_STRING being set because it's suppose to be always set (even to blank)  So if it's not set on some servers out in the wild we might want to handle that differently.

Do you know if it was it caused through the web or a command-line script (eg cron).  

And can you let me know some specifics from phpinfo? eg: admin.php?menu=admin&action=phpinfo

• PHP Version
• Server API
• _SERVER["SERVER_SOFTWARE"]
• Operating System  (should be listed on the bottom of admin > general).

>You could just suppress it I suppose but I'm not a big fan of suppressing errors.

Agreed on that point, you'll likely see less suppression in the codebase moving forward, especially since there's now the overhead of custom error handling functions being called.  ...and we're pragmatic, so sometimes you'll still see it. 

Thanks!

Hi Dave

This is my very old ITIStudios testing server that is about to be retired in a few weeks or so.

It's a win 2000 Advanced server running IIS ( IIS 5 I think?).

The php (v5.2.17) and the mysql (v5.0.51) versions are not compatible with the newer CMSB versions and didn't bother to mention it because it's not a flaw with 2.65

In the php.ini file "Notify" is part of the error reporting and may be excluded on production servers which could be why you haven't see this before.

The error only occurs when you login and logout otherwise everything is fine.

That being the case we still don't want to log it as an error when it's not.

As part of the test I added this code at line 104

if (isset($_SERVER['QUERY_STRING'])) echo "QUERY_STRING is set"; else echo "QUERY_STRING is not set";

Just to clarify:

When the page loads for the first time "it is not set"

After entering the login credentials and click the Login " button "it is not set"

Normal navigations if fine "is set"

When you click the "logoff" link, "it is not set" (but this is really the same as when the page loads for the first time)

Hi Glen, 

Yea, that's super weird because IIS isn't following the standards.  QUERY_STRING is suppose to always be set, even if only to a blank string (RFC 3875 - 4.1.7). 

Anyways, I added "if (isset($_SERVER['QUERY_STRING']) && " to the code as per your suggestion and that will be in the next beta.

Thanks!  And let us know if you spot anything else.  Cheers!