Joomla! Documentation - User contributions [en]

Fatal-error-in-registration

2013-05-15T12:05:11Z

Chris Davenport: Improved formatting.

When registration is done with administrator activation you may get this error:
<pre>
Fatal error: Call to a member function where() on a non-object in
ROOT/components/com_users/models/registration.php on line 109
</pre>
Where <tt>ROOT</tt> is the path to your Joomla files.

To solve this, change line 108 of <tt>ROOT/components/com_users/models/registration.php</tt>

from
<source lang="php$>
->from($db->quoteName('#__users')
</source>
to
<source lang="php">
->from($db->quoteName('#__users'))
</source>
(There should be an additional ) at the end of the line.)

<noinclude>
[[Category:Version 3.1.0 FAQ]][[Category:Version 3.1.1 FAQ]]
</noinclude>

Web Services Working Group

2013-05-12T10:26:22Z

Chris Davenport: Added link to magazine article and note about Skype chat.

The Web Services Working Group is a [[Production Working Groups|Production Working Group]].

==Coordinators & PLT Contact==
* The coordinator for this working group is Ashwin Date (mailto:coolbung@gmail.com).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/76d499c6ec12840a?hl=en Web Services Working Group update 4 June 2012]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/4547aeb290723d87/7608dd58300bbe57?hl=en%E1%B6%B8dd58300bbe57 Request for comments on first draft of web API specification]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/6474890e2453c6c3?hl=en# Request for comments on second draft of web services API specification]
==External resources==
* [http://magazine.joomla.org/issues/issue-may-2013/item/1303-thinking-outside-the-platform Thinking outside the platform] is a general introduction to the importance of web services in Joomla.
* Recommended reading: [http://offers.apigee.com/api-design-ebook-rr/ Web API Design] by Brian Mulloy, Apigee (NOTE: Registration required)
* Stefan Neculai is a GSoC student working on a [https://github.com/stefanneculai/Web-service-API Web service API]. Read about him in the [http://magazine.joomla.org/issues/Issue-June-2012/item/772-RESTful-Web-Service-API Joomla Magazine].
* Aaron Schmitz has done some work on an [https://github.com/aaronschmitz/joomla-platform/blob/b2b68507006e4e575858e1d103a75f2a56907215/libraries/joomla/oauth/oauth.php OAuth 2.0 library]
* Louis Landry has created an [https://github.com/LouisLandry/joomla-platform/tree/oauth OAuth connector]. Also take a look at Louis's [https://github.com/joomla/joomla-platform/pull/1259 new router proposal].
* [REST API by Techjoomla for Joomla Separate app approach Presentation | http://www.slideshare.net/coolbung/joomla-rest-api]
* [REST API by Techjoomla for Joomla Separate app approach Github | https://github.com/techjoomla/Joomla-REST-API]
* [com_api approach | https://github.com/techjoomla/com_api]
* [com_api Plugins | https://github.com/techjoomla/com_api-plugins]
* [https://github.com/rcorral/com_api Rafael Corral's web API extension for Joomla 2.5]
* [[Xml-rpc|Note on current architecture used in Joomla 2.5]]
* [http://www.slideshare.net/HermanPeeren/webservices-connecting-joomla-with-other-programs-4399412 Herman Peeren's presentation at J and Beyond 2010]
* [https://groups.google.com/group/api-craft?hl=en API Craft] mailing list.
* [https://github.com/chrisdavenport/j3-rest-api Proof-of-concept implementation of draft API specification] for Joomla 3.x.
* [http://www.kickstarter.com/projects/964120480/joomla-web-services Kickstarter project for getting web services into Joomla 3.2]
==Deliverables==
Create a POC using com_users by using the extending it to add webservices to Adding, Editing users, Listing users. Added by Parth Lawate as per webservices group discussion at #JWC12

==Technical work produced by this group==
* 24 Dec 2012: First draft of [https://docs.google.com/document/d/1PfJg8ec9PWa8oumIPXbVlO0GY8_8KQoL1Tx47K5blGA/edit Request For Comments: A Web Service API for the Joomla CMS]
* 10 Feb 2012: Second draft of Web Services API Specification
** [https://docs.google.com/document/d/1FVKGlV6BN6pu-YH2WR2pQHE3Ez7M6r7LD417GSw9ZSo/edit?usp=sharing Joomla CMS Web Services API Specification]
** [https://docs.google.com/document/d/11SqH-daKQV9SrFBMEpopjBk3vM1USIHnFWZB9rjJB94/edit?usp=sharing application/vnd.joomla.base.v1 media type specification]
** [https://docs.google.com/document/d/1wg3AcgStA26UwDcbHVV1bub4sa_BhsKfzAmX21eG-FM/edit?usp=sharing application/vnd.joomla.service.v1 media type specification]
** [https://docs.google.com/document/d/16xwxSDDPW0U1CG9l7JcwOyGvyjm7wv5zOSd9JwgF2iQ/edit?usp=sharing application/vnd.joomla.item.v1 media type specification]
** [https://docs.google.com/document/d/1PLym28MG5v1tWyvIyW-9483JNKh5AP21Fmsmg62plnA/edit?usp=sharing application/vnd.joomla.list.v1 media type specification]
** [https://docs.google.com/document/d/1d5qQ16r1Bo1BlXXuyS_eFB4BQcfuSg05pn9hsMpAgqk/edit?usp=sharing Joomla CMS Web Service API Implementation]
** [https://docs.google.com/document/d/1wI3cSm3y4aa8n8rojJKpiF6RUpSl63WFuLgJj2WqW8o/edit?usp=sharing Joomla CMS CLI Services API Specification]
==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in web services, then we will most likely start a separate mailing list.

There is also a Skype chat for informal communications. Please request to be added by contacting Ashwin Date or Chris Davenport.

==Roadmap==
* Initial implementation of a limited set of functions in Joomla 3.2 (September 2013).
* Feature complete implementation in Joomla 3.5 (March 2014).

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Bad Nauheim, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California.
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], Noordwijkerhout, The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Web Services Working Group]]
[[Category:Working Groups]]

Ftp-update-not-working

2013-05-03T12:00:45Z

Chris Davenport: Typo.

There have been reports that updates with the FTP layer enabled are not working. Currently there is not a fix for this, but it is suggested that rather than use the updater you install the new Joomla version using the standard extension manager install. If that does not work, you can ftp the update zip filed to your host and unzip the new files, replacing the old ones. You will need to manually run the database changes using the appropriate version script found in administrator/components/com_admin/sql.

You will also need to manually delete the Flash uploader files from the media folder.
<noinclude>
[[Category:Version 2.5 FAQ]][[Category:Version 2.5.11 FAQ]][[Category:Version 3.1.0 FAQ]][[Category:Version 3.1.1 FAQ]]
</noinclude>

Web Services Working Group

2013-04-07T08:41:56Z

Chris Davenport: Added link to Kickstarter project.

The Web Services Working Group is a [[Production Working Groups|Production Working Group]].

==Coordinators & PLT Contact==
* The coordinator for this working group is Ashwin Date (mailto:coolbung@gmail.com).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/76d499c6ec12840a?hl=en Web Services Working Group update 4 June 2012]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/4547aeb290723d87/7608dd58300bbe57?hl=en%E1%B6%B8dd58300bbe57 Request for comments on first draft of web API specification]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/6474890e2453c6c3?hl=en# Request for comments on second draft of web services API specification]
==External resources==
* Recommended reading: [http://offers.apigee.com/api-design-ebook-rr/ Web API Design] by Brian Mulloy, Apigee (NOTE: Registration required)
* Stefan Neculai is a GSoC student working on a [https://github.com/stefanneculai/Web-service-API Web service API]. Read about him in the [http://magazine.joomla.org/issues/Issue-June-2012/item/772-RESTful-Web-Service-API Joomla Magazine].
* Aaron Schmitz has done some work on an [https://github.com/aaronschmitz/joomla-platform/blob/b2b68507006e4e575858e1d103a75f2a56907215/libraries/joomla/oauth/oauth.php OAuth 2.0 library]
* Louis Landry has created an [https://github.com/LouisLandry/joomla-platform/tree/oauth OAuth connector]. Also take a look at Louis's [https://github.com/joomla/joomla-platform/pull/1259 new router proposal].
* [REST API by Techjoomla for Joomla Separate app approach Presentation | http://www.slideshare.net/coolbung/joomla-rest-api]
* [REST API by Techjoomla for Joomla Separate app approach Github | https://github.com/techjoomla/Joomla-REST-API]
* [com_api approach | https://github.com/techjoomla/com_api]
* [com_api Plugins | https://github.com/techjoomla/com_api-plugins]
* [https://github.com/rcorral/com_api Rafael Corral's web API extension for Joomla 2.5]
* [[Xml-rpc|Note on current architecture used in Joomla 2.5]]
* [http://www.slideshare.net/HermanPeeren/webservices-connecting-joomla-with-other-programs-4399412 Herman Peeren's presentation at J and Beyond 2010]
* [https://groups.google.com/group/api-craft?hl=en API Craft] mailing list.
* [https://github.com/chrisdavenport/j3-rest-api Proof-of-concept implementation of draft API specification] for Joomla 3.x.
* [http://www.kickstarter.com/projects/964120480/joomla-web-services Kickstarter project for getting web services into Joomla 3.2]
==Deliverables==
Create a POC using com_users by using the extending it to add webservices to Adding, Editing users, Listing users. Added by Parth Lawate as per webservices group discussion at #JWC12

==Technical work produced by this group==
* 24 Dec 2012: First draft of [https://docs.google.com/document/d/1PfJg8ec9PWa8oumIPXbVlO0GY8_8KQoL1Tx47K5blGA/edit Request For Comments: A Web Service API for the Joomla CMS]
* 10 Feb 2012: Second draft of Web Services API Specification
** [https://docs.google.com/document/d/1FVKGlV6BN6pu-YH2WR2pQHE3Ez7M6r7LD417GSw9ZSo/edit?usp=sharing Joomla CMS Web Services API Specification]
** [https://docs.google.com/document/d/11SqH-daKQV9SrFBMEpopjBk3vM1USIHnFWZB9rjJB94/edit?usp=sharing application/vnd.joomla.base.v1 media type specification]
** [https://docs.google.com/document/d/1wg3AcgStA26UwDcbHVV1bub4sa_BhsKfzAmX21eG-FM/edit?usp=sharing application/vnd.joomla.service.v1 media type specification]
** [https://docs.google.com/document/d/16xwxSDDPW0U1CG9l7JcwOyGvyjm7wv5zOSd9JwgF2iQ/edit?usp=sharing application/vnd.joomla.item.v1 media type specification]
** [https://docs.google.com/document/d/1PLym28MG5v1tWyvIyW-9483JNKh5AP21Fmsmg62plnA/edit?usp=sharing application/vnd.joomla.list.v1 media type specification]
** [https://docs.google.com/document/d/1d5qQ16r1Bo1BlXXuyS_eFB4BQcfuSg05pn9hsMpAgqk/edit?usp=sharing Joomla CMS Web Service API Implementation]
** [https://docs.google.com/document/d/1wI3cSm3y4aa8n8rojJKpiF6RUpSl63WFuLgJj2WqW8o/edit?usp=sharing Joomla CMS CLI Services API Specification]
==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in web services, then we will most likely start a separate mailing list.

==Roadmap==
* Initial implementation of a limited set of functions in Joomla 3.2 (September 2013).
* Feature complete implementation in Joomla 3.5 (March 2014).

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Bad Nauheim, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California.
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], Noordwijkerhout, The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Web Services Working Group]]
[[Category:Working Groups]]

Search Working Group

2013-04-05T20:44:35Z

Chris Davenport: Updated list of outstanding tracker items.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** <s>[[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]</s>
*** <s>[[jtracker:28616|28616 - Add French language stemmer to Smart Search]]</s>
*** <s>[[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]</s>
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]] Testers required
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** <s>[[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]</s>
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** <s>[[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]</s>
*** <s>[[jtracker:29551|29551 - Fixed list_price and sale_price]]</s>
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** [[jtracker:30245|30245 - articles are not reindexed by finder plugin properly when their category access changes]]
*** <s>[[jtracker:30266|30266 - Array to string conversion in smart search]]</s>
*** [[jtracker:30392|30392 - Smart Search broken for multilingual sites]]
*** <s>[[jtracker:30419|30419 - using foreach with nonarray in com_finder's feed view]]</s>
*** [[jtracker:30478|30478 - com_finder - smart search not filtering unpublished articles]]
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Search Working Group

2013-03-30T16:59:37Z

Chris Davenport: Updated list of outstanding tracker items.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** <s>[[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]</s>
*** <s>[[jtracker:28616|28616 - Add French language stemmer to Smart Search]]</s>
*** <s>[[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]</s>
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]] Testers required
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** <s>[[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]</s>
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** <s>[[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]</s>
*** <s>[[jtracker:29551|29551 - Fixed list_price and sale_price]]</s>
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** [[jtracker:30245|30245 - articles are not reindexed by finder plugin properly when their category access changes]]
*** <s>[[jtracker:30266|30266 - Array to string conversion in smart search]]</s>
*** [[jtracker:30392|30392 - Smart Search broken for multilingual sites]]
*** <s>[[jtracker:30419|30419 - using foreach with nonarray in com_finder's feed view]]</s>
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Enabling Search Engine Friendly (SEF) URLs

2013-03-26T17:21:38Z

Chris Davenport: Reverted edits by Deadjdona (talk) to last revision by Jamil-mohammadi

{{:Search Engine Friendly URLs}}
The procedure for enabling Search Engine Friendly URLs differs depending on the web server you are using. If you are using shared hosting, it is probably Apache. Ask your hosting provider for more information if you are uncertain.

Only the most popular web servers have been included on this page. Visit [[Enabling Search Engine Friendly (SEF) URLs on IIS]] and [[:Category:Search Engine Friendly URLs]] for more articles.

== Apache ==
{{:Enabling Search Engine Friendly (SEF) URLs on Apache}}

== IIS 7 ==
{{:Enabling Search Engine Friendly (SEF) URLs on IIS/IIS7}}

== Nginx ==
{{:Enabling_Search_Engine_Friendly_(SEF)_URLs_on_Nginx}}

<noinclude>[[Category:Search Engine Friendly URLs]]
[[Category:Joomla! 1.5]]
[[Category:Joomla! 1.6]]</noinclude>

Search Working Group

2013-03-25T07:56:58Z

Chris Davenport: Updated list of outstanding tracker items.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** <s>[[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]</s>
*** <s>[[jtracker:28616|28616 - Add French language stemmer to Smart Search]]</s>
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]] Testers required
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** <s>[[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]</s>
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** <s>[[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]</s>
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** [[jtracker:30245|30245 - articles are not reindexed by finder plugin properly when their category access changes]]
*** <s>[[jtracker:30266|30266 - Array to string conversion in smart search]]</s>
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Search Working Group

2013-03-24T20:45:32Z

Chris Davenport: Updated list of outstanding tracker items.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** <s>[[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]</s>
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** <s>[[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]</s>
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** [[jtracker:30245|30245 - articles are not reindexed by finder plugin properly when their category access changes]]
*** <s>[[jtracker:30266|30266 - Array to string conversion in smart search]]</s>
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Production Working Groups/Permanent Working Groups

2013-03-23T21:01:24Z

Chris Davenport: Added Tom to coordinators/contacts for Doc WG.

==Bug Squad==
For further information see the [[Bug Squad]] page and [[Portal:Bug Squad|Bug Squad Portal]].

* Coordinator: [mailto:mark.dexter@community.joomla.org Mark Dexter]
* PLT Contact: [mailto:mark.dexter@community.joomla.org Mark Dexter]

==Documentation Working Group==
The [[Documentation Working Group]] is a standing team of people dedicated to improving Joomla's documentation. This includes both user and developer documentation. Our primary focus is this wiki, but we are also responsible for maintaining [http://api.joomla.org api.joomla.org] and other resources.

* Coordinators: [mailto:tom.hutchison@community.joomla.org Tom Hutchison], [mailto:chris.davenport@joomla.org Chris Davenport]
* PLT Contacts: [mailto:tom.hutchison@community.joomla.org Tom Hutchison], [mailto:chris.davenport@joomla.org Chris Davenport]

==Joomla Security Strike Team==
This team is for experienced Joomla users and developers who want to help test and fix reported security issues. If you are interested in helping, please contact Mark Dexter. Thanks!

* Coordinator: [mailto:mark.dexter@community.joomla.org Mark Dexter]
* PLT Contact: [mailto:mark.dexter@community.joomla.org Mark Dexter]

==Translations Working Group==
For further information see [[Translations Working Group]].

* Coordinator: Jean-Marie Simonet
* PLT Contact: To be determined.

==User Experience Working Group==
The [[User Experience Working Group]] is a standing team focused on the Joomla User Experience. This includes the Joomla administrator user interface, sample templates, sample data and any other related aspects. For further information see [http://ux.joomla.org/ The Joomla User Experience Portal].

* Coordinator: [mailto:ron.severdia@joomla.org Ron Severdia]
* PLT Contact: [mailto:ron.severdia@joomla.org Ron Severdia]

<noinclude>[[Category:Landing subpages]]</noinclude>

Production Working Groups/Current Working Groups

2013-03-23T20:42:01Z

Chris Davenport: Removed dead link.

==Database Working Group==
There's plenty of work to do to improve the way that Joomla works with databases. We need database experts who can look at optimising queries, improving the data model and making Joomla work across multiple databases. If you are a database junkie and you'd like to help then contact Mark Dexter.

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

* Coordinator: '''Open'''
* PLT Contact: [mailto:mark.dexter@community.joomla.org Mark Dexter]

==Internet of Things Working Group==
This working group is looking into using the Joomla Platform to simplify and open source the "internet of things". Using several popular input/output devices to allow the world to connect to the internet and back to the world; for the device's data to be easily displayed on Joomla sites and Joomla sites to "talk back" to the environment.

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

* Coordinator: [mailto:phil@jthings.co.uk Phil Walton]
* PLT Contact: [mailto:chris.davenport@joomla.org Chris Davenport]

==JavaScript Working Group==

* Coordinator: Joe LeBlanc
* PLT Contact: [mailto:andrea.tarr@joomla.org Andy Tarr]

For further information see [[JavaScript Working Group]]

==Multi-site Working Group==

* Coordinator: Open
* PLT Contact: [mailto:mark.dexter@community.joomla.org Mark Dexter]

'''This group is currently inactive. If you are interested in working on this issue, contact Mark Dexter.'''

For further information see [[Multi-site Working Group]]

==Message Queue Working Group==

* Coordinator: [mailto:chris.davenport@joomla.org Chris Davenport]
* PLT Contact: [mailto:chris.davenport@joomla.org Chris Davenport]

'''This group is currently inactive. If you are interested in working on this issue, contact Chris Davenport.'''

For further information see: [[Message Queue Working Group]].

==Search Working Group==
Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series.

* Coordinator: Open.
* PLT Contact: [mailto:chris.davenport@joomla.org Chris Davenport]

For further information see [[Search Working Group]]

==Unified Content Model Working Group==
This is a working group for looking at how the CMS could take advantage of UCM.

* Coordinator: Elin Waring
* PLT Contact: To be determined.

For further information see [[Unified Content Model Working Group]]

==Unit Tests for CMS Working Group==

* Coordinator: Michael Babker
* PLT Contact: To be determined.

For further information see [[Unit Tests for CMS Working Group]]

==Update and Migration Working Group==
The Update and Migration Working Group looks to solve the immediate problem of Joomla 1.5 to 2.5+ core migration with extensibility to extensions of all types.

* Coordinator: [mailto:robert.jacobi@arctg.com Robert Jacobi]
* PLT Contact: [mailto:mark.dexter@community.joomla.org Mark Dexter]

For further information see [[Update and Migration Working Group]]

==Web Services Working Group==

* Coordinator: [mailto:coolbung@gmail.com Ashwin Date]
* PLT Contact: [mailto:chris.davenport@joomla.org Chris Davenport]

For further information see [[Web Services Working Group]]

<noinclude>[[Category:Landing subpages]]</noinclude>

Search Working Group

2013-03-23T20:20:35Z

Chris Davenport: Updated list of outstanding tracker items.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** [[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** <s>[[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]</s>
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** [[jtracker:30245|30245 - articles are not reindexed by finder plugin properly when their category access changes]]
*** [[jtracker:30266|30266 - Array to string conversion in smart search]]
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Enabling Search Engine Friendly (SEF) URLs on IIS/IIS7

2013-03-20T13:13:07Z

Chris Davenport: Reverted edits by Jamil-mohammadi (talk) to last revision by Mvangeest

If you have a server running IIS 7 and PHP, you can take advantage of IIS's own internal URL rewriting by using a web.config file similar to the one listed below.

You can create the file yourself or use the GUI in the IIS7 Manager. You can import .htaccess rules using the GUI/wizard.

This functionality depends on the presence of the '''IIS URL Rewrite Module''', which does not come with Windows. It is a free download and a Microsoft product.

===GUI===
If the IIS URL Rewrite module is installed, your website manager will have a tool for "URL Rewrite", visible in the IIS Manager's view of your site's configurable IIS modules. The interface is largely self-explanatory. Regular expressions, wildcards or exact matches are all supported.

In the Joomla config turn on both the SEF and Apache mod_rewrite, next create a rule under IIS URL Rewrite:
:Pattern field: '''^([^/]+)/?$'''
:Ignore case '''ON'''
:Action type: '''Rewrite'''
:Rewrite URL: '''index.php/'''

===web.config===
This has been tested on Joomla 1.5 with IIS 7 on Windows Server 2008 with no problems so far. For more information on converting .htaccess to web.config, check out http://learn.iis.net/page.aspx/557/translate-htaccess-content-to-iis-webconfig/

<source lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<rewrite>
<rules>
<clear />
<rule name="Common Exploit Blocking" stopProcessing="true">
<match url="^(.*)$" />
<conditions logicalGrouping="MatchAny">
<add input="{QUERY_STRING}" pattern="mosConfig_[a-zA-Z_]{1,21}(=|\%3D)" />
<add input="{QUERY_STRING}" pattern="base64_encode.*$.*$" />
<add input="{QUERY_STRING}" pattern="(\<|%3C).*script.*(\>|%3E)" />
<add input="{QUERY_STRING}" pattern="GLOBALS(=|\[|\%[0-9A-Z]{0,2})" />
<add input="{QUERY_STRING}" pattern="_REQUEST(=|\[|\%[0-9A-Z]{0,2})" />
</conditions>
<action type="Redirect" url="index.php" appendQueryString="false" redirectType="SeeOther" />
</rule>
<rule name="Joomla Search Rule" stopProcessing="true">
<match url="(.*)" ignoreCase="true" />
<conditions logicalGrouping="MatchAll">
<add input="{URL}" pattern="^/search.php" ignoreCase="true" />
</conditions>
<action type="Rewrite" url="/index.php?option=com_content&view=article&id=4" />
</rule>
<rule name="Joomla Main Rewrite Rule" stopProcessing="true">
<match url="(.*)" ignoreCase="true" />
<conditions logicalGrouping="MatchAll">
<add input="{URL}" pattern="(/[^.]*|\.(php|html?|feed|pdf|raw))$" />
<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
</conditions>
<action type="Rewrite" url="index.php/" />
</rule>
</rules>
</rewrite>
<caching>
<profiles>
<add extension=".php" policy="DisableCache" kernelCachePolicy="DisableCache" />
</profiles>
</caching>
</system.webServer>
</configuration>

</source>
<noinclude>
[[Category:IIS]]
[[Category:Search Engine Friendly URLs]]
</noinclude>

Events Working Group

2013-03-18T12:38:24Z

Chris Davenport: Reverted edits by Guvenguv (talk) to last revision by Hutchy68

The events working group or better the team of events mentors is responsible for the support for all world wide events. There is a small team of mentors that assist the regional organizers in their preparation for Joomla!Days or help the regional JUG's to participate on an exhibition or conference.

You can find further details about Joomla! events on the community page at: [http://community.joomla.org/events.html http://community.joomla.org/events.html]

==Events Team Wiki==
We intend to grow this wiki with further information and guidelines how to organize your event. If you have suggestions ideas and so on please feel free to add a page to this wiki below.

== Follow us on Twitter ==

[http://twitter.com/joomlaevents joomlaevents]

[[Category:Working Groups]][[Category:Events Working Group]][[Category:Events]]

Web Services Working Group

2013-03-16T22:24:18Z

Chris Davenport: Added link to experimental implementation on GitHub.

The Web Services Working Group is a [[Production Working Groups|Production Working Group]].

==Coordinators & PLT Contact==
* The coordinator for this working group is Ashwin Date (mailto:coolbung@gmail.com).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/76d499c6ec12840a?hl=en Web Services Working Group update 4 June 2012]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/4547aeb290723d87/7608dd58300bbe57?hl=en%E1%B6%B8dd58300bbe57 Request for comments on first draft of web API specification]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/6474890e2453c6c3?hl=en# Request for comments on second draft of web services API specification]
==External resources==
* Recommended reading: [http://offers.apigee.com/api-design-ebook-rr/ Web API Design] by Brian Mulloy, Apigee (NOTE: Registration required)
* Stefan Neculai is a GSoC student working on a [https://github.com/stefanneculai/Web-service-API Web service API]. Read about him in the [http://magazine.joomla.org/issues/Issue-June-2012/item/772-RESTful-Web-Service-API Joomla Magazine].
* Aaron Schmitz has done some work on an [https://github.com/aaronschmitz/joomla-platform/blob/b2b68507006e4e575858e1d103a75f2a56907215/libraries/joomla/oauth/oauth.php OAuth 2.0 library]
* Louis Landry has created an [https://github.com/LouisLandry/joomla-platform/tree/oauth OAuth connector]. Also take a look at Louis's [https://github.com/joomla/joomla-platform/pull/1259 new router proposal].
* [REST API by Techjoomla for Joomla Separate app approach Presentation | http://www.slideshare.net/coolbung/joomla-rest-api]
* [REST API by Techjoomla for Joomla Separate app approach Github | https://github.com/techjoomla/Joomla-REST-API]
* [com_api approach | https://github.com/techjoomla/com_api]
* [com_api Plugins | https://github.com/techjoomla/com_api-plugins]
* [https://github.com/rcorral/com_api Rafael Corral's web API extension for Joomla 2.5]
* [[Xml-rpc|Note on current architecture used in Joomla 2.5]]
* [http://www.slideshare.net/HermanPeeren/webservices-connecting-joomla-with-other-programs-4399412 Herman Peeren's presentation at J and Beyond 2010]
* [https://groups.google.com/group/api-craft?hl=en API Craft] mailing list.
* [https://github.com/chrisdavenport/j3-rest-api Experimental implementation of draft API specification] for Joomla 3.x.

==Deliverables==
Create a POC using com_users by using the extending it to add webservices to Adding, Editing users, Listing users. Added by Parth Lawate as per webservices group discussion at #JWC12

==Technical work produced by this group==
* 24 Dec 2012: First draft of [https://docs.google.com/document/d/1PfJg8ec9PWa8oumIPXbVlO0GY8_8KQoL1Tx47K5blGA/edit Request For Comments: A Web Service API for the Joomla CMS]
* 10 Feb 2012: Second draft of Web Services API Specification
** [https://docs.google.com/document/d/1FVKGlV6BN6pu-YH2WR2pQHE3Ez7M6r7LD417GSw9ZSo/edit?usp=sharing Joomla CMS Web Services API Specification]
** [https://docs.google.com/document/d/11SqH-daKQV9SrFBMEpopjBk3vM1USIHnFWZB9rjJB94/edit?usp=sharing application/vnd.joomla.base.v1 media type specification]
** [https://docs.google.com/document/d/1wg3AcgStA26UwDcbHVV1bub4sa_BhsKfzAmX21eG-FM/edit?usp=sharing application/vnd.joomla.service.v1 media type specification]
** [https://docs.google.com/document/d/16xwxSDDPW0U1CG9l7JcwOyGvyjm7wv5zOSd9JwgF2iQ/edit?usp=sharing application/vnd.joomla.item.v1 media type specification]
** [https://docs.google.com/document/d/1PLym28MG5v1tWyvIyW-9483JNKh5AP21Fmsmg62plnA/edit?usp=sharing application/vnd.joomla.list.v1 media type specification]
** [https://docs.google.com/document/d/1d5qQ16r1Bo1BlXXuyS_eFB4BQcfuSg05pn9hsMpAgqk/edit?usp=sharing Joomla CMS Web Service API Implementation]
** [https://docs.google.com/document/d/1wI3cSm3y4aa8n8rojJKpiF6RUpSl63WFuLgJj2WqW8o/edit?usp=sharing Joomla CMS CLI Services API Specification]
==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in web services, then we will most likely start a separate mailing list.

==Roadmap==
* Initial implementation of a limited set of functions in Joomla 3.2 (September 2013).
* Feature complete implementation in Joomla 3.5 (March 2014).

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Bad Nauheim, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California.
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], Noordwijkerhout, The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Web Services Working Group]]
[[Category:Working Groups]]

Pizza Bugs and Fun March 16, 2013

2013-03-12T16:21:50Z

Chris Davenport: Merged prior edit by Parth Lawate.

<div style="float:right; margin-left:1em;">__TOC__</div>
<div style="float:left; margin-right:1em;">[[Image:pbf.png|225px]]</div>

We are announcing a second Joomla! Pizza, Bugs and Fun event scheduled for Saturday, March 16, 2013. The event is global for virtual participants with local venues wherever they are organized. The key goal is to fix as many Joomla 3 and Joomla 2.5 bugs as possible before Joomla 3.1's, which will be on or around the 25th of March, and Joomla 2.5.10's release.

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_March_16,_2013#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #JoomlaPBF.
<div style="clear:left;" />
== Goals ==
* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.
* '''Documentation''' : If you want to help out writing documentation, you're also more than welcome. See the [http://docs.joomla.org/Pizza_Bugs_and_Fun_March_16,_2013#If_you_want_to_work_on_Documentation Documentation Details] below for suggestions.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF last September. To get an invitation, add nick.savov to your Skype contact list. To make sure you can get in, log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to your test instance of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester. If the test is successful check of a successful text box.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bugs_and_Fun_March_16,_2013#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

:<h5>Helpful Documentation</h5>
:* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
:* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

:<h5>Helpful documentation</h5>
:* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
:* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
:* [[Git for Testers and Trackers]]
:* [[Working with git and github/My first pull request]]
:* [[Secure coding guidelines]]
:* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* [Will add in the coming weeks]

=== Pizza ===
We are offering pizza (or any comparable locally popular main course) and soda for pre-registered groups. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Nick Savov (nick.savov[at]community.joomla[dot]org , replace [at] with @ and [dot] with .) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Nick Savov (nick.savov[at]community.joomla[dot]org , replace [at] with @ and [dot] with .). Feel free to contact him with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, add nick.savov to your Skype contact list. To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===

[http://www.viryatechnologies.com Virya Technologies] - 30 The Junction, Mallard House Business Centre, The Street, Little Bealings, Woodbridge, Suffolk, IP13 6LT - Space for 5-10 extra people (please email info@viryatechnologies.com if you want to join us!) - 0900-1800h

=== North America ===
[http://www.joomladayboston.com/schedule-sessions-speakers.html Joomla!Day Boston Bug Squash Events] Microsoft New England Research & Development Center
One Memorial Drive
Suite 100
Cambridge, MA 02142.
10:00 AM-12:15 PM EST and 1:30 PM-4:00 PM EST . Visit http://www.joomladayboston.com/ for more information.

[http://www.joomlachicagoloop.com/component/registrationpro/event/11/Joomla-Pizza-Bugs-and-Fun?Itemid=160 JoomlaChicago LOOP User Group Event]
The COOP - Cowork Space in Chicago
230 W Superior, 2nd Floor (Entrance on Franklin under the "L")
Chicago, IL 60654
10:00 AM - 3:00 PM
Note: Please sign-up at the link above to receive more information and directions on accessing the location on March 16.
'''''Space is limited!!!'''''

=== South America ===

=== Asia/Pacific ===
[http://marvelic.co.th Marvelic Engine Co.,Ltd.] : 719 KPN Tower 10/F, Rama 9 Road. Huaykwang, Bangkok. THAILAND. Tel.+66 2 717 1120 . Time : 1:00PM. - 5:30PM. [UTC+7]

[http://techjoomla.com Techjoomla, Tekdi Web Solutions] : 106, Saket Apts.Vithal Mandir Road.Karvenagar. Pune 411052. Maharashtra India. Tel.+91 020 25457905 . Time : 1:00PM. - 5:30PM. [GMT+5.5]. Please get your Laptops . Wifi & Pizza will be provided :)
=== Africa ===

=== Middle East ===

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_March_16,_2013#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun March 16, 2013/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://svn.github.com/joomla/joomla-cms

Q: Which one is 3.0?

A: On GitHub, it is the master branch.

Q: Which one is 2.5?

A: On GitHub, it is the 2.5.x branch.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun March 16, 2013/Contributors List}}

<noinclude>[[Category:Bug Squad]]
[[Category:Development]][[Category:Events]]</noinclude>

Pizza Bugs and Fun March 16, 2013

2013-03-12T16:20:17Z

Chris Davenport: Reverted edits by Parthlawate (talk) to last revision by Rkendallc

<div style="float:right; margin-left:1em;">__TOC__</div>
<div style="float:left; margin-right:1em;">[[Image:pbf.png|225px]]</div>

We are announcing a second Joomla! Pizza, Bugs and Fun event scheduled for Saturday, March 16, 2013. The event is global for virtual participants with local venues wherever they are organized. The key goal is to fix as many Joomla 3 and Joomla 2.5 bugs as possible before Joomla 3.1's, which will be on or around the 25th of March, and Joomla 2.5.10's release.

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_March_16,_2013#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #JoomlaPBF.
<div style="clear:left;" />
== Goals ==
* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.
* '''Documentation''' : If you want to help out writing documentation, you're also more than welcome. See the [http://docs.joomla.org/Pizza_Bugs_and_Fun_March_16,_2013#If_you_want_to_work_on_Documentation Documentation Details] below for suggestions.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF last September. To get an invitation, add nick.savov to your Skype contact list. To make sure you can get in, log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to your test instance of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester. If the test is successful check of a successful text box.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bugs_and_Fun_March_16,_2013#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

:<h5>Helpful Documentation</h5>
:* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
:* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

:<h5>Helpful documentation</h5>
:* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
:* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
:* [[Git for Testers and Trackers]]
:* [[Working with git and github/My first pull request]]
:* [[Secure coding guidelines]]
:* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* [Will add in the coming weeks]

=== Pizza ===
We are offering pizza (or any comparable locally popular main course) and soda for pre-registered groups. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Nick Savov (nick.savov[at]community.joomla[dot]org , replace [at] with @ and [dot] with .) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Nick Savov (nick.savov[at]community.joomla[dot]org , replace [at] with @ and [dot] with .). Feel free to contact him with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, add nick.savov to your Skype contact list. To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===

[http://www.viryatechnologies.com Virya Technologies] - 30 The Junction, Mallard House Business Centre, The Street, Little Bealings, Woodbridge, Suffolk, IP13 6LT - Space for 5-10 extra people (please email info@viryatechnologies.com if you want to join us!) - 0900-1800h

=== North America ===
[http://www.joomladayboston.com/schedule-sessions-speakers.html Joomla!Day Boston Bug Squash Events] Microsoft New England Research & Development Center
One Memorial Drive
Suite 100
Cambridge, MA 02142.
10:00 AM-12:15 PM EST and 1:30 PM-4:00 PM EST . Visit http://www.joomladayboston.com/ for more information.

[http://www.joomlachicagoloop.com/component/registrationpro/event/11/Joomla-Pizza-Bugs-and-Fun?Itemid=160 JoomlaChicago LOOP User Group Event]
The COOP - Cowork Space in Chicago
230 W Superior, 2nd Floor (Entrance on Franklin under the "L")
Chicago, IL 60654
10:00 AM - 3:00 PM
Note: Please sign-up at the link above to receive more information and directions on accessing the location on March 16.
'''''Space is limited!!!'''''

=== South America ===

=== Asia/Pacific ===
[http://marvelic.co.th Marvelic Engine Co.,Ltd.] : 719 KPN Tower 10/F, Rama 9 Road. Huaykwang, Bangkok. THAILAND. Tel.+66 2 717 1120 . Time : 1:00PM. - 5:30PM. [UTC+7]

=== Africa ===

=== Middle East ===

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_March_16,_2013#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun March 16, 2013/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://svn.github.com/joomla/joomla-cms

Q: Which one is 3.0?

A: On GitHub, it is the master branch.

Q: Which one is 2.5?

A: On GitHub, it is the 2.5.x branch.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun March 16, 2013/Contributors List}}

<noinclude>[[Category:Bug Squad]]
[[Category:Development]][[Category:Events]]</noinclude>

J2.5:Use an existing Joomla! site

2013-03-12T11:06:16Z

Chris Davenport: Reverted edits by Adarshame (talk) to last revision by Rafa.trevisan

{{version/tutor|1.6,1.7,2.5}}{{:Getting_Started_Page_Index/2.5}}
The aim of this short introduction is to help you use a site that has already been set up so that you feel that you are not just using a mysterious back box.

==Introduction==

===Who is it written for?===
:*Everyone.
:*The main focus is on people who do not have much experience of using web sites.
You also need:-
:*to have access to a Joomla! site with an appropriate level of permission

Many people start to use a web site that has been set up using Joomla! You are especially likely to do this if you are going to be adding content to an existing site and do not expect to go further with managing the site.

You do need to know something about the site and where the Articles are located. This will vary a great deal from site to site, so (obviously!) cannot be covered here in detail.

===How to login===
You will need a username with the right permissions for what you are going to do, such as add and edit articles.

You will be given a username (sometimes called a login) to allow you to alter the content of a site. This shows you how to login once you have a username and password. The positioning of the Login Form can vary but many sites place this to the left of the screen beneath the menus.
*Open the site in your browser
{{:How to login16}}

=== Usernames and permissions to see and do things===
Permissions are sometimes referred to as 'access control'.

Joomla! allows content to be created and edited by visitors who login with a username with appropriate permissions.
:*The usernames are created, and the permissions defined, by the person who looks after the Web site, usually called the Administrator.

In Joomla! 2.5 there are a number of pre-defined groups relevant to adding and editing Articles in a Joomla! Web site. Some web sites have many more groups, allowing access to specific parts of the site for specific people. You will need to know which group you are in and what rights you have to view and edit articles.

Typical groups include:-
* '''Guests:''' Some website visitors never login and are just able to read the content. They may also be limited in the pages they can see.
*'''Registered users:''' Others can login but have 'read only' access to the site - in other words they cannot alter anything.
*'''Author or Editor:''' You may be given 'author' or 'editor' permissions, which normally allows you to edit and add Articles, but does not allow you to 'publish' them. Authors can usually only edit articles that they have created.
*'''Publisher:''' Publishing an article makes it visible to visitors to the web site. You may have some 'publisher' permissions, which allows you to publish articles, as well as adding and editing them.

==Where Next?==
Once you have logged in to the site, there is a hands-on document (part of this series) to introduce you to altering an Article.
*[[Hands-on editing an article: Joomla! 1.6|Hands-on how to begin to edit an Article.]]

This will help you to become familiar with editing in Joomla!

==Further information==

There are other levels of access for managing a site. Access Control in Joomla! 1.6 is more granular than in earlier versions. You would need to know about this for looking after or creating a site, but the full detail is not needed for simply editing and adding content.

*[[How permissions work in Joomla! 1.6 |Controlling user access to a Joomla! Site]]

GSOC 2013 Project Ideas

2013-03-06T13:10:19Z

Chris Davenport: Added forum link and tidied up another link.

{{RightTOC}}

==Welcome!==
Welcome to the Joomla! Google Summer of Code (GSoC) 2013 project ideas page. As we move forward with the 2013 version of the Joomla! GSoC, we will use this page to develop possible project ideas. Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest possible project ideas. Please keep in mind that projects need to be realistically something that is able to be functionally completed by a student working full time for about eight weeks. Thanks!

Discussion of ideas and other GSoC related items is welcome on our Google Group: https://groups.google.com/forum/?fromgroups#!forum/joomla-gsoc-2013

If you are interested in participating as a student please review the materials on applying that are available at [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page]. We strongly encourage you to ask questions about process and ideas on the mailing list.

If you are interested in serving as a mentor, please fill out the [https://docs.google.com/a/community.joomla.org/spreadsheet/viewform?formkey=dHA2V1lJbThYQXpwMERiRG1FOTZlV3c6MA Mentor Application Form 2013].

==Ideas==

Opportunities exist for students to work with projects from either the Joomla CMS, the Joomla Platform or in some cases a combination of both.

In addition to this ideas list, the Joomla! Community is able to voice their opinion on features they would like to see via the [http://ideas.joomla.org/ Joomla! Idea Pool]. Those wishing to add ideas to this listing are encouraged to review the Idea Pool and base their idea on the input received there. You can also view the past lists for [http://docs.joomla.org/GSOC_2012_Project_Ideas 2012] [http://docs.joomla.org/Summer_of_Code_2010_Project_Ideas 2010] and [http://docs.joomla.org/Summer_of_Code_2009_Project_Ideas 2009], which may be useful for reference. We ask that you keep ideas realistic for the time frame that students will have to complete their projects.

Unless a mentor has proposed a specific project, mentors from the mentor pool will be matched with student projects. However members of the mentor pool are available to answer questions on the Joomla GSoC mailing list.

===Joomla CMS===

* [http://github.com/joomla/joomla-cms Source Code]
* [http://groups.google.com/d/forum/joomla-dev-cms Developer Mailing List]

====Project: Refactor Media Manager====

:'''Brief Explanation:''' The current media manager is outdated and limited. Refactor the media manager to include a better user interface, more robust functionality, and seemless integration for extensions to use. The improvements could include: add other not yet supported medias (PDF, MP·,...), providing a folder tree, file property information, upload capabilities, move/rename files and folders, use of JImage for image basic processing (resize, crop).

:'''Expected Results:''' Refactor the Media Manager to improve the usability, functionality, and reusability of the extension.

:'''Knowledge Prerequisite:''' Joomla Platform, PHP, MySQL, Javascript

:'''Difficulty:''' Medium

====Project: Convert JavaScript from MooTools to jQuery====

:'''Brief explanation:''' Version 3 of the CMS introduced [http://twitter.github.com/bootstrap Twitter Bootstrap] and [http://jquery.com jQuery] to the core code base. Previous versions of the CMS had been using MooTools as the preferred JavaScript library. Currently, both JavaScript libraries are shipped and used within the CMS, which occasionally causes conflicts with a user's JavaScript functionality. The CMS would like to reduce the dependency on MooTools by converting its core JavaScript behaviors from MooTools to jQuery.

:'''Expected Results:''' Dependency on MooTools is reduced within the CMS.

:'''Knowledge Prerequisite:''' Joomla CMS, PHP, JavaScript

:'''Difficulty:''' Medium

====Project: html contenteditable front-end editor for content, categories and modules====

:'''Brief explanation:''' Allow seamless ajax-driven content-editing in the fronted of existing content and allowing to insert new modules.

:'''Expected Results:''' Authors with ACL permissions should be able to directly edit the content (content and categories descriptions and titles) and modules (titles and content/settings, and inserting new modules as well from the front-end. The modules and content parameters editing should not be re-invented but just use the administration interface, if possible in front-end, otherwise with links to the corresponding administration page. This would at least allow to remove the guesswork of which module outputs what result. Using an open-source html-contenteditable javascript editor would help here in the formatting.

:'''Knowledge Prerequisite:''' A good knowledge of Joomla, of jQuery and Ajax techniques would help a lot here.

:'''Difficulty:''' Medium to Hard

====Project: Add field 'created' in frontend article edit view====

:'''Brief explanation:''' When creating or modifying an article via frontend, the 'created' date is set automatically. Add an input 'created' wherein the date of creation can be modified.

:'''Expected Results:''' The 'created' date of an article can be modified freely and even set to a future date.

:'''Knowledge Prerequisite:''' PHP, little HTML

:'''Difficulty:''' Easy

====Project: Add plugin 'modal'====

:'''Brief explanation:''' Generate a plugin that sets add the modal behaviour (JHTML::_('behavior.modal');). The plugin can be deactivated by a {}tag (like {modal state=0}).

::Create some buttons for backend as well, that allows to create links with the modal attribute.

::Background: A link with the attribute 'class="modal"' is opened in a kind of lightbox. Thus easily galleries can be generated. Additionally prepare editor(s) (e. g. via editor.css in template folder) to offer the modal class in their link edit display.

:'''Expected Results:''' The modal behaviour is always available - if plugin is published and it is not forbidden by a tag. And a link with class 'modal' can easily be generated - via button and/or via editor.

:'''Knowledge Prerequisite:''' PHP, HTML, Javascript

:'''Difficulty:''' Easy/Medium

====Project: Add plugin 'mvc override'====

:'''Brief explanation:''' Generate a plugin that enables the developer to overwrite models and controllers.

:'''Expected Results:''' Any model and controller can be overridden.

:'''Knowledge Prerequisite:''' Joomla! CMS, PHP

:'''Difficulty:''' Medium

====Project: Hathor is beautiful====

:'''Brief explanation:''' Make the admin template 'Hathor' more beautiful. Hathor is Isis' little sister. While Isis is breathtaking, Hathor still lacks a little css: She's edgy, and pale, and boring. Yet she always does what she is told. She deserves being tended a little. No additional functionality needed, no html changes, just css beauty.

:'''Expected Results:''' Hathor is beautiful.

:'''Knowledge Prerequisite:''' CSS

:'''Difficulty:''' Easy

====Project: Refactor document model containers====

:'''Brief explanation:''' When I say document model containers, what I'm really talking about is all those arrays in the document model that store things like metas, scripts, css, etc. Those can be rendered collectively in the template using the jdoc head tag. The project would refactor the document model to allow more robust methods of working with document containers. One solution would be to use PHP ArrayObjects instead of simple arrays.

:'''Expected Results:''' A robust solution should allow methods for appending and prepending items, method chaining, and the ability to create custom containers from within extensions and templates.

:'''Knowledge Prerequisite:''' Joomla! CMS, PHP, some html, some css, and some javascript.

:'''Difficulty:''' Medium

:'''References:'''
:* Joomla! Forums topic: [[jtopic:793482|The ArrayObject - a different approach to document containers]]
:: (the editor would not allow me to post the link)

====Project: Add fieldtype 'oclock' in fields====

:'''Brief explanation:''' Joomla!'s form generation offers a fix group of field types, such as text, textarea, radio, calendar etc. Write another field that enables the developer to create a time field, call it 'oclock' or something else sensible. The display of the time should be configurable via a format attribute. It should have the look'n'feel of the calendar field ([[Calendar form field type|Calendar form field type]])

:'''Expected Results:''' Generation of a time field called in xml via <field type="oclock" .../>

:'''Knowledge Prerequisite:''' PHP, HTML, Javascript

:'''Difficulty:''' Medium

{{dablink|Please add your project ideas here, you can use this '''[[GSOC 2013 Project template]]'''}}

===Joomla Platform===

The Joomla Platform allows for ideas that can work within the Joomla CMS, or could be completely separate applications that have no connection at all. The Joomla Platform allows for applications to be built for the command line, process daemons and the web. The follow list outlines some ideas that will be immediately useful for the Joomla Platform project that a student may consider taking on. In addition to PHP libraries, the Joomla Platform also ships with MooTools and project ideas can be related to client-side operations as well as server-side. One emphasis on this year's list is on the incorporation of packages for accessing web services, however other ideas for libraries and packages are welcome. In some instances multiple students may work on different aspects of the project. Two examples of this are unit testing and JStemmer.

References:
*[http://github.com/joomla/joomla-platform github Source Code]
*[http://developer.joomla.org/strategy.html Development Strategy]
*[http://groups.google.com/d/forum/joomla-dev-platform Developer Mailing List]

All code contributions must follow Joomla coding standards and include full unit test coverage.

====Project: Platform Unit Testing====

:'''Brief explanation:''' The Joomla Platform has a good suite of automated Unit Tests, but code coverage is lacking in some areas. The goal of this project is to improve the code coverage by writing unit tests for the Joomla Platform.

:'''Expected Results:''' The student will be expected to review the current [http://developer.joomla.org/coverage/ code coverage report] for the Joomla Platform and write and agreed-upon number of unit tests with particular attention to packages that are below 50% coverage. Preference should be given to non-deprecated classes but the student may choose from either the core tree (/libraries/joomla) or the legacy tree (/libraries/legacy).

:'''Knowledge Prerequisite:''' PHP, PHPUnit

:'''Difficulty:''' Medium

====Project: Object Relational Mapping (ORM) in Joomla====

:'''Explanation:''' Joomla uses an Active Record implementation. Via JTable and JTableNested data are CRUDded in models to and from database tables. Tables for different content types share the same kind of data and therefore code is duplicated. There are plans to solve this with a Unified Content Model (UCM), which would use a shared table for all content and a specialised table per content type. In order to implement that the MVC was simplified and decoupled from several dependecies. A JData class was made to store data in and a JDataMapper to map the database tables (the general content table and the specialised table for the content type) to the data. In terms of Martin Fowler's Patterns of Enterprise Architecture Patterns (PEAA, page 285-292): Class Table Inheritance. This UCM would be a replacement for the current JTable classes.

:This new model still has aspects of the Active Record pattern. A more general Data Mapper would make some implementations easier, especially when one-to-many and many-to-many relations are in play. A lot of this has already been worked out in the PHP-world with ORM-frameworks like Propel and Doctrine. No need to reinvent a complete new wheel; nowadays you can easily integrate other frameworks using Composer/Packagist. Some work has been done to use Doctrine ORM in Joomla extensions, but a more general approach would be great. The JDataMapper-class could eventually be a special case of this, or, as intended, be an interface between JData and a full blown ORM. The UCM-plans would be realised, but in a more general, object oriented and extendible way.

:'''Expected Results:''' The focus for a GSOC-project could be on a more general ORM interface in which specific ORM packages could fit, or could be a specific implementation (like Doctrine) with which core CMS extensions could be refactored. Both the Joomla Platform and the CMS would benefit from this project.

:'''Knowledge Prerequisite:''' Object Relational Mapping theory.

:'''References:'''
:* http://martinfowler.com/eaaCatalog/ and http://www.martinfowler.com/books/eaa.html
:* http://propelorm.org/documentation/
:* http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/index.html
:* https://github.com/eBaySF/joomla-platform/blob/data-package/docs/manual/en-US/chapters/packages/data.md#jdatamapper
:* https://github.com/joomla/joomla-platform/pull/1746

"As I'm using Doctrine when building complex Joomla extensions, I'd love to mentor this project" ~ Herman Peeren

{{dablink|Please add your project ideas here, you can use this '''[[GSOC 2013 Project template]]'''}}

<noinclude>[[Category:Google Summer of Code 2013]]</noinclude>

User talk:Chris Davenport

2013-02-21T20:10:43Z

Chris Davenport:

What was the reason my edits were removed?

Linking to external sites is classed as "self-promotion". If you wish to contribute videos (or any other resource) then they need to be hosted on our infrastructure. Ideally they will also be JEDL licensed, although we will consider material under other open licenses as long as the license terms are clearly shown. I look forward to seeing your videos. Just send them to me and I'll arrange to put them in an appropriate place. Thanks. [[User:Chris Davenport|Chris Davenport]] 03:43, 12 December 2008 (EST)

== basic template tutorial ==

You removed the warning notice I added to the tutorial, IMHO it is better to warn people that the basic tutorial will *not* give them a working template than letting them wonder why the template manager refuse to install their template. This notice should stay until someone fix the tutorial. For example removing the reference to the optional background.png from the xml because joomla will complain about a missing file and refuse to install the template. The xml example ought to be coherent with the outline of folder/file structure. Adding some mention of the role and importance the thumbnail file is another thing worth mention among the errors I had to fix for the template to actually install.

I removed your comments because they were not constructive. If you encountered a specific problem with the tutorial you should describe the issue in enough detail that someone would be able to reproduce it and then be able to amend the tutorial. You should also do that on the Talk: page rather than on the page itself. Better still you could amend the tutorial yourself; we welcome additions or amendments that improve the documentation. [[User:Chris Davenport|Chris Davenport]] 08:52, 15 November 2010 (UTC)

This revert thing is gonna get old quick. I can easily return the compliment and say I undid your removal because it's not constructive either, that If you encountered a specific problem with my editing, you should tell me about it in details on my talk page or point that warning readers that the tutorial is broken is improving the documentation, and the first step of actually fixing it. You should know better than what you did, I don't have the required knowledge and time to fix it myself. If you wanted to reproduce the issue, you just have to follow the tutorial step-by-step, better yet you can read the tutorial and you'll notice that it cannot work as is, or maybe just read what I wrote above and you'll see I did exactly what you asked me. On a related note don't invite someone to do something them block their account to prevent him from doing so, act stupid and treat people badly and they will act stupid too and behave as you expect them too. IMHO it's not smart to fight over such a ridiculous thing, but if you want me to waste both your and my time I'll take you on your challenge, so unless you're willing to block the whole ip range I'm using, I'll come back and do it again. This is the kind of behaviour you usually get from relying on http://meatballwiki.org/wiki/HardSecurity first and not trying to communicate instead of http://meatballwiki.org/wiki/SoftSecurity. see you soon from another ip. While at it also read http://meatballwiki.org/wiki/CriticismIsFeedback

All I am asking is that you edit the page in such a way that others can see the problem you encountered and can correct the information given. Simply saying that "...will end up in a few various errors..." does little to help us. What errors did you encounter? What version of Joomla were you using? What platform are you running Joomla on? Just stating that there are errors is like submitting a bug report that does nothing more than state that there is a bug in 1.6. Your hostile behaviour is uncalled for. 07:29, 16 November 2010 (UTC)

== Templates ==

Hello
I wanna ask, who can edit the Template Namespace in this Wiki? It would be cool, if a "normal" user could add some templates, cause I got a permission denied message --[[User:Bembelimen|Bembelimen]] 20:17, 23 December 2008 (UTC)

I wasn't aware that it was restricted. What page/template are you trying to edit/create? [[User:Chris Davenport|Chris Davenport]] 21:06, 23 December 2008 (UTC)
:It doesn't matter which one i try to edit or create. I get everytime this message:
:'''Permission error'''
:You do not have permission to edit pages, for the following reason:<br />
:You do not have permission to edit pages in the '''Template''' namespace.
:--[[User:Bembelimen|Bembelimen]] 21:37, 23 December 2008 (UTC)

I moved you to the Editors group. Try it now. [[User:Chris Davenport|Chris Davenport]] 23:36, 23 December 2008 (UTC)
:works now, thank you --[[User:Bembelimen|Bembelimen]] 23:52, 23 December 2008 (UTC)

== J1.6 Help system ==

I read that all will be different for Help in 1.6. Can you please point me to plans for Help 1.6? Tony Davis 06:02, 3 November 2009 (UTC)

Help for Joomla 1.5 and prior versions has traditionally been served from pages on http://help.joomla.org, which is itself a Joomla instance. In fact, the help system implemented in all Joomla versions up to 1.5 is hard-coded to require that the help server be a Joomla instance (probably not intentionally, but that's the way it worked out). That caused a couple of problems:
# When we moved the focus of the documentation effort to a wiki, it made sense to construct the help screens on the wiki too. However, this meant that we had to copy-paste the help screens from the wiki to help.joomla.org and whilst this is straightforward in theory, it is actually very labour-intensive and there is a lot of manual "fixing-up" that had to be done.
# It didn't solve a problem that had always existed with the help screens: clicking on a link in a help screen causes the next page to be loaded to appear with the full Joomla template, including headers, footers and modules, when it would be better to have just the help screen content display.
The first of these problems is addressed by serving the help screens directly from the wiki. However, this requires some minor code changes in Joomla itself. There is a patch to enable 1.5 to access non-Joomla help servers, but I believe it needs tweaking for 1.6 and I haven't had chance to do that yet. The second of these problems is addressed by serving the help screens via a proxy instead of directly from the wiki. The proxy is a Joomla instance running a small component and is already set up and running at http://help.joomla.org/proxy. It uses the wiki's web API to pull data from the wiki and because it has a stripped-down default template, it doesn't deliver any headers, footers or modules that are not intended.

As for the help screens themselves, the user interface for 1.6 is not yet fixed so it probably not wise to start writing the help screens (which generally involve a lot of screenshots) until it is. It is expected that the UI will be fixed when the first beta is released, so that should be the starting point for writing help screens. Of course, there's nothing to stop anyone starting before then, you just need to be aware that changes are very likely to happen.

The other area which is still "up for grabs" is a new key reference scheme. The help system works by having a "key reference" embedded in the code. This is then used to construct a URL from which the help screen is pulled. You can see the traditional naming scheme here: [[Help screens]]. However, with 1.6 we have the opportunity to completely revise this scheme if we want to. For example, we could add a namespace to the key reference, giving us "Joomla16:Config" instead of "screen.config.16", say. I'm not saying we should do that; I'm just illustrating the point that we have a great deal of flexibility and with 1.6 we don't have to worry about backwards-compatibility as there won't be any even if we stick with the current naming scheme.

In 1.5 (and before) the Joomla version number was appended to the basic key reference automatically. With the new help system, we can construct URL's with a lot more flexibility and we can make use of the following variables:
* keyref
*: The basic key reference itself
* major
*: The major part of the Joomla version number.
* minor
*: The minor part of the Joomla version number.
* maintenance
*: The maintenance part of the Joomla version number.
* language
*: The full language code (eg. "en-GB")
* langregion
*: The region part of the language code (eg. "GB").
These variables can be used anywhere within a help system URL to construct the page name to be retrieved.

Hope that helps.
[[User:Chris Davenport|Chris Davenport]] 09:36, 3 November 2009 (UTC)
Thanks for that Chris.

I take it from the above that one decision (or obvious thing) is that 1.6 Help will be a Joomla based system. Which leads to the question - Should the documentation be similarly based? I see it all being of a piece - the Help Screens being the descriptive part of the User Manual but there also being Introductory texts, Tutorials, Videos, Recipes (a lesser form of Tutorial to encourage folk to write them). It will be accessed either contextually - as a Help System - or like a Cookery Book or like a programming tutorial text. Is this totally daft?

I have built a whole heap of wiki pages and have learnt loads. see [http://docs.joomla.org/Manual_1_6 the root] I am concerned about controlling it. Could you look at Amy's Ning in two places [http://www.alltogetherasawhole.org/group/joomla16userguide/forum/topics/are-things-going-in-the-right bottom of this page] and [http://www.alltogetherasawhole.org/group/joomla16userguide/forum/topics/style-and-content this post] asking for volunteers.

All advice gratefully received. Tony Davis 22:02, 3 November 2009 (UTC)

Not sure I follow what you mean when you say that "1.6 Help will be a Joomla based system". The English help screens for 1.6 are going to be served from the wiki, although they are going through a proxy that happens to be running Joomla (I could just as easily have written some standalone PHP to act as a proxy, or if I knew how, a Drupal instance). The fact that all the documentation will be in the wiki, including the help screens, means that we can share content between the help screens and other forms of documentation. For example, I hope that the new 1.6 help screens will include links to more task-orientated pages. I wouldn't include the help screens as such in the User Manual as they mostly just describe what you see on a particular Administrator screen. I think that the User Manual (or Administrator's Manual as I prefer to call it) should be more task/goal orientated. I made a start at the sort of material I thought was appropriate on this page: [[Administrators]]. This is not to say that we cannot share content between the help screens and the User Manual though, but including an entire help screen in the User Manual is probably not very helpful.

I haven't had chance to read the Ning pages thoroughly, but I think Amy is right when she says that we should not expect authors to be wiki experts. We need to encourage people to write the raw material that can then be shaped by others into the modular, context-independent form that is the life-blood of a single-source, modular documentation system. [[User:Chris Davenport|Chris Davenport]] 23:19, 3 November 2009 (UTC)

== Vulnerable Extensions Updates ==

I noticed you are in process of updating the page. I am wondering if your update might contain any new information regarding Zoom Media Gallery (a now dead project), or Ice Gallery (Zoom's replacement project, which may also be either dead or in serious limbo). Ice Gallery, it seems, has a serious vulnerability, and is not yet listed here. In any event, Ice should be added, and Zoom entry should be updated as well. I have the info, and can do, if you don't. --[[User:Riverside|Riverside]] 00:16, 21 November 2010 (UTC)

I'm not involved in maintaining that information. Please email vel@joomla.org to report vulnerabilities. Thank you. [[User:Chris Davenport|Chris Davenport]] 00:25, 21 November 2010 (UTC)
:Sorry, I was looking at the wrong history page (talk, instead of the main page ~ so apparently it wasn't you editing it), but I will send what I've found there. Thanks. --[[User:Riverside|Riverside]] 18:58, 21 November 2010 (UTC)

==Templates for 1.6==
Chris,
Just wondering if you got my email regarding chunks and templates for the 1.6 help screens. I'd like to be editing and updating a lot of these screens but I'm not going to do anything until we can figure out a good way to handle chunks.
Would appreciate a response.
[[User:219jondn|219jondn]] 01:48, 21 January 2011 (UTC)

== Terminology ==

I note that you removed the material I put on the evaluators page about terminology.
Could you clarify your reasons please ? [[User:Vernonr|Vernonr]] 10:27 4 April 2011 (UTC)

Yes, you linked to material on your user page, which is not a good idea as all material should be in one of the main namespaces rather than in personal areas. Plus, your user page contained references to external sites which could be construed as self-promotion (see [[JDOC:Wiki_policy|Wiki_policy]]. Although the links are acceptable on user pages, they would not be acceptable on main documentation pages. You can fix it easily by writing directly in the Evaluators page and not linking to external sites. [[User:Chris Davenport|Chris Davenport]] 19:53, 4 April 2011 (UTC)

OK. How can one create a new page in the main namespace ?

I think it would make more sense to have an introductory page about terminology than to try and fit the material into the Evaluators page, and there could be other pages in the main namespace that should have the link. Would I be right in thinking that noting the authorship of articles is allowed under [[JDOC:Wiki_policy|Wiki_policy]] i.e. a link to the user page [[User:Vernonr|Vernonr]] 10:20 5 April 2011 (UTC)

You don't need any additional permissions to create pages in the main namespace, so just go right ahead. It is not necessary to note authorship in the pages themselves as all pages have full version history automatically recorded, including links to user pages (just click the "history" tab on any page). [[User:Chris Davenport|Chris Davenport]] 21:14, 5 April 2011 (UTC)

=== Change permission of content ===
Hi.
I would ask permission to move pages from the template namespace which are actually in course descriptions and pages that have links pointing to them.
I have as main objective the wiki organization and redesign the landing pages.

Thanks,
[[User:Wgviana|WGViana]]

Hi WGVianna. Can you give me some examples of the changes you are proposing? Moving templates needs to be done with care and I want to make sure that what you are proposing fits with our overall objectives. Thanks. [[User:Chris Davenport|Chris Davenport]] 14:39, 8 September 2011 (CDT)

Hi Chris.
List pages => [http://docs.joomla.org/index.php?title=Special%3AAllPages&from=&to=&namespace=10|SpecialPages:Allpages], there are pages in this namespace that are in my view should namespace '''description''' such as:
*[[Template:Beginner_profile]]
*[[Template:Framework]]
*[[Template:Model-View-Controller]]
*[[Template:Upgrade_Package]]
*[[Template:Upgrade-test]]
*[[Template:Version_Control_Software]]
[[User:Wgviana|WGViana]] 12:00, 9 September 2011

Hi Wgviana. I agree they should not be in the Template: namespace. However, I think they should be moved to the Chunk: namespace rather than Description:. The Description: namespace was set up specifically for class and method descriptions in the API Reference. I have added you to the Editors group so you should be able to make the changes yourself now. Thanks for volunteering. [[User:Chris Davenport|Chris Davenport]] 16:15, 12 September 2011 (CDT)

==Minor Spelling Issue==
Hi Chris, Top of the protected page:[http://docs.joomla.org/Vulnerable_Extensions_List Vulnerable_Extensions_List] "Jnuary" is probably "January" with an "a". Thank you

== Translations into french ==

Hi. I'm a french speaking Joomla enthousiast ;) I'd like to port Security Guide into French, as this seems to be a main concern for some french speaking users. I could of course host that on my personal page, or as a guide on the french forum about Joomla, but I think that the best way should be to start a translation of the Wiki into french. Do you think it could be possible to have a subpage like the ones available for the brochure ? Is there something specific to do ? Is it a good practice or not ?

[[User:Elnikoff|Elnikoff]] 03:25, 30 November 2011 (CST)

== Help25 ==

What are those changes you did with Help25?? [[User:Oc666|oc666]] 17:04, 25 December 2011 (CST)

Help25 is a new namespace for the Joomla 2.5 help screens. So far I have just copied across all the Joomla 1.7 help screens and amended all 1.6/1.7 references to 2.5. I'm just now trying to work systematically through all the toolbar sections. If you have some time and you'd like to lend a hand, just dive straight in, or let me know if you need some pointers. [[User:Chris Davenport|Chris Davenport]] 17:10, 25 December 2011 (CST)

== Define default name ==

What should be the correct nomenclature?
manager or management
{|
|-style="vertical-align:top"
|<categorytree>Extensions</categorytree>
|<categorytree>Components</categorytree>
|<categorytree>Languages</categorytree>
|<categorytree>Modules</categorytree>
|<categorytree>Plugins</categorytree>
|<categorytree>Templates</categorytree>
|}
I believe we should create the following categories:
* Language
** Language Management
and organizer:
* Extension Management
** Component Management
** Language Management
** Module Management
** Plugin Management
** Template Management
--[[User:Wgviana|Wgviana]] 14:49, 25 March 2012 (CDT)

I think that "manager" would refer to the component whereas "management" would refer to the process. Personally, I think "management" would be more appropriate in the category names. [[User:Chris Davenport|Chris Davenport]] 16:20, 25 March 2012 (CDT)

== External links come automatically with signature ==

Hello Chris,

Not to complain, but just to inform you why the link to my site appeared on [[http://docs.joomla.org/index.php?title=Accessing_the_database_using_JDatabase&action=history]] (and possibly make someone change this wiki automatisation):
It's because I put 3 tilda's there to let everyone know which user said this (as I thought was appropriate because it was rather a editing note and not joomla specific knowledge).
So, maybe the 3 tilda's should be changed somehow in this wiki? Because after all, I'd still want that link to exist in my User info.

Cheers
(No reply needed, you can immediatly delete this if you want)

:Hmm, okay. I usually use 4 tildas, so this is a test with 3 tildas. [[User:Chris Davenport|Chris Davenport]] ([[User talk:Chris Davenport|talk]])

:So for me using 3 tildas just adds links to the user's local profile page and profile talk page. Ahh, I wonder if you have a link in your signature. Please check the signature field in your user preferences and remove the external link if there is one. Thanks. [[User:Chris Davenport|Chris Davenport]] ([[User talk:Chris Davenport|talk]]) 15:18, 12 September 2012 (CDT)
::Apperently it had everything to do with my signature. I originally thought that had nothing to do with the tilda's, but it has. [[User:E-builds|E-motiv (former E-builds)]] ([[User_talk:E-builds|talk]]) 15:01, 21 September 2012 (CDT)
:::Thanks. [[User:Chris Davenport|Chris Davenport]] ([[User talk:Chris Davenport|talk]]) 03:32, 22 September 2012 (CDT)

== Deleting page sends mail "created page" ?? ==

Hello again Chris,

I got a mail from the wiki saying you just created the page http://docs.joomla.org/Using_a_custom_image_in_the_Menu_Bar_title.
I guess this is some template or other wiki misconfiguration, since you just deleted it.
I didn't know where to put this comment, so here it is. Feel free to forward to someone responsible, able or willing to fix it. :-)
[[User:E-builds|E-motiv (former E-builds)]] ([[User_talk:E-builds|talk]])

:It's a "bug" that's been in MediaWiki for years. The notification emails are identical whether a page is amended or deleted. I'm so used to it now I just don't notice it any more. [[User:Chris Davenport|Chris Davenport]] ([[User talk:Chris Davenport|talk]]) 14:25, 4 October 2012 (CDT)

== CodeExamples en categories with :: ==

Hallo again, Chris,
Weren't you the guy that included CodeExamples in this wiki?<br/>
If not, any idea who is or who is the wiki-responsible to talk to? <br/>
If so, read on..

I tried to help people by giving this CodeExample [[CodeExample:JHtml::stylesheet]], but it doesn't show up in the JHtml::stylesheet.<br/> On inspection of some of those pages, I noticed that a lot of (if not all) categories that have a "::" in them, show up as red (as if they don't exist), but they do. so I was wondering if that wasn't also the reason for my code-example not to show up.
[[User:E-builds|E-motiv (former E-builds)]] ([[User_talk:E-builds|talk]]) 12:26, 4 October 2012 (CDT)

:The CodeExample extension is currently broken following an upgrade to the MediaWiki software. I keep meaning to try to fix it, but workload keeps getting the better of me. If you're a developer and you'd like to take a look then please drop me a line. [[User:Chris Davenport|Chris Davenport]] ([[User talk:Chris Davenport|talk]]) 14:25, 4 October 2012 (CDT)

:: I don't think that I will have the time, but you can send me the php or template or whatever so I have it when I find the time and "power" ;-) [[User:E-builds|E-motiv (former E-builds)]] ([[User_talk:E-builds|talk]])

== Mediwiki Spam a better way to manage it ==
Hello Chris,

Looking thru the ''Recent Changes'' it seems like a lot of bogus wiki accounts are made and then used to spam the wiki. Has anyone looked at installing the [http://www.mediawiki.org/wiki/Extension:ConfirmAccount Extension:ConfirmAccount] and instead of requesting a 50 word biography for the request form only ask for about 5 words to prove they are human that then can be rejecting or accepted? The intent being to reduce the amount of time currently spent chasing and deleting the spam pages and is not to get a real bio only to see if it is a real person who is not planning just to spam the wiki.

The request wording: '''Are you a human, and not just signing up to spam our wiki? One of the Joomla! people will read what you write here and then confirm your account. Sorry for the inconvenience, but reducing spam on the wiki makes this step necessary...'''
* Q:Why do you want a login? (plain text only):
:Since we would need to examine all user registrations in order to accept or reject them, your proposal would, I think, involve more work rather than less. Although there are a lot of spam registrations, only a few confirm their email addresses and the present rate of at most a handful of spam posts per day is manageable. Thanks for the suggestion though. [[User:Chris Davenport|Chris Davenport]] ([[User talk:Chris Davenport|talk]]) 19:39, 29 October 2012 (CDT)
:: Your Welcome.. [[User:Cadrlp|Cadrlp]] ([[User talk:Cadrlp|talk]]) 01:29, 31 October 2012 (CDT)

== Delete Page ==

Hi Chris,
You just deleted the user who created this spammy page - but not the page itself :P Link:[[Need_To_Read_Shed_Buying_Suggestions]]
best,
George --[[User:Wilsonge|Wilsonge]] ([[User talk:Wilsonge|talk]]) 11:30, 21 February 2013 (CST)

Yeah, I got interrupted. Thanks for the reminder. [[User:Chris Davenport|Chris Davenport]] ([[User talk:Chris Davenport|talk]]) 14:10, 21 February 2013 (CST)

User talk:Chris Davenport

2013-02-21T20:09:00Z

Chris Davenport: Reverted edits by Chris Davenport (talk) to last revision by Wilsonge

User talk:Chris Davenport

2013-02-21T19:30:56Z

Chris Davenport: Blanked the page

Web Services Working Group

2013-02-17T11:08:37Z

Chris Davenport: Added links for second draft of API specification.

The Web Services Working Group is a [[Production Working Groups|Production Working Group]].

==Coordinators & PLT Contact==
* The coordinator for this working group is Ashwin Date (mailto:coolbung@gmail.com).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/76d499c6ec12840a?hl=en Web Services Working Group update 4 June 2012]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/4547aeb290723d87/7608dd58300bbe57?hl=en%E1%B6%B8dd58300bbe57 Request for comments on first draft of web API specification]
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/6474890e2453c6c3?hl=en# Request for comments on second draft of web services API specification]
==External resources==
* Recommended reading: [http://offers.apigee.com/api-design-ebook-rr/ Web API Design] by Brian Mulloy, Apigee (NOTE: Registration required)
* Stefan Neculai is a GSoC student working on a [https://github.com/stefanneculai/Web-service-API Web service API]. Read about him in the [http://magazine.joomla.org/issues/Issue-June-2012/item/772-RESTful-Web-Service-API Joomla Magazine].
* Aaron Schmitz has done some work on an [https://github.com/aaronschmitz/joomla-platform/blob/b2b68507006e4e575858e1d103a75f2a56907215/libraries/joomla/oauth/oauth.php OAuth 2.0 library]
* Louis Landry has created an [https://github.com/LouisLandry/joomla-platform/tree/oauth OAuth connector]. Also take a look at Louis's [https://github.com/joomla/joomla-platform/pull/1259 new router proposal].
* [REST API by Techjoomla for Joomla Separate app approach Presentation | http://www.slideshare.net/coolbung/joomla-rest-api]
* [REST API by Techjoomla for Joomla Separate app approach Github | https://github.com/techjoomla/Joomla-REST-API]
* [com_api approach | https://github.com/techjoomla/com_api]
* [com_api Plugins | https://github.com/techjoomla/com_api-plugins]
* [https://github.com/rcorral/com_api Rafael Corral's web API extension for Joomla 2.5]
* [[Xml-rpc|Note on current architecture used in Joomla 2.5]]
* [http://www.slideshare.net/HermanPeeren/webservices-connecting-joomla-with-other-programs-4399412 Herman Peeren's presentation at J and Beyond 2010]
* [https://groups.google.com/group/api-craft?hl=en API Craft] mailing list.

==Deliverables==
Create a POC using com_users by using the extending it to add webservices to Adding, Editing users, Listing users. Added by Parth Lawate as per webservices group discussion at #JWC12

==Technical work produced by this group==
* 24 Dec 2012: First draft of [https://docs.google.com/document/d/1PfJg8ec9PWa8oumIPXbVlO0GY8_8KQoL1Tx47K5blGA/edit Request For Comments: A Web Service API for the Joomla CMS]
* 10 Feb 2012: Second draft of Web Services API Specification
** [https://docs.google.com/document/d/1FVKGlV6BN6pu-YH2WR2pQHE3Ez7M6r7LD417GSw9ZSo/edit?usp=sharing Joomla CMS Web Services API Specification]
** [https://docs.google.com/document/d/11SqH-daKQV9SrFBMEpopjBk3vM1USIHnFWZB9rjJB94/edit?usp=sharing application/vnd.joomla.base.v1 media type specification]
** [https://docs.google.com/document/d/1wg3AcgStA26UwDcbHVV1bub4sa_BhsKfzAmX21eG-FM/edit?usp=sharing application/vnd.joomla.service.v1 media type specification]
** [https://docs.google.com/document/d/16xwxSDDPW0U1CG9l7JcwOyGvyjm7wv5zOSd9JwgF2iQ/edit?usp=sharing application/vnd.joomla.item.v1 media type specification]
** [https://docs.google.com/document/d/1PLym28MG5v1tWyvIyW-9483JNKh5AP21Fmsmg62plnA/edit?usp=sharing application/vnd.joomla.list.v1 media type specification]
** [https://docs.google.com/document/d/1d5qQ16r1Bo1BlXXuyS_eFB4BQcfuSg05pn9hsMpAgqk/edit?usp=sharing Joomla CMS Web Service API Implementation]
** [https://docs.google.com/document/d/1wI3cSm3y4aa8n8rojJKpiF6RUpSl63WFuLgJj2WqW8o/edit?usp=sharing Joomla CMS CLI Services API Specification]
==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in web services, then we will most likely start a separate mailing list.

==Roadmap==

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Bad Nauheim, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California.
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Web Services Working Group]]
[[Category:Working Groups]]

Help31:Joomla Version Additional Information

2013-02-04T20:19:48Z

Chris Davenport: Created page with "===Announcements and release notes=== * [http://www.joomla.org/announcements/release-news/5478-joomla-3-0-3-released.html Joomla 3.0.3 announcement] * [http://www.joomla.org/a..."

===Announcements and release notes===
* [http://www.joomla.org/announcements/release-news/5478-joomla-3-0-3-released.html Joomla 3.0.3 announcement]
* [http://www.joomla.org/announcements/release-news/5471-joomla-3-0-2-released.html Joomla 3.0.2 announcement]
* [http://www.joomla.org/announcements/release-news/5468-joomla-3-0-1-released.html Joomla 3.0.1 announcement]
* [http://www.joomla.org/announcements/release-news/5464-joomla-3-0-0-released.html Joomla 3.0.0 announcement]
===Frequently Asked Questions===
* [[:Category:Version 3.0 FAQ|Version 3.0 FAQ]] for FAQ information covering all releases in the 3.0.x series.
* [[:Category:Version 3.0.3 FAQ|Version 3.0.3 FAQ]] for known issues specific to 3.0.3, together with suggested resolutions.
* [[:Category:Version 3.0.2 FAQ|Version 3.0.2 FAQ]] for known issues specific to 3.0.2, together with suggested resolutions.
* [[:Category:Version 3.0.1 FAQ|Version 3.0.1 FAQ]] for known issues specific to 3.0.1, together with suggested resolutions.
* [[:Category:Version 3.0.0 FAQ|Version 3.0.0 FAQ]] for known issues specific to 3.0.0, together with suggested resolutions.

Help31:Joomla Version 3 0 0

2013-02-04T20:13:08Z

Chris Davenport: Created page with "{{ambox|type=serious|image=serious |text = '''Joomla! Version 3.0.0 is NOT the current version. Your website is NOT up-to-date.''' }} The current short-term support release ..."

{{ambox|type=serious|image=serious
|text = '''Joomla! Version 3.0.0 is NOT the current version. Your website is NOT up-to-date.'''
}}

The current short-term support release is {{CurrentSTSVer}}. As there have been security updates as well as bug fixes you should upgrade your website as soon as possible.

==Additional information==
{{Help30:Joomla Version Additional Information}}

Help31:Joomla Version 3 0 1

2013-02-04T20:12:33Z

Chris Davenport: Created page with "{{ambox|type=serious|image=serious |text = '''Joomla! Version 3.0.1 is NOT the current version. Your website is NOT up-to-date.''' }} The current short-term support release ..."

{{ambox|type=serious|image=serious
|text = '''Joomla! Version 3.0.1 is NOT the current version. Your website is NOT up-to-date.'''
}}

The current short-term support release is {{CurrentSTSVer}}. As there have been security updates as well as bug fixes you should upgrade your website as soon as possible.

==Additional information==
{{Help30:Joomla Version Additional Information}}

Help31:Joomla Version 3 0 2

2013-02-04T20:11:52Z

Chris Davenport: Created page with "{{ambox|type=serious|image=serious |text = '''Joomla! Version 3.0.2 is NOT the current version. Your website is NOT up-to-date.''' }} The current short-term support release ..."

{{ambox|type=serious|image=serious
|text = '''Joomla! Version 3.0.2 is NOT the current version. Your website is NOT up-to-date.'''
}}

The current short-term support release is {{CurrentSTSVer}}. As there have been security updates as well as bug fixes you should upgrade your website as soon as possible.

==Additional information==
{{Help30:Joomla Version Additional Information}}

Help31:Joomla Version 3 0 3

2013-02-04T20:10:16Z

Chris Davenport: Created page with "{{ambox|type=notice|image=notice |text = '''Joomla! version 3.0.3 is the current version. Your website is up-to-date.''' }} ==Additional information== {{Help30:Joomla Versio..."

{{ambox|type=notice|image=notice
|text = '''Joomla! version 3.0.3 is the current version. Your website is up-to-date.'''
}}

==Additional information==
{{Help30:Joomla Version Additional Information}}

Template:CurrentSTSVer

2013-02-04T20:07:49Z

Chris Davenport: Updated for Joomla 3.0.3 release.

{{#switch:{{{1}}}|
1|
major=3|
2|
minor=3.0|
3|
#default|
maintenance=3.0.3
}}<noinclude></noinclude>

Template:CurrentLTSVer

2013-02-04T20:06:31Z

Chris Davenport: Updated for Joomla 2.5.9 release.

{{#switch:{{{1}}}|
1|
major=2|
2|
minor=2.5|
3|
#default|
maintenance=2.5.9
}}<noinclude></noinclude>

Help25:Joomla Version 2 5 8

2013-02-04T20:04:17Z

Chris Davenport: Updated for Joomla 2.5.9 release.

{{ambox|type=serious|image=serious
|text = '''Joomla! Version 2.5.8 is NOT the current version. Your website is NOT up-to-date.'''
}}

The current long-term support release is {{CurrentLTSVer}}. As there have been security updates as well as bug fixes you should upgrade your website as soon as possible.

==Additional information==
{{Help25:Joomla Version Additional Information}}

Help25:Joomla Version 2 5 9

2013-02-04T20:02:13Z

Chris Davenport: Protected "Help25:Joomla Version 2 5 9" (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite)) [cascading]

{{ambox|type=notice|image=notice
|text = '''Joomla! version 2.5.9 is the current version. Your website is up-to-date.'''
}}

==Additional information==
{{Help25:Joomla Version Additional Information}}

Help25:Joomla Version 2 5 9

2013-02-04T20:00:57Z

Chris Davenport: Updated for Joomla 2.5.9 release.

Help25:Joomla Version Additional Information

2013-02-04T20:00:22Z

Chris Davenport: Updated for Joomla 2.5.9 release.

===Announcements and release notes===
* [http://www.joomla.org/announcements/release-news/5477-joomla-2-5-9-released.html Joomla 2.5.9 announcement]
* [http://www.joomla.org/announcements/release-news/5470-joomla-2-5-8-released.html Joomla 2.5.8 announcement]
* [http://www.joomla.org/announcements/release-news/5463-joomla-2-5-7-released.html Joomla 2.5.7 announcement]
* [http://www.joomla.org/announcements/release-news/5428-joomla-256-released.html Joomla 2.5.6 announcement]
* [http://www.joomla.org/announcements/release-news/5427-joomla-255-released.html Joomla 2.5.5 announcement]
* [http://www.joomla.org/announcements/release-news/5418-joomla-254-released.html Joomla 2.5.4 announcement]
* [http://www.joomla.org/announcements/release-news/5416-joomla-253-released.html Joomla 2.5.3 announcement]
* [http://www.joomla.org/announcements/release-news/5415-joomla-252-released.html Joomla 2.5.2 announcement]
* [http://www.joomla.org/announcements/release-news/5410-joomla-251-released.html Joomla 2.5.1 announcement]
* [http://www.joomla.org/announcements/release-news/5406-joomla-25-released.html Joomla 2.5.0 announcement] and [http://www.joomla.org/index.php?option=com_content&view=article&id=5403 release notes]
===Frequently Asked Questions===
* [[:Category:Version 2.5 FAQ|Version 2.5 FAQ]] for FAQ information covering all releases in the 2.5.x series.
* [[:Category:Version 2.5.9 FAQ|Version 2.5.9 FAQ]] for known issues specific to 2.5.9, together with suggested resolutions.
* [[:Category:Version 2.5.8 FAQ|Version 2.5.8 FAQ]] for known issues specific to 2.5.8, together with suggested resolutions.
* [[:Category:Version 2.5.7 FAQ|Version 2.5.7 FAQ]] for known issues specific to 2.5.7, together with suggested resolutions.
* [[:Category:Version 2.5.6 FAQ|Version 2.5.6 FAQ]] for known issues specific to 2.5.6, together with suggested resolutions.
* [[:Category:Version 2.5.5 FAQ|Version 2.5.5 FAQ]] for known issues specific to 2.5.5, together with suggested resolutions.
* [[:Category:Version 2.5.4 FAQ|Version 2.5.4 FAQ]] for known issues specific to 2.5.4, together with suggested resolutions.
* [[:Category:Version 2.5.3 FAQ|Version 2.5.3 FAQ]] for known issues specific to 2.5.3, together with suggested resolutions.
* [[:Category:Version 2.5.2 FAQ|Version 2.5.2 FAQ]] for known issues specific to 2.5.2, together with suggested resolutions.
* [[:Category:Version 2.5.1 FAQ|Version 2.5.1 FAQ]] for known issues specific to 2.5.1, together with suggested resolutions.
* [[:Category:Version 2.5.0 FAQ|Version 2.5.0 FAQ]] for known issues specific to 2.5.0, together with suggested resolutions.

Search Working Group

2013-02-02T09:47:55Z

Chris Davenport: Removed dead link to JAB12 and added new link to JAB13.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** [[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** [[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: Meeting at J and Beyond 2012, Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!
* 31 May - 2 June 2013: Meeting during [http://jandbeyond.org/ J and Beyond 2013], The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Web Services Working Group

2013-02-02T09:46:18Z

Chris Davenport: Removed dead link and added new link to JAB13.

Search Working Group

2013-01-20T17:56:52Z

Chris Davenport: Added future meetings.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** [[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** [[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: [http://jandbeyond.org/programme/sessions/session/session/43-search-working-group.html Meeting at J and Beyond 2012], Germany.
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!
* 31 May - 2 June 2013: Meeting during J and Beyond 2013, The Netherlands.
* November 2013: Meeting during Joomla World Conference, date and location to be determined.

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Web Services Working Group

2013-01-20T17:53:46Z

Chris Davenport: Added future meetings.

Search Working Group

2013-01-20T16:42:40Z

Chris Davenport: Added another tracker item to the list.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** [[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** [[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** [[jtracker:29953|29953 - smart search - this.toggleFocus.create is not a function]]
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: [http://jandbeyond.org/programme/sessions/session/session/43-search-working-group.html Meeting at J and Beyond 2012], Germany
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

How do you assign a module to a position?

2013-01-18T23:20:01Z

Chris Davenport: Reverted edits by HenryMaxwell (talk) to last revision by JoomlaWikiBot

Navigate to Extensions>>Module Manager.

(Note: all available modules show up under this Module Manager, even though some of them are built into Joomla! and are not extensions.)

On the left side of the page, on the third line, there is a menu that lets you select the position. You also can create a new position name on the fly but typing it in the same space as the menu. (In that case, make sure the same position name also appears in the template file.)

Modules that are not published will not display.

Modules can be assigned to unused positions (positions not available in the template) if you want to have them published but not displayed in a position (for example, if you want to display a module in content). See [[How do you put a module inside an article?]] for instructions on putting a module inside an article.

Multiple modules may be assigned to the same position. They will be displayed in the order shown for modules in that position in the module manager.

If you want to display a module in more than one position, use the module manager new icon to create an additional copy and assign that copy to the second position.

<noinclude>[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Version 1.5 FAQ]]
[[Category:Module Management]]</noinclude>

Getting Started with Joomla!

2013-01-16T00:40:12Z

Chris Davenport: Reverted edits by Zpcsolutions (talk) to last revision by Hutchy68

{{version/tutor|2.5|altlink=Getting Started with Joomla! 1.5|alt=1.5}}{{:Getting_Started_Page_Index/2.5}}
This series of documents introduces Joomla! to people who have not previously used it. This introduction aims to help you make the best use of the series.

==Background==

===Which versions are covered?===

There are two versions in common use:-
* '''Version 1.5''' is well established and widely used, and will be going to end of life April 2012. It will be supported for security fixes until September 2012. See [[Getting Started with Joomla! 1.5]] for the corresponding series.
* Version 1.6 was released January 2011 and is not supported anymore.
* Version 1.7 was released July 2011 and is not supported anymore.
* '''Version 2.5''' (long-term-support (LTS) version that replaced versions 1.6 & 1.7) was released January 2012.

There are many similarities between the versions but they are presented separately to newcomers to Joomla! in order to use 'hands-on' material.

===Who is it written for?===

The series is for anyone who wants to use Joomla! at a number of levels. Its main focus is:-
* on people with limited computing experience
* on using Joomla! for a small web site, such as a club or association or small business
but
* there are sections which will be useful to experienced designers and developers.

At the start of each article there is an indication of who it is aimed at and, on occasions, about the pitfalls for the inexperienced or unwary. </br>
[[GS/Readership|Some more detail about the intended readership]]

== Introduction to the Getting Started series ==

Joomla! is introduced using detailed 'hands-on' instructions about adding, altering and manipulating content. At the same time, general points about Joomla! are made which are intended to help people to learn more and do more. As the tasks require more background knowledge, so there are fewer hands-on instructions and more general pointers to the extensive documentation available for Joomla!

The series divides into four parts:-
:*'''Hands-on a Joomla! site:''' There is an initial section on how to get 'hands-on' a Joomla! site. This is followed by practical instructions about doing key tasks needed for adding, altering and manipulating content on an existing site.
:*'''Setting up a Joomla! site:''' This has background information about the design of a Joomla! Web site. There is a hands-on section on the mechanics of creating a new site using the core features that come with Joomla!
:*'''Looking after a Joomla! site:''' This is a brief introduction to the day-to-day adminstration of a Joomla! web Site.
:*'''Doing more and learning more:''' The final part links into other documentation and is intended as a guide ahead for taking Joomla! beyond the basics.

=== Hands-on a Joomla! site ===

You must have the use of a Joomla! Web site to use 'hands-on' instructions. There are several possibilites:-
:*[[Use an existing Joomla! 1.6 site| '''Use a site that has already been set up.''']] If you are going to be adding content to an existing site and do not have much computing experience this is a good option.
:* [[Use Joomla! on your own computer| '''Install a copy of Joomla! (with Sample Data) on your own computer.''']] This is sometimes referred to as a 'localhost' installation. Installing with Sample Data enables you to to explore a Joomla! site before you have created one for your own content. This is a good option for beginners.
:* [[Install_1.7| '''Install a copy of Joomla! (with Sample Data) on a Hosting server.''']] This is sometimes referred to as a 'remote host' installation. Installing with Sample Data enables you to to explore a Joomla! site before you have created one for your own content. This is a good option for beginners. [http://resources.joomla.org/directory/support-services/hosting.html]
:*'''Use the Demo on the Joomla! site.''' - Probably not doing this for version 1.6 Some example sites needed even if not interactive.

=== Hands-on adding and altering articles ===
Start here no matter what your previous experience. Articles are the building blocks of any Joomla! web site and everyone needs to know the basics of how to edit and create them. And doing this helps you to understand the inner workings of Joomla!

:*[[Hands-on editing an article: Joomla! 1.6| '''How to edit an Article''']] - aimed at helping everyone to use the editor and understand what articles look like and where they are stored.
:*[[Hands-on adding a new article: Joomla! 1.6| '''How to create a new Article''']] - aimed at helping everyone to add a new article to a web site

===More about editing articles===
These are aimed at helping everyone who wants to learn more about articles and managing them from the main Site, also called the Front-end.
:*[[Add links to other pages: Joomla! 1.6|'''Hands-on adding links to other pages''']]
:*[[Add a table: Joomla! 1.6|'''Hands-on adding a table''']]
:*[[Add an image: Joomla! 1.6|'''Hands-on adding a picture''']]
:*[[How to split an Article 1.6|'''Hands-on splitting a long article''']]
====Managing content using the Front-end of Joomla!====
:*[[Manage articles using the Front-end of Joomla! 1.6|'''Manipulating and publishing Articles''' ]] using the Front-end

===Setting up a Joomla! site===
There is a distinction between the mechanics of setting up a new site and the things you need to know before you set up a site. There is often a trial and error process involved in doing this, with muddle and frustration as a result. The problem is that you cannot design a site without knowing some background: and it is often easiest to learn the background by using a site. So this series presents the background to understanding how Joomla! sites work separately from the mechanics of creating a site. It emphasises that some initial thought can save hassle later.
====Background - things you need to know====
These are hands-on documents to familiarise you with designing a new site. The background is separate so that the flow of creating the site is not interrupted by asides. The background is aimed at helping you to understand what is going on, whether you have a large or a small site.
:*[[Get to know the Administrator Back-end of Joomla! 1.6|'''Background: get to know the Back-end''']]
:*[[How permissions work in Joomla! 1.6|'''Background: controlling user access to a Joomla! Site''']]
:*[[Design the content: Categories in Joomla! 1.6|'''Background: design the content - Categories in Joomla! 1.6''']]
:*[[Design appearance using Menus and Modules: Joomla! 1.6|'''Background:design appearance using Menus and Modules''']]
:*[[Design appearance using default Templates: Joomla! 1.6|'''Background: design appearance using default Templates''']]

====The mechanics of setting up a new site====
This covers the mechanics of creating new content and appearance of a simple site, using core Joomla! facilities.
:*[[The mechanics of creating a Joomla! 1.6 web site|'''Doing it: hands-on setting up a Joomla! site''']]

===General administration of a Joomla! site===
The work is not done even when a site is set up and there are people adding and altering the content. There are some day-to-day tasks that need attention, as well as minor alterations to the site.
:*[[Start to manage a Joomla! 1.6 site|'''Getting Started with day-to-day Administration of a Joomla! site''']]

==Take Joomla! beyond the basics==
There is more to learn about Joomla.
:* '''Beyond the basics: doing more Jooomla!''' - this is not yet completed - it points to ways ahead.

:*[[References|'''Books, links and helpful resources''']]
<noinclude>[[Category:Series Intro Pages]][[Category:Tutorials]]</noinclude>

Search Working Group

2013-01-02T09:25:15Z

Chris Davenport: Updated list of outstanding tracker items.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** [[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** [[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** <s>[[jtracker:29691|29691 - Smart Search auto complete.is issue]]</s>
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: [http://jandbeyond.org/programme/sessions/session/session/43-search-working-group.html Meeting at J and Beyond 2012], Germany
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Category:Top Level

2012-12-31T22:01:51Z

Chris Davenport: Reverted edits by Abu jaber 07 (talk) to last revision by Hutchy68

{{cat info|{{cat_header}}}}

Search Working Group

2012-12-31T11:03:17Z

Chris Davenport: Added some tracker items to the list and a couple of minor updates.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x and 3.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** [[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** [[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29100|29100 - mod_finder does not find correct route]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** <s>[[jtracker:29572|29572 - Smart Search Error: Unknown column 'm.weight' in 'field list' when doing empty searches]]</s> (Duplicate of [[jtracker:28978|28978]])
*** [[jtracker:29691|29691 - Smart Search auto complete.is issue]]
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: [http://jandbeyond.org/programme/sessions/session/session/43-search-working-group.html Meeting at J and Beyond 2012], Germany
* 17 November 2012: [http://conference.joomla.org/speakers/working-groups.html Meeting at Joomla World Conference], San Jose, California. This meeting was cancelled due to lack of interest and a scheduling conflict with the UCM group!

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Web Services Working Group

2012-12-26T09:12:16Z

Chris Davenport: Added a couple of links.

Search Working Group

2012-12-24T23:30:03Z

Chris Davenport: Added some tracker items to the list.

The Search Working Group is the [[Production Working Groups|Production Working Group]] responsible for the design and development of search in all its forms in Joomla.

Now that Finder has been integrated into Joomla 2.5 in the form of [[:Category:Smart Search|Smart Search]], the time has come to look forward to Joomla 3.x and how we want search to work in that series. Having gained considerable experience of implementing an advanced search capability the Search Working Group will look at embedding search as a core API in the Joomla Platform and exploiting that API to deliver an improved search in future versions of the CMS.

==Coordinators & PLT Contact==
* The (temporary) coordinator for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).
* The PLT Contact for this working group is Chris Davenport (mailto:chris.davenport@joomla.org).

==Announcements==
* [https://groups.google.com/group/joomla-dev-cms/browse_frm/thread/a03a0143ce5227f1?hl=en Search Working Group update 31 May 2012]

==External resources==
* [http://www.slideshare.net/chrisdavenport/jab2012-smart-search-presentation Smart Search and Beyond] (slides from [http://jandbeyond.org/programme/sessions/session/session/20-smart-search-and-beyond.html presentation at J and Beyond 2012])

==Deliverables==

==Technical work produced by this group==

==Communications==
Primary communications channel is the [https://groups.google.com/group/joomla-dev-cms?hl=en Joomla CMS Development mailing list]. If the volume of traffic becomes such that it might be deemed to be a nuisance by those not interested in search, then we will most likely start a separate mailing list.

==Roadmap==
The current plan is to focus on fixing outstanding issues for the 2.5.x series (and carrying those fixes forward into the 3.x branch as required). In parallel with that we should start to look at more extensive changes to be researched, coded and tested during the 3.x cycle for possible inclusion in Joomla 4.0.

* '''Short-term (address for 2.5.x)'''
** Multi-language fixes and improvements
*** [[jtracker:27511|27511 - Smart Search in Japanese is not working]]
*** [[jtracker:27807|27807 - Smart Search / Finder issues with languages with no spaces between words and double byte spaces]] Testers required
*** [[jtracker:28070|28070 - Smart Search indexer fails when iconv function is not available]] Testers required
*** [[jtracker:28409|28409 - Smart Search gives fatal error when searching with stemmer enabled]]
*** [[jtracker:28616|28616 - Add French language stemmer to Smart Search]] French-speaking testers required
*** [[jtracker:28971|28971 - Smart Search: wrong URL with multilingual site and SEF enabled]]
*** [[jtracker:28972|28972 - Smart Search: suggestions are not filtered by current language]]
*** <s>[[jtracker:29027|29027 - Add language data to Smart Search indexing's tokenize process]]</s>
*** <s>[[jtracker:29824|29824 - Finder saves * in language field]]</s>
** Multi-database fixes and improvements
*** <s>[[jtracker:27695|27695 - Smart Search Indexer does not work on SQL Server]]</s> See [[jtracker:28924|28924]]
*** <s>[[jtracker:28445|28445 - Smart Search throws an SQL error upon Indexing]]</s> (duplicate of [[jtracker:27695|27695]])
*** <s>[[jtracker:28799|28799 - Only run Smart Search indexer on supported databases]]</s> See [[jtracker:28918|28918]]
*** <s>[[jtracker:28918|28918 - Abstract FinderIndexer class for improved database support]]</s>
*** [[jtracker:28924|28924 - Add SQL Server subclass for FinderIndexer]]
** Large site fixes and improvements
*** [[jtracker:27627|27627 - Indexer stalling on large sites]]
*** [[jtracker:27628|27628 - Smart Search database size is too large]]
*** [[jtracker:28668|28668 - Smart Search CLI: Memory leak in JComponentHelper::isEnabled()]]
*** [[jtracker:28669|28669 - Smart Search CLI: Memory leak in FinderIndexer::index()]]
** Other fixes and improvements
*** [[jtracker:27715|27715 - Smart Search - Changes to Menu Items can cause errors with search results]]
*** <s>[[jtracker:27717|27717 - error saving _finder_tokens with big articles]]</s>
*** [[jtracker:27884|27884 - Inconsistent Itemid with Smart Search module when SEF enabled/disabled]]
*** <s>[[jtracker:27933|27933 - Smart Search module does not read static filter setting from module parameters]]</s>
*** [[jtracker:28029|28029 - FinderIndexerAdapter Optimization - Double Cost]] Testers required
*** [[jtracker:28035|28035 - Smart Search shows text from public articles from categories with special access levels in search results]]
*** [[jtracker:28081|28081 - Smart Search Results Page Displays Wrong Modules]]
*** [[jtracker:28197|28197 - Bug in the Smart Search indexer that is causing items ids to be indexed]]
*** [[jtracker:28403|28403 - Validation error on com_finder]] Testers required
*** <s>[[jtracker:28405|28405 - Smart Search - CLI Indexer doesn't catch exceptions]]</s>
*** [[jtracker:28480|28480 - Smart search fills up cache folder]]
*** [[jtracker:28590|28590 - Smart Search doesn't get the menu item title effectively when indexing]] Testers required
*** [[jtracker:28610|28610 - Several ACL & Toolbar fixes for com_finder (Smart Search)]] Testers required
*** <s>[[jtracker:28672|28672 - Fix PHP Strict errors with Smart Search auto-completion]]</s>
*** [[jtracker:28687|28687 - Escaping of quoted search terms alone]]
*** <s>[[jtracker:28689|28689 - FinderController duplicate lines]]</s>
*** [[jtracker:28712|28712 - Deleting an article doesn't delete the smart search entry]]
*** [[jtracker:28754|28754 - ModFinderHelper::getGetFields]]
*** <s>[[jtracker:28756|28756 - Enable Search Term Logging in Smart Search]]</s>
*** <s>[[jtracker:28797|28797 - Code Cleanup - Smart Search]]</s>
*** <s>[[jtracker:28858|28858 - Com_finder missing show_advanced_tips parameter => can't hide advanced tips]]</s>
*** <s>[[jtracker:28930|28930 - Deleting in Finder displays extra code]]</s>
*** [[jtracker:28939|28939 - Add Bootstrap Modal behavior, add toolbar button for a modal, use in Smart Search]]
*** <s>[[jtracker:28942|28942 - Use bootstrap markup in Fx.Progressbar; Use Fx.Progressbar in Finder]]</s>
*** [[jtracker:28978|28978 - Smart search (com_finder) - problem when using "Allow Empty Search"]]
*** [[jtracker:28998|28998 - Filter display not showing a filter in article category view]]
*** <s>[[jtracker:29028|29028 - Finder log messages showing on save]]</s>
*** [[jtracker:29058|29058 - Check parent state/access in Smart Search category plugin]]
*** <s>[[jtracker:29059|29059 - Smart Search - Filter Edit does not check the checked_out status to set the toolbar buttons]]</s>
*** [[jtracker:29077|29077 - Add a toolbar button to render a Bootstrap modal, add a helper method to render the modal, use it for Smart Search indexer]]
*** [[jtracker:29143|29143 - Smart Search Ajax suggestions do not respect static filters from module-settings]]
*** [[jtracker:29353|29353 - Smart Search Module Not Using Selected Filter]]
*** [[jtracker:29691|29691 - Smart Search auto complete.is issue]]
*** Investigate lack of ACL in auto-completion. [https://github.com/pasamio/joomla-cms/compare/secure_suggestions Possible solution]
* '''Medium-term (address during 3.x cycle for release in 4.0)'''
** [[jtracker:27592|27592 - Rename Finder plug-in group]]
** Save static filter definitions and restore them after a purge/rebuild cycle
** Mixed language content items
** Define a query language and build a parser to support it (with proper tests)
** Allow more than one "Did you mean?" suggestion
** Search API
** Swappable back-end search engine adapters
** Range query support
** Search logging via JLog and search statistics reporting
** Decouple indexing using message queues (see [[Message Queue Working Group]])
** Make it easier to load non-English common word lists
** Phonetic/morphological coding improvements - better multi-lingual Soundex support
** Improve multi-language tokenisation
** Multi-level taxonomy support
** Add parsers for PDF and MS Word documents
*** Look at porting the Finder plug-ins to Smart Search
** Dashboard view in Administrator
** Administrator search (see [[User Experience Working Group]])
* '''Long-term (address during 3.x and 4.x cycles for possible release in 5.0)
'''

==Meetings==
* 19 May 2012: [http://jandbeyond.org/programme/sessions/session/session/43-search-working-group.html Meeting at J and Beyond 2012], Germany

[[Category:Search Working Group]]
[[Category:Working Groups]]
[[Category:Smart Search]]

Web Services Working Group

2012-12-24T16:42:34Z

Chris Davenport: Changed link to draft RFC.

Web Services Working Group

2012-12-24T01:00:21Z

Chris Davenport: Added link to first draft of RFC.

Using nested sets

2012-12-18T00:15:44Z

Chris Davenport: Reverted edits by Pemdas21 (talk) to last revision by Hutchy68

Starting with version 11.1 the Joomla Platform now includes native support for storing and retrieving hierarchical information in the form of "nested sets" in database tables. This support is used in the implementation of menus and categories in the core Joomla CMS from version 1.6 onwards, but can of course be used in your own extensions too. This document assumes that you are already familiar with using the JTable, JDatabase and JDatabaseQuery classes to interact with a database, either the Joomla database itself, or some external database.

==Introduction==
In the nested sets model each data item is stored as a row in the database table in the normal manner. However, additional columns are present in the table to express the hierarchical relationship between the data items. Each data item is referred to as a node and the collection of nodes can be thought of as forming a tree. Nodes can have zero, one or many child nodes. A node that has no children is referred to as a leaf node. A child node can itself have children and this nesting can carry on to arbitrary depth. The table is assumed to hold a single tree with a single node being allocated as the root node. If you need to be able to store multiple trees then simply make the root node of each such tree a child node under the single root node and adjust your code to take this into account.

As each node contains columns labelled "lft" and "rgt" for "left" and "right" respectively, it is tempting to think that the data structure is a binary tree. However, these columns do not store node ids as they are not links to other nodes in the tree, but instead store sequence information. More information can be found on the theory behind nested sets here<ref>[[wikipedia:Nested set model]].</ref> The term "nested sets" is a little inaccurate as a set is, stricly speaking, an unordered collection of objects. In the Joomla implementation the order of nodes under a parent node is preserved and API calls are available to manipulate the order. A better term would perhaps be "nested ordered sets".

It should be noted that certain operations, such as inserting a new node, can be expensive in terms of disk access when dealing with a large tree and applications should be designed with this in mind.

==Getting Started==
The essential class is JTableNested, which extends the base JTable class, so instead of extending JTable you should extend your table class from JTableNested instead.

Your table must include a number of standard columns that are required for JTableNested to maintain the tree structure successfully. These are:-

* id (primary key)
* parent_id
* lft
* rgt
* level
* title
* alias
* access
* path

The primary key does not need to be called "id", but it is required. Other columns must have the names listed above.

For example, a suitable MySQL command to create a basic table compatible with JTableNested would be
<source lang="sql">
CREATE TABLE IF NOT EXISTS `#__nestedsets` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`parent_id` int(10) unsigned NOT NULL DEFAULT '0',
`lft` int(11) NOT NULL DEFAULT '0',
`rgt` int(11) NOT NULL DEFAULT '0',
`level` int(10) unsigned NOT NULL DEFAULT '0',
`title` varchar(255) NOT NULL,
`alias` varchar(255) NOT NULL DEFAULT '',
`access` tinyint(3) unsigned NOT NULL DEFAULT '0',
`path` varchar(255) NOT NULL DEFAULT '',
PRIMARY KEY (`id`),
KEY `idx_left_right` (`lft`,`rgt`)
) DEFAULT CHARSET=utf8;
</source>
You will, of course, need to add further columns for your specific data requirements. For the purposes of this documentation a column called "payload" will be used to indicate this custom data.

==Instantiating the table object==
You instantiate the nested sets table object in exactly the same way as you would for a regular table object. For example, if your table class file is located in a <tt>/tables</tt> directory in your component area, you could use code like this:
<source lang="php">
JTable::addIncludePath( JPATH_COMPONENT.'/tables' );
$table = JTable::getInstance( 'nestedsets', 'Table' );
</source>
This will instantiate your table class called 'TableNestedSets' in the file 'nestedsets.php'. Remember to extend from JTableNested instead of JTable:
<source lang="php">
class TableNestedSets extends JTableNested
{
// Your properties and methods go here.
}
</source>

==Adding a root node==
The quickest way to add a root node to an otherwise empty table is to use code like this, which can be added to your table class:
<source lang="php">
/**
* Add the root node to an empty table.
*
* @return integer The id of the new root node.
*/
public function addRoot()
{
$db = JFactory::getDbo();
$sql = 'INSERT INTO ckm_profiles'
. ' SET parent_id = 0'
. ', lft = 0'
. ', rgt = 1'
. ', level = 0'
. ', title = '.$db->quote( 'root' )
. ', alias = '.$db->quote( 'root' )
. ', access = 1'
. ', path = '.$db->quote( '' )
;
$db->setQuery( $sql );
$db->query();

return $db->insertid();
}
</source>
TODO: CHANGE THE ABOVE TO USE JDatabaseQuery.

It is perfectly reasonable to store payload data in the root node. For example, you might like to store component configuration data in the payload column of the root node.

==Getting the root node id==
To determine the id of the root node use the <tt>getRootId</tt> method. For example, in this example if the root node is not found, it is created.
<source lang="php">
$rootId = $table->getRootId();
if ($rootId === false) {
$rootId = $table->addRoot();
}
</source>

==Updating a node==
Updating the payload data in a node is done in exactly the same way as you would update a record in a regular database table using the JTable class. Given an array of data fields, this code binds it to the table object, checks its validity then stores it in the database table.
<source lang="php">
$table->bind( $data_array );
$table->check();
$table->store();
</source>
Updating a node in such a way that it alters the structure of the tree, for example, by moving a node from one location to another, is a little more involved and is described below. There are also some convenience methods for publishing/unpublished a node and these are also described in more detail below.

==Adding a new node==
Adding a new node to the table is done in a similar way to adding a row to a normal Joomla table. Data is bound to the Joomla table object using the bind method, followed by calls to check and store. These methods have been overridden in the JTableNested class to provide the additional functionality required for storing nested sets.

However, in order to determine where in the tree the new node is to be inserted, you need to make a call to the <tt>setLocation</tt> method. The setLocation method takes two arguments, the first is the id of a "reference" node in the tree. The new node will be inserted relative to this node with the relationship being specified by the second argument. Possible values for this relationship are:
* '''before''' - the new node will be inserted before the reference node but at the same level.
* '''after''' - the new node will be inserted after the reference node but at the same level.
* '''first-child''' - the new node will be inserted as the first child node of the reference node.
* '''last-child''' - the new node will be inserted as the last child node of the reference node.

In this example a new node is inserted as the first child of the reference node.
<source lang="php">
// Given an array of data fields in $data_array and a reference node id in $reference_id,
// this code will add the new node as the first child of the reference node.

// Get the table object.
// Note that in a model you can replace this with $table = $this->getTable();
$table = JTable::getInstance( 'yourtable' );

// Specify where to insert the new node.
$table->setLocation( $reference_id, 'first-child' );

// Bind data to the table object.
$table->bind( $data_array );

// Force a new node to be created.
$table->id = 0;

// Check that the node data is valid.
$table->check();

// Store the node in the database table.
$table->store();
</source>
In order to maintain the integrity of the data structure, the table is locked during a node insertion operation. Bear in mind that adding a new node to a large table is an expensive operation so the table could potentially be locked for a considerable period. You may need to take this into account when designing your application.

==Retrieving a single node by id==
If you know the id of a node then retrieving it can be done in the same way that you would retrieve a row in a regular Joomla table. For example,
<source lang="php">
// Get the node id from the request.
$id = JRequest::getInt( 'id' );

// Get the node from the table.
$table->load( $id );
</source>

==Is it a leaf node?==
A leaf node is one that has no child nodes beneath it. To determine if a node is a leaf node you can use code like the following:
<source lang="php">
// If $id is the id of a node, determine if it is a leaf node.
if ($table->isLeaf( $id )) {
echo 'This is a leaf node';
else {
echo 'This is NOT a leaf node';
}
</source>

==Retrieving a subtree==
To retrieve an entire subtree given the id of the base node of the subtree, you can use code like the following
<source lang="php">
// If $id is the id of a node, retrieve the subtree with this node as its root.
$subtree = $table->getTree( $id );
print_r( $subtree );
</source>
This will retrieve an array of all the nodes in the subtree. The array is one-dimensional and lists the nodes in preorder traversal order<ref>[[wikipedia:Tree traversal]]</ref>. Note that if your table is large calling getTree() from the root node will retrieve the entire table and very likely run you out of memory, so use it with caution.

==Retrieving a path==
To retrieve all the nodes along the path leading to a specified node, you can use code like this:
<source lang="php">
$pathNodes = $table->getPath( $id );
print_r( $pathNodes );
</source>
This will retrieve a one-dimensional array of all the nodes from the root node along the path leading to the specified node.

==Publish or unpublish a node or an entire branch==
Supporting the publish/unpublish feature is a little more involved than with a regular flat database table as the state of parent and child nodes must also be taken into account. Fortunately, the overridden publish and unpublish methods provided by JTableNested make the management of publish/unpublish almost transparent.

To publish or unpublish one or more nodes use code like the following:
<source lang="php">
// $ids can be a single node id, or an array of node ids.
$state = 1; // 0 = unpublish, 1 = publish
$userId = JFactory::getUser()->id;
if ($table->publish( $id, $state, $userId )) {
echo 'State changed successfully';
}
else {
echo 'State not changed';
}
</source>
The publish method respects rows checked out by other users and will attempt to checkin rows that it can after adjustments are made. The method will not allow you to set a publishing state higher than any ancestor node and will not allow you to set a publishing state on a node with a checked out child.

TODO: Using publish/unpublish with checkin/out requires some additional columns in the table. The documentation should be updated to reflect that.

==Changing the order of nodes in a branch==
There are a number of different ways of moving a node to a new location in the tree.

To move a node one position before or after its current position, but keeping it at the same level, you can use the orderUp or orderDown methods using code like the following:
<source lang="php">
if ($table->orderUp( $id )) {
echo 'Success';
}
else {
echo 'Failed to move node';
}
</source>

More generally, you can move a node by more than one position at a time using the <tt>move</tt> method. For example, the following code moves the node 2 positions before its current position, at the same level.
<source lang="php">
// Get the node id to be moved from the request.
$key = $this->_tbl_key;
$this->$key = JRequest::getInt( 'id' );

// Set the direction and magnitude of the move.
// Negative indicates "before", positive "after"
$delta = -2;

// Do the move.
// Notice that the node id is not passed as an argument to
// move; it must already be set in the table object.
if ($table->move( $delta )) {
echo 'Success';
}
else {
echo 'Failed to move node';
}
</source>

In the most general case, a node can be moved to an arbitrary position in the tree using the <tt>moveByReference</tt> method. This is very similar to adding a completely new node to the tree in that you need to specify the location to move the node to by reference to some other node.

In this example a new node is inserted as the last child of the reference node.
<source lang="php">
// Determine the reference node id.
$reference_id = JRequest::getInt( 'reference' );

// Determine the relationship with the reference node. Possible values are:-
// before - the new node will be inserted before the reference node but at the same level.
// after - the new node will be inserted after the reference node but at the same level.
// first-child - the new node will be inserted as the first child node of the reference node.
// last-child - the new node will be inserted as the last child node of the reference node.
$relation = 'last-child';

// Determine the node to be moved.
$node_id = JRequest::getInt( 'id' );

// Do the move.
if ($table->moveByReference( $reference_id, $relation, $node_id )) {
echo 'Success';
}
else {
echo 'Failed to move node';
}
</source>

==Deleting a node==
Deleting a node given its node id is very simple as the following example illustrates:
<source lang="php">
// Determine the node id from the request.
$node_id = JRequest::getInt( 'id' );

// Delete the node.
if ($table->delete( $node_id )) {
echo 'Node deleted';
}
else {
echo 'Failed to delete node';
}
</source>
Note that this operation will also delete all child nodes of the node being deleted, if any are present.

==References==
<references/>
<noinclude>[[Category:Platform 11.1]][[Category:Development Tips and Tricks]]</noinclude>

Web Services Working Group

2012-11-28T22:03:58Z

Chris Davenport: A few minor updates and corrections.

File:Installer Lang.jpg

2012-11-27T09:38:53Z

Chris Davenport: Reverted edits by Pastorgpayne (talk) to last revision by Guysmiley

Screenshot of Installer - Language