• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Bug
    • [4.1 Alpha 1] Area manager:SQL syntax error after attempting to save an existing area with changed parent

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

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: [4.1 Alpha 1] Area manager:SQL syntax error after attempting to save an existing area with changed parent

    • Issue Tools
      • View Changes
    1. issueid=5598 January 16, 2019 1:31 PM
      ACL ACL is offline
      Regular Member
      [4.1 Alpha 1] Area manager:SQL syntax error after attempting to save an existing area with changed parent
      I get this error when trying to save changes to an Area in Area manager, when the Parent Area has been changed. If Parent Area is not changed then I can save the other changes (such as Area title) just fine.

      When an area's parent is changed to a different area:
      XF\Db\InvalidQueryException: MySQL statement prepare error [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 '4,3,1547618914,'{"itemid":4,"itemtypeid":3,"areaid":4,"p refixid":0,"tit'

      Code:
      XF\Db\AbstractStatement->getException() in src/XF/Db/Mysqli/Statement.php at line 196
XF\Db\Mysqli\Statement->getException() in src/XF/Db/Mysqli/Statement.php at line 39
XF\Db\Mysqli\Statement->prepare() in src/XF/Db/Mysqli/Statement.php at line 54
XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 79
XF\Db\AbstractAdapter->query() in src/addons/vw/vw/_core/controller/db/xf2.php at line 117
vw_DB_Controller_XF2->query_write() in src/addons/vw/vw/_core/model/db/mysql/vw.php at line 1323
vw_DB_MySQL_Model->shutdown_or_run() in src/addons/vw/vw/_core/model/db/mysql/vw.php at line 1068
vw_DB_MySQL_Model->insert() in src/addons/vw/vw/_core/controller/dm/base/vw.php at line 1564
vw_DM_Base_Controller->move_lastupdate() in src/addons/vw/vw/_core/controller/dm/area/vw.php at line 449
vw_DM_Area_Controller->post_save_once() in src/addons/vw/vw/_core/controller/dm/area/xf2.php at line 94
vw_DM_Area_Controller_XF2->vwPostSaveOnce() in src/addons/vw/vw/XF/Entity/Entity.php at line 502
vw\vw\XF\Entity\Entity->vwSave() in src/addons/vw/vw/_core/controller/dm/xf2.php at line 363
vw_DM_Controller_XF2->save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 553
vw_CP_Area_Controller->do_save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 196
vw_CP_Area_Controller->process_save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 166
vw_CP_Area_Controller->save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 64
vw_CP_Area_Controller->execute() in src/addons/vw/vw/Admin/Controller/Wiki.php at line 90
vw\vw\Admin\Controller\Wiki->_actionIndex() in src/addons/vw/vw/Mvc/Dispatcher.php at line 30
vw\vw\Mvc\Dispatcher::dispatch() in src/addons/vw/vw/Admin/Controller/Wiki.php at line 51
vw\vw\Admin\Controller\Wiki->actionIndex() in src/XF/Mvc/Dispatcher.php at line 249
XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 88
XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 41
XF\Mvc\Dispatcher->run() in src/XF/App.php at line 1934
XF\App->run() in src/XF.php at line 333
XF::runApp() in admin.php at line 13
      When an area's parent is changed to None:
      XF\Db\InvalidQueryException: MySQL statement prepare error [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 '8) LIMIT 2' at line 1 in src/XF/Db/AbstractStatement.php at line 212
      Code:
      XF\Db\AbstractStatement->getException() in src/XF/Db/Mysqli/Statement.php at line 196
XF\Db\Mysqli\Statement->getException() in src/XF/Db/Mysqli/Statement.php at line 39
XF\Db\Mysqli\Statement->prepare() in src/XF/Db/Mysqli/Statement.php at line 54
XF\Db\Mysqli\Statement->execute() in src/XF/Db/AbstractAdapter.php at line 79
XF\Db\AbstractAdapter->query() in src/addons/vw/vw/_core/controller/db/xf2.php at line 117
vw_DB_Controller_XF2->query_write() in src/addons/vw/vw/_core/model/db/mysql/vw.php at line 1323
vw_DB_MySQL_Model->shutdown_or_run() in src/addons/vw/vw/_core/model/db/mysql/vw.php at line 366
vw_DB_MySQL_Model->delete() in src/addons/vw/vw/_core/controller/dm/base/vw.php at line 1611
vw_DM_Base_Controller->move_lastupdate() in src/addons/vw/vw/_core/controller/dm/area/vw.php at line 449
vw_DM_Area_Controller->post_save_once() in src/addons/vw/vw/_core/controller/dm/area/xf2.php at line 94
vw_DM_Area_Controller_XF2->vwPostSaveOnce() in src/addons/vw/vw/XF/Entity/Entity.php at line 502
vw\vw\XF\Entity\Entity->vwSave() in src/addons/vw/vw/_core/controller/dm/xf2.php at line 363
vw_DM_Controller_XF2->save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 553
vw_CP_Area_Controller->do_save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 196
vw_CP_Area_Controller->process_save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 166
vw_CP_Area_Controller->save() in src/addons/vw/vw/_core/controller/cp/area/vw.php at line 64
vw_CP_Area_Controller->execute() in src/addons/vw/vw/Admin/Controller/Wiki.php at line 90
vw\vw\Admin\Controller\Wiki->_actionIndex() in src/addons/vw/vw/Mvc/Dispatcher.php at line 30
vw\vw\Mvc\Dispatcher::dispatch() in src/addons/vw/vw/Admin/Controller/Wiki.php at line 51
vw\vw\Admin\Controller\Wiki->actionIndex() in src/XF/Mvc/Dispatcher.php at line 249
XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 88
XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 41
XF\Mvc\Dispatcher->run() in src/XF/App.php at line 1934
XF\App->run() in src/XF.php at line 333
XF::runApp() in admin.php at line 13
    Issue Details
    Issue Number 5598
    Issue Type Bug
    Project VaultWiki 4.x Series
    Category Admin Panel
    Status Fixed
    Priority 2 - Fatal / Database Errors
    Affected Version 4.1.0 Alpha 1 Public
    Fixed Version 4.1.0 Alpha 1 Public
    Milestone (none)
    Software DependencyXenForo 2.x
    License TypePaid
    Users able to reproduce bug 1
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. January 16, 2019 2:59 PM
      pegasus pegasus is offline
      VaultWiki Team
      Was this for the same area both times? In the database, does vw_area.area_parentlist contain an extraneous comma for this area?
      Reply Reply  
    2. January 16, 2019 3:10 PM
      ACL ACL is offline
      Regular Member
      This happens with more than one area. I just retested with two areas, each time trying to move to a different parent area or no parent area, both times resulting in errors as the first post above.

      column vw.area.area_parentlist is empty for all 5 area rows on my test wiki site.
      Reply Reply  
    3. January 16, 2019 3:23 PM
      pegasus pegasus is offline
      VaultWiki Team
      Empty is actually bad. It should at least list its own pageid in the parentlist. So I will see if I can reproduce the parentlist not being written properly.
      Reply Reply  
    4. January 16, 2019 3:28 PM
      ACL ACL is offline
      Regular Member
      area_childlist is also empty for all 5 areas. Is this also bad?

      The current hierarchy of my local test site has 3 areas at the parent level (including System and Wiki Pages), and two as child areas.
      Reply Reply  
    5. January 16, 2019 5:23 PM
      pegasus pegasus is offline
      VaultWiki Team
      Yes, both columns should contain a comma-separated listed of the area-tree relative to the current area, including the current area. I was able to reproduce the problem easily when creating a brand new area, and I have worked out a solution. It affects a significant number of files so I will not be posting the change, but it will be in the next build.

      Also, areas that were created already will need to be repaired by an upgrade step to Alpha 2, so you may continue to have issues using areas that were created while the bug existed.
      Reply Reply  
    6. January 17, 2019 2:58 PM
      pegasus pegasus is offline
      VaultWiki Team
      Upgrade script created; closing this issue.
      Reply Reply  
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 11:32 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
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2025 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2025 DragonByte Technologies Ltd.
    Copyright © 2008 - 2024 VaultWiki Team, Cracked Egg Studios, LLC.