Timeline for Multiple wp-config.php files in one home directory
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 16, 2021 at 16:46 | answer | added | John Ching | timeline score: 1 | |
Feb 13, 2012 at 21:57 | answer | added | fuxia♦ | timeline score: 1 | |
Feb 13, 2012 at 21:41 | answer | added | Sterling Hamilton | timeline score: 0 | |
Feb 13, 2012 at 21:41 | comment | added | EAMann | My apologies. Was reading too quickly before lunch and misinterpreted that Codex note. See my answer below. | |
Feb 13, 2012 at 21:41 | answer | added | EAMann | timeline score: 0 | |
Feb 13, 2012 at 21:25 | comment | added | markratledge | Read what I wrote and the WP docs: "up one directory level..." That's one level above /wp-includes/. That's what works right now. If I moved wp-config.php into wp-admin or another folder, it wouldn't work. | |
Feb 13, 2012 at 21:22 | history | edited | markratledge | CC BY-SA 3.0 |
details
|
Feb 13, 2012 at 19:02 | comment | added | EAMann |
Read that same note very carefully ... it talks about moving wp-config.php to the same level as /wp-includes ... not to the level of /home below /public_html . You're moving things in the opposite direction.
|
|
Feb 13, 2012 at 18:28 | comment | added | markratledge | See codex.wordpress.org/Hardening_WordPress#Securing_wp-config.php | |
Feb 13, 2012 at 18:28 | history | edited | markratledge | CC BY-SA 3.0 |
added 159 characters in body
|
Feb 13, 2012 at 18:15 | comment | added | EAMann |
What do you mean "for security"? No one can read your wp-config.php file through the browser anyway ...
|
|
Feb 13, 2012 at 18:07 | history | asked | markratledge | CC BY-SA 3.0 |