v8.8.0

This release introduces user inbox sorting by predefined keys - created at, latest message, and latest transition. In addition, this contains bug fixes e.g.

• Pickup line-item has been removed
• Integer range filter now takes into account that range end is exclusive on API
• Some number-only category ids were still causing issues

Translations changes

- "OrderBreakdown.providerTotalDefault": "You'll make",
- "OrderBreakdown.providerTotalReceived": "You made",
+ "OrderBreakdown.providerTotalDefault": "You'll earn",
+ "OrderBreakdown.providerTotalReceived": "You earned",

New translation keys:

"EditListingStyleForm.publishListingFailed": "Publishing a new listing failed.",
"EditListingStyleForm.updateFailed": "Failed to update listing. Please try again.",
"InboxPage.sortBy.createdAt": "Newest",
"InboxPage.sortBy.lastMessageAt": "Latest message",
"InboxPage.sortBy.lastTransitionedAt": "Latest status change",
"InboxSearchForm.sortLabel": "Sort by:",

Changes v8.8.0

• [add] Add ability to sort user inbox messages
  #656

• [add] Update one Marketplace text (to be aligned with the corresponding copy in Email texts).
  #661

• [add] Add currently available translations for DE, ES, FR.
  #658

• [add] Add accessibility improvements to components related to

  • search pages
  • listing page
  • listing editing pages
  • transaction page

  #649

• [change] Remove pickup fee line-item from the order breakdown.
  #655

• [add] Update EditListingPage README.md to describe the data gathered and updated.
  #654

• [fix] SearchPage.shared.js: category ids are always strings, so we need to convert query params to
  strings. #653

• [fix] SearchPage: fix a bug with integer range values. The range end value was not exclusive.
  #652

• [fix] IntegerRangeFilter: fix a bug with small text on grid layout.
  #650

• [add] render potential errors in EditListingStylePanel.
  #647

v8.7.0

This release introduces support for Provider and Customer minimum commissions. They will be preferred over percentage-based commissions when the minimum commission amount exceeds the fee calculated with the percentage-based commission.

In addition, there are improvements to accessibility on Topbar, Footer, and authentication pages - as well as, some bug fixes.

Translation changes

New translations

  "CheckoutPage.providerCommissionBiggerThanMinPrice": "This listing is currently unavailable. Please contact support.",
  "FetchLineItemsError.providerCommissionBiggerThanMinPrice": "This listing is currently unavailable. Please contact support.",
  "FetchLineItemsError.unknownError": "Oops, something went wrong. Please refresh the page and try again.",

Removed translations

- "BookingDatesForm.fetchLineItemsError": "Oops, something went wrong. Please refresh the page and try again.",
- "BookingFixedDurationForm.fetchLineItemsError": "Oops, something went wrong. Please refresh the page and try again.",
- "BookingTimeForm.fetchLineItemsError": "Oops, something went wrong. Please refresh the page and try again.",

Changes v8.7.0

• [add] Added support for Provider and Customer minimum commission handling
  #631
• [add] Add some accessibility improvements to Topbar, Footer, and AuthenticationPage.
  #639
• [add] Add currently available translations for DE, ES, FR.
  #641
• [fix] SearchPageWithMap: existing pagination page needs to be reset with map-based search. When
  bounds change, the search results are different and the previous pagination page number is not
  valid anymore. #640

v8.6.0

The main feature in this release is that it prepares sharetribe/web-template to handle listings without images.

The feature is build so that it works together with listings that have images: basically, operator will get ability to toggle images on/off per listing type on Console (this is not available at the time of Template's release). If images are not used, provider sees Style tab in EditListingWizard. There they get the possibility to choose between a selection of background colors - as the listing card on search page (and elsewhere) will still render a card with similar dimensions as defined in branding asset (Console > Build > Design > Branding).
In other words, listings without images have thumbnails with the same dimensions than what listings with images use on search page. On listing page, image is not shown as expected (no carousel nor cover photo).
#624

In addition, there are several bug fixes and improvements. The biggest highlight is that listings, using infinite items together with shipping option, didn't ask about shipping fee for additional items.

Translation changes

New translations

  "EditListingStyleForm.helpText": "Decide how your listing will look like in search results.",
  "EditListingStyleForm.title": "Choose a style",
  "EditListingStyleForm.preview": "Preview",
  "EditListingStylePanel.createListingTitle": "Style",
  "EditListingStylePanel.title": "Edit the style of {listingTitle}",
  "EditListingWizard.default-booking.new.saveStyle": "Publish listing",
  "EditListingWizard.default-inquiry.new.saveStyle": "Publish listing",
  "EditListingWizard.default-purchase.new.saveStyle": "Publish listing",
  "EditListingWizard.edit.saveStyle": "Save changes",
  "EditListingWizard.tabLabelStyle": "Style",
  "StripeConnectAccountForm.buttonTitleLimitedAccess": "You can't manage payout details on behalf of user.",
  "StripeConnectAccountStatusBox.getVerifiedButtonTitleLimitedAccess": "You can't manage payout details on behalf of user.",

Changed translations

-  "LimitedAccessBanner.message": "You're logged in as {firstName} {lastName}. You have limited access rights. You can't initiate transactions, move them forward, or send messages on the user's behalf.",
+  "LimitedAccessBanner.message": "You're logged in as {firstName} {lastName}. You have limited access rights. You can't add payout details, initiate transactions, move them forward, or send messages on the user's behalf.",

Changes v8.6.0

• [fix] EditListingDeliveryPanel: additional shipping fee was not asked and the related shipping fee
  was missing, when selecting multiple items.
  #636

• [add] Add support for listing types that do not require images.
  #624

• [fix] Remove mentions to legacy templates from README.md
  #630

• [fix] Small fixes

  • [fix] Renamed onRecoverableError param
  • [add] Improved schema for ProfilePage
  • [add] Added role, aria-label, and titles to social media icons
  • [change] Limited editing and added communication for operators using the 'log-in as' feature
  • [fix] Removed additional padding on primary integer filters
  • [fix] Added word-break to Message and OwnMessage in ActivityFeed.js

  #631

v8.5.0

This release prepares the template for the capability to differentiate user experience based on the user's user type. Soon, we will release the option in Console to configure the visibility of key elements based on user type, and this release will use those configurations to show or hide those key elements.

Read more in the associated pull request: #614.

In addition, this release includes a fix for the Search as CTA date range mode.

Changes 2025-06-11

• [add] Add conditional visibility for the following elements depending on Console configuration:

  • Visibility for create listings links for unauthenticated users configured in Top bar
  • Visibility for elements configured in User types:
    • Create listings and Manage listings links
    • Payment method and payout detail tab links
    • Inbox links for orders and sales
    • Profile page review tabs

  #614

• [fix] Fix an issue with the date filter in the Search CTA component, which was not observing
  nightly search configuration correctly. #625

v8.4.2

v8.4.2 2025-06-02

This release fixes mobile input zoom and booking time-slot issues, improves copy, and adds updated translations including DE, ES, and FR.

• [fix] Set the font size for the input fields in the Search as CTA component to 16px to prevent
  unintentional zooming on mobile.#622
• [fix] BookingFixedDurationForm: start time generation didn't count consecutive time-slots
  correctly when multiple seats were allowed.
  #620
• [add] Improve one copy text. #621
• [add] Add currently available translations for DE, ES, FR.
  #619

Changed translations:

- "EditListingPhotosForm.addImagesTip": "Tip: Upload the best 2-3 photos from different angles and with a good quality.",
+ "EditListingPhotosForm.addImagesTip": "Tip: Upload 2-3 good-quality photos from different angles.",

v8.4.1

v8.4.1 2025-05-26

• [fix] Modify two translation keys that were using an incorrect namespace.
  #617
• [fix] Add missing location prop to grid search page
  #615
• [fix] Corrected anchor link scrolling behavior on Privacy Policy and Terms of Service pages, when
  opened as modals (in signup/login). #612

Changed translations:

-  "PageBuilder.CategoryFilter.selectAll": "All categories",
+ "PageBuilder.SearchCTA.CategoryFilter.selectAll": "All categories",
- "PageBuilder.CategoryFilter.placeholder": "Select category",
+ "PageBuilder.SearchCTA.CategoryFilter.placeholder": "Category",

v8.4.0

With this release we introduce the new "Search as a CTA" component. The component is a search bar that can be included on any dynamic page. In addition, this release addresses a small bug when removing all images form a listing. It also adds support for prefilling the value in the password reset form with the value entered in the log in form: when a user clicks "Reset password" on the login page, the email address they have already typed (if any) is now correctly passed to the forgot password page.

Translations changes

New translation keys:

  "PageBuilder.CategoryFilter.selectAll": "All categories",
  "PageBuilder.CategoryFilter.placeholder": "Select category",
  "PageBuilder.SearchCTA.buttonLabel": "Search",
  "PageBuilder.SearchCTA.dateFilterPlaceholder": "Dates",
  "PageBuilder.SearchCTA.keywordFilterPlaceholder": "Search listings",
  "PageBuilder.SearchCTA.locationPlaceholder": "Location",
  "PageBuilder.SearchCTA.currentLocationPlaceholder": "Current location",

Changed translations:

-  "DatePicker.clearButton": "Clear value",
+  "DatePicker.clearButton": "Clear",

v8.4.0 2025-05-20

• [add] Added a "Search as CTA" component for embedding a search bar on any dynamic content page
  #561
• [add] Pass email from login to forgot password
  #609
• [fix] EditListingPhotosForm: removing all images from a listing caused the screen to go blank
  #608

v8.3.2

This update addresses a few bugs related to the listing page filtering feature:

• In mobile search filter view, clicking "cancel" now maintains listing type path parameter
• When showing LimitedAccessBanner, exclude both search page versions
• With the configuration "only show top bar search input on search page", include both search page versions
• If a listing field is restricted to multiple valid listing types, show that field on listing type specific search pages corresponding to any of those listing types

In addition, this update changes the way the listing type path parameter is passed to helper functions, making it possible to pass other path parameters more easily in the future.

Changes v8.3.2

• [fix] SearchPageWithMap: secondary filter count was not taking into use filters that were limited
  to category or listing type #606
• [fix] Handle multiple search page routes outside search page and clarify path param usage
  #605

v8.3.1

This patch fixes the way the listing type specific search page path /s/:listingType is handled:

• When a user visits the listing type specific search page with a non-existing listing type id, the search page shows an empty result set.
• When a user uses the topbar search input from the listing type specific search page, the path parameter is maintained.

In addition, this patch fixes a bug in Avatar component behavior when user is pending approval.

Changes 2025-05-06

• [fix] Fix listing type path param usage
  #599

• [fix] Avatar: use correct pending-approval variant link when user is pending approval.
  #601

• [add] Add currently available translations for DE, ES, FR.
  #597

v8.3.0

This release adds support to search pages for filtering listing search based on listing type.

When listing type search is enabled (either in src/config/configSearch.js or through Console once the configuration option is released), a listing type filter is shown as the first filter option on both search page versions. In addition, this change set introduces a new route, /s/:listingType, that only shows listings for a valid listing type specified in the URL. On the listing type specific search page, a separate listing type filter is not shown, but other filters work normally.

Read more about this feature in the associated pull request: #583 .

In addition, this release includes some bug fixes.

Translations

New translation keys

"FilterComponent.listingTypeLabel": "Listing type",

Changes

• [add] Add support to search pages for filtering listing search based on listing type
  #583
• [fix] BookingFixedDurationForm: undefined booking length with single fixed price variant.
  #595
• [fix] EditListingPricingPanel: Add initial value for the startTimeInterval.
  #594
• [add] Add currently available translations for DE, ES, FR.
  #593