• 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
    • Can't view article source in editor with VaultWiki using Chrome

    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: Can't view article source in editor with VaultWiki using Chrome

    • Issue Tools
      • View Changes
    1. issueid=2570 January 5, 2012 8:41 AM
      MrAJP MrAJP is offline
      New Member
      Can't view article source in editor with VaultWiki using Chrome

      I just upgraded our forum from 3.0.14 to 3.0.16, and updated to the latest version of VBulletin (4.1.9). Now, when I try to view the article source, instead of the WYSIWYG view using Chrome, it only shows a dark gray region, and the button to switch back to WYSIWYG is grayed out. This issue does not happen on the forum or CMS side.
    Issue Details
    Issue Number 2570
    Issue Type Bug
    Project VaultWiki 3.x Series
    Category Editing / Posting Articles
    Status Fixed
    Priority 3 - Loss of Functionality
    Affected Version 3.0.16
    Fixed Version (none)
    Milestone (none)
    Software DependencyAny
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 1
    Assigned Users (none)
    Tags editor




    1. January 11, 2012 10:14 PM
      pegasus pegasus is offline
      VaultWiki Team
      See: https://www.vaultwiki.org/issues/2550/#note13285

      Apply the same fix to vault/clientscript/tabs.js
      Reply Reply  
    2. This petition for a change to Unconfirmed was rejected
      January 12, 2012 7:54 AM
      MrAJP MrAJP is offline
      New Member
      Thanks for the update. I've applied the fix and getting the same result. In the process of verifying that Chrome loaded the correct and not cached instance of "tabs.js" from our site, I noticed that Chrome indicates the following error in the inspection pane:

      "ckeditor.js:134 Uncaught TypeError: Cannot call method 'setState' of undefined"

      I've checked to see if this same error occurs when performing the same operation on the CMS or Forum side, and it does not. So I would imagine that this error is related.

      I hope that helps you out. If there is any more information that you need, please let me know. Thanks.
       
    3. January 12, 2012 3:00 PM
      pegasus pegasus is offline
      VaultWiki Team
      The fix provided has been confirmed to correct the very 'setState' issue you mentioned on a number of sites. The problem was that it cycled through an Array and applied setState to each element, and for IE < 9 and Chrome, the method indexOf was assumed to be an element when it is not. Make sure that:
      • All copies of tabs.js on your server were updated correctly.
      • If you have a browser cache, it is cleared.
      • If you have a server cache for static files, it is cleared.
      • If you are using a Content Delivery Network for static files, it is cleared or updated.
      Reply Reply  
    4. January 25, 2012 7:44 AM
      MrAJP MrAJP is offline
      New Member
      Thanks pegasus for the reply however, my issue still remains.

      1. I only have one copy of tabs.js on my server (I've searched the whole machine).
      2. Cache is cleared. I experience the same issue on a brand new laptop (the reason behind the delayed response), now using Win 7 64bit instead of XP 32bit.
      3. We don't have a server cache.
      4. We don't have a Content Delivery Network.
      5. I've restarted Apache, error still persists
      6. Chrome inspector shows the modified version of tabs.js. If somehow the old version was being cached beyond my knowledge, I believe the inspector would show the old version.

      Please let me know if I can give you any more info.

      Edit: I've attached a screenshot of the error message to this post. I hope it can help you.
      Reply Reply  
    5. January 25, 2012 2:23 PM
      pegasus pegasus is offline
      VaultWiki Team
      I can't reproduce the issue here since the fix, so I will need access to your board to continue investigating it. Please send me a PM letting me know how I can see the error for myself.
      Reply Reply  
    6. January 25, 2012 3:01 PM
      pegasus pegasus is offline
      VaultWiki Team
      Okay, I see the issue now. This only occurs when editing articles that are also Books. The same code that was removed from tabs.js and autolink.js is also present in clientscript/vault/markread.js.

      Removing the Array.indexOf block from this file should fix the issue for Book editing.
      Reply Reply  
    7. January 25, 2012 3:47 PM
      MrAJP MrAJP is offline
      New Member
      Problem fixed. Thanks for your help!
      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 12:58 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 © 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.