Site is blank - Revision history

Patricia Schmidt: /* Backend is Blank, Too */

2013-03-09T07:08:42Z

‎Backend is Blank, Too

Patricia Schmidt: /* Backend is Blank, Too */

2013-03-09T03:35:06Z

‎Backend is Blank, Too

Patricia Schmidt: /* Back End Still Blank After the Custom Hack */

2013-03-09T03:34:48Z

‎Back End Still Blank After the Custom Hack

Patricia Schmidt: /* Back End still blank, even after trying the custom hack */

2013-03-09T03:34:34Z

‎Back End still blank, even after trying the custom hack

Patricia Schmidt: /* Backend is blank too */

2013-03-09T03:31:18Z

‎Backend is blank too

Patricia Schmidt: /* Error Not Displayed, Error Reporting Set to Maximum or Development */

2013-03-09T03:28:56Z

‎Error Not Displayed, Error Reporting Set to Maximum or Development

Patricia Schmidt: /* White Screen of Death */

2013-03-09T03:28:02Z

‎White Screen of Death

Sinisakrisan: /* White Screen of Death */

2013-01-23T00:29:26Z

‎White Screen of Death

Sinisakrisan: /* Error is not displayed even if error reporting is set to maximum or development */

2013-01-20T23:24:28Z

‎Error is not displayed even if error reporting is set to maximum or development

Sinisakrisan: /* Enable Error Reporting in Joomla! */

2013-01-20T22:32:45Z

‎Enable Error Reporting in Joomla!

@@ Line 34: / Line 34: @@
 Well, not really. If the site Backend returns a WSoD and you can't enable '''Error Reporting''', you will just have to use the nasty trick we mentioned earlier; however, this time, paste it into:
- ROOT/administrator/index.php
+* ROOT/administrator/index.php
 Open that file and immediately after:

@@ Line 33: / Line 33: @@
 '''''Houston, we have a problem!!!''''' <br />
-Well, not really. If the site Backend returns a WSoD and you can't enable '''Error reporting''', you will just have to use the nasty trick we mentioned earlier; however, this time, paste it into:
+Well, not really. If the site Backend returns a WSoD and you can't enable '''Error Reporting''', you will just have to use the nasty trick we mentioned earlier; however, this time, paste it into:
   ROOT/administrator/index.php

@@ Line 50: / Line 50: @@
 Now, you should be able to view the error behind blank screen.
-===Back End Still Blank After the Custom Hack===
+===Backend Still Blank After the Custom Hack===
 This is potentially the biggest problem you might experience, but the solution is the same as if it was for not displaying errors in the Frontend, only this time, you will have to disable extensions directly in the Joomla Database.
 {{alert|<strong>Warning:</strong> This can potentially be dangerous if you don't know what you're doing, so '''PLEASE''' make a '''Backup''' before you do anything.|alert-danger}}

@@ Line 50: / Line 50: @@
 Now, you should be able to view the error behind blank screen.
-===Back End still blank, even after trying the custom hack===
+===Back End Still Blank After the Custom Hack===
-This is potentially the biggest problem you might experience, but solution is the same as if it was for not displaying errors in Front End, only this time, You will have to disable extensions directly in the Joomla Database and that can be potentially dangerous if you dont know what you doing, so plese, make a backup before you do anything.

@@ Line 30: / Line 30: @@
 {{alert|<strong>Hint:</strong> It's not JomSocial, so you can confidently skip disabling any JomSocial extension provided in our download package.|alert-info}}
-===Backend is blank too===
+===Backend is Blank, Too===
 '''''Houston, we have a problem!!!''''' <br />
-Well, not really... If Back End of site returns WSoD and you cant enable '''Error reporting''' you will just have to use the nasty trick we mentioned earlier but this time, paste it into
   ROOT/administrator/index.php
 Open that file and immediately after
 <syntaxhighlight lang="php">
 define('_JEXEC', 1);
@@ Line 40: / Line 42: @@
 </syntaxhighlight>
 <br />
-paste this little nifty code
+Paste this little nifty code:
 <syntaxhighlight lang="php">
 error_reporting(E_ALL);
@@ Line 46: / Line 48: @@
 </syntaxhighlight>
 <br />
-Now you should be able to view the error behind blank screen.
+Now, you should be able to view the error behind blank screen.
 ===Back End still blank, even after trying the custom hack===
 This is potentially the biggest problem you might experience, but solution is the same as if it was for not displaying errors in Front End, only this time, You will have to disable extensions directly in the Joomla Database and that can be potentially dangerous if you dont know what you doing, so plese, make a backup before you do anything.

@@ Line 28: / Line 28: @@
 You will have to track down which extension prevents Joomla from displaying errors and that could potentially involve disabling many plugins, modules, and components, but, in most cases, it is the only way to properly identify the offender.<br />
-{{alert|<strong>Hint:</strong> It's not JomSocial so you can confidently skip disabling any JomSocial extension provided in our download package.|alert-info}}
+{{alert|<strong>Hint:</strong> It's not JomSocial, so you can confidently skip disabling any JomSocial extension provided in our download package.|alert-info}}
 ===Backend is blank too===

@@ Line 1: / Line 1: @@
-==White Screen of Death==
+===White Screen of Death===
-Blank Page or popularly called '''White Screen of Death (WSoD)''' indicates that there is an error on the page, '''not necessarily caused by jomSocial''' even if page that is expected to be loaded is one of the jomSocial's pages. These white screens usually hide the exact error behind it, but these errors are cleverly hidden by Joomla to prevent simple (or malicious) users viewing your site paths.
-===Enable Error Reporting in Joomla!===
+A '''Blank Page''' or often otherwise called the '''White Screen of Death (WSoD)''' indicates that there is an error on the page; however, this is '''not necessarily caused by JomSocial''' even if the page that is expected to be loaded is one of JomSocial's pages. These white screens usually hide the exact error behind it, but these errors are cleverly hidden by Joomla to prevent potentially malicious users from viewing your '''Site Paths'''.
-Enabling this setting in Joomla! Global Configuration is usually enough for most of the errors to show up.<br />
-Please navigate to the Joomla Global Configuration in the site Back End and under Server Settings locate the ''Error Reporting'' option. It should be set to '''System Default''' which would hide the error with blank page.<br />
-You change this setting to '''Maximum''' or even '''Development'''. Save and go back to the page with WSoD <br />
-In most cases, you should be able to see what is the exact error now.
-===Error is not displayed even if error reporting is set to maximum or development===
+===Enable Error Reporting in Joomla===
-On the System Pane in Joomla Global Configuration, enable '''Debug System''' option. Save, and try again. <br />
-If that dont show the error either, dont panic. Some developers put this code into their extensions
+Enabling this setting in the Joomla '''Global Configuration''' is usually enough for most of the errors to show up.<br />
 <syntaxhighlight lang="php">
 /* Enable this when debugging*/
@@ Line 17: / Line 24: @@
 </syntaxhighlight>
 <br />
-In essence, this little piece of code, if loaded on the page, will force Joomla! '''not to show''' any error even if you enable '''System Debug''' and '''Error Reporting'''. It is most commonly used by beginner developers to hide ''notices'' and ''warnings'' in their code, but rest asured, that jomSocial dont use this nasty trick to hide any errors in any piece of its code.<br />
+In essence, this little piece of code, if loaded on the page, will force Joomla to '''not show''' any error even if you enable '''System Debug''' and '''Error Reporting'''. It is most commonly used by beginner developers to hide '''notices''' and '''warnings''' in their code. Rest assured, JomSocial doesn't use this nasty trick to hide any errors in any piece of its code.<br />
-You will have to track down which extension prevents Joomla! to display errors, and that could potentially involve disabling many plugins, modules and components, but in most cases, it is the only way to hunt it down properly.<br />
-'''A hint:''' its not jomSocial, you can confidently skip disabling any jomSocial extension provided in our download package.
+You will have to track down which extension prevents Joomla from displaying errors and that could potentially involve disabling many plugins, modules, and components, but, in most cases, it is the only way to properly identify the offender.<br />
-===Back End is blank too===
+===Backend is blank too===
 '''''Houston, we have a problem!!!''''' <br />
 Well, not really... If Back End of site returns WSoD and you cant enable '''Error reporting''' you will just have to use the nasty trick we mentioned earlier but this time, paste it into