User is not able to see Page selector in Search Result webpart

Copper Contributor

The user does not see the page selector of the Search Results webpart. Direct colleagues do not have the issue. 

We have tried to remove the user from associated ADgroup(s) and from the sitecollection and then add user again but this did nothing. Also we have tried to add the user without a ADgroup but this also did not give the result we where looking for. Everything browser related was tried as well but to no avail.

 

Everything else in the site collection is working correctly. Filter webpart, Searchbox webpart ect. (there is also enough data searchable and user has access to all of this to even get a page selector. More than 100 items should be visible)

We are not able to reproduce the issue ourselves.

 

The expectex behaviour is that user is able to see and use the page selector in the Search Results webpart.

 

We are not able to add screenshots because of company data, but it is just the Search Results webpart without th epage selector at the bottom.

 


Is there anyone with some suggestions that we can try to make this correctly again?!

1 Reply

@Eline_SharePointFAB 

It sounds like a frustrating issue, but there are a few troubleshooting steps you can take to resolve the missing page selector in the Search Results web part for the user in SharePoint Online. Here's a comprehensive list of potential solutions:

1. Permissions Check

Even though you mentioned that the user has the necessary permissions, it's worth double-checking:

  • Ensure that the user has the same permissions as their colleagues who can see the page selector.
  • Check if there are any unique permissions set on the Search Results web part or the page hosting the web part.

2. Web Part Configuration

Verify the configuration of the Search Results web part:

  • Go to the page where the Search Results web part is added.
  • Edit the web part settings to ensure that the paging options are enabled.
  • Compare the settings with the working users’ configuration.

3. Personalization Settings

Check if the user has any personalized view settings:

  • Users might have personalized their view, which could affect how the web part is displayed.
  • Ask the user to reset their page view settings to the default or remove any personal views.

4. Clear Browser Cache and Cookies

You mentioned browser-related attempts, but ensure all the steps are followed:

  • Clear the browser cache and cookies.
  • Try accessing the site in a different browser or an incognito/private browsing window.
  • Ensure that the browser is updated to the latest version.

5. User Profile Issues

There might be an issue with the user's profile in SharePoint:

  • Go to the SharePoint Admin Center.
  • Navigate to User Profiles and search for the user.
  • Try re-indexing the user’s profile and see if it resolves the issue.

6. Different Machine or Network

Ask the user to try accessing the site from a different machine or network:

  • Sometimes network policies or machine-specific issues could be causing the problem.
  • This can help identify if the issue is related to the user’s specific environment.

7. Check Custom Scripts or Code

If there are any custom scripts or code on the page, verify:

  • Ensure that the custom code is not interfering with the rendering of the page selector.
  • Disable any custom scripts temporarily to see if the issue persists.

8. Check for SharePoint Updates

Ensure that SharePoint Online is up-to-date and check for any known issues:

  • Sometimes, Microsoft might have updates or known issues impacting certain functionalities.
  • Check the Microsoft 365 Service Health dashboard for any ongoing issues.

9. Reindex the Site

Reindex the entire site collection:

  • Go to the SharePoint Admin Center.
  • Select the site collection and reindex it to ensure that search results are updated properly.

10. Inspect Element and Console Log

Use browser developer tools to inspect the element:

  • Right-click on the page and select “Inspect” or press F12.
  • Check the console log for any errors or warnings that might provide clues about what’s going wrong.

By systematically working through these steps, you should be able to identify the root cause of the issue and restore the expected behavior for the user in SharePoint Online.

NOTE: My knowledge of this topic is limited, but since no one has answered it for at least one day or more, I entered your question in an AI. The text and the steps are the result of AI. Maybe it will help you further in your project, if not please just ignore it.

My answers are voluntary and without guarantee!

 

Hope this will help you.

Was the answer useful? Mark as best response and Like it!

This will help all forum participants.