Error in 1 click updater
Developer Preview
Its complaining about a config options “email_newline”. I got an error when it was in my config.php file and then when I removed it I got this error:
https://www.dropbox.com/s/ay6ku9wkoewldk4/Screenshot 2017-10-28 08.41.57.png?dl=0
I’m not sure how you’d be missing that config item in v4, nor what error might occur when it’s overridden in your config file. Was this installation on a previous version of ExpressionEngine? What was the error when it was in your config?
This was a 3.x upgrade. I am getting the same error message even if key isn’t in the config.php file. I’ve tried the upgrade with it there, without it, and commented out. Same result every time.
What version of v3 was it on before you upgraded? Are you using the Developer Preview license in the install?
This was a clean EE 4 set of files where I grabbed the database and config file from my EE 3 install to do an upgrade.
I was on 3.5.11. Forgot to mention.
Even curiouser. That preference was added in 3.5.0, and 3.5.3 fixed a bug that could lead those same PHP warnings:
Fixed a bug in the 3.5.0 update routine where the new email_newline and email_smtp_crypto settings might not be copied to all sites in the Site Manager, resulting in PHP warnings until the Email settings are saved in each Site.
Are you using the Site Manager on this install? Are you able to replicate the issue on another database?
I have 2 ee4 environments setup, one on each computer, and I get the same error on both. However, both are “upgrades” from ee3, which is using the database from my demo site that does not have MSM installed.
Ok, using that bit of info you provided I went into the CP to the “Outgoing Email” settings page, didn’t change anything, and just clicked Save. Then tried the auto-updater again and it worked fine.
Worth noting that my demo site db has been around since before 3.5… I just kept upgrading and updating the base db file used to generate the site.
Bizarre that you were not getting that error on v3 though, since it does look like your db may have been affected by that bug, and never repaired. Well, if you encounter it again, please let us know, thanks for the followup!
I guess I wasn’t getting the error before b/c I added $config[‘email_newline’] = ‘\r\n’; to my config.php file. I’m assuming the 4.0 updater didn’t take that value into account and only looked at the database.