Add new [SearchSettings] block to set the SortBy value [#620] #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…he ezFind extension
carlosmauri
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @pkamps ,
I completely forgot about this interesting PR so let's see if we can merge this one into our own forks. (Ibexa said no to this merge long time ago).
Basically this PR allows to set the 'sortBy' (sort order of the search result) reading the values from a new ini block.
https://ezpublishdoc.mugo.ca/Extensions/eZ-Publish-extensions/eZ-Find/eZ-Find-2.1/Customization/Template-fetch-functions#Sort_by
Right now the sortBy is hardcoded here:
extension/ezjscore/classes/ezjscserverfunctionsjs.php
The goal is to remove the hardcoded sort by logic and to be able to read either ini setting or post variable.
This PR is related to this one:
mugoweb/ezpublish-legacy#234
Thanks!
PS. This is the original ticket where this was implemented https://app.assembla.com/spaces/mugo-development-general/tickets/620