Error in logs

  • matthewbaker1979

    (@matthewbaker1979)


    9 years, 7 months ago

    Hi,

    Indeed, this is a nice plugin.

    I will not discuss about functionnal issue but technical one.
    I found errors in nginx logs which concern Rencontre plugin.

    Here comes an extract :

    2016/10/18 18:28:44 [error] 4351#0: *107403 FastCGI sent in stderr: “PHP message: PHP Fatal error: Class ‘RencontreWidget’ not found in /var/www/mysite.com/wp-content/plugins/rencontre/inc/rencontre_filter.php on line 42” while reading response header from upstream, client: a.b.c.d, server: http://www.mysite.com, request: “GET /membres.html?rencidfm=r0&rencoo=9B109iIDmcKawh3beuuKy4%2F3gUndFVxtzkeZ39CRM5k%3D&rencii=jEtZT2xdZq6zObbqEBSv3Q%3D%3D HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php5-fpm.sock:”, host: “www.mysite.com”

    It occurs many times. Sometimes, there is nothing for 90min and sometimes the errors occurs twice in 10min.

    Do you have an idea ?

    Feel free to ask for more details if ya want.

    Matthew

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jacques Malgrange

    (@sojahu)

    9 years, 7 months ago

    Hi Matthew,

    Thanks for your report.
    This part is launched too early. I will add an “init” condition to fix that.

    Regards,

    Thread Starter matthewbaker1979

    (@matthewbaker1979)

    9 years, 7 months ago

    Thanks for your quick reply.

    If you want I can beta test this quick fix for you.

    Regards.

    Plugin Author Jacques Malgrange

    (@sojahu)

    9 years, 7 months ago

    Yes, thanks.

    Move the code bellow from /inc/rencontre_filter.php line 30 :

    add_shortcode('rencontre', 'f_shortcode_rencontre');

    to line 74, at the top of the function f_cron() :

    
// CRON
add_action('init', 'f_cron');
function f_cron()
	{
	// Filters after "init"
	add_shortcode('rencontre', 'f_shortcode_rencontre');
	if(function_exists('wpGeonames')) add_action('wp_ajax_city', 'rencontreCity');

    I think it can be that.

    Regards

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Error in logs’ is closed to new replies.