Forum Replies Created

Viewing 15 replies - 1 through 15 (of 5,820 total)
  • Plugin Support RK a11n

    (@riaanknoetze)

    Hi Rok,

    As far as I’m aware, that’s the expected behaviour when the site has the new High-Performance Order Storage (HPOS) function enabled. The older system for saving orders relied on the postmeta, while the HPOS method relies on its own standalone database table. For the time being, WooCommerce is set up to be backwards compatible in case some plugins are still using the postmeta approach.

    Plugin Support RK a11n

    (@riaanknoetze)

    Hey there,

    I’m so glad to hear that everything worked out πŸ™‚

    In reviewing the answers here, I wanted to highlight that an even more ideal setup would be to create a child theme. Essentially you’ll copy the templates that my colleague mentioned into that of the child theme folder rather than the main parent theme folder.

    By doing this, it means that the changes won’t be lost when the parent theme itself gets updated. For more information on how a child theme works, have a look at the following guide:

    Hope it helps!

    RK a11n

    (@riaanknoetze)

    Hi Kristin,

    Thanks for getting in touch – The number input field (incl the arrows) are generated by the browser itself and isn’t something the WooCommerce has any direct control over (it’s the international standard for number input fields). I believe the reason for that is because the arrows are pretty small and while a mouse pointer is accurate enough, that accuracy is lost when using a finger as a pointer.

    With that being said, if this is a must-have requirement on the store, you could take a closer look at the following extension: Quantity Buttons for WooCommerce (these buttons use extra JavaScript that sits alongside the default number input fields).

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    In order to troubleshoot this further, please do the following:

    • Share a copy of your status report as found under WooCommerce > Status; and
    • Share a direct link to a product page where you’re seeing these blurry product images.

    Thanks!

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there

    Thanks for including those error logs; Based on the timestamps you shared and cross-referencing that with the logs, it looks like this might be linked to the ActiveCampaigns for WooCommerce plugin (the logs indicate some deprecated code being used). Are you still seeing the same thing when that plugin is disabled?

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    An SEO expert is definitely the best person to help out with here; In general – You can think of the short description being that little bit of text shown on search engine results: You’ll want to make a judgment call on whether users would find the mentioned of “free shipping” there helpful (or not).

    In terms of adding features/attributes of this product, you’ll want to make sure to list them using WooCommerce’s attributes. For more information on how that works, have a look at the following guides:

    Note: Attributes are often used as part of product variations, but they can definitely be used as standalone items to only communicate the features of the plugin.

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    I’d like to make sure we’re looking at the same thing: Can you share a screenshot of what you’re seeing on your side and highlight what you’re expecting to see? I’m asking as in both of those links, the categories are indeed shown:

    https://d.pr/i/RnLpYe
    Full Image: https://d.pr/i/RnLpYe

    And:

    https://d.pr/i/wE19u6
    Full Image: https://d.pr/i/wE19u6

    Thanks!

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    At the moment, Google Listing & Ads only supports the Product Bundles extension as sold on the WooCommerce Marketplace. To add support for a 3rd party bundles plugin like WPC Product Bundles for WooCommerce, I’d recommend one of the following:

    Hope it helps!

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    I had some trouble getting this to work for Hebrew, but here are the steps I took:

    1. Navigated to Dashboard > Updates
    2. Click on the “Update Translations” button at the bottom
    3. Navigate to Loco Translate > Plugins > WooCommerce
    4. Click on the “Sync” button
    5. Note that the Hebrew language file now shows 2,591 untranslated strings
    6. Locate the English string on the front-end that isn’t showing in Hebrew (e.g. Contact information) and manually add the translation
    7. Click Save

    Here’s what that looks like on my side:

    https://d.pr/i/2SPu0W
    Full Image: https://d.pr/i/2SPu0W

    On the front-end:

    https://d.pr/i/ko1IcK
    Full Image: https://d.pr/i/ko1IcK

    As indicated earlier, translations for WooCommerce are done by the community – it’s not something that WooCommerce.com maintains directly.

    Hope it helps!

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    Just to be sure we’re on the same page: You’re saying that when creating a new product on the front-end as a vendor, everything is working as expected BUT when creating a new product from the admin perspective, it doesn’t work – right?

    Assuming that’s correct, can you share a bit more about how you’re creating that product from the admin side? You mentioned using Gutenberg – Can you share a screenshot of that action and also confirm whether you’re using the new New product editor that’s currently in beta (which can be toggled under WooCommerce > Settings > Advanced)?

    Thanks!

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    This is a tricky one to troubleshoot as I don’t see any updates on the WooCommerce side that could have triggered that. One thing I’m wondering though: Have you checked with your hosting provider on whether they deleted/recreated the webhooks on your site?

    Alternatively, I’m also wondering whether this might be something for the folks on Erply to look into as I do see some similar references from other 3rd party plugins.

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    To remove the product meta (SKU, categories, tags) from the single product page in WooCommerce, you need to unhook the woocommerce_template_single_meta action from the woocommerce_single_product_summary hook. The code you provided seems correct for this purpose, but it’s important to note that the quotes used in your code are not standard single quotesβ€”they are typographic quotes, which can cause issues in PHP. Make sure to use standard single quotes or double quotes in your PHP code.

    Here’s the corrected code:

    remove_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_title', 5 );
    remove_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_rating', 10 );
    remove_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_price', 10 );
    remove_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_excerpt', 20 );
    remove_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_meta', 40 );
    remove_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_sharing', 50 );

    To ensure that this code works regardless of the theme, you should place it in your child theme’s functions.php file, or in a custom plugin. Additionally, it’s possible that some themes or plugins might alter the default WooCommerce hooks or priorities. In such cases, you may need to adjust the priority of your remove_action calls to ensure they execute after the theme or plugin has added its actions.

    If the code still doesn’t work, you may need to increase the priority of the remove_action call to ensure it runs after the actions have been added by the theme or plugin. For example:

    remove_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_meta', 100 );

    If you’re unsure about the correct priority to use, you can try using a very high number to ensure your remove_action is called last.

    Finally, if your theme or a plugin is using a different hook or function to display the product meta, you will need to investigate the theme or plugin files to find the correct hook and callback function name to remove.

    As a last resort, if you’re unable to find the correct hook or if the theme is hardcoding the meta without using actions, you can override the woocommerce_template_single_meta function in your child theme. You would copy the original function from woocommerce/templates/single-product/meta.php to your child theme’s WooCommerce folder (typically your-child-theme/woocommerce/single-product/meta.php) and then make your changes there. However, this should be a last resort as it can make future updates more difficult.

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi @gilles66

    Thanks for sharing that; I reviewed the code for that method but return $gateways already happens on line 681: https://github.com/woocommerce/woocommerce-gateway-stripe/blob/8.0.0/includes/class-wc-gateway-stripe.php#L681

    I’m wondering whether the reorder_available_payment_gateways function is called with a null argument or if the $gateways variable becomes null at some point before the array_keys() function is called. With this in mind, please do the following:

    • Share a copy of your system status report as found under WooCommerce > Status; and
    • Confirm whether there is any custom code on the site that’s targeting gateways, specifically gateway ordering.

    Thanks!

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi @strategio

    Thanks for bring that up – The account connection flow has indeed changed with 8.0. Given the tests that you’ve already run, would you mind opening a bug report for this over at: https://github.com/woocommerce/woocommerce-gateway-stripe/issues ?

    Plugin Support RK a11n

    (@riaanknoetze)

    Hi there,

    The scripts linked in your first code block all refer to the Gutenberg block checkout method. Those aren’t really removable without breaking checkout.

    Conversely, the second code block refers to multiple different scripts used across a multitude of page but doesn’t include any from the block cart/checkout experience.

    While we don’t have direct access to your site to confirm, I’d recommend switching to the classic checkout mode as a way to prevent the block-based checkout scripts to be loaded.

    With that being said, can you elaborate a bit more on why you’re looking to remove those scripts? Is this linked to a deeper issue of a slow-loading site perhaps?

Viewing 15 replies - 1 through 15 (of 5,820 total)