Well I haven't got far with this, but I found a reference to a similar issue

Installing the debug error-logging tool will create debug logs of PHP problems for you to review.

Be sure to remove the utility when not needed, or it will slow down your site and consume large amounts of disk space.

on http://www.zen-cart.com/forum/showthread.php?t=84613

So is b2evol initiating this error log. It doesn't have with my other opensource php application, like phpBB.

????

amoun

Ok this is effectively a bump.

The questions are

1. How do I stop error logging?
2. What are these errors? (see [blockquote] in first post)
3. Are they really errors?
3. If they are. How can I stop them?

I have emailed my remote server manager to see if it is happening there, but no reply yet.

Ok Here's an update.

I have just removed the path for the php_error.log php.in

I commented out

error_log = F:\apache2triad\php\logs\php_error.log

The problem is that whereas it takes 7 seconds for b2evolution to come up when their is an error log path, without it, it takes 25 seconds and then I get a blank page.

and its the same if I comment out

error_reporting = E_ALL & ~E_NOTICE

Ant ideas folks.

Clearly b2evolution needs to be able to report php errors and be able to write them as removing either option stops it.

So why does it need to?
and
Why the errors?

/**
 * Log application errors through {@link error_log() PHP's logging facilities}?
 *
 * This means that they will get logged according to PHP's error_log configuration directive.
 *
 * Experimental! This may be changed to use regular files instead/optionally.
 *
 * @todo Provide logging into normal file instead (more useful for backtraces/multiline error messages)
 *
 * @global integer 0: off; 1: log errors; 2: include function backtraces (Default: 1)
 */
$log_app_errors = 1;

/conf/_advanced.php line 49

Thanks Afwas

I thought you'd cracked it for me, but alas it doesn't stop the error logging, and even if it did, it would still mean the errors are being made.

I keep imagining there must be a simple error in the php, which doesn't seem fatal. However on breakdown of a 3.3Mb file 3M is for warnings and 300k for fatal errors????

I'm still inclined to think some of the code isn't right for php 4.3.8

On the warnings side I have read that an uninitiated variable will cause a warning.

OK

What I have found is that if I comment out [error_reporting( E_ALL )]

// Most of the time you'll want to see all errors, including notices:
// b2evo should run notice free! (plugins too!)
// error_reporting( E_ALL );

Its better.

1. no log is created as no errors are reported
2. the application start in only 2 seconds on a clean install instead of 7 seconds and only 2 seconds on one with default blogs etc instead of 25 seconds.

However the two issues remaining are

1. why didn't [$log_app_errors = 0;] work and
2. it hasn't removed the fact that there are thousands of php errors for every page.

Thanks again Afwas for your directions at least I can play on my local machine, but I am still very concerned about this error issue.

Is there anyone else out there that runs a local install and if so
1. what php are they using etc and
2. Do they a similar problem and/or
3. Have they hacked theconfig/ _advanced.php file

If it's your local machine you can easily upgrade to a decent php version.
Things go wrong somewhere else, but I didn't find it. It tries to use xdebug. Possibly it does find xdebug on your system, but that isn't configured properly (can't write to disc).

Run WAMP or Xampp

Thanks again Afwas.

I'll look into WAMP and XAMPP: I see they are apache bundles similar to my apache2triad.

However I'm on dial-up so will have to wait to visit a friend with broadband to download.

Will look into the other issue meanwhile.

Possibly it does find xdebug on your system, but that isn't configured properly (can't write to disc).

amoun

Your error log errors really don't make sense, line 26 of /conf/_locales.php is simply setting a variable to 2, most of the rest of the errors are due to NT_()

I'd be tempted to grab a fresh copy of the files in case you have a corrupted download.

Also, check your error log settings in your php.ini as I'm pretty sure that this isn't an evo problem ( I've certainly never had this problem whilst running localhost )

¥

Hi ¥åßßå ¥åßßå wrote:

Your error log errors really don't make sense, line 26 of /conf/_locales.php is simply setting a variable to 2, most of the rest of the errors are due to NT_()

I'd be tempted to grab a fresh copy of the files in case you have a corrupted download.

Also, check your error log settings in your php.ini as I'm pretty sure that this isn't an evo problem ( I've certainly never had this problem whilst running localhost )

¥

Yeap! it doesn't. Afwas said it could be the "xdebug on your system, but that isn't configured properly"

Well I've installed a new Apache2triad version with php 4.4.2 instead of 4.3.8 and all seems fine.

I've undone the edits in config/_advanced.php and no php_error.log is created and the application loads and runs faster.

So whether it was the xdebug or the php version, I will never find out.

Thanks Afwas

Great job, well done :p

Bugger *reverts name back to bimbo* :(

¥

Hey ¥åßßå What's up don't cry.

It wasn't evo in some sense, except that it did insist on getting rid of its error messages no matter what I did with my php.ini settings.

And of course we'll never know why as I'm not going back there.

But at least the download seems ok, as it's fine now, so that's a good sign.

Have a cup of tea and a :cookie: Go to bed early and wear a warm hat.

Goodnight

¥åßßå wrote:

Your error log errors really don't make sense, line 26 of /conf/_locales.php is simply setting a variable to 2, most of the rest of the errors are due to NT_()

I'd be tempted to grab a fresh copy of the files in case you have a corrupted download.

Also, check your error log settings in your php.ini as I'm pretty sure that this isn't an evo problem ( I've certainly never had this problem whilst running localhost )

¥

:)

*puts on warm hat* .... urm, I'll allow a session only :cookie: but anything else ..... ohhh and I can't stand bloody tea, so I'll replace that with a decent whiskey ;)

Glad it's resolved ;)

¥