[Forum] can't edit posts

[hilary]

Hi,
I've upgraded from 4.1.3 to 4.1.7 and posts can't be edited in thread view.
This doesn't work in our custom style and also doesn't work in the default style.

In FF when I load the thread I get the javascript error.
Error: this.config.vbulletin is undefined
Source File: http://www.xxxx.com/forums/clientscr...tedit.js?v=417
Line: 11
Line 11 is a minified line of javascript.

Then if I press 'edit post' I get another javascript error.
Error: CKEDITOR is not defined
Source File: http://www.bubhub.com.au/community/f..._edit.js?v=417
Line: 11
Line 11 is a minified line of javascript.

Then if I press 'edit post' on any other post, the page editpost.php?p=6120671&do=editpost loads.
This page allows me to save the edit.

How can I fix it so that I can edit in the thread (inline)?

I have reuploaded the non image files twice now.

[hilary]

It has something to do with the plugin
'Move smilies below textarea'

http://www.vbulletin.org/forum/misc.php?do=producthelp&pid=lynne_smilies_below

[hilary]

To get this to work with 4.1.4 (or above) Quick Reply:
Edit the plugin "Add smilies to Quick Reply also" and remove, or comment out, the line:
PHP Code:

$editor_template_name = 'showthread_quickreply';

[anzs]

I can explain this; just upgraded my forum to 4.2.0 and meet this problem.
The issue does not related somehow to plugins and other stuff.

JS error is caused by BOM (Byte Order Mark) in CKEditor JS scripts. For some stupid reason it was not removed by VBulletin team.
As a result of this problem, both FireFox and Opera does not display toolbar buttons in the text editor, in forum and CMS.

How to fix that:
1. Download and run File BOM Detector
2. Point it to the temporary VBulletin directory where you have a copy of your forum, to the clientscript\ckeditor\ folder.
3. Click 'Start' button; it will list files with BOM
4. Select files with BOM in the list, right-click and select 'Remove BOM' in the context menu
5. Upload the ckeditor folder to your live forum.


To VBulletin Team: I suggest you guys follow this instruction before releasing a new version.
BTW, thank you for adding the new editor. And if you don't mind, I have one more suggestion; it would be great if you will perform much more testing before allowing new version to be released to production

[Ace]

If this was actually the case, not one single 4.2 installation would be working.

[anzs]

If this was actually the case, not one single 4.2 installation would be working.

I think this depends on environment in which the forum is running, including localization settings of hosting and probably the database. If output encoding is UTF-8, everything should work fine. My forum output is "Content-Type: text/html; charset=windows-1251" which is not default as far as I concerned, and not UTF-8. I believe other people having non-default / non UTF-8 encoding will experience the same problem.