On 12/15/05, Daniel Watts <d@...> wrote:
> >>I upgraded from 1.3 and the release notes said that only to remove the
> >>previous patch from 2.0.3.
> >>I did run the patch with this latest version...I can see the line in
> >>strings.php as it is supposed to be:
> >>include_once(SM_PATH . 'plugins/compatibility/functions.php');
> > That's OK. You need to get rid of any patch from earlier versions,
> > since those may run the code before $version is initialized. There
> > were two patch locations prior to the newest one in strings.php. Make
> > sure they are both gone. The only other reason this may be happening
> > is if maybe a plugin is including the compatibility functions file
> > directly before the time is right. There are still a bunch of plugins
> > out there
> [sorry paul - i forgot to cc this to the newsgroup. doing so now]
> So just so I'm clear - this part of the code is *supposed* to remain
> commented out and the reason it doesn't work is that I must have a patch
> in place from my version 1.3 install?
Yes, it is commented out on purpose.
> However I only have one reference to the compatibility plugin in all my
> functions/* files:
> [root@... functions]# grep compatibility * -i
> strings.php:include_once(SM_PATH . 'plugins/compatibility/functions.php')=
Well, then try removing your plugins (easiest to just put block
comments around them all) and reenable one at a time until it breaks.=20
If plugins are not the cause, we can fish around in the core I guess,
but I don't see any reason this would be broken for you.