• 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
    • CMS Broken after Upgrade

    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: CMS Broken after Upgrade

    • Issue Tools
      • View Changes
    1. issueid=2251 March 1, 2011 4:41 PM
      ashley76 ashley76 is offline
      Regular Member
      CMS Broken after Upgrade
      Can't post articles after upgrade

      This is a super high priority issue. After upgrading a few minutes ago, I can not post articles in the CMS. Here is the error message I get after clicking save...
      Code:
      An unexpected error has occured. Please try again later. If this error continues to occur, please notify the administrator.
      
      Home
    Issue Details
    Issue Number 2251
    Issue Type Bug
    Project VaultWiki 3.x Series
    Category Non-Wiki Threads / Posts
    Status Not a Bug
    Priority 1 - Security / Login / Data Loss
    Affected Version 3.0.11
    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. March 1, 2011 5:05 PM
      pegasus pegasus is offline
      VaultWiki Team
      Can you visit any other part of your site? I am not having trouble posting CMS articles here. In my experience, "unexpected error" usually means that vBulletin was unable to connect to the database.
      Reply Reply  
    2. March 1, 2011 5:12 PM
      ashley76 ashley76 is offline
      Regular Member
      Yep everything seems to be working with the exception of posting new CMS articles. The CMS works, I just can't post new articles. I can post new forum threads, and edit vaultwiki entries. It has to be the upgrade though. I posted an article a few minutes before doing the upgrade. Then after the upgrade I can't...

      Just to be sure, I tried posting an article again and I got the same error, I then disabled vault wiki and the article posted successfully
      Reply Reply  
    3. March 1, 2011 5:35 PM
      pegasus pegasus is offline
      VaultWiki Team
      Anything special in the article? Attachments? WYSIWYG? What article settings did you use?
      Reply Reply  
    4. March 1, 2011 5:39 PM
      ashley76 ashley76 is offline
      Regular Member
      The article did have attachments, but then I just created an article with default settings that was titled test with the word test in the article and still the same error...
      Reply Reply  
    5. March 1, 2011 6:04 PM
      pegasus pegasus is offline
      VaultWiki Team
      Oh, this is an error 500. Okay, please refer to the other thread you started on vBSEO, and read what happened to tagman. This is a bug in vBSEO and has been reported to them.
      Reply Reply  
    6. March 1, 2011 7:02 PM
      ashley76 ashley76 is offline
      Regular Member
      yep, that fixed it, curious though that it only started after the upgrade.
      Reply Reply  
    7. March 1, 2011 10:16 PM
      tagman tagman is offline
      Junior Member
      I just had the same thing happen. Same error message as Ashley too, not the 500 error like yesterday. I tried to edit a CMS article and got the error so I disabled vbseo to see if that was the culprit. I still couldn't edit with vbseo disabled so I re-enabled it. I then disabled VW and I could post. I tried re-enabling VW and I could post. I think the new update is causing the database to hang somehow in regards to CMS. At any rate, disabling and re-enabling VW seemed to fix it. Or perhaps disabling and re-enabling vbseo fixed it since I didn't try creating an article directly after re-enabling vbseo. Hmmmm.....
      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 6:48 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.