Finder Integration Working Group
From Joomla! Documentation
Revision as of 06:37, 24 September 2011 by Chris Davenport
The purpose of the Finder Integration Working Group is to migrate JXtended's Finder extension package to be compatible with Joomla! 1.7+ in order to allow it to be considered for inclusion in a future release of the Joomla! CMS. At present, a realistic goal for this inclusion would be for Joomla! 3.0, scheduled for release in July 2012.
What is Finder?
Finder is an advanced search extension for Joomla! 1.5. The full package includes the Finder component, a front-end search module, a back-end status module, a group of plugins for processing data from core components, and a system plugin. Finder includes features such as term highlighting, suggestions, and allows for taxonomy support. Finder is used to power the search on extensions.joomla.org.
Finder documentation is a work in progress and we need people to help us improve and adapt it as the integration work proceeds. The documentation pages listed below were initially imported, with slight adaptations, from the original documentation with the kind permission of the Finder's original developers: Rob Schley, Louis Landry and Andrew Eddie.
The ultimate goal is to enable Finder to be integrated into the Joomla! CMS, replacing the existing search component. Below are additional goals that should be met during the migration process:
- Component follows proper MVC structure
- All old version code updated to current supported version (for example, MooTools based script)
- Meets code style standards as defined in the Joomla! Platform
- Uses no deprecated methods (i.e. JRequest)
- Where possible, queries formed using JDatabaseQuery to enable multi-database compatibility
- Migrate existing command line method to extend JCli
All work on the migration of Finder is being performed from a GitHub repository. In the repository is a simple Phing script to enable those who check out the repository to package the extension suite for easy installation. Feel free to fork the repo and work to resolve known issues then submit a pull request to merge those changes in. If you are interested in being added to the GitHub organization (which allows commit access to the main repo), send a message to Michael Babker.
Below is the status as of 18 September 2011:
- Administrator Component
- All of the code has been converted to follow the native MVC structure
- The indexer is working with the exception of a known conflict with the loadmodule plugin; it must be disabled for the indexer to work with articles (the patch in the root of the repo handles this)
- There is a baseline indexer for com_newsfeeds, but it needs to be reviewed to find the best way to gather data (Issue 17)
- Index Updater:
- Change state, save, and delete events converted to use native content plugin events
- JModelAdmin needs to be patched to fire the finder plugins during publish, delete, and save (patch in repo handles this)
- Need an event to replace the onChangeJoomlaCategory event
- Need an event to handle access changes from onChangeJoomlaXXX
- Administrator Module
- The module is working, but work is in progress to move it's functionality to a system plugin (see below)
- Site Component
- Site Module
- The module appears to be working as intended
- Content Plugin (former System Plugin for highlighting)
- The plugin appears to be working as intended
- Work is in progress to convert it to a reusable content plugin for use with all extensions
- A pull request is active against the Platform adding the highlighter HTML Helper and media (Pull Request 371 on Platform)
- System Plugin
- A new system plugin is being designed to handle the Finder script to automatically update indexed data
- The code has been copied out of the admin module, but is currently not auto-enabled or tested
- Optimally, the text output currently in the status bar should be added to the system debug output so this information is not lost in case troubleshooting is needed
- Finder plugins
- Each of the plugins for core methods have had basic review and refactoring to allow the indexer to run correctly
- All dependencies on section data have been broken
- Still needs further review and refactoring as methods are converted
- Most of the MooTools based code has been reviewed and most deprecated/removed methods from 1.2 have been replaced with the appropriate 1.3 methods
- The SliderFilter script needs to be fully converted to MooTools 1.3 (it was never updated from 1.1 and the slide functionality is currently lost) (Issue 29)
- All script needs to be tested
- Script needs to be reviewed and, where available, replaced with existing scripts from the system library
Work on conversion is being conducted from a GitHub repository until the extension package is 100% converted and ready to be feature requested into the CMS. At that point, the repository will move to a branch of the SVN where the package will be integrated into the core CMS installation.