What are the drawbacks of hard-coding the SUPERUSER_PROFILE?

**AeoAeo330** · 12 Jan 2012, 08:06 PM

I've been in the process the last couple of days fending off errors updating one of our zen cart installations from 1.3.9h to 1.5.0. It has been an entirely manual process, not an upgrade script. It is a self-hosted store, currently on a CentOS 6.2 install with all the current patches.

The front-end of our store has worked just fine so far (not done testing yet), but the admin side has had error after error. Most have had a satisfyingly simple solution (Oh, I forgot to merge this file... Oh, for some reason this file didn't upload...) Up until I encountered this one:

Code:

WARNING: An Error occurred, please refresh the page and try again.

Following this error log in the cache directory...

Code:

PHP Fatal error: 1054:Unknown column 'SUPERUSER_PROFILE' in 'where clause' :: SELECT admin_id from admin
          WHERE admin_id = 2
          AND admin_profile = SUPERUSER_PROFILE in /var/www/sites/pocketdoorproducts/includes/classes/db/mysql/query_factory.php on line 101

...I wound up at line 53 of /admin/includes/functions/admin_access.php, specifically staring that SUPERUSER_PROFILE in the face. For some odd reason the SQL query is receiving the string quite literally as SUPERUSER_PROFILE instead of substituting it for the number 1 as defined in /admin/includes/init_includes/init_admin_auth.php.

What's got me, though, is it's receiving the value for ADMIN_TABLE just fine. I hard-code in the value of 1 in place of SUPERUSER_PROFILE and it loads right up.

My question then is: What are the drawbacks to just leaving that? I'm not real keen on the idea, but the boss is getting antsy. Would I just be committing sacrilege or will this break some functionality that I'm not seeing?

**DrByte** · 12 Jan 2012, 10:45 PM

Is your init_admin_auth.php actually loading?
Or do you have one in the subfolder named overrides which is taking precedence, which you've not upgraded with the new content?

**AeoAeo330** · 13 Jan 2012, 03:22 PM

Thanks, DrByte. That not only solved the issue, it also gave me the admin rename warning I was expecting but never saw.

I really need a new job... lol - All this rush rush pressure and I'm skipping over the obvious.

Thanks, again.

**welchyboy** · 2 Jan 2015, 02:26 AM

I am receiving this error which is resulting in a blank page when I log into the admin side. Any ideas on how to fix it. It occurred whenever I upgraded my site from 1.38a to 1.54

[01-Jan-2015 18:26:48 America/Chicago] PHP Fatal error: 1054:Unknown column 'SUPERUSER_PROFILE' in 'where clause' ... ==> (as called by) /home/stxmill/public_html/testzen/admin/includes/functions/admin_access.php on line 69 <== in /home/stxmill/public_html/testzen/includes/classes/db/mysql/query_factory.php on line 155

**DrByte** · 2 Jan 2015, 03:49 AM

Originally Posted by welchyboy

I am receiving this error which is resulting in a blank page when I log into the admin side. Any ideas on how to fix it. It occurred whenever I upgraded my site from 1.38a to 1.54

[01-Jan-2015 18:26:48 America/Chicago] PHP Fatal error: 1054:Unknown column 'SUPERUSER_PROFILE' in 'where clause' ... ==> (as called by) /home/stxmill/public_html/testzen/admin/includes/functions/admin_access.php on line 69 <== in /home/stxmill/public_html/testzen/includes/classes/db/mysql/query_factory.php on line 155

Same resolution as given to the person whom you replied to above.