COutputProcessor - Yii is looking for clas that is NOT being used?
Posted 19 March 2011 - 04:51 AM
I wanted to use qtip2 extension and run into problem I see for the very first time in my whole Yii and PHP history. I'm asking here because both me and extension's author have no idea, what is going on? Maybe some forum user had similar experience and can help up?
Either I'm missing something or doing something really wrong or Yii (PHP) is looking for class that is not being used anywhere in the code.
Just as I wrote on qtip2's page - after installing extension, any attempt to run it ends with PHP error saying "Fatal error: Class 'COutputProcessor' not found in [path]\protected\extensions\qtip\QTip.php on line 57". The problem is that COutputProcessor class is NOT being used / called / extended in neither extension code nor my application code - as this is first time I heard about this class.
Line 57 is extension's __construct() method. But qtip2 as nearly any other extension is descending from CComponent not COutputProcessor.
I would like to use this extension, but current situation renders it completely useless for me. Can anyone got any idea, what is going on here?
Posted 06 April 2011 - 05:40 PM
I ran into this error when using an extension where I was causing an exception to be thrown. At that point the app as attempting to output things when I had not expected it too. I think Yii was capturing the exception and calling classes it couldn't find because I had disabled autoloading for the extension I was using.
May be unrelated, but an idea, I figured, would be better than no response.
Posted 07 April 2011 - 01:51 AM
See if you use some of it's subclasses like CHtmlPurifier, CContentDecorator, CMarkdown or CTextHighlighter
Posted 08 April 2011 - 03:17 PM
@mdomba: Nope, non of classes mentioned by you is being used inside code of qtip extension and since it is descenting from a very low-level component (CComponent) I don't thing problem lies somewhere around. Beside - if you only have a bit of spare time - you can examine this extensions' source code:
It is DEADLY simple - it has only 70 lines of code (including commens) so it can't be made simplier and that is why I was so surprised to see this error message.
Posted 08 April 2011 - 03:32 PM
At least you can try a simple test case... a new webapp... one model / crud... and see if then this extension works...
Posted 26 April 2011 - 01:27 AM
You might be right and as usual, the simplest solutions are beyond my looking.
The only thing, why this time I haven't started from testing my own code was, that the class is being reported by error message was unknown to me until first display of the error text. I've never heard about it before and that is why I assumed that it must me somewhere connected to the extension, not my code. This assumption seems to be wrong right know, but even if connection between error message and my own code exists, it must be somewhere deep.
Anyway, thanks for pointing this out. I'll try to do some extensive check out of my own code to see if the problem actually doesn't lies somewhere there.
Posted 21 January 2013 - 05:19 PM
1. index.php DEBUG flag, set to TRUE.
2. now the error is different:
Declaration of Docs::onBeforeValidate() should be compatible with CModel::onBeforeValidate($event)
now, for what reason the original error was referencing to "COutputProcessor" and now is referencing another distinct issue ?
i am trying to see what is happening..
Posted 15 January 2014 - 09:15 AM
This reason is valid.
I experienced the same problem when the parent class got some functions which were found in it's child class and then the child class began to complain.
Be Good To You