Forum Replies Created

Viewing 15 replies - 136 through 150 (of 1,795 total)
  • I am getting the same errors with Twenty Sixteen, a default theme, and don’t have Elementor installed. It appears to be happening whenever I have legacy WooCommerce widgets installed in the Widget Block Editor and access Appearance > Widgets.

    If I remove all the legacy WooCommerce widgets; e.g., Cart, including removing them from Inactive Widgets, and access Appearance > Widgets, I don’t get any errors.

    I can use the Woo Commerce Mini Cart widget without generating the errors.

    It looks to me like it’s a WooCommerce legacy widget issue.

    Plugin Author linux4me2

    (@linux4me2)

    Hi @abitofmind,

    Yes, that’s the way I understand it.

    As you mention, the Navigation Block already offers a lot of features, and more may be added.

    Plugin Author linux4me2

    (@linux4me2)

    When I first heard about the Gutenberg Navigation Block, I was hoping it would make Menu In Post obsolete, but I don’t think there is a definitive answer. Yet.

    As far as I know, the Navigation Block creates menus as an unordered list of links, and can collapse them for a mobile menu, but it doesn’t (yet) give you the option of creating the menu as a select element; i.e., a drop-down, which Menu In Post will optionally do. (You can set the menu to display either as a list of links or a drop-down select.)

    While it’s possible to convert an unordered list of links like the Navigation Block creates into what appears to be a drop-down menu with CSS, it would be extra work, so I guess if you’re determined to have a drop-down select element, and don’t mind adding an additional plugin to do it easily, then Menu In Post would still be the way to go.

    Personally, I always prefer to accomplish things with native elements like the Gutenberg Navigation Block instead of using a plugin, so I recommend trying to make the Gutenberg Navigation Block meet your needs.

    Plugin Author linux4me2

    (@linux4me2)

    @cparkinson, Thanks for confirming the fix works!

    Plugin Author linux4me2

    (@linux4me2)

    Hi @clipb

    I haven’t been able to reproduce this, but PHP 8.x definitely deprecates optional parameters coming before required ones, so I altered the code accordingly and uploaded a version (1.1.9) with the correction. It should be available shortly.

    Thanks for pointing this out. I’m going to mark this as resolved, but if you have any further issues with this, let me know.

    Thread Starter linux4me2

    (@linux4me2)

    I had to make a small tweak to the snippet you provided to get it to work.

    The line:

    
    apply_filters( 'wpml_object_id', tinv_get_option( 'page', 'wishlist' ), 'page', true )
    

    returned the ID of the Wishlist page, so it always evaluated as true and the filter didn’t fire.

    I changed the snippet so it compared the current page’s ID to the Wishlist page ID as follows, and it works:

    
    add_action('wp_enqueue_scripts', 'tinvwl_wishlist_webfont', 9);
    
    function tinvwl_wishlist_webfont() {
    	if (class_exists('TInvWL') && !is_shop() && !is_product() 
                && apply_filters(
                    'wpml_object_id', 
                     tinv_get_option('page', 'wishlist'), 'page', true) !== get_the_ID()
            ) {
                add_filter('tinvwl_load_webfont', '__return_false');
    	}
    }
    

    Thanks again! I wouldn’t have gotten there without the help.

    Thread Starter linux4me2

    (@linux4me2)

    Hi @templateinvaders

    I understand what you’re saying. The snippet is very helpful. Thanks for that! I will give it a try.

    By the way, I haven’t noticed anything other than the heart icon that is using a webfont, but I haven’t looked in depth. If that is all you’re using the webfont for, maybe you could use the heart HTML code, and not need the webfont?

    • This reply was modified 3 years, 7 months ago by linux4me2.
    Thread Starter linux4me2

    (@linux4me2)

    I think I have it figured out, or at least one solution that works for me.

    In case anyone else wants to prevent a custom order item meta from appearing in an invoice and packing slip, you can add the following code snippet to your child theme’s functions.php:

    
    add_filter('woocommerce_order_item_get_formatted_meta_data', 'unset_specific_order_item_meta_data', 10, 2);
    function unset_specific_order_item_meta_data($formatted_meta, $item){
        /*
        // Only on emails notifications
        if(is_admin() || is_wc_endpoint_url()) {
            return $formatted_meta;
        }
        */
    
        foreach($formatted_meta as $key => $meta){
            if(in_array($meta->key, array('<name of your order item meta to remove>'))) {
                unset($formatted_meta[$key]);
            }
        }
        return $formatted_meta;
    }
    

    Just replace <name of your order item meta to remove> with a comma-separated list (in single quotes) of the order item meta(s) names you want to remove. This is a WordPress function, and will also remove the order item meta from notification emails.

    If you want the order item meta to appear in admin-generated PDF invoices and admin email notifications, you can try un-commenting this section:

    
    if(is_admin() || is_wc_endpoint_url()) {
        return $formatted_meta;
    }
    

    I haven’t tested that part, because I wanted the item meta hidden everywhere.

    Using this solution is perfect for my needs, because it doesn’t delete the custom order item meta name/value, it just doesn’t include them in the formatted output.

    I found the answer here, so thanks to LoicTheAztec.

    That’s the only solution I’ve seen.

    Maybe someone from WC will chime in.

    You might try the solution described in this post and see if you can then do the database upgrade successfully.

    Forum: Plugins
    In reply to: [WooCommerce] FATAL ERROR

    The error message suggests that the error may be due to the Rearrange WooCommerce Products plugin.

    The first thing I’d try is disabling that plugin and re-trying what you did that triggered the error; e.g., viewing a product.

    If you don’t have access to the WP Admin to disable the plugin, you can use your hosting control panel to view the /public_html/wp-content/plugins folder, and rename the folder rearrange-woocommerce-products to something else like rearrange-woocommerce-products-disabled, which will disable the plugin.

    Do some testing once that plugin is disabled and see if it fixes the problem.

    linux4me2

    (@linux4me2)

    Not a perfect answer, but you can hide the Admin Bar for all users but admins by adding the following to wp-config.php:

    
    show_admin_bar(false);
    

    If you want to retain the Admin Bar, but just hide the “Delete Cache” link in it, I guess you could use this CSS:

    
    #wp-admin-bar-delete-cache {
    	display: none;
    }
    
    Thread Starter linux4me2

    (@linux4me2)

    WooCommerce 6.5.1 is out, and I tested to make sure this issue didn’t occur with it, but it seems to work fine. Logging in with Login Security active works just fine.

    Thread Starter linux4me2

    (@linux4me2)

    It turns out it’s WooCommerce 6.5.0 that broke things, and I guess in the time it took me to figure it out and post this, it was rolled back to 6.4.1, which works just fine, so I’m marking this one as resolved. Sorry about the confusion.

    Plugin Author linux4me2

    (@linux4me2)

    I haven’t heard back from you, so I’m going to mark this one as resolved. Let me know if you have additional questions.

Viewing 15 replies - 136 through 150 (of 1,795 total)