Jigoshop Official MailChimp Integration plugin causes complete crash on

  • Resolved iahipinternet

    (@iahipinternet)


    7 years, 7 months ago

    Since upgrading to latest version of Jigoshop, the plugin “Jigoshop Official MailChimp Integration” Version 3.1.2 caused the entire wordpress site to crash – completely. Because I had done a group update of several plugins, it took me a while to figure out which plugin had caused this fatal error by renaming the plugins one by one by FTP. I’d also updated the WP mailchimp plugin to Version 1.5.2 and Jigoshop to Version 1.18.

    Could anyone let us know when an upgrade for this plugin could be made available? I know Mailchimp are needing API keys now, is this the problem?

    Best wishes

    dermod

    https://wordpress.org/plugins/jigoshop/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Jigoshop Support – Marcin

    (@azrielnefezen)

    7 years, 7 months ago

    While inspecting the code I found nothing suspicious.
    Testing the plugin on our test servers also didn’t result in anything suspicious.
    Could you turn on the plugin and set WP_DEBUG (in the wp-config.php file) to true and post the error message?

    Thread Starter iahipinternet

    (@iahipinternet)

    7 years, 7 months ago

    Thanks Marcin,

    Here you go:

    I activated the plugin and the debug messages are as below. The website crashed completely.
    In Chrome, I get:
    “The iahip.org page isn’t working
    iahip.org is currently unable to handle this request.
    HTTP ERROR 500″

    here are the debug messages:

    Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: Undefined variable: text_domain in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-content/plugins/wp-category-posts-list/wp-category-post-list.php on line 56 Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php:3995) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-content/plugins/wp-custom-admin-bar/custom-admin-bar-functions.php on line 8 Notice: Undefined index: widgets in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-content/plugins/cforms/cforms.php on line 1456 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: register_sidebar_widget is deprecated since version 2.8.0! Use wp_register_sidebar_widget() instead. in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3706 Notice: register_widget_control is deprecated since version 2.8.0! Use wp_register_widget_control() instead. in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3706 Notice: register_taxonomy was called incorrectly. Taxonomy names must be between 1 and 32 characters in length. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: register_taxonomy was called incorrectly. Taxonomy names must be between 1 and 32 characters in length. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: register_taxonomy was called incorrectly. Taxonomy names must be between 1 and 32 characters in length. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3995 Notice: The called constructor method for WP_Widget in html_javascript_adder_widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3766 Notice: The called constructor method for WP_Widget in WP_Category_Post_List_itg is deprecated since version 4.3.0! Use
    __construct()
    instead. in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3766 Notice: The called constructor method for WP_Widget in sb_cl_pages_widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3766 Notice: has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php on line 3890 Warning: Cannot modify header information – headers already sent by (output started at /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php:3995) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/pluggable.php on line 1174 Warning: Cannot modify header information – headers already sent by (output started at /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php:3995) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/pluggable.php on line 1174

    Best wishes

    Dermod

    Plugin Author Jigoshop Support – Marcin

    (@azrielnefezen)

    7 years, 7 months ago

    Basing on the error messages you sent, I’d recommend turning off:
    – wp-category-posts-list
    – wp-custom-admin-bar
    – cforms
    Since I cannot see anything MailChimp related in these.

    Thread Starter iahipinternet

    (@iahipinternet)

    7 years, 7 months ago

    Hi

    I disabled those plugins, and debugged, and got this related to jigoshop:

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php:3995) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-content/plugins/jigoshop/classes/jigoshop_session.class.php on line 22 Notice: The called constructor method for WP_Widget in html_javascript_adder_widget is deprecated since version 4.3.0! Use
    __construct()
    instead.

    I activated the Jigoshop Official MailChimp Integration plugin with the above plugins deactivated, and again the entire site crashed. There were two new warnings in the debug screen:

    Warning: Cannot modify header information – headers already sent by (output started at /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php:3995) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/pluggable.php on line 1174 Warning: Cannot modify header information – headers already sent by (output started at /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/functions.php:3995) in /usr/local/pem/vhosts/361440/webspace/httpdocs/wp-includes/pluggable.php on line 1174

    Any clues? is there another way to find out what causes such a spectacular crash? It’s been a while since I’ve seen that.

    Thanks

    Dermod

    Plugin Author Jigoshop Support – Marcin

    (@azrielnefezen)

    7 years, 7 months ago

    Check line 3995 in your wp-includes/functions.php – what is it?

    Thread Starter iahipinternet

    (@iahipinternet)

    7 years, 7 months ago

    /**
	 * Filters whether to trigger an error for _doing_it_wrong() calls.
	 *
	 * @since 3.1.0
	 *
	 * @param bool $trigger Whether to trigger the error for _doing_it_wrong() calls. Default true.
	 */
	if ( WP_DEBUG && apply_filters( 'doing_it_wrong_trigger_error', true ) ) {
		if ( function_exists( '__' ) ) {
			$version = is_null( $version ) ? '' : sprintf( __( '(This message was added in version %s.)' ), $version );
			/* translators: %s: Codex URL */
			$message .= ' ' . sprintf( __( 'Please see <a href="%s">Debugging in WordPress</a> for more information.' ),
				__( 'https://codex.wordpress.org/Debugging_in_WordPress' )
			);
			trigger_error( sprintf( __( '%1$s was called <strong>incorrectly</strong>. %2$s %3$s' ), $function, $message, $version ) );
		} else {
			$version = is_null( $version ) ? '' : sprintf( '(This message was added in version %s.)', $version );
			$message .= sprintf( ' Please see <a href="%s">Debugging in WordPress</a> for more information.',
				'https://codex.wordpress.org/Debugging_in_WordPress'
			);
			trigger_error( sprintf( '%1$s was called <strong>incorrectly</strong>. %2$s %3$s', $function, $message, $version ) );
		}
	}
}

    Line 3995 is the line beginning trigger_error

    Thanks for your attention to this Marcin!

    Plugin Author Jigoshop Support – Marcin

    (@azrielnefezen)

    7 years, 7 months ago

    This is strange, since it looks like a regular WordPress file. The error states that it has “echoed” something. Could you turn off WP_DEBUG and check if that changes things?

    Thread Starter iahipinternet

    (@iahipinternet)

    7 years, 7 months ago

    Hi Marcin,

    It’s very weird I agree.

    When I activate the plugin I get a 500 error across the whole installation. With or without debug on.

    It’s rather weird that debug is so unhelpful.

    Best

    Dermod

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Jigoshop Official MailChimp Integration plugin causes complete crash on’ is closed to new replies.