Common behavior of content widgets

When you drop two content widgets on one page, by default, they share the following behavior:
  • Paging
  • Switching to detail mode and back to list
  • URL filtering (by date through the Archive widget, or by a classification through the Tags or Categories widget)

This means that clicking a page in one widget also changes the page in the other. Clicking a single item in one widget switches the other to detail mode, filtering by date or classification filters both widgets.

If you do not want the widgets to behave in this way, perform the following for each widget:

  1. Click the Edit button in the upper-right corner of the widget.
  2. Click Advanced button in the lower-right corner of the widget.
  3. In field UrlKeyPrefix, for each widget enter a different string.
    When you perform an action like paging, filtering, or opening the detail mode, this string is added to the URL. If you perform the action on one widget, the system does not perform it on the other widgets on the page, however if you have performed the action on one widget and then perform it on another, the system returns the first widget in its original state.
    To overcome this, perform Step 4.
  4. In any of the widgets, in field UrlEvaluationMode, enter QueryString.
    This is applied automatically to all other widgets.

    NOTE: The Forums widget does not support QueryString. If you have such widget on the page, you cannot perform this step.

  5. Click Save » Save.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Web Security for Sitefinity Administrators

The free standalone Web Security lesson teaches administrators how to protect your websites and Sitefinity instance from external threats. Learn to configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?