• 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
    • Importer stuck at 1%: Cannot modify header information

    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: Importer stuck at 1%: Cannot modify header information

    • Issue Tools
      • View Changes
    1. issueid=3818 July 2, 2014 1:44 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Importer stuck at 1%: Cannot modify header information

      Code:
      Cannot modify header information - headers already sent by (output started at public_html/vault/core/controller/progress/vw.php:135)
      vw_CP_Progress_View->handle_php_error()
      header() in vault/core/controller/progress/vw.php at line 138
      vw_Progress_Controller->start_stream() in vault/core/controller/install/upgradepath/vw.php at line 374
      vw_Install_UpgradePath_Controller->open() in vault/core/controller/install/upgradepath/steps/4/0/0/gamma/7/C/xf.php at line 25
      {closure}() in vault/core/controller/install/upgradepath/vw.php at line 59
      vw_Install_UpgradePath_Controller->call() in vault/core/controller/cp/install/vw.php at line 299
      vw_CP_Install_Controller->exec_step() in vault/core/controller/cp/install/vw.php at line 264
      vw_CP_Install_Controller->upgrade_type() in vault/core/controller/cp/install/vw.php at line 201
      vw_CP_Install_Controller->upgrade() in vault/core/controller/cp/install/vw.php at line 71
      vw_CP_Install_Controller->execute() in library/vw/XenForo/ControllerAdmin/Wiki.php at line 107
      vw_XenForo_ControllerAdmin_Wiki->actionIndex() in library/vw/XenForo/ControllerAdmin/Wiki.php at line 136
      vw_XenForo_ControllerAdmin_Wiki->actionUpgrade() in library/XenForo/FrontController.php at line 347
      XenForo_FrontController->dispatch() in library/XenForo/FrontController.php at line 134
      XenForo_FrontController->run() in admin.php at line 13
    Issue Details
    Issue Number 3818
    Issue Type Bug
    Project VaultWiki 4.x Series
    Category Install / Upgrade
    Status Fixed
    Priority 2 - Fatal / Database Errors
    Affected Version 4.0.0 Gamma 7
    Fixed Version 4.0.0 Gamma 7
    Milestone VaultWiki 4 Gamma X
    Software DependencyXenForo 1.x
    License TypePaid
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. July 2, 2014 1:50 PM
      pegasus pegasus is offline
      VaultWiki Team
      In vault/core/controller/progress/vw.php, find:
      Code:
      header('Cache-Control: no-cache');
      Remove it.
      Then find:
      Code:
      ob_implicit_flush(true);
      Add after:
      Code:
      header('Cache-Control: no-cache');
      That should resolve this particular error here, although I don't know what output would have already been started before getting here. The output it's not showing is probably an error.
      Reply Reply  
    2. January 19, 2015 11:07 PM
      boldplan boldplan is offline
      New Member
      I have the same problem. It appears that the new version of VaultWiki has made this change but I'm still stuck at 1%. Hitting manual mode I get the following.

      set_time_limit() has been disabled for security reasons

      Enabling it in php.ini worked. I'm guessing this is a problem to many who are on shared hosting.
      Reply Reply  
    3. January 21, 2015 2:12 PM
      pegasus pegasus is offline
      VaultWiki Team
      Added the @ operator everywhere set_time_limit() is used in the next release.
      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 7:30 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
  • 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.