Direct calls to wp-config.php return "not found" errors in many WP setups.

[GoogleCodeExporter]

WordPress plugins should never call wp-config directly.  It can break in 
multiple situations.  Perhaps a fix involving hooking template calls?

Original issue reported on code.google.com by stephen....@gmail.com on 21 May 2011 at 2:46

[GoogleCodeExporter]

Issue 19 has been merged into this issue.

Original comment by stephen....@gmail.com on 21 May 2011 at 2:58

[GoogleCodeExporter]

Original comment by stephen....@gmail.com on 21 May 2011 at 3:03

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

sk_captcha_graphic.php also calls wpconfig.php directly.  This should be fixed 
also.

Original comment by stephen....@gmail.com on 2 Jul 2011 at 4:49

• Changed title: Direct calls to wp-config.php return "not found" errors in many WP setups.

[strider72]

Replaced direct call with wp_redirect(). See https://github.com/strider72/spam-karma/commit/94d5bb8bac62fe0d6a27dd40748b152f8a575651

[strider72]

Reopening this. Need to double check that wp_redirect doesn't introduce errors. Second Chance doesn't work currently.