This page has been updated to include our SEO test links. I'll be checking back here soon for a P.O.C.

Not at this time. This requires the redistribution of a GEO-IP database that must be kept regularly updated.
Joomla! 1.5, 1.6, 1.7 and 2.5 are supported. Joomla 3.0 is not supported at this time.

The majority of settings for the Workflow extension are found in the Content - Workflow Plugin.

You can find these settings by going to the Plugin Manager, and clicking the the Content - Workflow plugin.

Settings are defined as follows:

Content - Workflow

Approval Notify Users: Users selected here will recieve email notifications of staged content.

Allow Users to Enter Notify Emails: When set to yes, this presents a text-entry field on the workflow screen that allows for the ad-hoc entry of one or more email addresses to be included on email notifications of staged content.

Can View Staged Versions: Specifies which users will be able to review and use staged content from the Versions window below the article.

Always Notify?: Hides the checkbox allowing the optional notification of staged content.

Always Notify On New?: When set to yes, emails Approval Notify Users when new content is created.

Unpublish New Articles?: When set to yes, will force new articles to be unpublished. Note that users with sufficient access can use Joomla's Article Manager to later publish that same content.

Unpublish Only From Usergroup: Works in tandem with "Unpublish New Articles" and forces unpublishing only from the selected user groups. Does not support custom Joomla user groups.

Stage All Changes? A global setting that will force all article changes into a staged state regardless of the workflow window settings or display.

Always Stage From Usergroup: Forces staging of articles from the selected user groups.

Button - Workflow

Display on Front End?: When set to yes, will also enable the Workflow button for front-end users. Otherwise displays as a disabled button.

Popup Window Width/Height: Allows for setting the dimensions of the Workflow popup window.

If you want to add, for example, a contact form that will send an email to you or your location's email address you can follow the steps below using the Locator Component alongside Fabrik, a form generator component.

This is covered in two videos:

Part 1:

Part 2:

Step 1: Install, configure Fabrik and set up your Form. You have to install the Fabrik Component and the Fabrik Joomla Content Plugin. Be sure the Fabrik Content Plugin is published, it does not publish by default.

Create your form, and use this code in the form submission plugin.

$db->setQuery('select value from #__location_fields_link where location_fields_id=10 and location_id=' . JRequest::getInt('id'));
return $db->loadResult();

Create your fields and include a special LocationID field that contains this code in the "Default" option:

return JRequest::getInt('origid');

Ensure your Elements (fields), Forms and Tables are all published in Fabrik.

Step 2: Set up your locations to include an Email and the Fabrik plugin code as shown in the video. Your description field for your location might look like:

<p>Sample Description</p>
<hr id="system-readmore" />
<p>{fabrik view=form id=2}</p>

Step 3: Set up your menu items to "Trigger Content Plugins" and also set "Display only Introtext" to "Yes". You may also optionally alter the position of the {description} tag in the "Item address format" so it appears last in the list.

That's it!


While this isn't officially supported, it's quite possible by editting the combined template.

See components/com_locator/views/directory/tmpl/combined.php This file includes both combined_item and combined_map_item to create the combined view. You'll find this block of code that outputs the results:

Move that block of code past the map output and it will appear on the right of the map as shown here:

This can happen when the TLD on your menu item is not set correctly. The TLD must be set in the back end for geocoding then also on the Menu Item Component Configuration as shown here: Searches are geocoded on demand, and the system needs to know what country the postal code is in. Also, if you incorrectly set your TLD, and perform multiple searches, those possibly incorrect search results are cached so all future searches for that postal code will continue to return incorrect results. To clear that cache, click the "Delete Geocode Cache" just above the list of geocoding results on the Geocode screen in the back end.

This is currently not supported within our software.  Instead, use your hosting company's mail utilities to create an alias email address (sometimes called a reflector).  That way you can set the donation software to use that alias and control the alias recipients via your hosting company's mail services.

International charcters must be from a UTF8 encoded file to import properly.  Various versions of Excel are not the best tool to ensure UTF8 encoding.  Notepad++ is a free application that will allow you to open your .CSV file and convert it to UTF8.  Then save your file and retry your import.  

Visit for more information.

When the map doesn't show, this almost always means you have a Javascript issue *above* the Javascript the Locator inserts in your page to initialize the map.

1)  A single location may be causing your map to not display correctly.  This may be evident if one set of search results displays the map, but another search does not.  That usually indicates there is some bad data in one or more location's data fields.  The most typical culprit is "newline" characters added during the import process causing the javascript to fail.  Using the Javascript Console (Activated by F12 in Windows and  CMD+ALT J in OSX can show you exactly which location is causing the problem.  Click on the red error message displayed for details.

2)  A conflicting component or template may interrupt the map.  Joomla relys on your template to output Javascript in the correct position and we rely on that as application developers.  Some templates are better than others and may not follow Joomla's rules.  Similarly, some components may interrupt, change or remove our Javascript code output.  We can't support all templates or components but will do our best to help you identify the problem area.  Your browser's Javascript console (described above) can be indispensible in helping you identify the cause.

3) CSS may hide your map.  Similar to #2, your template's style may happen to have rules in it that hide your map.  We can't provide detailed advice on that matter here, but you may contact your template developer or investigate using your browser's built-in Element Inspector to see the CSS affecting a given element.  

Page 1 of 4