Legacy Knowledge Base
Published Jul. 2, 2025

Duplicated back button on search results

Written By

József Géczi

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

During search, duplicated back buttons appear on the result item's page.

Steps to reproduce:
1) Set up a vanilla Liferay DXP 7.2
2) Create a Web Content to be searched on (for example name it as 'test')
3) Search for its name at the Search Bar 'test'
4) Open the listed item (in context)

Actual behavior:

There are two back buttons appearing on the page of the search result item.

Depending on which 'back' button is clicked, the user is navigated to a slightly different Search widget page.
It is expected to see only one of these back buttons.

Environment

  • DXP 7.2

Resolution

Actually, the presence of the two separate 'back' buttons are intended - as both of them has separate functions on the UI and redirecting to different pages.

Although, if the "Look and Feel" of the Search Results widget is edited and "Application Decorators" setting is applied as "Decorate" or "Borderless", the portlet title is displayed which describes its function better.

In case their look might wanted to be customized (or one of them to be hidden), such expectation may be achieved by applying the change via a custom theme.

 

Did this article resolve your issue ?

Legacy Knowledge Base