-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LPS-131654 Intermediate pages in page-iterator do not update when SPA is enabled #1205
Conversation
CI is automatically triggering the following test suites:
|
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-134423 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#2055 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-frontend#1205 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#6109 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#2242 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-frontend#1205 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - holatuwol > liferay-frontend - PR#1205 - 2021-06-29[23:35:41] Testray Importer:publish-testray-report#6114 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously passed test suites: |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#103815 |
Steps to reproduce
Expected behavior is that now that it's 60 results per page, we should see 17 pages. Actual behavior is that we still see 50 pages.
Solution notes
Originally I fixed it only for documents and media's search, rather than the normal search portlet, and I (incorrectly) assumed that the same fix would work in both places. However, since the search results portlet is instanceable, the solution for the documents and media portlet didn't work for the search results portlet.