loadINI: Undefined array key "PATH_INFO" while upgrading from 2.14 to 3.65

7 posts by 3 authors in: Forums > CMS Builder
Last Post: Yesterday at 10:43am   (RSS)

By garyhoffmann - Saturday at 7:06am

I have a site that I have to upgrade from 2.14 to 3.65.  I get the following error while doing the upgrade:

loadINI: Undefined array key "PATH_INFO"

This is at the earliest spot in the upgrade, so I think it's OK to not restore the database.  If I take it back to the saved cmsAdmin folder, it comes up OK.

I looked at the software and it seems to be doing the right thing with PATH_INFO, but I can't say for sure.

I am looking at the code now, but there is quite a bit.  Has anyone run into this?

By Tim - Monday at 5:15pm - edited: Monday at 5:17pm

Hi Gary,

Well I know that $_SERVER["PATH_INFO"] would not be defined if you are attempting to run the code through the Command Line Interface (CLI) like can be done through scheduled tasks. I would start there in finding a cause. In the error message, does it show a filename and line number or is that just appearing on the front-end of the site as a generic error? Do you see anything in the error logs of CMSB?

Have you tried disabling all your scheduled tasks? I am not too familiar with the very old versions of CMSB so perhaps there is a script there that is breaking on the upgrade and could be ran through a scheduled task.

Let us know if you find any additional information. :)

Tim Hurd
Senior Web Programmer
Interactivetools.com

By garyhoffmann - Yesterday at 5:03am

I am not running through the command line nor is there any more for the error message.  That is it.  I will look at the database directly to see if there are any scheduled tasks, but I doubt it.

I was hoping you'd have a bit of a better answer :).  Oh well, I will try to solve it on my own.

By garyhoffmann - Yesterday at 7:38am

Now I have two sites that won't upgrade because of loadINI: Undefined array key "PATH_INFO".  I will have to solve this condition quickly.

By garyhoffmann - Yesterday at 9:55am

I did that!

By garyhoffmann - Yesterday at 10:43am

Wow, that is strange...The PATH_INFO error was coming out of parse_ini_file which is built in to PHP.  

I commented out the die() statement from within loadINI and it seemed to work without issue...at least that I have seen.

I'm going to do the same for the other site that is a problem right now, but food for thought on this one.