vBulletin 4.2.5

[Mark.B]

What version of vBulletin is your current forum running?

only 4.2.5 is compatible with php 7. Earlier versions such as 4.2.3 are not.

[Bere]

Fresh install of 4.2.5 alpha 3 on my new nginx/php7 server seems to work fine.

Moving my current forum over doesn't:

#1 : vbstop() called in ..../includes/class_core.php on line 5854
#2 : us_get_string() called in ..../includes/class_core.php on line 5724
#3 : us_get_value() called in ..../includes/class_core.php on line 5771
#4 : us_get_array() called in ..../includes/class_core.php on line 5720
#5 : us_get_value() called in ..../includes/class_core.php on line 5695
#6 : vb_unserialize() called in ..../includes/class_core.php on line 1582
#7 : vB_Datastore->register() called in ..../includes/class_core.php on line 1725
#8 : vB_Datastore->do_db_fetch() called in ..../includes/class_core.php on line 1694
#9 : vB_Datastore->fetch() called in ..../includes/init.php on line 238
#10 : require_once(..../includes/init.php) called in ..../includes/class_bootstrap.php on line 101
#11 : vB_Bootstrap->init() called in ..../includes/class_bootstrap.php on line 72
#12 : vB_Bootstrap->bootstrap() called in ..../global.php on line 26
#13 : require_once(..../global.php) called in ..../forum.php on line 67

Expected " at position 17823 found .

Disabled hooks, same issue. Any ideas?

I ran into the same error, see my post from Wed 5th Oct '16, 8:57am. All smilietext fields were wrong (colon and quotes were twisted). I fixed this within tools.php and "Bitfiled Cache" update.

Paul M
Seems the problem with the smilietext fields in the datacache table is available in long running installations.

best regards

Guido

[Paul M]

4.2.5 Alpha versions are set to throw a fatal error if they encounter unserialize errors, which is what is happening here.

This was deliberate to track down areas that we could not use the emulator (mainly where serialized objects are used).
Beta 1 onwards will return false (as the php function does) and carry on running - it will, however, log a php warning for the failure.

The root problem here is the data you are trying to unserialize - its is broken or invalid, we cannot fix that.

[sub_ubi]

4.2.5 Alpha versions are set to throw a fatal error if they encounter unserialize errors, which is what is happening here.

This was deliberate to track down areas that we could not use the emulator (mainly where serialized objects are used).
Beta 1 onwards will return false (as the php function does) and carry on running - it will, however, log a php warning for the failure.

The root problem here is the data you are trying to unserialize - its is broken or invalid, we cannot fix that.

I'm not sure if this qualifies for Jira, but I believe I found the issue:

from the "datastore" table under the "options" value, there were several cases of ";i:" that didn't work until they became ";d:". Here's one line for example:

before

comic_sans_ms|'Comic Sans MS', Arial, Helvetica, sans-serif";s:17:"vbblog_ratingpost";i:2;s:20:"vbblog_usermaximages";i:4;s:20:"vbblog_usermaxvideos";i:1;s:18:"vbblog_stat_cutoff";i:30;s:13:"vbblog_blocks";i:127;s:20:"vbblog_blockmaxchars";i:2500;s:21:"vbblog_blockmaximages";i:10;s:21:"vbblog_blockmaxvideos";i:1;s:19:"vbblog_pagemaxchars";i:7500;s:20:"vbblog_pagemaximages";i:10;s:20:"vbblog_pagemaxvideos";i:1;s:19:"vbblog_blogthispost";i:1;s:20:"vbblog_nextprevlinks";i:0;s:20:"blog_commentsperpage";i:20;s:23:"vbblog_commentmaxvideos";i:1;s:23:"vbblog_commentmaximages";i:4;s:18:"postrelease_enable";s:1:"0";s:17:"allowchangestyles";i:1;s:11:"cleargifurl";s:9:"clear.gif";s:14:"storecssasfile";i:1;s:6:"cssurl";s:0:"";s:9:"usepopups";i:1;s:13:"legacypostbit";i:1;s:11:"showimicons";i:1;s:21:"searchenginereferrers";s:40:".google.

after

comic_sans_ms|'Comic Sans MS', Arial, Helvetica, sans-serif";s:17:"vbblog_ratingpost";d:2;s:20:"vbblog_usermaximages";d:4;s:20:"vbblog_usermaxvideos";d:1;s:18:"vbblog_stat_cutoff";i:30;s:13:"vbblog_blocks";d:127;s:20:"vbblog_blockmaxchars";d:2500;s:21:"vbblog_blockmaximages";d:10;s:21:"vbblog_blockmaxvideos";d:1;s:19:"vbblog_pagemaxchars";d:7500;s:20:"vbblog_pagemaximages";d:10;s:20:"vbblog_pagemaxvideos";d:1;s:19:"vbblog_blogthispost";i:1;s:20:"vbblog_nextprevlinks";i:0;s:20:"blog_commentsperpage";d:20;s:23:"vbblog_commentmaxvideos";d:1;s:23:"vbblog_commentmaximages";d:4;s:18:"postrelease_enable";s:1:"0";s:17:"allowchangestyles";i:1;s:11:"cleargifurl";s:9:"clear.gif";s:14:"storecssasfile";i:1;s:6:"cssurl";s:0:"";s:9:"usepopups";i:1;s:13:"legacypostbit";i:1;s:11:"showimicons";i:1;s:21:"searchenginereferrers";s:40:".google.

I didn't make the change myself, but after copying & pasting a few times it suddenly changed on its own. I have no idea why. Any clues?

No more errors, and the upgrade proceeded well. Enjoying PHP 7, apcu and opcache.

[Paul M]

Of course, I meant 4.2.5 above, not 4.2.3, corrected that typo.

I would expect i to work, i is integer, d is double, those look like integers, but either should work.

The error you got doesnt indicate it failed on those anyway, it failed on decoding a string.

[ivanp]

Does 4.2.5 work on PHP 7.1, too?

[Paul M]

It should do, that is the intention,but obviously it relies on people using 7.1 and reporting any issues.


JFYI, Beta 1 should be released before the ThanksGiving weekend

[Paul M]

4.2.5 Beta 1 has been released today.

[WriteToEnlight]

(Didn't see a button to choose to try to delete at the moment)

[Bere]

Great news! Is it suitable for productive use?

[Paul M]

It should be, there are no know issues atm.

Of course, the more people who do use it, the more likely it is we will find any (as yet unknown) problems.

[Domenico]

Hmm, it stops here on my test forum.

[LIST][*][B]Upgrading to 4.2.4 Beta 1[/B][*]Step 1 - Skipping step, not needed[*]Step 2 - Altering strikes Table (1 of 1)[*]Step 3 - Altering adminlog Table (1 of 1)[*]Step 4 - Altering moderatorlog Table (1 of 1)[*]Step 5 - Altering user Table (1 of 1)[*]------ Query Status ------[*]Time Elapsed: 00:02:16, State: copy to tmp table, Query: ALTER TABLE post CHANGE ipaddress ipaddress VARCHAR(45) NOT NULL DEFAULT ''[*]------ Query Status ------[*]Time Elapsed: 00:02:32, State: copy to tmp table, Query: ALTER TABLE post CHANGE ipaddress ipaddress VARCHAR(45) NOT NULL DEFAULT ''[*]------ Query Status ------[*]Time Elapsed: 00:02:57, State: copy to tmp table, Query: ALTER TABLE post CHANGE ipaddress ipaddress VARCHAR(45) NOT NULL DEFAULT ''[/LIST]

[Paul M]

You either have a very slow server, or a large post table, its simply taking MySQL a long time to run the ALTER.

You can either wait for it to complete and run the upgrader again if necessary, or better still, use the CLI upgrader (a far better choice on large forums).

[CB|Steffen]

Please ignore this post. I just want to subscribe to this topic but the clicking the "Subscribe" button shows an error "Can not subscribe".

[sub_ubi]

I kept getting vb_unserialize errors, but after each error I'd run upgrade again and it eventually finished.

<?xml version="1.0" encoding="windows-1252"?> <br /> <b>Warning</b>: vb_unserialize: 01 - Finished, but not at end of string in <b>/var/www/blah/forums/includes/class_core.php</b> on line <b>5709</b><br /> <upgrade> <message replace="0">Product upgrade completed</message> <status>Status: Processing XML, Step 1 of 9</status> <longversion>forumrunner</longversion> <version>final</version> <nextstep>1</nextstep> </upgrade>

[Paul M]

Errors & warnings indicate a potential problem, and should be investigated.

Unfortunately, the line you posted is not enough information to know what was generating them.

I wish you had stopped at that point so we could have taken a look.
Do you happen to have a copy of your database, before you upgraded ?