Support » Plugin: Frontend Publishing » Front end posts 502 error

  • The front end posts page gives me a 502 error on Nginx 1.10.1 and PHP 5.6.23. Browser php-fpm5.6 process is using almost 50% of server CPU (only for one vistor) and continues to do so until error 502 Bad Gateway is returned. Looking at strace it tries to do quite big number of database queries – in about 20 seconds 1313 SELECTs. Possibly there’s a bug in the plugin.. it worked on an older version of Nginx and PHP.

    https://wordpress.org/plugins/front-end-publishing/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author WP Gurus

    (@khaxan)

    The plugin does no database queries at all. It calls the wordpress function get_option a few times but WP caches those calls so it should not be a problem.

    There must be an issue with your server configuration or another plugin because I have never encountered the problem and I have tested it on some very low-power servers.

    It turns out your plugin conflicts with Awesome Support plugin https://wordpress.org/plugins/awesome-support/
    Hope you guys can look into it.

    Hi, your plugin still conflicts with Awesome Support https://wordpress.org/plugins/awesome-support/
    Would you be able to solve this? We’d love to use your plugin but as long as it conflicts all we get is a 502 error.

    Awesome Support looked into this matter and can provide you the following feedback:


    I just installed the version of front-end-publishing that is in the wordpress.org directory. It generates an out of memory message no matter how much memory I throw at it. I think its trying to do something weird with our tickets. Their pro version apparently allows you to handle custom post types so if this version has that capability built-in (but hidden( then it might just be trying to do something weird with our tickets and replies and running out of memory in the process. I’ve given it as much as 2 gigs of memory and it just uses it all up until it generates a php fatal error.

    We’re not going to be able to drill into this – I think you should turn this over to the FEP folks – no way should it’s page be running out of memory regardless of which CPT it’s trying to handle.

    The php log file only generates one line with this error: /wp-includes/class.wp-scripts.php, line 457. (That line in the file is core to WP and seems to be related to translations – maybe that will give them some idea as to what is going on.)

    Please look into this. Sounds like a bug in your plugin.

    Plugin Author WP Gurus

    (@khaxan)

    Hi. I have released a new version with what I think should resolve the issue. Let me know if it doesn’t. Thanks.

    Hi @khaxan, thank you for looking into this. Unfortunately the 502 error remains –
    I get the following error after activating
    2016/09/25 04:45:03 [error] 30949#30949: *383696 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: <del datetime="2016-09-25T10:22:40+00:00">123.45.67.8</del>, server: www.mysite.com, request: "GET /guides-dashboard/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:8080", host: "mysite.com", referrer: "https://mysite.com/wp-login.php?redirect_to=https%3A%2F%2Fmysite.com%2Fguides-dashboard%2F&reauth=1"

    these are the last few errors from that log

    [25-Sep-2016 05:09:45 UTC] PHP Warning:  strip_tags() expects parameter 1 to be string, object given in /www/vhosts/mysite.com/httpdocs/wp-includes/formatting.php on line 1949
    [25-Sep-2016 05:09:45 UTC] PHP Warning:  preg_match() expects parameter 2 to be string, object given in /www/vhosts/mysite.com/httpdocs/wp-includes/formatting.php on line 1500
    [25-Sep-2016 05:09:45 UTC] PHP Warning:  strip_tags() expects parameter 1 to be string, object given in /www/vhosts/mysite.com/httpdocs/wp-includes/formatting.php on line 1949
    • This reply was modified 3 years, 1 month ago by belleair.
    • This reply was modified 3 years, 1 month ago by belleair.
    Plugin Author WP Gurus

    (@khaxan)

    Hi. This error doesn’t seem relevant. Do you see it every time you activate the plugin?

    Have you checked the form page? Is the 502 error still there?

    Hi. Yes, both plugins (Front end and Awesome Support) are active. The front end pages are then the only pages showing a 502 error. Awesome support tickets display OK.
    The front end pages load ok (no 502 error) with Awesome Support deactivated.

    Also when both Front end and Awesome Support are active, it is impossible to save any changes to posts/pages. It gives a ‘leave/stay’ pop-up upon hitting save, and save keeps loading.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Front end posts 502 error’ is closed to new replies.