Ok, I think I figured out where these PEAR_LOG errors I was
having came from:
Notice: Use of undefined constant PEAR_LOG_DEBUG - assumed
'PEAR_LOG_DEBUG'
in /var/www/mailguard/config.php on line 81
Notice: Use of undefined constant PEAR_LOG_DEBUG - assumed
'PEAR_LOG_DEBUG'
in /var/www/mailguard/config.php on line 84
One of the first things admin/configtest.php does is
"include ../config.php",
but at this moment log.php is not yet included so this will
generate these
two errors in this log.
This is not a problem for the website itself since core.php
includes log.php
for every site. This is a test script specific error.
But I still only get a white empty site when I surf to
login.php
But I am quite sure it isn't a php error.
I tried adding a simple echo "hi"; to login.php
and the text gets displayed as
it should. also when I set the debug window to true this
gives me a window
with Time|Ident|Priority|Message, however without any other
information.
It looks like smarty simply doesn't show anything. but it is
very quiet as to
the reason why. no popup debug, no notes in the apache logs,
no system log
entries.. nothing...
even when I change
$smarty->display("login.tpl"); in login.php to
something
like $smarty->display("login2.tpl"); which
naturally doesn't exist I still
get nothing in the form of errors.
does anyone have any idea as to approach this problem?
or perhaps how I can make smarty shout a bit more at me :p
Thanks!
Mark Hannessen
Mark Hannessen wrote:
> Hi list,
>
> I ran into a little problem trying to get maia to run.
according to the
> configtest.php file I should be pretty much ok, but
when I run login.php all
> I see is an empty page. when I use the browser to view
the document source
> there is nothing at all. which i think would suggest
some php problem. But i
> can't find the reason.
Blank pages point to errors in PHP scripts, and usually this
is
explained in your PHP logs, or your web server's logs as
some sort of
error. Usually the lines to look for refer specifically to
"errors"
(which are fatal), not "warnings" or
"notices" (which are non-fatal, but
may still point to configuration problems).
> I scanned the apache logs and also found a (probably
unrelated) "warning" in
> the config file which I fixed.
>
> Notice: Use of undefined constant PEAR_LOG_DEBUG -
assumed 'PEAR_LOG_DEBUG'
in
> maia/config.php on line 79
>
> Notice: Use of undefined constant PEAR_LOG_DEBUG -
assumed 'PEAR_LOG_DEBUG'
in
> maia/config.php on line 82
>
> I found that putting quotes around 'PEAR_LOG_DEBUG'
made the warning go
away.
There should have been no reason to do this; you suppressed
an
informational notice by essentially changing a variable name
to a string
constant, which silences the notice but defeats the
variable's purpose.
Get rid of those quotes, they don't belong there.
There's some mystery to why that constant (PEAR_LOG_DEBUG)
was not
defined, however, since your configtest.php reports that you
do have the
PEAR::Log module installed.
If you have $debug_popup set to true in config.php, you
should be seeing
a popup window appear whenever you try to load a Maia page
and a notice,
warning, or error occurs. If the popup is not appearing
(and you have
$debug_popup set to true), then the problem involves
PEAR::Log somehow.
In that case, set $debug_popup to false.
> But It still didn't make it run.
That's understandable; that was a "notice", rather
than an "error", so
it was not the cause of the blank page. Look further in the
web logs
for something that explicitly reports an
"error"--that's what should
point you to the cause.
> I tried the trunk as well just to be sure and found
that it contained
similair
> quote bugs.
>
> Notice: Use of undefined constant MAIA_VERSION -
assumed 'MAIA_VERSION' in
> maia/smarty.php on line 195
These are not "quote bugs"; there is no need for
quotes around variables
like MAIA_VERSION, they are defined in the constants.php
file, and in
other PHP scripts that are supposed to be included at the
beginning of
the PHP scripts that reference them. Putting quotes around
them will
silence the notices, but it won't solve the problem that
those notices
are trying to alert you to.
I'm a bit concerned about your comment about using the trunk
version,
and this may point to the problem. The trunk version is
alpha code for
the 1.1.x series, whereas the release version is the 1.0.x
series.
These two are not database-compatible, and there will be
code
incompatibilities as well. If you've got a mixture of
release code and
trunk code, and/or you're trying to use trunk code on a
1.0.x database,
you're going to get all sorts of strange errors--that may
well be what
you're experiencing here.
--
Robert LeBlanc <rjl renaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamail
guard.com/>
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
|
