Dissecting server error log - ckeditor vblink errors

[ForceHSS]

Originally Posted by DF031

in a different directory it does excist:

/clientscript/ckeplugins/vblink

This is were it should be in vb4 so dont no why it is trying to look for it else where. You could either fix that pointing it to the right place or copy the files over to where it is looking for them even know it is the wrong place

[DF031]

Thanks for all the help guys.

You could either fix that pointing it to the right place

How do I know which file is looking for it in the wrong place ?

[ForceHSS]

It tells u that in the first post

[DF031]

Thanks, but it does not. At least I could not find it :-( The file editpost.php has no reference to ckeditor or vblink or ckplugins

Might be an included file.

[ozzy47]

Lets test if this is from a addon.

Open your config.php and below<?php add this line:

PHP Code:

 define('DISABLE_HOOKS', true); 


So it looks like this:

PHP Code:

<?php
define('DISABLE_HOOKS', true);
/*=================================================  =====================*\
|| ##################################################  ################## ||
|| # vBulletin 4.2.1

Then go to a post, and edit it, then look in your server error logs again, to see if the error shows up.

If it don't, then remove that line from the config.php file, edit the post again and see if the error shows up then.

[DF031]

Thanks Ozzy.

Since I can not produce the error at will, it happens max. a dozen times a day, I might have to wait a few hrs for the error to pop up. I can not cripple the forum for such a long time.

But I did overwrite all files in the ckeditor and ckplugins directory with brand new ones from the VB members area.

[ozzy47]

Well one of them editpost.php that is calling for the file, that's why I wanted you to test with plugins disabled, and edit a post, then with plugins enabled.

[DF031]

Editing a post does not trigger it when I try. I have not found a way yet to reproduce the error at will.

[ozzy47]

Well that is a bummer, hopefully you can find a way to reproduce it at will, so we can get this figured out.

[nhawk]

I reported this as a bug way back in December 2011...

http://tracker.vbulletin.com/browse/VBIV-13840