Rodrigue T .a11n

Hi Darren,

I have created an issue on the repo for the team to investigate further (https://github.com/woocommerce/facebook-for-woocommerce/issues/2825).

Thanks,

R

• This reply was modified 3 months, 3 weeks ago by Rodrigue T .a11n.

Hi,

I’m glad to hear that updating the status in the database resolved the issue.

If you have any other questions or need further assistance, please feel free to reach out.

Best regards,

R

That’s a great question! If I had to guess, I’d say the WooCommerce documentation specifies that the CSV file must be in UTF-8 format because most users would not differentiate between UTF-8-sig and UTF-8. UTF-8-sig is essentially UTF-8 encoding with an added Byte Order Marker (BOM) at the beginning of the file.

Since your tests show that UTF-8-sig works better for you without affecting content quality, it makes sense to continue using it.

Let me know if you have any other questions!

• This reply was modified 3 months, 3 weeks ago by Rodrigue T .a11n.

I’m glad to hear that you’ve tested both UTF-8 and UTF-8-sig and found that UTF-8-sig works best for you. Using UTF-8-sig makes sense if it provides faster import times without affecting content quality.

If you have any more questions or need further assistance, feel free to reach out.

Best regards,

R

@phanduynam, I had another look, and you’re right—WooCommerce has exported CSV files with UTF-8 BOM (UTF-8-sig) since version 3.2.6. I’d say it makes sense to use UTF-8-sig for importing as well.

The Byte Order Marker (BOM) in UTF-8-sig files helps WooCommerce recognize the file encoding immediately, which could explain the faster import times. Using the same encoding as WooCommerce’s export ensures better compatibility and fewer issues. ?As always, it’s a good idea to test the import with a small sample first to make sure everything works smoothly.

Thanks,

R

Hello,

Thanks for reaching out. I recommend using UTF-8 encoding instead of UTF-8-sig when importing Vietnamese product CSV into WooCommerce. UTF-8 correctly handles Vietnamese characters, while UTF-8 with BOM (UTF-8-sig) can cause import issues due to the extra marker at the beginning of the file.

Tips to ensure a smooth import:

• Save CSV in UTF-8: Use a text editor or spreadsheet software to specify UTF-8 encoding and not UTF-8-sig (with BOM — Byte Order Marker) (e.g., Notepad++, Visual Studio Code, LibreOffice Calc).
• Verify Encoding: Double-check that the file is saved in UTF-8 to prevent character display errors.
• Test with a Small Sample: Before importing all products, do a trial run with a few entries to ensure Vietnamese characters display correctly.

No special considerations beyond using standard UTF-8 are needed, as it fully supports Vietnamese characters.

Thanks,

R

Hello @ahanastorepro,

There’s an open PR that aim at addressing the issue you describe. This should coming to an upcoming release, but you can test this changes on a staging site.

Thanks,

R

Hello @rokaklih ,

Thank you for your detailed investigation and for identifying the conflict between LSCWP and Cloudflare cache.

I recommend reaching out to the developers of LSCWP or Cloudflare for further assistance on resolving this compatibility issue.

If you have any other questions or need additional support in the future, feel free to reach out.

Best regards,

R

Hello Frank,

I would advise against changing the plugin’s source code. To redirect users to their LearnPress profile after a password reset, you can hook into the WooCommerce password reset flow and change the redirection URL. WooCommerce has a filter for customizing the redirect after a password reset, which makes this relatively straightforward.

Here’s how you can implement it:

1. Add a Custom Function in Your Theme’s functions.php File: This function will hook into the WooCommerce password reset flow and change the redirection URL.

Here’s a sample code snippet to add to your functions.php file:

add_filter( 'woocommerce_login_redirect', 'custom_learnpress_password_reset_redirect', 10, 2 );

function custom_learnpress_password_reset_redirect( $redirect, $user ) {
    // Check if LearnPress is activated
    if ( class_exists( 'LearnPress' ) ) {
        // Replace this with your actual LearnPress profile URL structure
        $learnpress_profile_url = site_url() . '/lp-profile
        return $learnpress_profile_url;
    }
    
    return $redirect;
}

Thanks,

R

Thanks, @alexdigital
We’ve made made an update to our middle to address the “Could not assign System User to asset” error.

I also see that you’re seeing Facebook for WooCommerce version 2.0.3, which is really outdated. I recommend upgrading to the latest version (version 3.1.15) for the best experience.

Thanks,

R

Thank you @alexdigital.

We’re currently investigating this issue.

Could you share with us your site’s?System Status Report.
You can find it via WooCommerce > Status.
Select Get system report and then Copy for support.

Once you’ve done that, you can paste the text in https://gist.github.com
After that, you can paste the Gist link here in your reply.

Thanks,
R

Hi @dabesa,

Purchase event is triggered either when:

• WooCommerce signals a payment transaction complete (most gateways)
• Customer reaches Thank You page skipping payment (for gateways that do not require payment, e.g. Cheque, BACS, Cash on delivery…)

We bind the trigger to the woocommerce_thankyou action hook. So, depending on how you customize your thank-you page, it will either work as expected, or you will need to call the hook manually.

Hi?@rajeevbagra2025

We’re glad that the suggestion worked for you!

Please don’t hesitate to start a new topic if you have any more questions.

Thanks,
R

Hello there,

You can try to manually disable the WooCommerce plugin before reinstalling it:

1. Navigate to wp-content > plugins.
2. Find the folder (WooCommerce in this case) for the plugin that you need to disable.
3. Right click on the plugin folder and select Rename.
4. Rename the plugin folder to disabled.[pluginname].
5. Then try reinstalling WooCommerce.

Let us know if you need any more help.

Thanks,

R

Hello there,

To hide products in specific categories from the “All Products” section in WooCommerce while keeping them visible on their respective category pages, you can achieve this with some custom code. Here’s a high-level approach to solve this problem:

1. Child Theme: If you’re not already using a child theme for your WordPress site, create one. This is important to ensure your changes are not lost when you update your theme.
2. Custom Functions: In your child theme’s functions.php file, you can add custom functions to filter the products that appear in the “All Products” section.
3. Use the pre_get_posts Hook: You can use the pre_get_posts hook to modify the query that retrieves products. Here’s an example of how you can do this to exclude certain categories:

add_action('pre_get_posts', 'exclude_categories_from_all_products');

function exclude_categories_from_all_products($query) {
       if (is_admin() || !$query->is_main_query()) {
           return;
       }

       if (is_shop() || is_product_category()) {
           $excluded_categories = array(1, 2, 3); // Replace with the IDs of the categories you want to exclude
           $query->set('tax_query', array(
               array(
                   'taxonomy' => 'product_cat',
                   'field' => 'id',
                   'terms' => $excluded_categories,
                   'operator' => 'NOT IN',
               ),
           ));
       }
   }

Replace 1, 2, 3 with the actual category IDs you want to exclude.

4. Save and Test: After adding this code, save your functions.php file and test it. Products from the specified categories should no longer appear on the “All Products” page while remaining visible on their respective category pages.

Remember to back up your site or test this in a staging environment before implementing it on a live site to ensure it works as expected. Also, be cautious when modifying code to avoid any syntax errors.