strider72 / spam-karma

A flexible and modular anti-spam plugin for WordPress
GNU General Public License v2.0
3 stars 3 forks source link

wp-config.php at another place than www root #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. move wp-config.php one level below your www directory. this is advised for 
security reasons
2. make a comment, it will spill something like: wp-config.php cannot be found 
at ../../../ , whereas ../../../ seems to be hardcoded but false in my case

What is the expected output? What do you see instead?

the correct page telling the user that the comment was accepted

What version of the product are you using? On what operating system?

wp 3.01, sk2 2.2 r3

Please provide any additional information below.

Moving the wp-config.php out is mentioned here: 
http://www.devlounge.net/code/protect-your-wordpress-wp-config-so-you-dont-get-h
acked

Original issue reported on code.google.com by gmmda...@googlemail.com on 23 Sep 2010 at 4:58

GoogleCodeExporter commented 9 years ago
I cannot reproduce this error simply by moving wp-config.php up one level.  In 
fact that is how I run my site and have never had issues.

My site's setup:  in root directory public_html I have wp-config.php.  
WordPress files are within public_html/wp.  Entire site is run from WordPress.

Marking "invalid" for now.  If you can further identify the issue please do 
resubmit so we can track it down.

Original comment by stephen....@gmail.com on 11 Jan 2011 at 10:54

GoogleCodeExporter commented 9 years ago
If this issue is valid, it will probably be fixed when fixing Issue 23.  As 23 
is a broader description, I'll mark this a dupe of that.

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

GoogleCodeExporter commented 9 years ago
Interestingly, I just figured out why I could not replicate this bug.  Both 
wp-config.php and my wp-content are moved up one directory, so relative to each 
other they were unchanged.  Oops.

So... Issue 19 was entirely valid.  It just didn't happen on my particular 
install.

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