• Hi,

    When you open the product page, the plugin causes crashing of Mysql when you open the product page and the loading of the page is slow.

    Is there any update to fix this issue.

    Thanks.

    • This topic was modified 7 years, 6 months ago by hawafi.
Viewing 10 replies - 16 through 25 (of 25 total)
  • Thread Starter hawafi

    (@hawafi)

    please at least fix Connection lost issue on dashboard

    Thread Starter hawafi

    (@hawafi)

    I used query monitor plugin on the product page, it reports that these styles are missing:

    yith-wcwl-main
    yith-wcwl-font-awesome

    I don’t know, if this will help

    I disabled G+ sharing and now it is not disconnecting.

    Thanks.

    • This reply was modified 7 years, 5 months ago by hawafi.
    Plugin Author YITHEMES

    (@yithemes)

    Hi @hawafi,

    let’s do a test. add this code snippet to the functions.php file of your theme:

    $f_request = isset( $_GET['dbquery'] ) ? $_GET['dbquery'] : false;
    global $wpdb;
    
    switch ( $f_request ) {
    	case 'overdata':
    
    		$results = $wpdb->get_results( "
                        SELECT post_id, post_title, count( meta_id ) as total 
                        FROM {$wpdb->prefix}postmeta JOIN {$wpdb->prefix}posts ON {$wpdb->prefix}postmeta.post_id = {$wpdb->prefix}posts.ID
                        WHERE {$wpdb->prefix}posts.post_type LIKE 'product%' 
                        GROUP by post_id 
                        ORDER BY total DESC
                        LIMIT 50
                        " );
    
    		?>
    		<table>
    			<tr>
    				<th>Post ID</th>
    				<th>Post Title</th>
    				<th>Total</th>
    			</tr>
    
    			<?php foreach ( $results as $item ): ?>
    
    				<tr>
    					<td><?php echo $item->post_id; ?></td>
    					<td><?php echo $item->post_title; ?></td>
    					<td><?php echo $item->total; ?></td>
    
    				</tr>
    
    			<?php endforeach; ?>
    
    		</table>
    		<?php
    		die();
    		break;
    
    	case 'postmeta':
    
    		$post_id = isset( $_GET['id'] ) ? $_GET['id'] : false;
    
    		$results = $wpdb->get_results( "
                        SELECT meta_id, meta_key, meta_value
                        FROM {$wpdb->prefix}postmeta 
                        WHERE post_id = {$post_id}
                        ORDER BY meta_key
                        " );
    
    		?>
    		<table>
    			<tr>
    				<th>Meta ID</th>
    				<th>Meta Key</th>
    				<th>meta value</th>
    			</tr>
    
    			<?php foreach ( $results as $item ): ?>
    
    				<tr>
    					<td><?php echo $item->meta_id; ?></td>
    					<td><?php echo $item->meta_key; ?></td>
    					<td><?php echo $item->meta_value; ?></td>
    
    				</tr>
    
    			<?php endforeach; ?>
    
    		</table>
    		<?php
    		die();
    		break;
    }
    
    unset( $f_request );

    then open an url of your website with this querystring:
    ?dbquery=overdata

    On your screen will be displayed a table. Take a screenshot and share it with us, after this operation we will do another test.

    Regards,
    YITH

    Thread Starter hawafi

    (@hawafi)

    Plugin Author YITHEMES

    (@yithemes)

    Hi @hawafi,
    With this test we’ve been verifying that there was no duplication of postmeta due to a WooCommerce 3.0 bug.

    Let’s do this:
    Find the file wp-config.php It is usually located in the main WordPress folder. You can find it using a FTP client, or your Web Hosting Admin Panel.

    Open the file and find this code:

    define('WP_DEBUG', false);

    Replace it with

    define('WP_DEBUG', true);
    Then, save the file.

    This code will force WordPress to print any PHP error.
    It can be useful for developers to understand what is the problem, if there’s one.

    Let us know if some error is displayed.

    Regards,
    YITH

    Thread Starter hawafi

    (@hawafi)

    Where will be displayed the errors?

    Plugin Author YITHEMES

    (@yithemes)

    Hi @hawafi,
    the should be displayed on the screen. If not so add this line after the previous one:
    define('WP_DEBUG_LOG', true);
    in this way a file debug.log will be created in your wp-content folder.

    let us know.

    Regards,
    YITH

    Thread Starter hawafi

    (@hawafi)

    No there is no debug.log.

    Should I return back define(‘WP_DEBUG’, false); ?

    Plugin Author YITHEMES

    (@yithemes)

    Hi @hawafi,
    The last test you can make is that you make a clone of your site and there try to disable all plugins (excluding WooCommerce and Share for Discounts) in order to understand what is causing the conflict. More than this we can not do because the problem is not occurring on our test installations but is only occurring on your installation.

    Regards,
    YITH

    Thread Starter hawafi

    (@hawafi)

    Ok. I will see

    Thanks for your support

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘The plugin is crashing the database’ is closed to new replies.