white page after last update

Latest update seems to wipe out the wp-config.php file completely, glad I had a backup of it! Looks like .htaccess is also edited. So I just restored both files and the site is working again. iThemes, what’s going on with that update??

Thank you very much MDC. what’s going on with that update ?
I just restored both files and the site is working again

You’re welcome. I have no idea. The other day, the Code Snippets plugin update busted my site too. Seems to be a bad week for plugin updates.

Hi guys, I don’t know if it is of any helpto your issue, but what happened to my wp-config.php is just this:
after its own ithemes settings and comments, the new updated version 6.9.0 just closed automatically the ?> php tag, leaving all the WordPress settings lingering just as plain text comments.
I removed the ?> closing tag and all went normal.
Though since I didn’t like ithemes settings on top of my wp-config.php I moved them at the bottom, so if it happens is just closing the php markup at the end without causing any problem.

<?php
// BEGIN iThemes Security - Do not modify or remove this line
// iThemes Security Config Details: 2
define( 'FORCE_SSL_ADMIN', true ); // Force SSL for Dashboard - Security > Settings > Secure Socket Layers (SSL) > SSL for Dashboard
define( 'DISALLOW_FILE_EDIT', true ); // Disable File Editor - Security > Settings > WordPress Tweaks > File Editor
// END iThemes Security - Do not modify or remove this line?>
....
the rest of my code was below this point

note the // END iThemes Security – Do not modify or remove this line?>

Hope this helps.
G.

• This reply was modified 6 years, 9 months ago by Giorgio25b. Reason: code typo
• This reply was modified 6 years, 9 months ago by Giorgio25b. Reason: code typo
• This reply was modified 6 years, 9 months ago by Giorgio25b.

Hi (@giorgio25b) thanks for posting your solution. My version seems to work OK on my end, what is interesting is I don’t have an opening <?php or a closing ?> on my .htaccess file

@lechon yes, but .htaccess is where most of the ithemes settings are stored, so my wild guess would be on some sort of sanitizing function that is stepping in after ithemes settings, regardless which file they are in.
Would be interesting to compare your .htaccess before and after update. In my case was so simple and straight forward that it took me a minute to fix it, though for a minute my dn name/user/password were visible as plain text on my homepage. I had to create and clone a new db and user and I changed passwords, table prefix and salts after.

@giorgio25b thanks for that explanation. I did compared the file with the one before the update and there was no change from one version to the other. I have boomarked your solution on my end just in case I run into this situation.