Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Hi Leonardo,

    This is the new site:
    https://locateandfilter.com/

    • This reply was modified 1 year, 7 months ago by ronald.kubo. Reason: open link in new tab

    I had the same error, this is because this feature requires the Google Maps JavaScript API – so if you do not use this API this particular feature does not work. If you just fill in the coordinates and save the post the marker will be added to the map anyway.

    Hi,

    If you want to continue using this plugin with 3D secure, it seems like Cardinal Commerce (PayPals official parnter) supplies a plugin to integrate 3D secure into WooCommerce. You can read about it here:
    https://www.paypal.com/uk/webapps/mpp/psd2

    It has a link to register with Cardinal Commerce near the bottom of the page.
    Ronald

    Hi,

    If you want to continue using this plugin with 3D secure, it seems like Cardinal Commerce (PayPals official parnter) supplies a plugin to integrate 3D secure into WooCommerce. You can read about it here:
    https://www.paypal.com/uk/webapps/mpp/psd2

    It has a link to register with Cardinal Commerce near the bottom of the page.
    Ronald

    Hi everybody,

    If you want to continue using this plugin with 3D secure, it seems like Cardinal Commerce (PayPals official parnter) supplies a plugin to integrate 3D secure into WooCommerce. You can read about it here:
    https://www.paypal.com/uk/webapps/mpp/psd2

    It has a link to register with Cardinal Commerce near the bottom of the page.
    Ronald

    Hi @akamaro

    I ran into the same problem, and spent quite some time delving into the issue, and I came up with a workaround. I’m not familiar with how to override plugin functions in a child-theme’s funtions.php, so I edited the plugin file directly. For me, the following works:

    Find and open this file: …/wp-content/plugins/woo-local-pickup/front/class-woo-local-pickup-location.php

    On line 48 you’ll see this code:

    
    add_filter('woocommerce_email_order_meta_keys', array( $this, 'woo_update_order_email' ) );
    

    replace it with:

    
    add_action('woocommerce_email_after_order_table', array( $this, 'woo_pickup_detail_front') );
    

    The original function it calls outputs the id# of the location as you have have noticed. This same plugin-file also has a function that outputs the pickup location on the order confirmation page, where it loads nicely. So what I did is just replace the above function with the one written for the order confirmation page. I also replaced the hook woocommerce_email_order_meta_keys with woocommerce_email_after_order_table because the first one failed to load the correct data as well.

    Hope it helps!

    • This reply was modified 6 years, 11 months ago by ronald.kubo. Reason: wrong closing quote for code
    ronald.kubo

    (@ronaldkubo)

    Hi,

    I ran into the same thing, and solved it with CSS. Like the plugin author mentioned, it’s a browser thing designed for accesibility, so removing it should be considered as such. I agree it’s annoying though. Add this to either the style.css in your child-theme or in the custom CSS section of this plugin settings to remove it (this will remove the same effect from happening on all buttons on your site, if you don’t want that then find the selector for this specific button):

    button:active { outline: none; border: none;}
    button:focus {outline:0;}

    Had the same problem on one of my sites. As James Huff pointed on WordPress 4.4 Master List a few hours ago, a patch for this problem has been made:

    https://core.trac.www.ads-software.com/attachment/ticket/34723/34723.patch

    To fix, open your category-template.php and replace lines 1144 – 1158…

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
    	if ( false === $terms ) {
    		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		$to_cache = array();
    		foreach ( $terms as $key => $term ) {
    			$to_cache[ $key ] = $term->data;
    		}
    		wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
    	}
    
    	$terms = array_map( 'get_term', $terms );

    …with the new code from the patch:

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
     	if ( false === $terms ) {
     		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		if ( ! is_wp_error( $terms ) ) {
    			$to_cache = array();
    			foreach ( $terms as $key => $term ) {
    				$to_cache[ $key ] = $term->data;
    			}
    			wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
     		}
     	}
    
    	if ( ! is_wp_error( $terms ) ) {
    		$terms = array_map( 'get_term', $terms );
    	}

    So is now line 1144 – 1162. This fix will be included in the future 4.4.1 I suppose

    Don’t know if this will fix your entire error message concerning this plugin, but the category-template.php error has been noted with the 4.4 release. As James Huff pointed on WordPress 4.4 Master List a few hours ago, a patch for this problem has been made:

    https://core.trac.www.ads-software.com/attachment/ticket/34723/34723.patch

    To fix, open your category-template.php and replace lines 1144 – 1158…

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
    	if ( false === $terms ) {
    		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		$to_cache = array();
    		foreach ( $terms as $key => $term ) {
    			$to_cache[ $key ] = $term->data;
    		}
    		wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
    	}
    
    	$terms = array_map( 'get_term', $terms );

    …with the new code from the patch:

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
     	if ( false === $terms ) {
     		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		if ( ! is_wp_error( $terms ) ) {
    			$to_cache = array();
    			foreach ( $terms as $key => $term ) {
    				$to_cache[ $key ] = $term->data;
    			}
    			wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
     		}
     	}
    
    	if ( ! is_wp_error( $terms ) ) {
    		$terms = array_map( 'get_term', $terms );
    	}

    So is now line 1144 – 1162. This fix will be included in the future 4.4.1 I suppose

    Had the same problem on one of my sites. As James Huff pointed on WordPress 4.4 Master List a few hours ago, a patch for this problem has been made as Marius mentioned above:

    https://core.trac.www.ads-software.com/attachment/ticket/34723/34723.patch

    To fix, open your category-template.php and replace lines 1144 – 1158…

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
    	if ( false === $terms ) {
    		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		$to_cache = array();
    		foreach ( $terms as $key => $term ) {
    			$to_cache[ $key ] = $term->data;
    		}
    		wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
    	}
    
    	$terms = array_map( 'get_term', $terms );

    …with the new code from the patch:

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
     	if ( false === $terms ) {
     		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		if ( ! is_wp_error( $terms ) ) {
    			$to_cache = array();
    			foreach ( $terms as $key => $term ) {
    				$to_cache[ $key ] = $term->data;
    			}
    			wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
     		}
     	}
    
    	if ( ! is_wp_error( $terms ) ) {
    		$terms = array_map( 'get_term', $terms );
    	}

    So is now line 1144 – 1162. This fix will be included in the future 4.4.1 I suppose

    @pet Mart

    Had the same problem on one of my sites. As James Huff pointed on WordPress 4.4 Master List a few hours ago, a patch for this problem has been made:

    https://core.trac.www.ads-software.com/attachment/ticket/34723/34723.patch

    To fix, open your category-template.php and replace lines 1144 – 1158…

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
    	if ( false === $terms ) {
    		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		$to_cache = array();
    		foreach ( $terms as $key => $term ) {
    			$to_cache[ $key ] = $term->data;
    		}
    		wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
    	}
    
    	$terms = array_map( 'get_term', $terms );

    …with the new code from the patch:

    function get_the_terms( $post, $taxonomy ) {
    	if ( ! $post = get_post( $post ) )
    		return false;
    
    	$terms = get_object_term_cache( $post->ID, $taxonomy );
     	if ( false === $terms ) {
     		$terms = wp_get_object_terms( $post->ID, $taxonomy );
    		if ( ! is_wp_error( $terms ) ) {
    			$to_cache = array();
    			foreach ( $terms as $key => $term ) {
    				$to_cache[ $key ] = $term->data;
    			}
    			wp_cache_add( $post->ID, $to_cache, $taxonomy . '_relationships' );
     		}
     	}
    
    	if ( ! is_wp_error( $terms ) ) {
    		$terms = array_map( 'get_term', $terms );
    	}

    So is now line 1144 – 1162. This fix will be included in the future 4.4.1 I suppose

    Thread Starter ronald.kubo

    (@ronaldkubo)

    Resolved.

    In the php on line #357

    } elseif ( $stock > 1 ) {

    Should be:
    } elseif ( $stock >= 1 ) {

    James, could you please update the plugin with this fixed?

    Thank you Juan @ Nice Themes for your help!

    Thread Starter ronald.kubo

    (@ronaldkubo)

    Example can be seen here:
    https://www.postma-development.com/product-category/plants/

    When you scroll down, you’ll see product showing no stock information, those are the ones with ‘1’ in stock. Would appreciate any insights, I couldn’t figure out where this goes wrong. In single product pages it does show stock as ‘1 in stock’. Like here:
    https://www.postma-development.com/product/apple-malus-domestica-hollow-core-m27/

    I’m using both ‘Product Archive Customiser’ and ‘Grid/List toggle’ by James. There are no other plugins involved in product display, and this problem also occurred before having added any custom css.

    @cencaldave; I had the exact same problem in my web shop. As the plugin suggests, I am developing a site, and need to import/trial many products. Now that I need to remove them, I need to do it manually.

    The same problems occurs, the plugin will stop after removing 1 product, and then ask me to continue.

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