Closed andysprout closed 10 years ago
To be honest I'm not a wordpress expert, so I don't fully understand the implications of the WP_USE_EXT_MYSQL setting, I just read the source of version 4.0 and it looked like this would fix the errors I was getting when running locally with MAMP, then after reading https://discussion.heroku.com/t/solved-php-legacy-buildpack/580/5 it seemed related, so I gave it a go and it seems to have fixed #89
This didn't fix the problem for #89.
Did f96d36a9072605472ef162ae6c9c837152386696 fix or cause issues with running WordPress locally?
without f96d36a I was not able to run locally with MAMP, I tested this fix a few hours ago and was able to deploy to a fresh heroku app, but I only tested without the legacy build pack.
This does appear to fix deploy on the default PHP heroku buildpack. It prevents the use of mysqli
commands with a later version of PHP.
Potentially fixes issue #89