vBulletin 4.2.5

[Mark.B]

This happens where the blog product is disabled.

You need to make sure the blog product is enabled before running the upgrade script (you can disable it again afterwards).

[rrk]

I am upgrading from 4.2.1 to 4.2.5. When I ran the upgrade script I got below error.

• Upgrading to 4.2.5 Release Candidate 2
• Upgrading to 4.2.5
• Processing Blog
• .........................
• Step 17 - Skipping step, not needed

At this stage of upgrade after Step #17, I got below error. How do I proceed from this point? Please help


Unexpected Text:
<?xml version="1.0" encoding="windows-1252"?>
<br />
<b>Warning</b>: mysqli_query(): (42000/1064): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ' )
)
WHERE ipid IS NULL' at line 6 in <b>/home/rrkr2i/public_html/forums/includes/class_core.php</b> on line <b>1386</b><br />
<?xml version="1.0" encoding="windows-1252"?>
<errors>
<error><![CDATA[<p>Database Error</p>

Invalid SQL:

SELECT bt.userid, bt.dateline, blogtextid, ipaddress, firstblogtextid
FROM blog_text bt
JOIN blog bl USING (blogid)
LEFT JOIN ipdata ip ON (
bt.ipaddress = ip.ipid AND bt.blogtextid = ip.contentid
AND bt.userid = ip.userid AND ip.contenttypeid IN (, )
)
WHERE ipid IS NULL;

You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ' )
)
WHERE ipid IS NULL' at line 6]]></error>
<error_html><![CDATA[<p>Database error in vBulletin 4.2.5</p>
<p>Invalid SQL:

SELECT bt.userid, bt.dateline, blogtextid, ipaddress, firstblogtextid
FROM blog_text bt
JOIN blog bl USING (blogid)
LEFT JOIN ipdata ip ON (
bt.ipaddress = ip.ipid AND bt.blogtextid = ip.contentid
AND bt.userid = ip.userid AND ip.contenttypeid IN (, )
)
WHERE ipid IS NULL;<p>
<p>
<strong>MySQL Error</strong> : You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ' )
)
WHERE ipid IS NULL' at line 6<br />
<strong>Error Number</strong> : 1064<br />
<strong>Request Date</strong> : Tuesday, November 10th 2020 @ 07:17:37 AM<br />
<strong>Error Date</strong> : Tuesday, November 10th 2020 @ 07:17:38 AM<br />
<strong>Script</strong> : http://xxxx/forums/install/upgrade.php<br />
<strong>Referrer</strong> : http://xxxx/forums/install/upgrade.php<br />
<strong>Classname</strong> : vB_Database_MySQLi<br />
<strong>MySQL Version</strong> : 10.3.27-MariaDB<br />
</p>]]></error_html>
</errors>

[BirdOPrey5]

As of the time this thread was current. it worked. At this point there is no longer any point to logging bugs in 4.2.5. Security exploits can be reported to [email protected] but nothing else will be recorded or fixed.

[Mikethemix]

The snag is that the Jira tracker link posted here is ONLY for v5, not v4.2.5

[TheLastSuperman]

Add the disable hooks code to config.php then see if it will run on php7.0, I had one site recently that worked fine on php7.0 just not 7.1 . Needless to say if you disable the mods it should work, then you can simply disable them all (screenshot the active ones first so you know what to run back on) and turn mods back on one-by-one after each other each time checking to see if the mod you turned back on breaks the site or not (sometimes the error will state the file so you can skip adding disable hooks to config and disable the mod related to the file).

vBSEO can be replaced and mod-rewrite friendly urls used instead with some redirect magic alternatively you can install and run DBSEO (pay for them to install and ask for url hierarchy to be setup the same way note to them that it's important as you wish to retain the old link structure (hierarchy).

It's more than likely vBSEO. Sometimes though errors can show if for example when you recompiled to PHP7.0/7.1 was mysqli extension active? *If it was required the mod may not work until it's working*. Something can simply be disabled and a quick recompile using easy apache could sort.

[Mark.B]

As I mentioned above....old add ons may not be compatible with php 7.

You should not use vBSEO anyway. It was abandoned years ago, it is riddled with security holes, and it certainly isn't compatible with php 7.

[faquick]

I *think* that the problem might be in old add-ons I still have, that I cannot absolutely remove without breaking my site structure and SEO (i.e. the old VBSEO). Still, I am curious to know why I get that syntax error on a core vBulletin file instead of getting another kind of error.

[faquick]

actually now I am getting a problem after switching to PHP 7.x

if I keep it on 5.6.x it works as before, if I use 7.0.x or 7.1.x I get the old syntax error: unexpected '*' in functions.php on line 1576 (that should not happen unless I am running a version lower than 5.6, what could be wrong with php7?)

[Mark.B]

Yup, that is exactly what I am going to do. Since I have other software running on the server, I hoped I could upgrade the PHP interpreter last, so I am going to alter slightly my plans. But the vBulletin steps will be as you advised.

Thank you.

You can always use php 5.6 if that helps. 4.2.5 works with that.

[faquick]

Yup, that is exactly what I am going to do. Since I have other software running on the server, I hoped I could upgrade the PHP interpreter last, so I am going to alter slightly my plans. But the vBulletin steps will be as you advised.

Thank you.

[Mark.B]

So, the correct path would be FIRST updating to PHP 7.x and THEN upgrading vBulletin, otherwise the upgrade script would not work. Did I understand correctly?

Yes, that's correct.

You need to do the two in close succession though, as your existing forum won't work on php 7.

Best to close the site, back up database, upgrade php, upgrade vBulletin, open site.

[faquick]

So, the correct path would be FIRST updating to PHP 7.x and THEN upgrading vBulletin, otherwise the upgrade script would not work. Did I understand correctly?

[too_cool_3]

Went from 4.2.1 to 4.2.5 yesterday with ZERO issues!

I first asked my host, URLJet, to upgrade MySQL to version 5.6.35 > then I downloaded vB 4.2.5 from here and uploaded it to my server > went to run the upgrade script and ran into an error page due to my outdated PHP version (Parse error: syntax error, unexpected '*' in /yoursite/includes/functions.php on line 1576), so popped into my cPanel and used PHP Selector to upgrade to PHP 7.1.4 > then was able to run the vB upgrade script flawlessly without a hiccup > upgraded to vBadvanced CMPS 4.3.0

Everything works great, noticed a speed boost in page load times and a major drop in server load. Thanks for all your help and answering my questions prior to the upgrade. vB support team, you rock!

Now to save up a few bucks and upgrade to vB5!

[Paul M]

It works perfectly well on php 7.1.3.

You must sort out your database error.

[Alshalan]

Not working on PHP 7.1.3

Database error