Issue: Can't view article source in editor with VaultWiki using Chrome

See: https://www.vaultwiki.org/issues/2550/#note13285

Apply the same fix to vault/clientscript/tabs.js

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.

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.

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.

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.

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.

Problem fixed. Thanks for your help!