Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter han2red

    (@han2red)

    Hi Shahzeen and Woo team,

    We had two products affected by this issue. One was fixed by changing WebP images to JPG, but that solution did not work for the second product, suggesting that the problem may not be related to the image format after all.

    As you suggested, we deactivated all plugins except WooCommerce and switched to the Storefront theme btw, yet the problem persists with that specific product.

    Would it be possible to share the product URL with you via email? We would prefer not to display the website errors openly, if that’s fine with you.

    Thread Starter han2red

    (@han2red)

    We finally found the culprit, this issue only happens when the product image (not the product gallery image) is in .webp format.

    So, to recap clearly as you may want to look this odd issue:

    All our product created up to the February 19, 2025, using a .webp format as main product image, display the correct thumbnail in block editor (wp) version of the cart and checkout pages.

    All our products created from February 23, 2025, using a .webp format as main product image, display the Product Gallery first image as the Product thumbnail in the block editor (wp) version of the cart and checkout page. When we do not use any product gallery image, the .webp product image is displayed correctly in the cart and checkout page.

    For the time being we’ll change .webp images to jpg to fix that temporaily.

    • This reply was modified 1 year, 2 months ago by han2red.
    • This reply was modified 1 year, 2 months ago by han2red.
    Thread Starter han2red

    (@han2red)

    We realize while investigating further the issue that it only happens with the block type Cart page, with the classic Cart shortcode page, the product thumbnail is correctly displaying the product image.

    @boldproducts, We encountered the same issue and realized that it was not caused by the plugin or Woocommerce itself, but rather because we had changed the default login URL using a plugin.

    We resolved this problem by customizing the default “password reset” email template and modifying it to use our custom login URL into it.

    You can test this fix by adding the following code to your functions page:

    // Override the password reset email URL add_filter( 'retrieve_password_message', 'custom_password_reset_url', 10, 4 ); function custom_password_reset_url( $message, $key, $user_login, $user_data ) { // Replace the default reset URL with your custom login URL $reset_url = site_url('/your-custom-login-page?action=rp&key=' . $key . '&login=' . rawurlencode($user_login)); // Customize the email message $message = __('Someone has requested a password reset for the following account:', 'your-text-domain') . "\r\n\r\n"; $message .= sprintf(__('Username: %s', 'your-text-domain'), $user_login) . "\r\n\r\n"; $message .= __('If this was a mistake, ignore this email and nothing will happen.', 'your-text-domain') . "\r\n\r\n"; $message .= sprintf(__('To reset your password, visit the following address: %s', 'your-text-domain'), $reset_url) . "\r\n\r\n"; return $message; }

    Replace “your-custom-login-page” with your custom login URL and “your-text-domain” with your domain name.

    Hope this helps.

    Cheers, Han.

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