Search Advanced v2.0
Release Notes
- added: ajax submitted search form from any page
- added: allow class to be passed to the vars of search/layout view
- added: auto submit on type selection if query is not empty
- added: basic support for history.js when browsing search results
- added: combine all feature
- added: container filter is now showing above search results
- added: count added as data attribute to search type menu items
- added: custom hook to influence search params
- added: german translation thanks to @Beaufort8
- added: list type is added as a css class to the search results
- added: members sidebar default field now has a placeholder text
- added: page title now contains the number of items found
- added: search page title now is its own view
- added: search params to search menu
- added: seperated search results error page check and html to a view
- added: setting introduced to control where the search filters show
- added: setting to enable/disable search advanced to take over search hooks
- added: settings notice to inform about settings that could not work
- added: sidebar filters are now applied when searching
- added: support for enclosed search words
- added: switch between menu or dropdown for sidebar search types selection
- added: the ability to switch between different result layouts
- added: user profile field search on members page
- added: you can now control sidebar menu sorting with a view var
- changed: additional search filters now use a generic approach
- changed: allowing pagination on combined:all search
- changed: always show sidebar menu item for current specific search
- changed: cleanup of search index page code
- changed: code beautification
- changed: improved default search list view
- changed: improved functionality of the ajax_submit feature
- changed: move type selection js to own file
- changed: moved page search to a custom hook
- changed: moved search autocomplete js to own file and made it toggleable
- changed: moved search widget related js to own file
- changed: no longer filter out page_top in search page as it is unregistered in start as searchable
- changed: reinstated the tags search as a custom type
- changed: scroll top top of page after ajax search
- changed: search input field is now a required field
- changed: search param name for returning count is now named count
- changed: search type refinement is now shown in a sidebar module
- changed: sidebar type selection now support parent menu items and no longer shows sections as optgroups
- changed: simplified the way menu items are added to the search sidebar
- changed: split logic in multiple parts and started using the layout view
- changed: updated dutch language
- changed: use new 1.11 language key exist function
- changed: user search form is no longer a table
- fixed: always make sure the searched type menu item is available
- fixed: always show quotes in search title around search words
- fixed: combined search for discussions and pages
- fixed: combined:all listing did not have the correct title
- fixed: correctly destroy/recreate autocompletes when needed
- fixed: correctly reset menu label to fetch correct item count
- fixed: correctly reset to all when changing type selection
- fixed: correctly set selected sidebar menu item
- fixed: count param not set correctly for custom search types
- fixed: css and js issue with search_list menu
- fixed: custom search types dissapearing from sidebar menu on entity pages
- fixed: do not fetch results html for non entity searches
- fixed: do not query metastring ids per metastring but query in bulk
- fixed: do not show empty double quotes on result page
- fixed: do not show menu items with an empty count
- fixed: escape function with return instead of continue
- fixed: line endings
- fixed: load ajax loaded content into correct html element
- fixed: menu items disappearing on search pages with offset
- fixed: no longer lose container_guid when switching to all content
- fixed: non entity searches now have correct menu item url query params
- fixed: only set combined content title if all else fails
- fixed: php typehint warning
- fixed: replaced deprecated jquery .live functions with .on
- fixed: respect profile field order showing user search fields
- fixed: search box input has no need for forced cell width
- fixed: set correct base url for pagination
- fixed: show submit button on top of search results if there is a filter
- fixed: some minor z-index issues with the search_list menu
- fixed: soundex filter now also has correct field name
- fixed: subtype should be NULL for non object searches
- fixed: use count if hook for all:combined search instead of menu total
- fixed: user profile field filter is not working correctly
- fixed: user profile field filter not showing up on members page
- fixed: wordwrap added to search_list child menu items
- fixed: you can now submit filters in the sidebar using enter key
- removed: multisite features are no longer part of this plugin
- removed: no longer provide custom discussion_reply search view
- removed: no longer support global_tags and site_categories plugins
Jeroen Dalsem
Owner of ColdTrick IT Solutions, developing social networking sites for the dutch market
Project Info
Stats
- Category: Tools
- License: GNU General Public License (GPL) version 2
- Updated: 2024-6-28
- Downloads: 5894
- Recommendations: 5
Other Projects
View Jeroen Dalsem's plugins
Hi, Jeroen.
There is a little layot problem in Elgg 2.2.
The searchbox is too large.
regards
Hi,
same on my site the searchbox is a little bit to large and is it possible to deactivate the searchbox in the right sidebar?!
thx
No, there is no problem.
The plugin "Aalborg Theme" have to be at the end of plugins list.
That's alright again.
How do I limit the search objects in the select list? I just wanted everyone, users, blog and groups.Plugins register their own objects as searchable. You can solve this programmatically by deregistering those type/subtypes as being searchable.
Thank you Jeroem. I already understood and could not find the file for this change. What is the name of the file?Thank you Jeroem. I already understood and could not find the file for this change. What is the name of the file?How do I cancel my objects as searchable?Thank you Jeroem. But where should I put this code? What is the PHP file?You need to write your own plugin to be able to make customizations. Check out http://learn.elgg.org/en/stable/tutorials/hello_world.html to learn how to build your own plugin.
I'm already this tutorial. But I do not find where this elgg_unregister_entity_type ('object', 'group') fits; I put in the start.php of the plugin group? Or not start.php plugin advanced_search?I found this in the star.php of the plugin group.I'm already this tutorial. But I do not find where this elgg_unregister_entity_type ('object', 'group') fits; I put in the start.php of the plugin group? Or not start.php plugin advanced_search?I got it. placeelgg_unregister_entity_type ('object', 'group')at the end/mod/search_advanced/views/default/search_advanced/search/type_selection.php
well that is not a good place to do it. You should do it in the init of your own plugin or if you need to do this in this view file, you need to include the view file in your own plugin. That way (if you update search_advanced) you are not losing your customizations.
Thank you Jereom. I'll make it try.I was interested in taking some of the objects I thought were unnecessary from the drop down list of the search option. So Jeroem helped with elgg_unregister_entity_type ('object', 'your_subtype') code. To get items from the list there are two modes: the first by placing unregister in /mod/search_advanced/views/default/search_advanced/search/type_selection.php (end of file). In your_subtype replace with the subtype name of prugin you want to remove from the list. The other method is to go in the start.php of the subtype of the plugin that you want to delete from the list and change I was interested in pulling from the drop down list of the search option some objects that I thought were unnecessary. So Jeroem helped with elgg_unregister_entity_type ('object', 'your_subtype') code. To get items from the list there are two modes: the first by placing unregister in /mod/search_advanced/views/default/search_advanced/search/type_selection.php (end of file). In your_subtype replace with the subtype name of prugin you want to remove from the list. The other method is to go in the start.php of the subtype of the plugin that you want to delete from the list and change I was interested in pulling from the drop down list of the search option some objects that I thought were unnecessary. So Jeroem helped with elgg_unregister_entity_type ('object', 'your_subtype') code. To get items from the list there are two modes: the first by placing unregister in /mod/search_advanced/views/default/search_advanced/search/type_selection.php (end of file). In your_subtype replace with the subtype name of prugin you want to remove from the list. The other method is to go in the start.php of the subtype of the plugin you want to delete from the list and changeElgg_register_entity_type ('object', 'your_subtype') for elgg_unregister_entity_type ('object', 'your_subtype'). This take away from the search option however the subtype does not appear in any search attempt, not even when selected all from the drop-down list. So it's best to opt for the first method in the file type_selection.phpWhat was done above does not change the drop-down list option list in the user profile widget. But I believe the concept is the same.1) When I do a search on my website, I have to put "quotes" to get accurate results. If I dont put quotes and search for the name of an exact group or even user, the search results are different. The actual result is not appearing even after searching the group name as it is. But if I search a single word (part of group name), the result shows accurate results. Am I missing some configuration or something?
2) I like how LinkedIn and Facebook display the search results. Can this plugin be modified to make it look like this (tabs for each section)?