Title: befantasy's Replies | WordPress.org

---

# befantasy

  [  ](https://wordpress.org/support/users/befantasy/)

 *   [Profile](https://wordpress.org/support/users/befantasy/)
 *   [Topics Started](https://wordpress.org/support/users/befantasy/topics/)
 *   [Replies Created](https://wordpress.org/support/users/befantasy/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/befantasy/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/befantasy/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/befantasy/engagements/)
 *   [Favorites](https://wordpress.org/support/users/befantasy/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 23 total)

1 [2](https://wordpress.org/support/users/befantasy/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/befantasy/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[ParcelWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce] Performance Bug: ‘public’ => true in order statuses pollutes post queries](https://wordpress.org/support/topic/performance-bug-public-true-in-order-statuses-pollutes-post-queries/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [3 days, 6 hours ago](https://wordpress.org/support/topic/performance-bug-public-true-in-order-statuses-pollutes-post-queries/#post-18930368)
 * Thanks for your fix
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Variation Swatches for WooCommerce] Bug Report: Attribute values with decimals (e.g., “7.5ml”) fail to save](https://wordpress.org/support/topic/bug-report-attribute-values-with-decimals-e-g-7-5ml-fail-to-save/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [1 month ago](https://wordpress.org/support/topic/bug-report-attribute-values-with-decimals-e-g-7-5ml-fail-to-save/#post-18898224)
 * Based on the detailed breakdown I provided earlier—specifically the three different
   behaviors between the **Product Edit “Add New” tool**, **Quick Edit**, and the**
   Full Term Edit page**—have you been able to reproduce this bug on your end?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Variation Swatches for WooCommerce] Bug Report: Attribute values with decimals (e.g., “7.5ml”) fail to save](https://wordpress.org/support/topic/bug-report-attribute-values-with-decimals-e-g-7-5ml-fail-to-save/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [1 month ago](https://wordpress.org/support/topic/bug-report-attribute-values-with-decimals-e-g-7-5ml-fail-to-save/#post-18898209)
 * After further testing, I found that this is **not a bug within Variation Swatches**,
   but rather a **WooCommerce Core sanitization inconsistency**. I confirmed this
   by disabling your plugin and the issue persisted with the default WooCommerce
   dropdowns.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Variation Swatches for WooCommerce] Bug Report: Attribute values with decimals (e.g., “7.5ml”) fail to save](https://wordpress.org/support/topic/bug-report-attribute-values-with-decimals-e-g-7-5ml-fail-to-save/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [1 month ago](https://wordpress.org/support/topic/bug-report-attribute-values-with-decimals-e-g-7-5ml-fail-to-save/#post-18898123)
 * Thanks for your help. I think I fond the root cause.
 * **Summary**
 * There is a sanitization mismatch between the **inline “Add New” attribute tool**(
   on the Product Edit page) and the **Global Attribute Manager**. When an attribute
   slug is created with a decimal point (e.g., `7.5ml`), the web admin UI fails 
   to match the variation, causing it to revert to **“Any…”**.
 * **The Root Cause (Discovery)**
 * I have identified that WooCommerce/Variation Swatches handles slugs differently
   depending on where they are created:
    1. **Method A (The Problem):** Creating a term via **Product Edit Page > Attributes
       > “Add New”**. This allows the slug to be saved with a decimal point (e.g., 
       Name: `7.5ml`, Slug: `7.5ml`).
    2. **Method B (The Standard):** Creating a term via **Products > Attributes > Configure
       Terms**. This automatically sanitizes the slug (e.g., Name: `7.5ml` becomes 
       Slug: `7-5ml`).
 * When **Method A** is used, the variation selection fails to save/display in the
   web admin (reverting to “Any”), likely because the UI or the Swatches plugin 
   expects a sanitized slug without dots.**Steps to Reproduce**
    1. Go to a specific Product Edit page.
    2. Under the **Attributes** tab, click **“Add New”** to create a value like **“
       7.5ml”**.
    3. Go to the **Variations** tab and create a variation using this “7.5ml” attribute.
    4. Click **“Save Changes”**.
    5. **Result:** The dropdown resets to **“Any…”**.
    6. **Verification:** Check the WooCommerce **iOS App**. The attribute appears as**“
       7-5ml”**.
 * **Expected Behavior**
 * The inline attribute creation should follow the same sanitization rules as the
   global attribute manager (converting `.` to `-`), or the Web UI/Swatches plugin
   should be updated to support slugs containing decimal points to ensure data consistency.
 * **Workaround Found**
 * Manually editing the attribute slug in the Global Attribute settings from `7.5ml`
   to `7-5ml` resolves the issue immediately, and the variation saves correctly.
 * Furthermore, I’ve noticed an inconsistency in WooCommerce’s internal slug standardization.
   On the “Edit” term page under Global Attribute settings, it’s impossible to save
   a slug as “7.5ml” because it’s automatically corrected to “7-5ml”. However, using
   the “Quick Edit” feature in the same list view allows “7.5ml” to be saved without
   any standardization. This bypass is likely how these problematic slugs are being
   introduced into the system.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/page/2/#post-18587524)
 * Thanks a lot！
 * It’s really strange — the problem is that what I see in my browser is an HTTP
   200 internal redirect. There’s indeed no 30x response, but it definitely does
   redirect.
 * And it’s not even all URL parameters that trigger an HTTP 200 internal redirect—
   only parameters like ‘srsltid’ behave this way. I don’t have access to another
   computer at the moment, but I’ll test it on a different machine when I get the
   chance.
 * Thanks again！
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/#post-18587484)
 * I never denied your test results — I’ve also conducted the corresponding tests
   myself.
 *  But you never followed the steps I described in your own testing. I’m just trying
   to figure out where this redirect is coming from.
 * Again：Did you ever run a test in edge or chrome browser?
    -  This reply was modified 10 months, 1 week ago by [befantasy](https://wordpress.org/support/users/befantasy/).
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/#post-18587340)
 * I’m fully aware of your test results. I got the same outcome when testing with
   curl, and I even bypassed Cloudflare locally. But did you see the screenshot 
   I shared earlier? In the test using the Edge browser, which I highlighted, the
   browser recognized it as an HTTP 200 internal redirect. What’s more, I tested
   on many other WordPress-based sites using the browser and was able to reproduce
   the same redirect behavior. I’m puzzled as well.
 * So, It’s not a wordpress core built-in feature?
 * Did you ever run a test in edge or chrome browser?
    -  This reply was modified 10 months, 1 week ago by [befantasy](https://wordpress.org/support/users/befantasy/).
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/#post-18587088)
 * That’s right, it’s an HTTP 200 response, but it then shows an **internal redirect**.
   Could this be a browser behavior (feature)? When I tested it locally, I bypassed
   the Cloudflare CDN using local DNS resolution(host file).
 * I uploaded a snapshot.
 * [image hosted at ImgBB — ImgBB](https://ibb.co/yF3yCxFF)
 * ![](https://ibb.co/yF3yCxFF)
    -  This reply was modified 10 months, 1 week ago by [befantasy](https://wordpress.org/support/users/befantasy/).
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/#post-18586162)
 * Thanks [@sirlouen](https://wordpress.org/support/users/sirlouen/)
 * According to your suggestion, I used the browser’s developer mode (Edge 138.0.3351.121)
   and disabled the cache. The URL with the `srsltid` parameter still redirects,
   showing as an internal redirect. However, if other unrecognized parameters are
   used, there is no redirect.
 * ![](https://wordpress.org/cd733278-4a44-42c5-accc-af1d10fa9879)
 * ![](https://wordpress.org/1d0a0bd0-1c88-4ab6-a009-4f24fc3913fb)
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/#post-18586014)
 * Thanks [@sirlouen](https://wordpress.org/support/users/sirlouen/)
 * I’m also puzzled, because I couldn’t find any related strings in the WordPress
   code. But in actual tests, a fresh installation of WordPress does strip these
   parameters and performs the redirect. Did you test the URL I just posted?
 * Auto-redirect Params: [https://wp.linz.link/?srsltid=AfmB](https://wp.linz.link/?srsltid=AfmB)
 * Non-redirected Params: [https://wp.linz.link/?unstripped=AfmB](https://wp.linz.link/?srsltid=AfmB)
 * Auto-redirect Params: [https://demos2.exsthemewp.com/child-medic/contacts?srsltid=sdafsadf](https://demos2.exsthemewp.com/child-medic/contacts?srsltid=sdafsadf)
 * Non-redirected Params: [https://demos2.exsthemewp.com/child-medic/contacts?unstripped=sdafsadf](https://demos2.exsthemewp.com/child-medic/contacts?unstripped=sdafsadf)
 * Based on these tests, I thought it was a WordPress core function.
 * Because if the redirect were implemented at the server level, then all parameters
   should be redirected — not just those related to source tracking.
    -  This reply was modified 10 months, 1 week ago by [befantasy](https://wordpress.org/support/users/befantasy/).
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/#post-18585983)
 * Thanks for youre reply.
 * I should be able to confirm that this has nothing to do with Yoast SEO or W3 
   Total Cache.
 * As I mentioned in the post above, I disabled every plugin I could think of that
   might affect parameter stripping — including SEO, caching, redirection, statistics,
   and so on.
 * In addition, I created a fresh WordPress installation with no plugins or themes
   installed（v6.8,2）. I tested it and it can automatically redirect: [https://wp.linz.link/?srsltid=AfmB](https://wp.linz.link/?srsltid=AfmB)
    -  This reply was modified 10 months, 1 week ago by [befantasy](https://wordpress.org/support/users/befantasy/).
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [redirect_canonical() doesn’t strip known tracking parameters like srsltid](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 1 week ago](https://wordpress.org/support/topic/redirect_canonical-doesnt-strip-known-tracking-parameters-like-srsltid/#post-18585764)
 * Another question：
 * WordPress core does not strip all URL parameters, only certain ones like `srsltid`
   and `fbclid`. I’m not sure what the full list includes. I would like to know 
   where in the source code the logic is defined to decide which parameters are 
   stripped and which are preserved. I searched the codebase and database but couldn’t
   find any files that contain the strings `srsltid` or `fbclid`.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Rank Math SEO – AI SEO Tools to Dominate SEO Rankings] Sitemap Not Updating When Posts Are Published via WordPress Mobile App](https://wordpress.org/support/topic/sitemap-not-updating-when-posts-are-published-via-wordpress-mobile-app/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 2 weeks ago](https://wordpress.org/support/topic/sitemap-not-updating-when-posts-are-published-via-wordpress-mobile-app/#post-18572432)
 * Thanks for your reply.
 * Since I migrated from Yoast SEO, I had already configured the page cache and 
   CDN cache to exclude the sitemap. However, after adding this filter, it seems
   that the sitemap now updates correctly when publishing posts via the iOS WordPress
   app.
 * May I ask why, without the filter, publishing or editing posts via the web interface
   would update the sitemap, but publishing via the iOS WordPress app would not?
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Unable to select products when inserting a URL link, only posts are available.](https://wordpress.org/support/topic/unable-to-select-products-when-inserting-a-url-link-only-posts-are-available/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [10 months, 4 weeks ago](https://wordpress.org/support/topic/unable-to-select-products-when-inserting-a-url-link-only-posts-are-available/#post-18554709)
 * Thank you for the explanation. I don’t quite understand—do you mean that the 
   link insertion feature in the desktop block editor can search for products, and
   this is made possible by the WooCommerce plugin? Is it also possible for WooCommerce
   to enable this feature in WordPress mobile app?
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Unable to select products when inserting a URL link, only posts are available.](https://wordpress.org/support/topic/unable-to-select-products-when-inserting-a-url-link-only-posts-are-available/)
 *  Thread Starter [befantasy](https://wordpress.org/support/users/befantasy/)
 * (@befantasy)
 * [11 months ago](https://wordpress.org/support/topic/unable-to-select-products-when-inserting-a-url-link-only-posts-are-available/#post-18553206)
 * I don’t think this feature can be implemented within WooCommerce. Isn’t the link
   insertion functionality part of the UI in the WordPress mobile app?
 * Also, when using “Link to existing content,” I can only search for posts and 
   pages by entering keywords — products don’t appear in the results. I believe 
   the key to resolving this issue lies in the WordPress mobile app, not WooCommerce.
 * In the built-in block editor on the WordPress web version, I _can_ search for
   products when inserting a link.
 * ![](https://wordpress.org/d36f1020-a39b-412f-ae78-36e0698d6e1f)
 * ![](https://wordpress.org/9be8a2d8-c768-414a-adee-e43d070d6e8b)
 * ![](https://wordpress.org/b709b7b4-c129-4ab3-8a51-72379289a4fc)

Viewing 15 replies - 1 through 15 (of 23 total)

1 [2](https://wordpress.org/support/users/befantasy/replies/page/2/?output_format=md)
[→](https://wordpress.org/support/users/befantasy/replies/page/2/?output_format=md)