The White Screen Of Death. How many of you have seen it? Chances are, just about everyone who visits WPTavern on a daily basis has at one time, seen the WsOD or have created it. The error is not caused by a single mistake but can be caused by any number of ways. The most common is a mistake in plugin PHP file or a non properly formatted WP-Config file. The most aggravating part of the WsOD is the lack of information to determine what caused the error. This is when setting Debugging to True within the WP Config file can be your friend. It should look like this: define(‘WP_DEBUG’, true); It’s not recommended that this be turned on all of the time since sensitive information regarding the server environment could be seen by the public.
SFGate takes a look at the WsOD issue and how WordPress 3.0 will help to combat the screen from appearing. The article includes quotes from both Mark Jaquith and Andrew Nacin.
“Our hands … are mostly tied here, especially since WordPress is extended through code from others,”
Interestingly enough, there is not a page in the WordPress Codex devoted to the White screen Of Death. I’ll see what the Doc team thinks about adding one and if it’s created, I’ll update this post.
Episode 42 of WordPress Weekly which fell on the same day as Friday the 13th contained a round table discussion where we talked about the various events or circumstances that would need to take place in order for WordPress to meet its demise. Although in the end, none us believed that WordPress would be disappearing anytime soon.
Ad Copy:
This episode of WordPress Weekly is sponsored by, WebDevStudios.com. WebDevStudios is a website development company specializing in WordPress support and development services. Contact them today for help with your WordPress powered website.
WordPress Trivia Question:
Give me the exact date the first post was published on the WordPress.org blog. Date should be in month, day, year format.
Each week from now on, I’ll be featuring a new listener poll question on WPTavern.com The poll is located in the sidebar on the right hand side of the site.
Last weeks poll question was: Should The Sandbox Theme Be The Next Default Theme In WordPress?
Out of a total of 30 votes, 47% or 14 of you voted Keep Kubric But Remove Classic Theme. 37% or 11 of you said Yes and 17% or 5 of you voted No.
This Weeks Poll Question Is: Is Friday The 13th Lucky Or Unlucky?
Plugin Picks Of The Week:
Jeff – Supple forms – Supple Forms is a CMS plugin for WordPress that lets you easily add a custom write panel or meta box to the Write Post/Write Page screen. It differs from other custom write panel plugins in that you can store your data in either WordPress Custom Fields or your own custom table that the plugin will create for you. Additionally, it provides a powerful HTML snippet tool that lets you format and insert your data into pages and posts with shortcodes, and without tweaking templates.
David – SEO Blogroll – Lets you decide which blogroll links have the nofollow attribute.
WordPress Trivia Answer:
April 6th, 2003
Brian Gardner Theme Giveaway:
Member ID 12 was the lucky recipient of a single site license for a Revolution theme of their choosing. Member ID 12 on the WPTavern forum is ksolomon. If ksolomon does not claim the prize or chooses not to accept, I’ll use the random number picker to choose another winner.
Announcements:
There will be no episode of WordPress Weekly next Week. Instead, the next episode will be on February 27th.
WPWeekly Meta:
Next Episode: Friday February 27th, 2009 8P.M. EST
The White Screen Of Death. How many of you have seen it? Chances are, just about everyone who visits WPTavern on a daily basis has at one time, seen the WsOD or have created it. The error is not caused by a single mistake but can be caused by any number of ways. The most common is a mistake in plugin PHP file or a non properly formatted WP-Config file. The most aggravating part of the WsOD is the lack of information to determine what caused the error. This is when setting Debugging to True within the WP Config file can be your friend. It should look like this: define(‘WP_DEBUG’, true); It’s not recommended that this be turned on all of the time since sensitive information regarding the server environment could be seen by the public. 