Issue: Upgrade to 4.1.0 from 4.0.19 - blank page when running upgrade

A blank page is probably a PHP error. You will need to determine what that error message and stack trace are before we can assist. You can usually find this information in your PHP error logs, or by enabling display_errors in php.ini.

If you need direct assistance, you can submit a ticket and we will investigate your installation: https://www.vaultwiki.org/members/?d...e&productid=20

Hi and thanks for getting back so soon. I'll gather a little more info and will post the specific error messages here.

I don't see anything in my PHP error log. It's empty actually. I uploaded all of the 4.1.0 files just now and tried the upgrade again just to make sure that I hadn't made a mistake there but no luck. Still getting a blank page at /wiki_cp.php?panel=upgrade.

I've opened a ticket and would be grateful if you could take a look at my site.

Fixed on your site and in the next release. This was related to the usage of internal PHP output buffers.

Hi and many thanks for looking into this. The upgrade dialogue was available but after many restarts I'm now stuck as follows:

Upgrading to 4.1.0 RC 2
Step 41

and with the following error:

An exception occurred: <ul><li>A required field called <em>contenttypeid</em> is missing or has an invalid value.</ul>Unable to proceed with save while $errors array is not empty in class <strong>vB_DataManager_IP_Data</strong> in [vw-depot]/includes/class_dm.php on line 849

#0: vw_CP_Progress_View->handle_php_error()
#1: trigger_error() in [vw-depot]/includes/class_dm.php at line 849
#2: vB_DataManager->has_errors() in [vw-depot]/includes/class_dm.php at line 872
#3: vB_DataManager->save() in [vw-depot]/includes/class_dm_ip_data.php at line 143
#4: vB_DataManager_IP_Data->save() in [vw-core]/model/ip/vb4.php at line 54
#5: vw_IP_Model_vB4->log() in [vw-depot]/vault/install/lib/upgradepath/steps/4/1/0/rc/2/3X/vb3.php at line 255
#6: vw_Install_UpgradePath_Steps_410rc2_3X_Controller_vB3->import_ip_id() in [vw-depot]/vault/install/lib/upgradepath/steps/4/1/0/rc/2/3X/vb3.php at line 173
#7: vw_Install_UpgradePath_Steps_410rc2_3X_Controller_vB3->{closure}() in [vw-core]/controller/progress/steps/vw.php at line 85
#8: vw_Progress_Steps_Controller->call() in [vw-core]/controller/progress/steps/vw.php at line 56
#9: vw_Progress_Steps_Controller->execute() in [vw-depot]/vault/install/lib/upgradepath/vw.php at line 78
#10: vw_Install_UpgradePath_Controller->exec_script() in [vw-core]/controller/progress/vw.php at line 169
#11: vw_Progress_Controller->execute() in [vw-core]/view/response/progress/vw.php at line 27
#12: vw_Response_Progress_View->stream() in [vw-core]/view/response/progress/vw.php at line 63
#13: vw_Response_Progress_View->render() in [vw-core]/view/ui/vw.php at line 75
#14: vw_UI_View->output() in [vw-depot]/vault/helper/vb/global.php at line 98
#15: require_once() in [vw-depot]/admincp/wiki_cp.php at line 91

Thanks for reporting this issue. Some of the steps were being performed in the wrong order.

The upgrade is now finished on your site. However, I noticed that some other templates are giving you syntax errors, which makes it difficult to rebuild styles and possibly other tasks. Mostly they are CSS templates. You may want to investigate that because it could make your life difficult in the future. Unfortunately vBulletin 4 is no longer supported by their developers, but maybe there is a solution posted somewhere.

Again, thanks for sorting this out. Not your fault but unfortunately this has resulted not only in css errors but also in the total loss of at least one very large wiki page. I was hoping that it was just a formatting issue but when I tried to edit the page all of the content was missing. That's a few months work gone just on that page. I'll have to revert to a backup for now but will try the upgrade again at a later point.

Which wiki page was affected in this way? Feel free to PM me a link.

As for the CSS errors, please elaborate on what you were seeing. I saw the style rebuild complain about not being able to parse many CSS templates, but none of the templates listed were part of VaultWiki.

Hi Pegasus,

The errors (forum home page missing colours in header and footer, different font type etc) disappeared on the main site after a couple of hard refreshes. They are only now visible in the wiki with menus on the landing page stacked at top left and a couple of other things.

As I thought I might have to revert to a backup anyway I upgraded vb to 4.2.5. to see if it would work. Only one hack seemed to be problematic but there was a fix for it at vbulletin.org so as far as I can tell, 4.2.5 seems to be working normally on PHP 7.0 (not on 7.1 though which throws errors).

I have sent a PM with a link to the page that I mentioned.

Another problem is with wiki attachments that were inside pages prior to the upgrade. With lazyload on, a red cross ("Resource not found") is shown instead of the attachment. With it off, the attachments do not load.

Edit:

admincp attachment search results show that attachments uploaded exclusively to a wiki page are no longer available so they seem somehow to have been deleted.

The CSS problem appears to be related to the vBulletin setting "Add Template Name in HTML Comments" which is putting HTML inside the CSS and making the CSS unreadable by the browser. This should not be hard to fix.

I will look at the case of the mysteriously missing page-content shortly.

Wiki attachments will not be listed in vBulletin AdminCP's attachment search since wiki attachments are not post-attachments. I have PM'd you about the attachments for you to check.

I don't believe there is any need to restore a backup at this point, at least for VaultWiki. If you have a backup, we can pull missing data from it directly without restoring.

That's great news, thank you. Attachments are now working correctly. Also good news that I don't need to restore the site just yet. I have a full site backup in my home directory currently but I'll upload just the .sql.gz to the same place in a bit.

CSS issue is now fixed on your site and in the next release.
The missing content on the cited page was due to TABLE BB-Code having been renamed somehow, possibly by the upgrade, depending what all your starting versions were and what order you upgraded things. I have changed it back to TABLE and now the content is back.

If you notice any other issues, I'd be glad to look into them. For now, I think we've addressed everything on your list.

That's fantastic. Thank you very, very much!

There is one thing that I just noticed. Autolinking isn't working currently and in settings-->wiki links-->Enable Auto Links to Wiki Content there is no option to include forum posts. I just see checkboxes for:

wiki
nonwiki
vbcms
calendar
signature
social
other

With wiki and non-wiki (I assume that this is for the forum?) selected, my wiki pages do autolink to each other but posts on the forum don't autolink to the wiki.

Also noticed that any post on the forum that included a table has now lost formatting. That isn't a huge problem though as I can recreate the tables manually and then save them anew.