Skip to content

Settings and activity

5 results found

  1. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Leanne Walker shared this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    I can confirm that currently Commerce Search v3 does not support Local Development.

    • Until local support is available, partners are currently working from Sandbox environments or if working on non search related activities they may be switching to alternative provider while working locally.

    While the suggestion to automatically fallback to Search v2 during local development is technically possible, it would mask actual system behavior and could lead to incorrect assumptions, missed issues, or inconsistent environment (sandbox vs local). For that reason, we are unlikely going to implement an automatic fallback to alternative search provider and switching search providers will remain a manual action at this time.

    • We fully understand your frustration, and how the inability to debug or run the site locally with Search v3 enabled is a significant disruption.
    • We are actively evaluating options to enable limited local development against sandbox instances, and work is underway to determine…
    Leanne Walker supported this idea  · 
  3. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Leanne Walker commented  · 

    Preferably at the Website level. Thank you.

    Leanne Walker shared this idea  · 
  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Leanne Walker shared this idea  · 
  5. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Currently we provide space via a pinned banner to allow customers to link to their appropriate privacy policy for additional details. This is for 'acceptance' only in that all cookies leveraged out of the box are considered first party functional cookies (https://support.optimizely.com/hc/en-us/articles/4413199721229-Cookies-in-Spire-CMS) for the website

    • The Accept button allows the pinned banner to disappear in acceptance of the policy
    • The other option is to 'close' the window, which is why it still displays if not 'accepted' on future pages/navigation of the user. This is not a 'reject' button out of the box today.

    Rejection of cookies or enhanced cookie management requires use of third party consent management system and is encouraged especially if additional cookies are leveraged or if changes are made to existing flows altering the functional first party cookie status of existing out of the box cookies.

    While looking into making existing cookies more configurable we found we…

    Leanne Walker supported this idea  ·