Issue: Bug on Import from v 3.0.19 to 4

Issue Tools
- View Changes

November 16, 2018 6:16 PM

popit

Junior Member

Bug on Import from v 3.0.19 to 4

Unfortunately dies here

Step 13

Importing wiki permissions

Importing wiki pages

Importing wiki pages
Importing wiki pages

mysqli_query(): Couldn't fetch mysqli

#0: vw_CP_Progress_View->handle_php_error()
#1: mysqli_query() in [path]/includes/class_core.php at line 1386
#2: vB_Database_MySQLi->execute_query() in [path]/includes/class_core.php at line 505
#3: vB_Database->query_first() in [path]/vault/core/controller/db/vb3.php at line 325
#4: vw_DB_Controller_vB3->query_first() in [path]/vault/core/model/db/mysql/vw.php at line 27
#5: vw_DB_MySQL_Model->select() in [path]/vault/core/controller/dm/attach/file/vw.php at line 93
#6: vw_DM_Attach_File_Controller->verify_filetypeid() in [path]/vault/core/controller/dm/attach/file/vb3.php at line 36
#7: vw_DM_Attach_File_Controller_vB3->verify_filetypeid() in [path]/includes/class_dm.php at line 491
#8: vB_DataManager->verify() in [path]/includes/class_dm.php at line 341
#9: vB_DataManager->set() in [path]/vault/core/controller/dm/vb3.php at line 259
#10: vw_DM_Controller_vB3->set() in [path]/vault/core/controller/import/handle/vw3/attach/vw.php at line 765
#11: vw_Import_Handle_VW3_Attach_Controller->create_attachment() in [path]/vault/core/controller/import/handle/vw3/attach/vw.php at line 147
#12: vw_Import_Handle_VW3_Attach_Controller->do_item_attachments() in [path]/vault/core/controller/import/handle/vw3/page/vw.php at line 970
#13: vw_Import_Handle_VW3_Page_Controller->add_page() in [path]/vault/core/controller/import/handle/vw3/page/vw.php at line 547
#14: vw_Import_Handle_VW3_Page_Controller->do_page() in [path]/vault/core/controller/import/handle/vw3/page/vw.php at line 254
#15: vw_Import_Handle_VW3_Page_Controller->do_pages() in [path]/vault/core/controller/import/steps/vw3/vw.php at line 262
#16: vw_Import_Steps_VW3_Controller->{closure}() in [path]/vault/core/controller/progress/steps/vw.php at line 83
#17: vw_Progress_Steps_Controller->call() in [path]/vault/core/controller/progress/steps/vw.php at line 53
#18: vw_Progress_Steps_Controller->execute() in [path]/vault/core/controller/progress/vw.php at line 92
#19: vw_Progress_Controller->exec_script() in [path]/vault/core/controller/progress/vw.php at line 74
#20: vw_Progress_Controller->execute() in [path]/vault/core/controller/cp/progress/vw.php at line 37
#21: vw_CP_Progress_Controller->process() in [path]/vault/core/controller/cp/impex/vw.php at line 339
#22: vw_CP_ImpEx_Controller->import() in [path]/vault/core/controller/cp/impex/vw.php at line 53
#23: vw_CP_ImpEx_Controller->execute() in [path]/vault/helper/vb/global.php at line 64
#24: require_once() in [path]/admincp/wiki_cp.php at line 24

Issue Details

Issue Number 5536

Issue Type Bug

Project VaultWiki 4.x Series

Category Unknown

Status Working as Designed

Priority 2 - Fatal / Database Errors

Affected Version 4.0.24

Fixed Version (none)

Milestone (none)

Software DependencyAny

License TypePaid

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

November 19, 2018 12:10 PM

pegasus

VaultWiki Team

This occurred because an operation took longer than the MySQL server's connection timeout, and then attempted to perform a MySQL query. Unfortunately there is no truly reliable way to determine how long an operation will take before performing it, and vBulletin doesn't automatically refresh database connections on long-lived scripts. For now, the issue can be worked around by simply retrying the operation. In extreme circumstances, we might need to isolate the specific page ID with edits to the importer files and limit what is imported about it.

This occurs because the amount of time taken to process any one wiki page is related to the length and complexity of that page's content. It is possible that any single page by itself exceeds timeouts even if you just attempt to view that page; this is one vulnerability of VaultWiki 3.x, which basically allowed users to modify pages in such a way that the page is no longer accessible or modifiable (denial of service). Once you are upgraded, VaultWiki 4.x provides a number of settings that will prevent users from being able to do this moving forward.

Reply
November 19, 2018 1:33 PM

popit

Junior Member

ok thanks for update,
I see after the ticket some pages were imported but by far many are missing....

Usually a script that does this properly like vbulletin admin cycles through pages eg page 1 import 1-10, page 2 import 11-20 etc

I can retry the operation but wondering if this will duplicate pages?

Can i retry the import now?

Also it seems there are several issues still which i will submit bug / pm you to figure out how we can work around these.
They seem to be minor issues and should have a quick fix from 3 to 4

Reply

+ Reply

All times are GMT -4. The time now is 4:12 AM.

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: Bug on Import from v 3.0.19 to 4

Issue Tools