Hi Thomas,
Can you please post a link to your site’s front-end which is displaying this text so we can take a quick look?
Thread Starter
Thomas
(@enungman)
I deleted the plugin and had to manually remove the rule from wp-config.php so the text is gone now, but it seemed to be some kind of error when the rule was written and (not) erased in the .php-file
I found another plugin though so the ticket is resolved from my side for now. Might try this plugin again on another site later.
Ok no problems.
I’ve never seen this happen before so it would have been good to know what was causing it on your site.
Another thing you could’ve done instead of manually editing the wp-config.php file is to have restored from your backup copy, ie, the plugin automatically creates one in your root folder when you enable that feature.
I will now set this thread to resolved.
thanks
Same thing happened to me today. Fresh update to WP 3.6 and brand new DL of “All in one WP Security…”
Below is a snippet from the wp-config file. You’ll see that the plugin is writing the disable file edits to the END of the wp-config file…. Outside the PHP closing tag:
// Change this to localize WordPress. A corresponding MO file for the
// chosen language must be installed to wp-content/languages.
// For example, install de.mo to wp-content/languages and set WPLANG to ‘de’
// to enable German language support.
define (‘WPLANG’, ”);
/* That’s all, stop editing! Happy blogging. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
require_once(ABSPATH . ‘wp-settings.php’);
?>//Disable File Edits
define(‘DISALLOW_FILE_EDIT’, false);
Ok thanks for the info.
I can see the cause now.
In PHP 5.x there is no need for an ending “?>” tag.
However, earlier versions of WP which coincided with PHP 4.x used to have the ending PHP “?>” tag because it was mandatory.
So when people with the older versions of WP upgrade to the current version of WP, they effectively keep their old wp-config.php file which has the “?>” tag, but people who do a fresh install of the current WP will not have that tag.
Our code currently assumes that everyone is running PHP5 or newer.
We will fix our code to cater for both cases.
Yep! Knew that to be the case with WP sites that are several years old and when I saw that the the disallow was just appended to the config file.
Thanks for the fast reply!
