WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: eShop] eShop plugin not working (26 posts)

  1. Peter Nemcok
    Member
    Posted 5 years ago #

    Page http://www.jericha.sk is not working after a new wordpress 2.7 installation and activating eShop plugin. On the other hosting it is working. Are there any special requirements on hosting for WordPress with eShop plugin?

  2. elfin
    Moderator
    Posted 5 years ago #

    if wordpress works, then eshop shouldn't have a problem.

    Try re-uploading both, just in case a file didn't transfer correctly.

  3. Peter Nemcok
    Member
    Posted 5 years ago #

    Tried this twice. I have tried it on another server (hosting) without problems. Any clue?

  4. elfin
    Moderator
    Posted 5 years ago #

    anything showing up in the servers error log?

    I have no idea as to why it would work on one but not the other.

  5. alfeinar
    Member
    Posted 5 years ago #

    I've got the same problem. Just installed WordPress without a hitch and then added eShop, and suddenly all WP-pages goes blank. As I just reinstalled Ubuntu on my server I suppose I may have forgotten some settings, but I can't seem to figure out which. Only clue is in the Apache error-log:

    [notice] child pid 11140 exit signal Segmentation fault (11)

  6. elfin
    Moderator
    Posted 5 years ago #

    eShop is running successfully in various locations now, so I can only assume that this problem is caused by the web hosting. I don't know enough about that side to know whether your error affects anything or not.

    Sorry :(

  7. alfeinar
    Member
    Posted 5 years ago #

    Could this be due to the fact that I'm running PHP5 as opposed to PHP4?

  8. zackisaiah
    Member
    Posted 5 years ago #

    I've had the same problem. On my local wordpress installation (XAMPP), it works. On a dreamhost.com site, it works. When I run it on my client's corporate server, the entire site goes blank as soon as I activate the eShop plugin.

    I'm not a server genius, so I'm not entirely sure what to look for, but one of the tech guys said "something is dying with an 'Illegal Instruction' error when you try to view the page, which can be caused by running a Linux binary instead of a FreeBSD binary."

  9. elfin
    Moderator
    Posted 5 years ago #

    My test server runs php5.2.8 - I develop locally with php4 - so I doubt that's the problem.

    Is anything showing up in the error logs that can give me a clue as to where to look?

    I've done some searching on the error:
    child pid exit signal Segmentation fault
    and eventually found this php bugs - could that be the issue? Which version of php5 is being run?

  10. alfeinar
    Member
    Posted 5 years ago #

    Sorry for the late reply.

    I run PHP 5.2.6 at the momement, but I have tried running it with both 5.2.4 and 5.2.8 without any difference as such. Something causes a segfault when accessing the WordPress front page after activating the eShop plugin. The admin section works as normal though.

    In the plugin manager a notice on the top says "eShop 3.0.0 is installed, however you still need to deactivate and re-activate the plugin." However, doing as instructed just causes the notice to reappear.

  11. elfin
    Moderator
    Posted 5 years ago #

    At the moment I have no idea why this happening.

    Is there anything else in the error logs that might help?

  12. alfeinar
    Member
    Posted 5 years ago #

    Nope. The logs are empty apart from the segfault (which causes Apache's child pid to crash).

    I'll give lighttpd a try and see what happens. But my guess is that there is too much recursion somewhere or a problem with an extension that I am not able to pin down at the moment.

  13. elfin
    Moderator
    Posted 5 years ago #

    I've been doing some bug hunting, and although I've found a few I don't think any of them would affect things in the way reported. However, feel free to test things and download the development version.

  14. alfeinar
    Member
    Posted 5 years ago #

    Thanks but that didn't work either. I've now tried running lighttpd instead of Apache but it's basically the same. The front-end now returns a 500 Internal Server Error, and in the error logs I find only this:

    2009-02-10 12:37:56: (mod_fastcgi.c.2489) unexpected end-of-file (perhaps the fastcgi process died): pid: 13096 socket: unix:/tmp/php.socket-1
    2009-02-10 12:37:56: (mod_fastcgi.c.3299) response not received, request sent: 1115 on socket: unix:/tmp/php.socket-1 for /wordpress/index.php , closing connection

    I've tried eliminating in which file the problem might be, and the 500-errors stops (and thus the segfaults) when removing the cart-funtions.php out of the equation.

  15. elfin
    Moderator
    Posted 5 years ago #

    Still doesn't help me track it down unfortunately.

    Are you able to open cart-functions.php and resave it as unix/utf8 as opposed to PC/ansi in case that helps at all (wild guess).

    Also, are you able to cut down cart-functions.php a bit at a time to try and find the problem? (a lot of work...)

  16. alfeinar
    Member
    Posted 5 years ago #

    I'll try to cut it down further, but I don't have the time at the moment As you say it is a lot of work.

  17. elfin
    Moderator
    Posted 5 years ago #

    well I'd be prepared to do it myself - but I'd need access to WordPress, FTP and possibly phpmyadmin as well...

  18. fdask
    Member
    Posted 5 years ago #

    Hey,

    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?

  19. elfin
    Moderator
    Posted 5 years ago #

    Another note, once enabling eshop, it says we have to deactivate then reactivate it to complete the setup.

    I'll look into that one for the next release - should be easy to solve.

    Well the comments above seem to suggest a possible problem in cart-functions.php - so that would need testing by removing things until the culprit is found. As I can't replicate this problem anywhere I am unable to help further without access.

  20. fdask
    Member
    Posted 5 years ago #

    Just 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.

  21. fdask
    Member
    Posted 5 years ago #

    In 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.

  22. elfin
    Moderator
    Posted 5 years ago #

    poot - I'd hoped never to see that error ever again.

    I'll try and read in a check for the existence of the relevant directories. If you manually create:
    wp-content/eshop_downloads and wp-content/uploads/eshop_files
    and then copy the files from plugins/eshop/downloads and plugins/eshop/files into those directories does the error still appear?

  23. tallbiker66
    Member
    Posted 5 years ago #

    Rich,

    I just gave your plugin a shot and ran into the same problem ->

    [Fri May 01 16:07:46 2009] [notice] child pid 9773 exit signal Segmentation fault (11)

    My setup:
    Server version: Apache/2.2.11 (Unix)
    Server built: Apr 28 2009 08:08:59

    PHP 5.2.9 (cli) (built: Apr 28 2009 08:25:38)

    WordPress is 2.7.1

    The segfault happens after re-activating the plugin. I have been playing around with different PHP 5 versions (5.2.8 and 5.3 RC1). The segfault does occur no matter which version is in use.

    HELP! ;-)

    tallbiker66

  24. elfin
    Moderator
    Posted 5 years ago #

    wish I could, but as I said in a previous reply without access to a server (WP and FTP) I can't. it isn't an error I'm familiar with at all and would need to do a lot of testing to try and find out what is causing it.

  25. tallbiker66
    Member
    Posted 5 years ago #

    You probably don't have time to set up a WordPress 2.7.1, Apache 2.2.11, PHP 5.2.9 installation to reproduce the issue, right? That's unfortunate, but I won't be able to offer you access to the server.

    Anyway, I hope you'll find a solution soon.

    Thanks.
    tallbiker66

  26. elfin
    Moderator
    Posted 5 years ago #

    I don't play with servers :)

    So no i wouldn't be able to set anything up to match, sorry.

Topic Closed

This topic has been closed to new replies.

About this Topic