php-general Digest 5 Jun 2011 12:38:31 -0000 Issue 7345
php-general Digest 5 Jun 2011 12:38:31 - Issue 7345
Topics (messages 313371 through 313379):
Re: php causes HTTP 500, but results in blank page in apache
313371 by: Sean Greenslade
Re: phpsadness - P.C. shmee seee.
313372 by: Sean Greenslade
313377 by: Tamara Temple
313378 by: Tim Streater
Found this and I thought of you.
313373 by: Richard Quadling
313375 by: Joshua Kehn
313376 by: admin.buskirkgraphics.com
Re: Best authentication system
313374 by: Eric Butera
313379 by: Richard Quadling
Administrivia:
To subscribe to the digest, e-mail:
php-general-digest-subscr...@lists.php.net
To unsubscribe from the digest, e-mail:
php-general-digest-unsubscr...@lists.php.net
To post to the list, e-mail:
php-gene...@lists.php.net
--
---BeginMessage---
That's what I was thinking, thanks for confirming it.
On Jun 3, 2011 3:49 PM, Tamara Temple tamouse.li...@gmail.com wrote:
On Jun 2, 2011, at 7:09 PM, Stephon Chen wrote:
Hello Sean,
1. while I directed connected to these error pages such as 403, 404,
and 500.html,
they works correctly, showing correct error page
2. but while I use something like header('HTTP/1.1 500') to trigger
apache 500
the content of 500.html does not show, but blank page only.
both header('HTTP/1.1 403') and header('HTTP/1.1 404') shows the
correct custom error page.
Thanks a lot
--
stephon
On Fri, Jun 3, 2011 at 07:21, Sean Greenslade
zootboys...@gmail.com wrote:
So do you get the contents of that page in the response? What
happens when you browse to that page manually?
On Jun 1, 2011 2:14 AM, Stephon Chen step...@gmail.com wrote:
All 403, 404, 500.html are static html pages like:
div
500 error happens
/div
On Wed, Jun 1, 2011 at 14:10, Tamara Temple
tamouse.li...@gmail.com wrote:
On May 31, 2011, at 8:14 AM, Stephon Chen wrote:
Hello Sean,
Here is my apache config for error handling.
403, 404 works fine, but 500 shows blank page
Alias /errorpage/ /usr/local/www/apache22/errorpage/
Directory /usr/local/www/apache22/errorpage/
AllowOverride None
Options -Indexes FollowSymLinks MultiViews
Order allow,deny
Allow from all
/Directory
#
ErrorDocument 403 /errorpage/403.html
ErrorDocument 404 /errorpage/404.html
ErrorDocument 500 /errorpage/500.html
What's in 500.html?
Stephen,
This doesn't quite work how you're expecting it to.
If you have a php script that emits a 500 server error header, *you*
have to supply the document contents. Thus:
?php
header('HTTP/1.1 500 Server Error');
include('/path/to/error_docs/500.html');
?
Will get you what you want.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
---End Message---
---BeginMessage---
Well said. I agree completely with your distaste for extreme political
correctness. Like I always say, it's not a stereotype if it's true.
On Jun 3, 2011 4:53 PM, Daevid Vincent dae...@daevid.com wrote:
Reminds me (obliquely) of an entry in the index for The C Programming
Language for recursion, which points right back to that index page. I
about doubled over when I first discovered it.
That's hilarious. I love subtle humor like that.
This whole thread seems to echo the original subject recursively too...
;-)
How sad this topic has devolved from what was IMHO a fairly honest page
someone created (with valid grievances) to one of religion and name calling.
I tried to avoid commenting at all but I do have to agree with Tedd here:
Instead, I think you saw an opportunity to be politically correct
and rise to the occasion in righteous indignation.
I personally think Politically Correctness is a load of $h!t and causes
more harm and trouble than it's worth. I'm so sick of it being dictated to
me everywhere from media to schools to work to now even a programming
language list. People need thicker skins. If you are so easily offended,
then block that person's email from your mailbox. It's called the 1st
Amendment. I may not agree with, or even like the things you say, but I'll
defend to the death your right to say it -- whatever it is! I don't agree
with radical Muslims wanting to kill me either, but I'll defend their right
to protest and say whatever they want (as long as it's true!). Same goes for
KKK or any other extremist group.
http://en.wikipedia.org/wiki/First_Amendment_to_the_United_States_Constitution
Ross Perot said it best, every time you pass a new law, you give up some
of your freedoms.
And this P.C. crap is just an un-official law that is being imposed on
people.
People aren't visually impaired, they are blind. They're not dwarfs
or little people, they're midgets. A retard is handicapped and isn't
mentally challenged. (there, how many people did I just offend?) DEAL WITH
IT. I have a big nose and
php-general Digest 6 Jun 2011 00:41:46 -0000 Issue 7346
php-general Digest 6 Jun 2011 00:41:46 - Issue 7346 Topics (messages 313380 through 313404): Re: phpsadness - P.C. shmee seee. 313380 by: Geoff Shang 313381 by: Richard Riley 313382 by: Geoff Shang 313383 by: Richard Riley 313386 by: Geoff Shang 313387 by: Tim Streater 313389 by: Richard Riley 313390 by: Ashley Sheridan 313391 by: Paul M Foster 313392 by: Robert Cummings 313393 by: Robert Cummings 313394 by: Robert Cummings 313395 by: Richard Riley 313396 by: Robert Cummings 313397 by: Geoff Shang 313399 by: Tim Streater 313401 by: tedd 313402 by: tedd 313403 by: Richard Quadling 313404 by: Robert Cummings Help needed with php.ini 313384 by: Adam Tong 313385 by: Richard Quadling 313400 by: Camilo Sperberg Re: Found this and I thought of you. 313388 by: Jonesy 313398 by: Ken Kixmoeller Administrivia: To subscribe to the digest, e-mail: php-general-digest-subscr...@lists.php.net To unsubscribe from the digest, e-mail: php-general-digest-unsubscr...@lists.php.net To post to the list, e-mail: php-gene...@lists.php.net -- ---BeginMessage--- On Sun, 5 Jun 2011, Tim Streater wrote: Anyone whose site says that sort of crap needs a good smack. Don't get me started on Facebook. If they don't like your browser, they redirect you to theirWe don't support your browser page. They don't even let you try with your unsupported browser, which might well work if you're clicking on a link to a particular status update. Geoff. ---End Message--- ---BeginMessage--- Geoff Shang ge...@quitelikely.com writes: On Sun, 5 Jun 2011, Tim Streater wrote: Anyone whose site says that sort of crap needs a good smack. Don't get me started on Facebook. If they don't like your browser, they redirect you to theirWe don't support your browser page. They don't even let you try with your unsupported browser, which might well work if you're clicking on a link to a particular status update. Geoff. Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? If people want to use Lynx or W3m then go ahead : just dont expect everyone else to pander to your desire to stay old school. Google are now refusing to support older browsers like ie7 too. ---End Message--- ---BeginMessage--- On Sun, 5 Jun 2011, Richard Riley wrote: Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. I can use the mobile site fine, but if someone posts a link to a status message or some other item on Facebook, it's to the main site and not the mobile one. I don't even bother clicking because I know Facebook won't even try to send me the page I want. Geoff. ---End Message--- ---BeginMessage--- Geoff Shang ge...@quitelikely.com writes: On Sun, 5 Jun 2011, Richard Riley wrote: Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. If you really want a half arsed user experience then set your browser string ;) Would that not work for you? ---End Message--- ---BeginMessage--- On Sun, 5 Jun 2011, Richard Riley wrote: I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. Rubbish. All they need to do is what everyone else does and say This site may not work well on your browser, we recommend using Internet Explorer or firefox (or whatever they support). Then if I choose to use it, it's on my own head, which is fine by me. If you really want a half arsed user experience then set your browser string ;) Would that not work for you? It probably would. But this tangent began with the principle of Use IE or Firefox and how we hated sites that said that. It's the principle of the thing. Geoff. ---End Message---
Re: Re: [PHP] phpsadness - P.C. shmee seee.
On 05 Jun 2011 at 06:08, Tamara Temple tamouse.li...@gmail.com wrote: On Jun 3, 2011, at 3:52 PM, Daevid Vincent wrote: ...actually, I do have some good ones here: http://daevid.com/content/examples/procmail.php It appears your browser does not support some of the advanced features this site requires. Please use Internet Explorer or Firefox. ROFL. Good one. Anyone whose site says that sort of crap needs a good smack. -- Cheers -- Tim -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Best authentication system
On 4 June 2011 23:21, Sean Greenslade zootboys...@gmail.com wrote: IIRC, there is a google code project for a php login system. You might want to check it out. http://code.google.com/p/loginsystem-rd/ Login system to prevent XSS, SQL Injection and CSRF May be of interest. -- Richard Quadling Twitter : EE : Zend : PHPDoc @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: Re: [PHP] phpsadness - P.C. shmee seee.
On Sun, 5 Jun 2011, Tim Streater wrote: Anyone whose site says that sort of crap needs a good smack. Don't get me started on Facebook. If they don't like your browser, they redirect you to theirWe don't support your browser page. They don't even let you try with your unsupported browser, which might well work if you're clicking on a link to a particular status update. Geoff. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: phpsadness - P.C. shmee seee.
Geoff Shang ge...@quitelikely.com writes: On Sun, 5 Jun 2011, Tim Streater wrote: Anyone whose site says that sort of crap needs a good smack. Don't get me started on Facebook. If they don't like your browser, they redirect you to theirWe don't support your browser page. They don't even let you try with your unsupported browser, which might well work if you're clicking on a link to a particular status update. Geoff. Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? If people want to use Lynx or W3m then go ahead : just dont expect everyone else to pander to your desire to stay old school. Google are now refusing to support older browsers like ie7 too. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On Sun, 5 Jun 2011, Richard Riley wrote: Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. I can use the mobile site fine, but if someone posts a link to a status message or some other item on Facebook, it's to the main site and not the mobile one. I don't even bother clicking because I know Facebook won't even try to send me the page I want. Geoff. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: phpsadness - P.C. shmee seee.
Geoff Shang ge...@quitelikely.com writes: On Sun, 5 Jun 2011, Richard Riley wrote: Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. If you really want a half arsed user experience then set your browser string ;) Would that not work for you? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Help needed with php.ini
Hi, I can't set correctly the error display and reporting properties. I don't know what i'm doing wrong. Here is the section that i modified in php.ini: - display_errors = On ; Default Value: On ; Development Value: On ; Production Value: Off display_startup_errors = On ; Default Value: Off ; Development Value: On ; Production Value: Off error_reporting = E_ALL | E_STRICT ; Default Value: E_ALL ~E_NOTICE ; Development Value: E_ALL | E_STRICT ; Production Value: E_ALL ~E_DEPRECATED And here is the output of phpinfo(): - display_errors Off Off display_startup_errors Off Off doc_rootno valueno value docref_ext no valueno value docref_root no valueno value enable_dl Off Off error_append_string no valueno value error_log no valueno value error_prepend_stringno valueno value error_reporting 22527 22527 - I'm using a default installation (using yum) of php on Fedora14. This is my development environment, and want to see all the errors on standard output. Thank you -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Help needed with php.ini
And here is the output of phpinfo(): - In the same phpinfo() output, what is the path/location of the php.ini file you are using? Loaded Configuration File D:\PHP\INI\php-cgi-fcgi.ini for example. -- Richard Quadling Twitter : EE : Zend : PHPDoc @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On Sun, 5 Jun 2011, Richard Riley wrote: I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. Rubbish. All they need to do is what everyone else does and say This site may not work well on your browser, we recommend using Internet Explorer or firefox (or whatever they support). Then if I choose to use it, it's on my own head, which is fine by me. If you really want a half arsed user experience then set your browser string ;) Would that not work for you? It probably would. But this tangent began with the principle of Use IE or Firefox and how we hated sites that said that. It's the principle of the thing. Geoff. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 05 Jun 2011 at 16:23, Geoff Shang ge...@quitelikely.com wrote: On Sun, 5 Jun 2011, Richard Riley wrote: I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. Rubbish. All they need to do is what everyone else does and say This site may not work well on your browser, we recommend using Internet Explorer or firefox (or whatever they support). Then if I choose to use it, it's on my own head, which is fine by me. If you really want a half arsed user experience then set your browser string ;) Would that not work for you? It probably would. But this tangent began with the principle of Use IE or Firefox and how we hated sites that said that. It's the principle of the thing. Yes. You might (just) be able to justify something really old [1], but Safari 5.0.5? I find that to be a damn cheek. I expect sites to be standards-based. [1] Don't ask me what that means. I've not kept up with what new stuff is around now that wasn't, ten years ago. -- Cheers -- Tim -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: Found this and I thought of you.
On Sun, 5 Jun 2011 00:34:30 +0100, Richard Quadling wrote: http://www.exxcire.com/login.php If nothing more than a good bad example. ROTFLMAO!!! Where Experts Exchange Sweet Jeezuz! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: phpsadness - P.C. shmee seee.
Geoff Shang ge...@quitelikely.com writes: On Sun, 5 Jun 2011, Richard Riley wrote: I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. Rubbish. All they need to do is what everyone else does and say This site may not work well on your browser, we recommend using Internet Explorer or firefox (or whatever they support). Then if I choose to use it, it's on my own head, which is fine by me. Not rubbish at all. They owe you nothing. Not everyone is you. If they allowed incompatible browsers that caused havoc then before you know it the great unwashed would be demanding more and better support or complaining about lack of functionality. Doing what they do they make it very clear from day one. Dont like it? The APIs are open. Write your own interfaces to their authentication and graph API and target the parts that wont result in your accuont being banned for chucking access tokens around and breaking their security model. Simple solution : use an uptodate capable browser if you want to use these technologies. I really dont see why people whine. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On Sun, 2011-06-05 at 19:23 +0200, Richard Riley wrote: Geoff Shang ge...@quitelikely.com writes: On Sun, 5 Jun 2011, Richard Riley wrote: I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. Rubbish. All they need to do is what everyone else does and say This site may not work well on your browser, we recommend using Internet Explorer or firefox (or whatever they support). Then if I choose to use it, it's on my own head, which is fine by me. Not rubbish at all. They owe you nothing. Not everyone is you. If they allowed incompatible browsers that caused havoc then before you know it the great unwashed would be demanding more and better support or complaining about lack of functionality. Doing what they do they make it very clear from day one. Dont like it? The APIs are open. Write your own interfaces to their authentication and graph API and target the parts that wont result in your accuont being banned for chucking access tokens around and breaking their security model. Simple solution : use an uptodate capable browser if you want to use these technologies. I really dont see why people whine. I think his point is that a lot of websites ignorantly stop browsers not on their list of compatible ones, and end up blocking browsers that would work perfectly well, just the original developer either wasn't aware or didn't care. This used to be in the form of Javascript detecting if a browser was IE, and if it wasn't, assuming blindly it was Netscape Navigator. Now Fx seems to be in that position, and many sites ignore perfectly good browsers like Chrome, Safari, Opera Konqueror to name a few. All of these are modern browsers, yet they will be blocked by stupid code. -- Thanks, Ash http://www.ashleysheridan.co.uk
Re: [PHP] phpsadness - P.C. shmee seee.
On Fri, Jun 03, 2011 at 01:52:15PM -0700, Daevid Vincent wrote: and I'm balding from Alopecia Me too, but in my case, it's just 'cause I'm old. ;-} Paul -- Paul M. Foster http://noferblatz.com http://quillandmouse.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 11-06-05 09:33 AM, Richard Riley wrote: Geoff Shangge...@quitelikely.com writes: On Sun, 5 Jun 2011, Tim Streater wrote: Anyone whose site says that sort of crap needs a good smack. Don't get me started on Facebook. If they don't like your browser, they redirect you to theirWe don't support your browser page. They don't even let you try with your unsupported browser, which might well work if you're clicking on a link to a particular status update. Geoff. Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? If people want to use Lynx or W3m then go ahead : just dont expect everyone else to pander to your desire to stay old school. Google are now refusing to support older browsers like ie7 too. 2 words... progressive enhancement. If your browser doesn't support a feature then it should degrade gracefully. Accessible web philosophy 101. I hate going on to some website, especially government, and finding that it sniffs my browser and then completely excludes me if it doesn't like what it finds. Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 11-06-05 01:23 PM, Richard Riley wrote: Geoff Shangge...@quitelikely.com writes: On Sun, 5 Jun 2011, Richard Riley wrote: I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. Rubbish. All they need to do is what everyone else does and say This site may not work well on your browser, we recommend using Internet Explorer or firefox (or whatever they support). Then if I choose to use it, it's on my own head, which is fine by me. Not rubbish at all. They owe you nothing. Not everyone is you. If they allowed incompatible browsers that caused havoc then before you know it the great unwashed would be demanding more and better support or complaining about lack of functionality. Doing what they do they make it very clear from day one. Dont like it? The APIs are open. Write your own interfaces to their authentication and graph API and target the parts that wont result in your accuont being banned for chucking access tokens around and breaking their security model. If it's that easy to break their security model then it's not secure! Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] phpsadness - P.C. shmee seee.
On 11-06-05 01:40 PM, Paul M Foster wrote: On Fri, Jun 03, 2011 at 01:52:15PM -0700, Daevid Vincent wrote: and I'm balding from Alopecia Me too, but in my case, it's just 'cause I'm old. ;-} My sympathies to you both... I'm baling because I produce a lot of testosterone :D Although, everything I read about having children suggests my estrogen is likely at an all time high! Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: phpsadness - P.C. shmee seee.
Ashley Sheridan a...@ashleysheridan.co.uk writes: On Sun, 2011-06-05 at 19:23 +0200, Richard Riley wrote: Geoff Shang ge...@quitelikely.com writes: On Sun, 5 Jun 2011, Richard Riley wrote: I don't. I just don't want them to lock out my browser just because they don't support it. Many pages which don't work optimally under Lynx can still be read, which is all I'm wanting to do anyway. They need to or there can be unintentional side affects that will reflect badly on them and possibly you. Rubbish. All they need to do is what everyone else does and say This site may not work well on your browser, we recommend using Internet Explorer or firefox (or whatever they support). Then if I choose to use it, it's on my own head, which is fine by me. Not rubbish at all. They owe you nothing. Not everyone is you. If they allowed incompatible browsers that caused havoc then before you know it the great unwashed would be demanding more and better support or complaining about lack of functionality. Doing what they do they make it very clear from day one. Dont like it? The APIs are open. Write your own interfaces to their authentication and graph API and target the parts that wont result in your accuont being banned for chucking access tokens around and breaking their security model. Simple solution : use an uptodate capable browser if you want to use these technologies. I really dont see why people whine. I think his point is that a lot of websites ignorantly stop browsers not on their list of compatible ones, and end up blocking browsers that would work perfectly well, just the original developer either wasn't aware or didn't care. This used to be in the form of Javascript detecting if a browser was IE, and if it wasn't, assuming blindly it was Netscape Navigator. Now Fx seems to be in that position, and many sites ignore perfectly good browsers like Chrome, Safari, Opera Konqueror to name a few. All of these are modern browsers, yet they will be blocked by stupid code. Ignorant blocking is a different matter and I would agree. Blocking because someone is using out of date or incapable browsers is another issue. It is the latter, and specifically something with a rich UI that requires secure connections like FB that I am discussing. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 11-06-05 02:25 PM, Richard Riley wrote: Ashley Sheridana...@ashleysheridan.co.uk writes: I think his point is that a lot of websites ignorantly stop browsers not on their list of compatible ones, and end up blocking browsers that would work perfectly well, just the original developer either wasn't aware or didn't care. This used to be in the form of Javascript detecting if a browser was IE, and if it wasn't, assuming blindly it was Netscape Navigator. Now Fx seems to be in that position, and many sites ignore perfectly good browsers like Chrome, Safari, Opera Konqueror to name a few. All of these are modern browsers, yet they will be blocked by stupid code. Ignorant blocking is a different matter and I would agree. Blocking because someone is using out of date or incapable browsers is another issue. It is the latter, and specifically something with a rich UI that requires secure connections like FB that I am discussing. Secure connection and rich UI should not in any way tread on the other's role and responsibility. Authentication and authorization control security, not the UI. If the UI controls the level of security then the solution is broken. A well designed website should be navigable with a screen reader without any of the DHTML and Ajax bits. That some sites aren't, is just pure laziness. Information is information, websites just present the information and it can be presented in multiple ways. Progressive enhancement should be able to take a plain vanilla webpage and blingify it, while leaving a navigable website via traditional means. Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On Sun, 5 Jun 2011, Richard Riley wrote: If they allowed incompatible browsers that caused havoc then before you know it the great unwashed would be demanding more and better support or complaining about lack of functionality. Doing what they do they make it very clear from day one. This would be a fair enough attitude if they only applied it to their member sections, but they don't. They set themselves up as publishers of information, page hosts of sorts, then don't let anyone in who wants to *read* them. Dont like it? The APIs are open. Write your own interfaces to their authentication and graph API and target the parts that wont result in your accuont being banned for chucking access tokens around and breaking their security model. Totally not the point. Quite aside from the fact that Mobile Facebook works extremely well with Lynx, and so did Facebook Lite until they sadly took it away, it's not what I'm having trouble with. An example of what I'm talking about is the following tweet: ABCGrandStand: #nrl : NSW ORIGIN team game two.. Dugan, Hayne, Hopoate, Gasnier, Uate, Soward, Pearce, Gallen, Ennis, Mannah,... http://fb.me/uPHxKiFC http://twitter.com/abcgrandstand/status/77271757383413760 Now, correct me if I'm wrong, but there's no need to log in or anything remotely 21st-century required to read the rest of this post. All you need to do is click the URL and the appropriate Facebook status will come up, which you're free to read without any further clicking on your part. But only if you're using a browser that's been blessed by the Facebook gods. If you're not, you're sent to http://www.facebook.com/common/browser.php with no other course of action. I hope you can appreciate my point. The choice to use Facebook was a decision made by the person sending the tweet, not me. It's not going to kill them to either let me see the page with appropriate functionality warnings, or to flick-pass me to the equivalent mobile Facebook page. I can't view it on the mobile site myself without first resolving where the shortened URL points to, changing the www to m and hoping it works, or signing in and trying to find it myself. Even Twitter, who don't let me login to the regular site without javascript, are quite happy to let me view tweets unauthenticated on their site with Lynx. If I want to login, I need to use their mobile site. Not a problem - if I try to use their main site and it doesn't work, it doesn't work. At least they let me try. Geoff. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: Found this and I thought of you.
On Sun, Jun 5, 2011 at 11:44 AM, Jonesy gm...@jonz.net wrote: On Sun, 5 Jun 2011 00:34:30 +0100, Richard Quadling wrote: http://www.exxcire.com/login.php If nothing more than a good bad example. ROTFLMAO!!! Where Experts Exchange Sweet Jeezuz! At least they have a cute 404 page. Gotta count for *something*! g Ken -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 05 Jun 2011 at 21:28, Geoff Shang ge...@quitelikely.com wrote: On Sun, 5 Jun 2011, Richard Riley wrote: If they allowed incompatible browsers that caused havoc then before you know it the great unwashed would be demanding more and better support or complaining about lack of functionality. Doing what they do they make it very clear from day one. This would be a fair enough attitude if they only applied it to their member sections, but they don't. They set themselves up as publishers of information, page hosts of sorts, then don't let anyone in who wants to *read* them. This sums it up better than I could: Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network. -- Tim Berners-Lee -- Cheers -- Tim -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Help needed with php.ini
On 05-06-2011, at 10:31, Adam Tong adam.to...@gmail.com wrote: Hi, I can't set correctly the error display and reporting properties. I don't know what i'm doing wrong. Here is the section that i modified in php.ini: - display_errors = On ; Default Value: On ; Development Value: On ; Production Value: Off display_startup_errors = On ; Default Value: Off ; Development Value: On ; Production Value: Off error_reporting = E_ALL | E_STRICT ; Default Value: E_ALL ~E_NOTICE ; Development Value: E_ALL | E_STRICT ; Production Value: E_ALL ~E_DEPRECATED And here is the output of phpinfo(): - display_errorsOffOff display_startup_errorsOffOff doc_rootno valueno value docref_extno valueno value docref_rootno valueno value enable_dlOffOff error_append_stringno valueno value error_logno valueno value error_prepend_stringno valueno value error_reporting2252722527 - I'm using a default installation (using yum) of php on Fedora14. This is my development environment, and want to see all the errors on standard output. Thank you -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php Have you modified the example values instead of the ones mid-way php.ini? If so, scroll down to check. The latest settings should override the previous one. Have you restarted apache with service httpd restart or /etc/init.d/httpd restart? (or apachectl restart) In your php script or htaccess file, do you override those values? Sent from my iPhone 5 Beta [Confidential use only] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
At 6:29 PM +0100 6/5/11, Ashley Sheridan wrote: I think his point is that a lot of websites ignorantly stop browsers not on their list of compatible ones, and end up blocking browsers that would work perfectly well, just the original developer either wasn't aware or didn't care. This used to be in the form of Javascript detecting if a browser was IE, and if it wasn't, assuming blindly it was Netscape Navigator. Now Fx seems to be in that position, and many sites ignore perfectly good browsers like Chrome, Safari, Opera Konqueror to name a few. All of these are modern browsers, yet they will be blocked by stupid code. -- Thanks, Ash 1+ Absolutely. If you want to have a web site it figures that you want as many visitors as possible. If you restrict visitors to specific browsers then runs contrary to your interest-- and that is just plain ignorant. For example, I just found a web site where I wanted to order a car part. In their search form they asked for my auto's make and year. After I provided that information, without providing me anything, they asked me for the part number I was interested in purchasing. What How do I know what their part number is for the auto-part I want? I'm going to use their web site as an example of how NOT to design a form. While they may know the auto-parts biz, they are clueless about how to provide their products to visitors via their web site. I've had more than one client tell me Just have the computer do it -- to which I reply I tried, but the computer just sits there. How do you do it? Ignorance in leaps and bounds everywhere. Cheers, tedd -- --- http://sperling.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
At 2:15 PM -0400 6/5/11, Robert Cummings wrote: On 11-06-05 09:33 AM, Richard Riley wrote: Geoff Shangge...@quitelikely.com writes: On Sun, 5 Jun 2011, Tim Streater wrote: Anyone whose site says that sort of crap needs a good smack. Don't get me started on Facebook. If they don't like your browser, they redirect you to theirWe don't support your browser page. They don't even let you try with your unsupported browser, which might well work if you're clicking on a link to a particular status update. Geoff. Why do you feel FB should support some antiquated browser that doesnt support any of the newer technoogies which enable security and more advanced client side rendering? If people want to use Lynx or W3m then go ahead : just dont expect everyone else to pander to your desire to stay old school. Google are now refusing to support older browsers like ie7 too. 2 words... progressive enhancement. If your browser doesn't support a feature then it should degrade gracefully. Accessible web philosophy 101. I hate going on to some website, especially government, and finding that it sniffs my browser and then completely excludes me if it doesn't like what it finds. Cheers, Rob. Rob: Yeah, I agree, but it is also *you* -- so exclusion is understandable. :-) Cheers, tedd -- --- http://sperling.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 5 June 2011 19:15, Robert Cummings rob...@interjinn.com wrote: 2 words... progressive enhancement. If your browser doesn't support a feature then it should degrade gracefully. Accessible web philosophy 101. I hate going on to some website, especially government, and finding that it sniffs my browser and then completely excludes me if it doesn't like what it finds. There is another approach. Regressive Enhancement. Essentially, create your site with all the bells and whistles enabled. Make full use of all / any standards compliant feature. For browsers not capable of supporting that, use emulation techniques. Sitepoint have a blog about this technique : http://blogs.sitepoint.com/regressive-enhancement-with-modernizr-and-yepnope/ -- Richard Quadling Twitter : EE : Zend : PHPDoc @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 11-06-05 07:28 PM, tedd wrote: At 2:15 PM -0400 6/5/11, Robert Cummings wrote: 2 words... progressive enhancement. If your browser doesn't support a feature then it should degrade gracefully. Accessible web philosophy 101. I hate going on to some website, especially government, and finding that it sniffs my browser and then completely excludes me if it doesn't like what it finds. Cheers, Rob. Rob: Yeah, I agree, but it is also *you* -- so exclusion is understandable. :-) As my kids are all too fond of saying to me... *PTHTHTHTHTTHTH*! :D Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: phpsadness - P.C. shmee seee.
On 11-06-05 07:28 PM, Richard Quadling wrote: On 5 June 2011 19:15, Robert Cummingsrob...@interjinn.com wrote: 2 words... progressive enhancement. If your browser doesn't support a feature then it should degrade gracefully. Accessible web philosophy 101. I hate going on to some website, especially government, and finding that it sniffs my browser and then completely excludes me if it doesn't like what it finds. There is another approach. Regressive Enhancement. Essentially, create your site with all the bells and whistles enabled. Make full use of all / any standards compliant feature. For browsers not capable of supporting that, use emulation techniques. Sitepoint have a blog about this technique : http://blogs.sitepoint.com/regressive-enhancement-with-modernizr-and-yepnope/ From my cursory read... regressive enhancement would need to rely on progressive enhancement to work :) If there's no JavaScript to do the lifting, then how can you regress? An interesting read all the same. It's kind of like the compatibility layer PEAR releases for older versions of PHP so they have access to newer functions and stuff but implemented in PHP rather than C. Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] phpsadness - the second tangent...
Really? This thread is going to tangent yet again to something completely irrelevant? FWIW, I used some stupid WinLIKE JS framework by http://ceiton.com These bastards haven't updated it since 2007 http://wiki.winlike.net/index.php/Version_History Normally not a big deal, but they patented it (or tried), and it's all minified and IN GERMAN! So trying to figure out how and where to remove that browser check has been a futile effort that I just don't care to spend any more time on. This is yet another reason and example as to why I HATE frameworks. I should have never used their crappy one and just built everything myself. My current PERSONAL site is starting to show its age and is due for a re-vamp, but honestly I just have too much other work on my plate that pays me. 90% of the people out there use FF or IE and so I don't really care about Safari or Opera or the other fringe browsers for my PERSONAL site. -Original Message- From: Tamara Temple [mailto:tamouse.li...@gmail.com] Sent: Saturday, June 04, 2011 10:09 PM To: Daevid Vincent Cc: php-general@lists.php.net Subject: Re: [PHP] phpsadness - P.C. shmee seee. On Jun 3, 2011, at 3:52 PM, Daevid Vincent wrote: ...actually, I do have some good ones here: http://daevid.com/content/examples/procmail.php It appears your browser does not support some of the advanced features this site requires. Please use Internet Explorer or Firefox. ROFL. Good one. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
