• 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 3.x Series
    • Bug
    • Forum.php stopped working

    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: Forum.php stopped working

    • Issue Tools
      • View Changes
    1. issueid=2855 August 30, 2012 11:01 PM
      JesterP JesterP is offline
      Junior Member
      Forum.php stopped working

      Hi there,

      I added several forums and namespaces tonight. After I finished, I clicked on "forum" in my navbar which executes forum.php. We are greeted with an error which is result code 400 in my access logs.

      The forums start working again after I disable vaultwiki in my product manager. Once I re-enable vaultwiki, I get the same error.

      The steps I took to create the namespaces:

      Created the forums. Set their permissions. Added them in the namespace manager. I rebuilt the namespaces.

      Vaultiwiki is now disabled and I'm at a loss. :/
    Issue Details
    Issue Number 2855
    Issue Type Bug
    Project VaultWiki 3.x Series
    Category Forum Display
    Status Not a Bug
    Priority 2 - Fatal / Database Errors
    Affected Version 3.0.19
    Fixed Version (none)
    Milestone (none)
    Software DependencyAny
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. August 30, 2012 11:30 PM
      JesterP JesterP is offline
      Junior Member
      Update: I removed all new namespaces, re-enabled the wiki, got the same error. Disabling Vaultwiki under VaultWiki: Server Settings allows the forums to work. :/
      Reply Reply  
    2. August 31, 2012 12:13 PM
      pegasus pegasus is offline
      VaultWiki Team
      If you recently upgraded PHP on your server, was PHP compiled with the mbstring extension? If not, check VaultWiki: Server Settings, and make sure UTF-8 support is turned off.
      Reply Reply  
    3. August 31, 2012 12:24 PM
      JesterP JesterP is offline
      Junior Member
      Quote Originally Posted by pegasus
      If you recently upgraded PHP on your server, was PHP compiled with the mbstring extension? If not, check VaultWiki: Server Settings, and make sure UTF-8 support is turned off.

      Code:
       '--enable-mbstring'
      Just for good measure, I disabled utf-8 support for urls in vw: server settings, still got the error.
      Reply Reply  
    4. August 31, 2012 6:14 PM
      JesterP JesterP is offline
      Junior Member
      Any other possibilities?
      Reply Reply  
    5. August 31, 2012 10:34 PM
      pegasus pegasus is offline
      VaultWiki Team
      Have you run the VaultWiki upgrade script since updating to vB 4.2? If you haven't, you need to run the script. It will rebuild some things that the vB upgrade might have broken.

      Do PHP errors normally display out to your browser? If not, try turning on display_errors in your php.ini file, or add the following code after the copyright block in forum.php:
      Code:
      @ini_set('display_errors', 1);
      HTTP 400 Bad Request implies that either:
      1. the browser requested a URL from your server that the server doesn't know how to handle, or
      2. the server isn't sending a valid HTTP 200 response and other types of error reporting are currently turned off or unavailable for the content being requested.
      Reply Reply  
    6. August 31, 2012 10:39 PM
      JesterP JesterP is offline
      Junior Member
      I haven't upgraded VB, I merely added namespaces.

      I'll add that and report back.
      Reply Reply  
    7. August 31, 2012 10:48 PM
      JesterP JesterP is offline
      Junior Member
      Quote Originally Posted by JesterP
      I haven't upgraded VB, I merely added namespaces.

      I'll add that and report back.
      Code:
      Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 125829120 bytes) in /var/www/htdocs/pirate/forums/includes/class_core.php(4623) : eval()'d code on line 49594
      Ah hah! I can adjust this. Thank you for the help troubleshooting!!

      Bumped from 128 to 196 memory allowed in php.ini, forums now work.

      Thank you
      Reply Reply  
    8. August 31, 2012 10:52 PM
      pegasus pegasus is offline
      VaultWiki Team
      That's a really long plugin (50k lines), or you have a lot of products installed. You may want to review.
      Reply Reply  
    9. August 31, 2012 10:55 PM
      JesterP JesterP is offline
      Junior Member
      I guess I'm not following. I only added namespaces, no plugins or new products.
      Reply Reply  
    10. August 31, 2012 11:15 PM
      pegasus pegasus is offline
      VaultWiki Team
      If you added new namespaces, it would increase the memory requirement somewhat, but not by much. Unless you added hundreds of new namespaces, or if you already have hundreds of sub-forums, you were probably already close to your memory limit before adding the extra namespaces.

      According to the error message you posted, just one of your plugins (products have lots of plugins put together) has just under 50,000 lines of code. That is a red flag. I would try to track down the plugin that is that long and improve it or remove it. By comparison, most VaultWiki plugins are between 4 and 10 lines long.

      EDIT: Some more info...

      If your vB version is 4.2.0, class_core.php ~ line 4623 is the hook template_render_output, so if you have any products using that hook, you might want to start looking there. If your vB version is < 4.2.0, it's possible the line is the actual rendering of the template output, in which case, you would be looking for very long templates that are likely to be used on forum.php.

      Either way, if you added multiple namespaces and they all have hundreds of thousands of articles in them, that might have an effect on performance if all the namespaces appear together in the forum list on forum.php. In this case, you might want to hide the wiki namespaces from the forum bits and just rely on the Wiki tab, or you may want to show only one forum that has a Forum Link to the Wiki tab.
      Reply Reply  
    11. September 1, 2012 12:14 PM
      JesterP JesterP is offline
      Junior Member
      Quote Originally Posted by pegasus
      If you added new namespaces, it would increase the memory requirement somewhat, but not by much. Unless you added hundreds of new namespaces, or if you already have hundreds of sub-forums, you were probably already close to your memory limit before adding the extra namespaces.

      According to the error message you posted, just one of your plugins (products have lots of plugins put together) has just under 50,000 lines of code. That is a red flag. I would try to track down the plugin that is that long and improve it or remove it. By comparison, most VaultWiki plugins are between 4 and 10 lines long.

      EDIT: Some more info...

      If your vB version is 4.2.0, class_core.php ~ line 4623 is the hook template_render_output, so if you have any products using that hook, you might want to start looking there. If your vB version is < 4.2.0, it's possible the line is the actual rendering of the template output, in which case, you would be looking for very long templates that are likely to be used on forum.php.

      Either way, if you added multiple namespaces and they all have hundreds of thousands of articles in them, that might have an effect on performance if all the namespaces appear together in the forum list on forum.php. In this case, you might want to hide the wiki namespaces from the forum bits and just rely on the Wiki tab, or you may want to show only one forum that has a Forum Link to the Wiki tab.
      I haven't upgraded to 4.2 yet, I am still at 4.1.11. We don't have much in the wiki, so we don't have the hundreds of thousands of pages yet.

      It could be as simple as how I have the wiki forums/namespaces configured. Please see the attached screenshot. I would like to hide them all, regular members should really have no need to see the forums, only staff (and that's a maybe). How would you recommend I hide them from view?

      Reply Reply  
    12. September 1, 2012 2:29 PM
      pegasus pegasus is offline
      VaultWiki Team
      In your Forum Manager, set the "Wiki Forums" item to Display Order = 0. This will hide them all from your forum home.
      Reply Reply  
    13. September 1, 2012 2:55 PM
      JesterP JesterP is offline
      Junior Member
      Thank you
      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:11 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 © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.