Upgrade error, after upgrading from 4.8d to 4.85

[hotfocus]

Can't seem to figure out the problem.

Notice: Use of undefined constant MOBILE_CAT - assumed 'MOBILE_CAT' in on line 31

Notice: Use of undefined constant MOBILE_CAT - assumed 'MOBILE_CAT' in on line 31

Notice: Use of undefined constant VB3_INTEGRATION - assumed 'VB3_INTEGRATION' in on line 41

Notice: Use of undefined constant VB3_ENHANCEDINT - assumed 'VB3_ENHANCEDINT' in on line 42

Notice: Use of undefined constant VB3_COMMWYSIWYG - assumed 'VB3_COMMWYSIWYG' in on line 43

Notice: Use of undefined constant VB2_INTEGRATION - assumed 'VB2_INTEGRATION' in on line 49

Notice: Use of undefined constant VBP2_INTEGRATION - assumed 'VBP2_INTEGRATION' in on line

[hotfocus]

P.S. I tried a test fresh install and I still get the same errors.

[Michael P]

Make sure your config-int.php file was uploaded.

[AllenAyres]

I'm getting the same errors. It's on a Win2K server, if that helps. That file is uploaded

[Michael P]

Well, it appears the error is coming from config-int.php - although I'm not sure why since it's on a define() statement. You might consider turning off "notices" in your PHP.INI setup since it can produce unnecessary messages like these.

We also have this line in pp-inc.php:

error_reporting (E_ALL ^ E_NOTICE);

which could be added to the top of config-int.php to turn off these messages.

The only other thing I can find, which may or may not resolve the issue for your configurations, is to add quotes around the variables in the lines with define():

define( "MOBILE_CAT", -1 );

and do that for each line 31, 41-43, 49 and 56.

[hotfocus]

Hi Michael, yes the config-int.php was uploaded and it's running on a Win 2003 Server.

[hotfocus]

Ok I just turned off the errors and everything seems to be working fine. But is there anyway to fix this issue in the next release? I do like to keep the errors on so that I can diagnose other site related problems. If we didn't have our own server, I don't think hosting companies will turn off errors just for us.

[AllenAyres]

Thanks, looks like the quotation marks fixed the issue