Fatal error: Please upgrade to vBulletin 3.5.0 or greater in /includes/init.php on li

[dwh]

I've gotten this repeatedly on one box where I upgraded from an earlier vbulletin and also on another box with a clean install:

Fatal error: Please upgrade to vBulletin 3.5.0 or greater in /includes/init.php on line 169

Reuploading the include files helps temporarily but shortly thereafter I get the same problem again.

Anyone else have this problem? Any idea what's going on?

[Zachery]

Disable TurkMMCache

[Scott MacVicar]

TurkMMCache is old use eAccelerator

[dwh]

I never installed Turk on that box. I think I did do eaccellarator. What files and where should I look to try and find it. And how to uninstall it?

[dwh]

I see eaccelerator in /tmp but no turkmmcache

[Steve Machol]

Update it to the latest version.

[dwh]

Thank you Steve.

[Mr_Butter]

Is that error going to change some day to actually say it has to do with eaccelerator and turk?

[Scott MacVicar]

Well we dont know if it has to do with eaccelerator or turk, its actually just caused by a variable that should be filled being empty.

I think you can fix it by just restarting apache since its caching old scripts.

[somedudeer]

I don't have any of those, but im still getting the error.

[paulius]

It's funny...

I've had the same issue. But, this error came out of the blue! I've been playing with vBulletin 3.5.0 RC1 the whole day and WHAM is appeared.

Now, I had eAccelerator installed. So I disabled it and it works well.

However, I had the latest version and I would like to know how could I make eAccelerator live in harmony with vB. How can I clear the eAccelerator cache?

[somedudeer]

Well, i was using vB 3.5.0 Beta 3, upgrade to 4 (in rc1) then RC 1, and bam, i got this!

[FlowerChat]

Same problem here ... host disabled caching and restarted apache, no improvement.

Ryan

[paulz]

I have this problem as well. My host confirms that TurkMMCache is not installed on my server. Stupid me accidentally ran the upgrade on my live server instead of my test one. Is there any way to downgrade from RC1 until this problem is flushed out totally and fixed?

[Steve Machol]

There is no way to downgrade. You would need to restore a backup of the database made prior to the attempted upgrade.