Shameem R. a11n

Hi @gx24

As you have already reached out to us by email, I will go ahead and close this thread.

Feel free to create a new topic if you need further help with WooCommerce core.

Thanks!

Hi @dplsig100

Thank you for explaining the situation in detail. I understand the priority is maintaining a private, logged-in user environment without redirecting to a Coming Soon page. Let’s explore how we can achieve this while keeping your privacy settings intact.

First, set the WooCommerce Site Visibility to “Live” to prevent the Coming Soon page from displaying. This will override WordPress’s default privacy setting. After that, you can add a custom filter to restrict access to logged-in users only. This way, logged-in users can bypass the Coming Soon page and be directed to their intended page after login:

add_filter( 'woocommerce_coming_soon_exclude', function( $is_excluded ) {
    if ( is_user_logged_in() ) {
        return true;
    }
    return $is_excluded;
}, 10 );

You can also try using this small plugin to disable the “Coming Soon” mode entirely, which may help prevent users from being redirected: https://gist.github.com/adrianduffell/8792c104401aaf2aa4fd7c43986d5e54

If you need further assistance, I suggest reviewing this guidance from our developer team:

• https://developer.woocommerce.com/2024/06/18/introducing-coming-soon-mode/
• https://developer.woocommerce.com/docs/integrating-with-coming-soon-mode/

Additionally, considering the nature of your setup, I’d recommend submitting this feedback as an enhancement request to enhance functionality and control over the Coming Soon mode on private sites.

I hope this helps! Please let me know how it goes or if you need further assistance.

Hi @marktrader

I’m glad you were able to find a solution to your inquiry here and thanks for sharing it with the community too! ??

Should you have further inquiries, kindly create a new topic here.

Thanks!

Hi @pglad

You can use a redirection plugin to redirect the old “book-category” URLs to the new “category” URLs. This way, when Google or any user clicks on the old link, they will be automatically redirected to the new URL. This should resolve the issue that Google is complaining about.

Please note that URL changes should be made carefully to avoid SEO issues. If you’re not comfortable doing this, you might consider hiring a professional to assist you.

I hope this helps! If you have any other questions, feel free to ask.

Hi @exitoffroad

Email addresses are technically case-sensitive, however, it is a common practice to treat them as case-insensitive. This is because most email providers do not distinguish between uppercase and lowercase characters.

In WooCommerce, the email address field should be case insensitive by default. This is to ensure that only the person with the exact email address can view the order details.

That being said, we understand that this can cause confusion for your customers. As a workaround, we recommend you to always input the email addresses in lowercase when creating an order. This way, even if your customers type their email address in any case, they should be able to access the order details.

Thank you for your understanding and patience. If you have any other questions or concerns, please don’t hesitate to ask.

Hi @scottcwilson

Indeed, the images must be uploaded to the Media Library before they can be referenced in the CSV file for product import. Simply dropping the file in the wp-content/uploads/ directory isn’t sufficient. WooCommerce needs to create various sizes of images for different areas of your store, which happens during the upload process to the Media Library.

I understand you have a large number of images, but this step is crucial for WooCommerce to display them correctly. You can bulk upload images to the Media Library, which should speed up the process.

WooCommerce should technically be able to handle filenames with spaces, but as mentioned, it’s generally recommended to avoid spaces for compatibility reasons. Using underscores or hyphens is a best practice.

Additional tips:

• Make sure your server has enough memory and execution time for large imports.
• Consider splitting very large imports into smaller batches.
• Always backup your database before large imports.

Please try uploading your images to the Media Library and then import your products again. Let us know how that goes. Looking forward to helping you.

Hi @westham00

From the screenshot you shared, the issue might be related to the product data itself. Please check whether the prices for all variations are correctly entered. Also, if a product variation has a lower price, then the product will show on top by default.

Additionally, head over to WooCommerce → Status → Tools, and do the following:

• WooCommerce transients – Clear
• Expired transients – Clear
• Clear template cache – Clear
• Capabilities – Reset Capabilities
• Clear customer sessions -Clear
• Product lookup tables – Regenerate
• Regenerate the product attributes lookup table – Regenerate

Next, please clear your browser cache and check again.

I hope this provides some clarity. Please let us know if you have any other questions!

Hi @devworlds

This looks like a stack trace from WordPress/WooCommerce that’s causing high CPU usage on your server. The trace shows multiple function calls related to WooCommerce and Jetpack connection/configuration, which could be causing performance issues. Here are some suggestions to address this:

• Please try temporarily disabling WooCommerce and Jetpack. This will help us determine if these are the source of the CPU spike.
• Increase PHP resources. Check and potentially increase of max_execution_time and memory_limit.
• Implement caching If you haven’t already, implement a caching solution like FlysingPress, W3 Total Cache or Redis object caching.
• Check for conflicts. To do so, you can follow the step by step guide shared here: https://woocommerce.com/document/how-to-test-for-conflicts/

I hope this helps! Please let us know how it goes or if you need further assistance.

Hi @thedrumdoctor

The URL for a standard YouTube video is much simpler than the one for a clip. The standard YouTube video URL is parsed by WordPress’s oEmbed feature, which allows it to be embedded directly into a post using the ‘Add Media’ function. However, the URL for a YouTube clip is more complex and may not be recognized by the oEmbed feature, resulting in the issue you’re experiencing.

While YouTube is indeed on the list of WordPress oEmbed providers, it’s possible that the oEmbed feature doesn’t support the specific URL structure of YouTube clips. This could be why the clip URL isn’t being parsed correctly and why it isn’t working with the “Add Media” function.

As a workaround, you could embed the video into your product description using the standard YouTube video URL instead of the clip URL. Alternatively, you could use a different method, such as a plugin like StreamWeasels YouTube Integration that supports the YouTube clip URL structure.

Please note that while iframes can be used to embed videos, they are generally not recommended due to potential security risks.

I hope this provides some clarity. Please let us know if you have any other questions!

Hi @renovomotors

It looks like I can’t access the screenshot link and site links you shared. Could you kindly provide a publicly accessible and correct URL once more?

Looking forward to hearing from you!

Hi @gmeweb

I understand that you’re experiencing issues with testing orders getting the same order number, causing problems with your cargo integration systems. This is certainly not the expected behavior.

For better assistance, can you provide a video showing the issue on your end? For video, you may use https://loom.com or https://www.awesomescreenshot.com/. Please follow the instructions on that page and then paste the URL into this thread.

However, this could be due to a conflict between plugins or a setting within your WooCommerce configuration. To fix this, you might need to check if you have any order number customization plugins active and ensure they are correctly configured.

If you continue to experience this issue, please provide us with more details about your current setup, including the active, themes, plugins and WooCommerce version, so we can assist you more effectively.

Let us know how that goes for you.

Hi @kirstylmarks

I’ve tested your site and found that the card input form loads perfectly fine on my end.

Often, these types of issues could be related to the web browser you’re using. A good first step to troubleshooting this would be to try clearing your site and browser’s cache. This can often help in resolving general site loading or performance issues.

You can follow our detailed guide on clearing browser cache here: https://wordpress.com/support/browser-issues/#clearing-your-browser-cache

If this doesn’t work or you have more questions, just let us know, and we’ll be happy to help!

Hi @nabeelahmad2580

The new WooCommerce Checkout block uses a different architecture than the classic checkout, which is why your current implementation isn’t affecting the field visibility as expected.

However, to make your plugin compatible with the new Checkout block, you’ll need to:

1. Implement WooCommerce Blocks integration
2. Add JavaScript functionality to control field visibility

Here’s an example to update your plugin:

1. Add a new PHP class to handle the integration:

add_filter('woocommerce_blocks_checkout_block_registration', 
  array($this, 'register_checkout_block_integration'));

2. Create a JavaScript file to handle the field visibility:

registerCheckoutFilters('your-plugin-name', {
  additionalFields: (defaultFields, extensions) => {
    // Your field visibility logic here
  }
});

3. Enqueue the JavaScript file when the Checkout block is present:

add_action('wp_enqueue_scripts', array($this, 'enqueue_checkout_block_scripts'));

More info:

• https://developer.woocommerce.com/docs/cart-and-checkout-handling-scripts-styles-and-data/
• https://github.com/woocommerce/woocommerce-checkout-integration-example/blob/main/woocommerce-checkout-integration-example.php
• https://rudrastyh.com/woocommerce/checkout-block-payment-method-integration.html

If you are still having problems, we recommend asking development questions on the #developers channel of the WooCommerce Community Slack. Many of our developers hang out there and will be able to offer insights into your question. You can also seek help from the following:

• A local web developer
• Codeable.io
• WooExperts

I wish I could help more, but hopefully, this gets you going in the right direction to get the job done.

Hi @mayank29gupta

Your server environment looks great, though PHP 8.2 is available and could improve performance. Consider upgrading if possible.

Here are other additional optimization steps you may follow:

• Install and configure Query Monitor plugin to identify slow database queries
• Consider implementing database sharding or table partitioning for large tables
• Review and potentially increase your MySQL Max Connection Limit to 300
• Implement a more aggressive caching strategy, such as Object caching (which you already have), Page caching and Database query caching.
• Consider using a CDN for static assets if you aren’t already
• Implement lazy loading for images if not already in place
• Review your Cloudflare settings, particularly, enable Auto Minify for HTML, CSS, and JavaScript. Set Browser Cache Expiration to at least a month and enable Brotli compression if available.

If this makes no difference, I would suggest hiring a professional developer or speed optimization expert to analyze and help further from the following:

• A local web developer
• Codeable.io
• WooExperts

I hope this helps! If you have any other questions, feel free to ask.

Hi @egostudio

This kind of problem is usually caused by a conflict with your theme or with another plugin. The best way to determine this is to:

• Temporarily switch your theme to Storefront or Twenty Twenty-Four
• Disable all plugins except for WooCommerce
• Repeat the action that is causing the problem

If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

I hope that helps! Let me know once you have done a conflict test!