UBB.threads PHP Forum Software Community Forums UBB.threads 7 Installation and Upgrade Support PHP has encountered a Stack overflow

Ok, I figured I'd give it a go at installing 7.0 and then upgrading from 6.5.5

I go thru the install with pretty much no issues and then run through thread_import.php just fine, except as soon as it finishes and give me the link to go ahead and log into my newly setup/imported 7.0, I click the link and get a "PHP has encountered a Stack overflow" error trying to load "/ubbthreads.php?ubb=login".

Running Win2k3 SP1, IIS6 (isapi), MySQL - 4.0.26-nt, PHP 4.4.4 (php4isapi.dll).

Download of 7.0 was today.
Imported from a fully functioning 6.5.5 site.

What little I can find on that error hints at Zend Optimizer, but I don't even have that installed.

Any help would be greatly appreciated...thanks in advance.

Ok, not sure how header.php's usage has changed, but I found the problem lies there.

If I blank out that file (remove all my custom header stuff), the problem goes away, but the very same custom header that works under 6.5.5 on the very same server throws that error under 7.0.

**Edit: If I leave out everything from <? to ?> and leave in only the regular html, it loads just fine.... I'm obviously doing something wrong for how it's done now, just not sure what.

Hmm, the header.php include file really hasn't changed at all from the old version. It includes it in the same manner as before. Can you post the php portion of your header code here? Or if you don't want to do that, if you can open a support ticket or PT me with your admin info and put the full header back that errors out then maybe I can take a look and get some kind of idea.

I figured it out actually.... I was using the authenticate() function in the header to get the logged in user's name and some other info up there to display some stuff based on the users age (it was a quick copy/paste type hack from another script, so I didn't really think about what other fields authenticate() was grabbing). Something in there was the cause, but I haven't fully isolated it yet. I probably just need to change how I'm getting some info up there.