PHP parse error

[shk.naim]

Hello All,

I'm facing a strange problem. Whenever I try to edit and save any existing templates I get a PHP parse error as:

Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in /home/vexxnutr/public_html/fuelfitness.info/community/forums/includes/adminfunctions_template.php(3537) : eval()'d code on line 1

This is likely caused by a malformed conditional statement. It is highly recommended that you fix this error before continuing, but you may continue as-is if you wish.

Interestingly above errors eval()'d code on line 1 this lines line number (line 1) is changing to 1 or 2 or anything.

What could be the reason(s)? I'm not been able to modify my vb forum due to this error. Kindly help on this asap.
Thanks!!

[Greg]

What version of vBulletin and what template are you using?

[bigH2O]

Have you attempted to upgrade vBulletin with modifications installed? That's what it sounds like, because those fields don't exist in a default vBulletin installation. vBulletin 4 is a serious re-write, and will break almost every < 4.0 installation out there if you don't completely disable the mods. Try adding the following line to the beginning of your config.php file, right under the <?php> directive:
define('DISABLE_HOOKS', true);


This will disable all addons that you have on your site and if the site works as expected from there, then you're sniffing the trail as to where the problem is. Let us know how that works for you, and we can give you further advice as to how to proceed.

[shk.naim]

My vBulletin version is 3.5.4
Recently I've copied my vBulletin forum to a testing server to make some modifications.
Is this causing problem?
Also I put the above code in config.php but the same problem still persisting.

[shk.naim]

No one is there to try on this issue?:mad:

[bigH2O]

vB 3.5.4 is way past End Of Life at this point, and so many changes have been made to PHP that there is no telling what is going on with your problem. You might find somebody to debug it and bring the problems into compliance, but I don't know anybody who would take on the challenge for less than the cost of just bringing your vB software up to current.

[shk.naim]

OK I understand what you are saying.
But I'm curious on what could be the causes of such malfunction?
Please clarify if you don't mind.

[bigH2O]

I can only assume that you are running vB on a host somewhere. That host is going to upgrade their software (Apache, PHP, MySQL, etc) to the latest stable release of the available software on a weekly, if not nightly basis, for security reasons. All of the vendors of software that rely on other software will then upgrade their software so that it all stays compatable.

3.5.4 of vBulletin is right about 4 years old now. You can't expect 4 year old software to stay compatable with the latest builds of the server software that it runs on top of.

Besides that, 3.5.4 is so full of security holes at this point that it's amazing that your host will let you run it anyway. I wouldn't let you run it on my server. My suggestion is to buy the latest version of vBulletin, but don't install 4.0 yet, downgrade to 3.8.4 which is stable and compatable with all of the backend stuff that your server is likely running.

[shk.naim]

Thanks bigH20 for the quick reply.
If the above mentioned issue is ignored ,what can be the other causes?
I'm just asking to get better understanding with vB issues.

[bigH2O]

There really is no ignoring of the above mentioned issue. Is your license a valid owned license or are you running a bootleged copy?

[shk.naim]

I've a valid license copy. I just copied my forums file into a test server to make some changes.This server has php version above 5.2. Is this causing problem?

[bigH2O]

I'm sorry, but supporting a 4 year old legacy system is beyond what I'm willing to do at this point. I have a full plate supporting current software. Maybe somebody else here will step up to the plate and give you some advice... but I've already told you everything I know... you've got tables that are not part of vBulletin reporting MySQL errors which are most likely caused by an incompatibility in PHP. I simply don't have the time to dig back through old versions of vBulletin to determine what versions of various software they were compatable with. I'm truly sorry. You can ask for paid services at vBulletin.org if nobody here can step up to the plate... but for me, I just don't have an answer nor the time to research it for you, no matter what the price.