fdask
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Â showing up after upgrade to 2.8.1Hey… I encountered a similar issue.
Posted my fix, and some reasons why this might have happened to you on my blog: http://blog.ffff.ca/2009/02/27/funny-characters-showing-up-in-wordpress-posts/
Forum: Plugins
In reply to: [Plugin: eShop] eShop plugin not workingIn that block I pointed out, in cart-functions.php, it tries to do a wp_mkdir_p($upload_dir). $upload_dir is coming from $dirs[‘basedir’], but the only thing the $dirs array contains is the below:
Array ( [error] => Unable to create directory /usr/local/apache22/htdocs/wordpress/wp-content/uploads/2009/02. Is its parent directory writable by the server? )
This was a brand new WordPress installation, and the uploads directory was not yet created.
Forum: Plugins
In reply to: [Plugin: eShop] eShop plugin not workingJust did a binary search in the cart-functions.php trying to narrow down what was causing the error.
I’ve tracked it down to the line around 960 that starts with
if (!function_exists(‘eshop_files_directory’)) {If I comment out this if block, the page renders again.
I’ll look into it further and let you know what I find.
Forum: Plugins
In reply to: [Plugin: eShop] eShop plugin not workingHey,
I’m experiencing a similar issue here.
On our initial server running FreeBSD, WordPress 2.7, we had eshop up and running fine, no problems.
Just recently we migrated to a new host, a VPS, so the memory constraints were a little tighter.
Trying the old database and code I was getting a blank front page. Disabling plugins one by one I discovered eshop was the culprit. Enabling it results in a blank front page.
Trying with a fresh WordPress 2.7.1 install, with the latest eshop release (3.0), I get the same thing.
Nothing in PHP error logs, just messages like this in my apache error log:
kernel: pid 1632 (httpd), uid 80: exited on signal 4
It seems trying to access the site with eshop enabled, the apache child handling the request crashes. The admin area still works fine.
We tested on a seperate server with more memory, to rule that out. Same issue occurred.
Another note, once enabling eshop, it says we have to deactivate then reactivate it to complete the setup. On trying to reactivate it, the plugins.php file pops up as a download, instead of executing.
What I’m thinking is maybe I’ve missed some PHP module that eshop needs in order to function.
All I have it compiled with at this point is mysql and libxml2. Everything else is stock.
Any suggestions for what to try?