Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Community edition "Login Failed" due to PHP warnings.
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Daniel Benoy  
View profile  
 More options Jun 1 2012, 10:21 am
From: Daniel Benoy <dan...@benoy.name>
Date: Fri, 1 Jun 2012 07:21:31 -0700 (PDT)
Local: Fri, Jun 1 2012 10:21 am
Subject: Community edition "Login Failed" due to PHP warnings.

The PHP code on my installation was generating warnings like this one:

[Fri Jun 01 10:03:51 2012] [error] [client x.x.x.x] PHP Warning:  date()
[<a href='function.date'>function.date</a>]: It is not safe to rely on the
system's timezone settings. You are *required* to use the date.timezone
setting or the date_default_timezone_set() function. In case you used any
of those methods and you are still getting this warning, you most likely
misspelled the timezone identifier. We selected 'America/New_York' for
'EDT/-4.0/DST' instead in
/var/www/www.muck.ca/htdocs/pw/php/objects/class.record.php on line 223,
referer: http://www.muck.ca/pw/php/beta/

The warnings were also appearing in the output of the page itself,
corrupting the JSON results, and I kept seeing "Login Failed" and clicking
on the button wouldn't make the dialog go away, and it looked like it 'half
logged in'.

To fix it, I did this in my php.ini:
error_reporting = E_COMPILE_ERROR | E_ERROR | E_CORE_ERROR

Perhaps the most ideal solution would be:
1) Get the PHP code to be as aggressive as possible at calling functions
which turn off error logging and warnings if it's going to be returning
JSON output.
2) Have the javascript fail more gracefully when it receives garbarge
output, and perhaps display it to the user in some limited way to help with
diagnostics.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »