Closed tjoozey closed 10 years ago
I have the same issue.
Me too
This seems to be a problem with the PHP legacy build pack. Launching Apache is throwing an error on the libssl version. Its likely that a later version of libssl is installed on the Heroku instance.
httpd: Syntax error on line 57 of /app/apache/conf/httpd.conf: Cannot load /app/apache/modules/libphp5.so into server: libssl.so.0.9.8: cannot open shared object file: No such file or directory
I just did a clean install using the same fix I did to get this working on locally using MAMP, I removed the if(test_localhosts())
test on line 47 of wp-content/db.config
and it also seemed to work without using the legacy build pack.
Okay, so I have clean installs working now.
I believe the legacy PHP buildpack is currently having issues with libssl so I have the project now configured on Heroku's latest default PHP buildpack. This is ultimately what it should be using anyway.
A small change was needed in pg4wp in order for it to work correctly. WP detects the PHP version and will decide which database driver to use. If the version is greater than or equal to 5.5 then it will use mysqli
. Pg4wp only replaces commands for mysql_*
. I removed the version check so that it will now use mysql_*
and properly replace it with postgres processed queries.
Please test out this fix in the branch: https://github.com/mhoofman/wordpress-heroku/tree/fix_pg4wp
Soon I would like to completely remove pg4wp and switch the project to use mysql since there are now good mysql addons available.
Should be resolved with PR #90.
+1 for sql. this fix works tho! thx!
I'm receiving an application error on new installs following the read me.MD.
I've been using this repository for months and since the new db update fix you pushed I haven't been able to push new word press installs for my domains.
If you could look into it that would be great