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

Issue Tools
- View Changes

June 17, 2020 5:44 AM

stained

Junior Member

Upgrade to 4.1.0 from 4.0.19 - blank page when running upgrade

Had a bit of a nightmare yesterday after deciding to go from VB 4.2.4 to 4.2.5. Things seemed to have worked initially but then the errors started piling in. Found a couple of problematic plugins that didn't like PHP 7.1 and applied fixes. Many hours later things still weren't working correctly (including a failed install of VW 4.1.0 so I decided to go back to PHP 5.6 and to revert the database to a previous save and to overwrite all forum directory files from a backup. I tried to upgrade Vaultwiki again but after a few 404s when trying to find /vault/install/index.php it eventually asked for my admin password and moved to the /wiki_cp.php?panel=upgrade page but this is blank currently (in all browsers). I can't open my Vaultwiki admin page either and when I click on a link (inside a post) that used to open the corresponding wiki page I see the "Vaultwiki is currently being upgraded" notice. So, I'm kinda stuck and would appreciate any pointers as to what to try next.

Thanks

Issue Details

Issue Number 6063

Issue Type Bug

Project VaultWiki 4.x Series

Category Install / Upgrade

Status Fixed

Priority 4 - Warnings / Script Errors

Affected Version 4.1.0 RC 3

Fixed Version 4.1.0

Milestone (none)

Software DependencyvBulletin 4.x w/ ckEditor

License TypePaid

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

June 23, 2020 8:13 AM

stained

Junior Member

In addition to the autolink problem above but related to the tables problem, I'm seeing the following error when I attempt to edit a forum post that existed prior to the upgrade to VW4 and that contains a table:

Fatal User Error: Method vB_BbCodeParser_Wysiwyg::get_cycles is undefined. in ..../vault/core/model/parser/default/wrapper/vw.php on line 50
Trace Data:

#1 : vbstop() called in ..../includes/class_core.php on line 6089
#2 : vbulletin_error_handler() called in on line
#3 : trigger_error() called in ..../vault/core/model/parser/default/wrapper/vw.php on line 50
#4 : vw_Parser_Default_Wrapper_Model->__call() called in ..../vault/core/model/parser/obfuscate/vw.php on line 220
#5 : vw_Parser_Obfuscate_Model->prepare_skip_tags() called in ..../vault/core/model/parser/obfuscate/vw.php on line 47
#6 : vw_Parser_Obfuscate_Model->run() called in ..../vault/core/model/parser/handle/table/vw.php on line 199
#7 : vw_Parser_Handle_Table_Model->protect_tag_pipes() called in ..../vault/core/model/parser/handle/table/vw.php on line 73
#8 : vw_Parser_Handle_Table_Model->parse() called in ..../vault/core/model/parser/handle/vw.php on line 1507
#9 : vw_Parser_Handle_Model->handle_bbcode_table() called in ..../vault/core/model/parser/handle/vb4.php on line 26
#10 : vw_Parser_Handle_Model_vB4->handle_bbcode_table() called in ..../vault/helper/vb/functions/bbcode.php on line 87
#11 : vw_external_callback() called in ..../includes/class_bbcode.php on line 1782
#12 : vB_BbCodeParser->handle_external() called in ..../includes/class_bbcode.php on line 1587
#13 : vB_BbCodeParser->parse_array() called in ..../includes/class_bbcode_alt.php on line 424
#14 : vB_BbCodeParser_Wysiwyg->parse_bbcode() called in ..../includes/class_bbcode.php on line 563
#15 : vB_BbCodeParser->do_parse() called in ..../includes/class_bbcode.php on line 477
#16 : vB_BbCodeParser->parse() called in ..../includes/class_wysiwygparser.php on line 271
#17 : vB_WysiwygHtmlParser->parse_wysiwyg_html() called in ..../includes/functions_editor.php on line 716
#18 : process_toolbar_text() called in ..../includes/functions_editor.php on line 483
#19 : construct_edit_toolbar() called in ..../editpost.php on line 1079
#20 : require(..../editpost.php) called in ..../dbseo.php on line 995

Var Type:

[ NULL ]

Var Data:

null

I can open posts containing tables only if I haven't edited them previously (between VW4 being installed and now). If I edit such posts and save them I am unable to carry out any further edits. I have a few of this type of post that I need to create new tables for but obviously with that error it's impossible.

Would appreciate assistance with this.

Reply

June 23, 2020 11:54 AM

pegasus

VaultWiki Team

For the fatal error, in vault/core/model/parser/obfuscate/vw.php, find:

Code:

foreach ($this->parent->get_cycles() AS $cycle)
				{
					if (!empty($this->parent->tag_definitions["$cycle"]) AND !empty($this->parent->tag_definitions["$cycle"]["$has_option"]))
					{
						foreach ($this->parent->tag_definitions["$cycle"]["$has_option"] AS $tag => $taginfo)
						{
							if ($tag == 'autolink')
							{
								continue;
							}

							$this->preg_skip["$tag"] = preg_quote($tag, '#');
						}
						unset($taginfo);
					}
				}

Replace with:

Code:

				if (isset($this->parent->tag_definitions))
				{
					foreach ($this->parent->tag_definitions AS $defs)
					{
						if (!empty($defs["$has_option"]))
						{
							foreach ($defs["$has_option"] AS $tag => $taginfo)
							{
								if ($tag == 'autolink')
								{
									continue;
								}

								$this->preg_skip["$tag"] = preg_quote($tag, '#');
							}
							unset($taginfo);
						}
					}
				}
				else if (!empty($this->parent->tag_list["$has_option"]))
				{
					foreach ($this->parent->tag_list["$has_option"] AS $tag => $taginfo)
					{
						if ($tag == 'autolink')
						{
							continue;
						}

						$this->preg_skip["$tag"] = preg_quote($tag, '#');
					}
					unset($taginfo);
				}

June 23, 2020 12:00 PM

pegasus

VaultWiki Team

For autolinks, first thing is to check the individual forum settings and make sure under the Wiki-Related Options that autolinking is turned on and set to the correct wiki prefix for the pages you want it to look for. If that is correct, I will need to see an example post that is not linking and the corresponding wiki page that it should link to.

Reply
June 23, 2020 2:03 PM

stained

Junior Member

Nice. The edit worked (obviously) Thanks.

Autolinking: I have one book in the wiki but the rest of the pages are item-specific articles with no prefix. The forums where I need autolinking to happen are set to "no prefix" so in theory it should work.

I'll include examples in the post below this one.

Reply
June 23, 2020 5:19 PM

pegasus

VaultWiki Team

Fixed autolinking on your site and in the next release. The vBulletin settings XML for vw_autolinks was using the wrong data-type since 4.1.0 Alpha 1. This resulted in the setting having the data in the wrong format.

Reply
June 24, 2020 2:21 AM

stained

Junior Member

Excellent. Thanks again for your work on this.

Reply
June 24, 2020 3:31 AM

stained

Junior Member

Sorry, back again

Combination of vb 4.2.5 and PHP 7.0 produce the following error when editing a forum in vb admincp. The options for vault on the forum edit screen only reappear if I revert to PHP 5.6 which is why I was wondering whether this error may be connected to vault.

Call to undefined function eregi() on line 12 in /home/me/public_html/forum/admincp/forum.php(248) : eval()'d code
#0 /home/me/public_html/forum/admincp/forum.php(248): eval()
#1 {main}

Fatal User Error: Call to undefined function eregi() on line 12 in ..../admincp/forum.php(248) : eval()'d code in ..../vb/vb.php on line 286
Trace Data:

#1 : vbstop() called in ..../includes/class_core.php on line 6089
#2 : vbulletin_error_handler() called in on line
#3 : trigger_error() called in ..../vb/vb.php on line 286
#4 : vB::handleException() called in on line

Var Type:

[ NULL ]

Var Data:

null

Reply
June 24, 2020 3:40 AM

stained

Junior Member

Ah, this is being caused by the plugin "Forum Category Icons". The fix there worked.

Reply
June 24, 2020 7:49 AM

stained

Junior Member

Okay, back to the tables:

I'm unable to add a full grid to a table in a forum post. Any values that you change in the source editor are instantly reversed when switching back to the WYSIWYG editor so I can edit a post, add a grid using ckeditor and can see it but when I hit save, nothing. The source editor prior to me adding a full grid to a table created after the vw 4.1.0. upgrade shows:

[table] class="vw-table" width="70%" style="width: 70%"
|- class=""
| class="" | Year
| class="" | No of participants etc

after editing the table properties to add a full grid (prior to saving) I see the following:

[table] class="wysiwyg_grid" width="70%" style="width: 70%"
|- class="wysiwyg_grid_tr"
| class="wysiwyg_grid_td" | Year
| class="wysiwyg_grid_td" | No of participants etc

If I save the second code the grid is not applied. When I then take a look at the source code in the saved post the editor shows that my entries have been reverted to:

[table] class="vw-table" width="70%" style="width: 70%"
|- class=""
| class="" | Year
| class="" | No of participants

Seems that Vault and vB are fighting each other. Any ideas what I can do here?

Reply
June 24, 2020 10:55 AM

pegasus

VaultWiki Team

Stock vBulletin TABLE classes not being preserved on editor-mode switching has been fixed on your site and in the next release. For Javascript changes, you may need to clear your browser cache.

Reply
June 24, 2020 11:35 AM

stained

Junior Member

Thank you. We're getting there If I save a table with just an outer border it works perfectly but if I select a full grid it doesn't display after saving the post.

Reply
June 25, 2020 5:48 AM

stained

Junior Member

In addition to the table problem above I'm seeing the following errors when I attempt to edit and then save a wiki page:

Error 1 (I added text above the menu and attempted to save).

Call to undefined method vB_WysiwygHtmlParser_vw:arse_wyswiyg_tag_attribute() on line 97 in /home/me/public_html/forum/vault/helper/vb/class/ckeditor.php
#0 /home/me/public_html/forum/includes/class_wysiwygparser.php(1623): vB_WysiwygHtmlParser_vw->parse_tag_a(' href="https://...', ' #2 /home/me/public_html/forum/vault/core/model/plugins/bbcode/wysiwyg/vb3.php(146): vB_WysiwygHtmlParser->parse_tag_by_name('a', ' #4 /home/me/public_html/forum/includes/class_wysiwygparser.php(231): eval()
#5 /home/me/public_html/forum/vault/core/model/editor/vb4.php(51): vB_WysiwygHtmlParser->parse_wysiwyg_html_to_bbcode('

or:

Error 2 (I added a single letter and attempted to save).

Call to a member function presave_called() on null on line 73 in /home/me/public_html/forum/vault/core/controller/dm/batch/vw.php
#0 /home/me/public_html/forum/vault/core/controller/dm/page/vw.php(1374): vw_DM_Batch_Controller->pre_save(NULL)
#1 /home/me/public_html/forum/vault/core/controller/dm/page/vw.php(922): vw_DM_Page_Controller->process_links()
#2 /home/me/public_html/forum/vault/core/controller/dm/page/vw.php(811): vw_DM_Page_Controller->process_revision()
#3 /home/me/public_html/forum/vault/helper/vb/class/dm.php(165): vw_DM_Page_Controller->pre_save(true)
#4 /home/me/public_html/forum/vault/core/controller/dm/vb3.php(350): vw_vB_DataManager->pre_save(true)
#5 /home/me/public_html/forum/vault/core/controller/ui/edit/page/vw.php(584): vw_DM_Controller_vB3->pre_save()
#6 /home/me/public_html/forum/vault/core/controller/ui/edit/vw.php(159): vw_UI_Edit_Page_Controller->start_dm(Object(vw_UI_Page_Controller), Array, Array)
#7 /home/me/public_html/forum/vault/core/controller/ui/page/vw.php(472): vw_UI_Edit_Controller->save(Array)
#8 /home/me/public_html/forum/vault/core/controller/ui/page/vw.php(170): vw_UI_Page_Controller->save()
#9 /home/me/public_html/forum/vault/core/controller/ui/stack/vw.php(294): vw_UI_Page_Controller->execute()
#10 /home/me/public_html/forum/vault/core/controller/ui/stack/vb3.php(180): vw_UI_Stack_Controller->execute(true)
#11 /home/me/public_html/forum/wiki_index.php(236): vw_UI_Stack_Controller_vB3->execute()
#12 /home/me/public_html/forum/showwiki.php(15): require('/home/jlmv506wm...')
#13 {main}

Fatal User Error: Call to a member function presave_called() on null on line 73 in ..../vault/core/controller/dm/batch/vw.php in ..../vb/vb.php on line 286
Trace Data:

#1 : vbstop() called in ..../includes/class_core.php on line 6089
#2 : vbulletin_error_handler() called in on line
#3 : trigger_error() called in ..../vb/vb.php on line 286
#4 : vB::handleException() called in on line

Var Type:

[ NULL ]

Var Data:

null

Also, after one attempt to save a page I see the message "Another user is performing a similar action at the moment. Please try again in a few seconds." and I can't proceed.

Reply
June 25, 2020 11:04 AM

pegasus

VaultWiki Team

Fixed the grid lines not showing in the rendered TABLE in the next release.

Fixed both fatal errors on your site.

Reply
June 25, 2020 12:25 PM

stained

Junior Member

Excellent. Thank you. So there is definitely no fix for the grid lines that can be applied now?

Reply
June 25, 2020 12:28 PM
pegasus

VaultWiki Team
For now, put the following in your vw_additional.css template:

Code:

.vw-table td.cms_table_grid_td { border: {vb:stylevar bbcode_table_border}; }

You should be able to remove it after the next release.
Reply

+ Reply

All times are GMT -4. The time now is 3:38 PM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

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

Issue Tools