StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUsing FirePHP with Zend Framework 2
primarykey
Id
13727592
data
AcceptedAnswerId
13733240
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-05T16:16:28.930
FavoriteCount
3
LastActivityDate
2012-12-18T14:35:39.303
LastEditDate
2012-12-06T14:18:06.890
LastEditorUserId
1012803
OwnerUserId
1012803
ParentId
0
PostTypeId
1
Score
0
ViewCount
2718
LastEditorDisplayName
text
Body
I'm trying to use FirePHP with Zend Framework 2, but there seems to be something missing. Here's the basic code I'm trying to run: <pre><code>$writer = new Zend\Log\Writer\FirePhp(); $logger = new Zend\Log\Logger(); $logger->addWriter($writer); $logger->info('FirePHP logging enabled'); </code></pre> The error I get is "FirePHP Class not found". I was initially puzzled because I do have a FirePhp class in my Zend/Log/Writer folder. But then I saw that the class constructor requires a FirePhp\FirePhpInterface object. So I checked the Zend/Log/Writer/FirePhp folder and there's a FirePhpBridge class in there that implements FirePhpInterface, but it also requires a FirePHP instance in the constructor. I don't have any FirePHP.php file in my Zend/Log/Writer/FirePhp folder. Am I supposed to get this from somewhere else? Update I now have managed to get FirePHP working, but I'm trying to figure out how to do it in a clean way so this works. The only way I've gotten it to work is putting it in the root directory of my project and doing the following: <pre><code>include_once('FirePHP.php'); $writer = new Zend\Log\Writer\FirePhp(new Zend\Log\Writer\FirePhp\FirePhpBridge(FirePHP::getInstance(true))); $logger = new Zend\Log\Logger(); $logger->addWriter($writer); $logger->info('FirePHP logging enabled'); </code></pre> I assume that normally I should be able to create a writer like so: <pre><code>$writer = new Zend\Log\Writer\FirePhp(); </code></pre> However, where this goes wrong I believe is in the getFirePhp() function of the Zend\Log\Writer\FirePhp class. The class does this: <pre><code>if (!$this->firephp instanceof FirePhp\FirePhpInterface && !class_exists('FirePHP') ) { // No FirePHP instance, and no way to create one throw new Exception\RuntimeException('FirePHP Class not found'); } // Remember: class names in strings are absolute; thus the class_exists // here references the canonical name for the FirePHP class if (!$this->firephp instanceof FirePhp\FirePhpInterface && class_exists('FirePHP') ) { // FirePHPService is an alias for FirePHP; otherwise the class // names would clash in this file on this line. $this->setFirePhp(new FirePhp\FirePhpBridge(new FirePHPService())); } </code></pre> This is where I get lost as to how I'm supposed to set things up so that this class_exists('FirePHP') call finds the right class and new FirePHPService() also works properly.
Tags
<php><zend-framework2><firephp>
Title
Using FirePHP with Zend Framework 2
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USRocket04
UserOwnerUserId
1. USRocket04
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.