Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.14.4

Bug #1121 receive Call to a member function on a non-object on test files
Submitted: 2004-04-03 12:56 UTC
From: bryanhahn at yahoo dot com Assigned:
Status: No Feedback Package: Log
PHP Version: 4.3.1 OS: Linux
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 35 + 28 = ?

 
 [2004-04-03 12:56 UTC] bryanhahn at yahoo dot com
Description: ------------ I installed version 1.8.4 of the logging package and attempted to run some basic tests from the docs/examples directory. When I run the examples, I get the following error: Fatal error: Call to a member function on a non-object in /home2/www/eorderme/commercecollab/includes/Log-1.8.4/docs/examples/file.php on line 8 The sample uses the singleton method, so I tried the factory method and receive the same error. php -version PHP 4.3.1 (cli) (built: Apr 22 2003 18:36:14) Copyright (c) 1997-2002 The PHP Group Zend Engine v1.3.0, Copyright (c) 1998-2002 Zend Technologies Is there some other requirements to running this package other than having PHP v 4.3.0 or greater? Reproduce code: --------------- <?php require_once 'Log.php'; $conf = array('mode' => 0600, 'timeFormat' => '%X %x'); $logger = &Log::factory('file', 'out.log', 'ident', $conf); for ($i = 0; $i < 10; $i++) { $logger->log("Log entry $i"); } Expected result: ---------------- Fatal error: Call to a member function on a non-object in /home2/www/eorderme/commercecollab/includes/Log-1.8.4/docs/examples/file.php on line 8

Comments

 [2004-04-04 04:16 UTC] jon
That example runs fine for me. Have you actually installed the Log package before running the example?
 [2004-05-10 03:04 UTC] jon
No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you.