Posted on

Where can I find GeoDirectory Developers for hire?

If you need to hire one or more GeoDirectory Developers to customize your website, make sure to visit this directory of GeoDirectory developers for hire.

You will find Full Stack developers, Front end developers, Back end developers, Implementers and SEOs.

If you have a great experience with a developer, please don’t hesitate to give him a great review. If you had problems with one of them, you can get in touch with us directly and we will try to help negotiate a favorable solution. If that doesn’t happen, they’ll deserve your negative review.

Posted on

Better Search Replace plugin

  1. Better Search Replace will assist with changing URLs or slugs etc in your database.
  2. It is also very helpful when changing your site from HTTP to HTTPS.

Changing slugs that have -1 appended

  1. Sometimes when you add a new location or category etc, the slug [part URL] might get a “-1” appended. For example mysite.com/location/east-sussex-1/
  2. This happens because WP does not allow duplicate slugs, and there already is something else using the slug east-sussex.
  3. This can be a tag, or a post name etc.
  4. It can also still be in the database from an old plugin you deleted.
  5. The solution is to search the database for the slug east-sussex and change it to east-sussex-2
  6. Then search for east-sussex-1 and replace all results (except the one you just changed) with east-sussex.

First replace the “correct” slug in the database

  1. Go to your database using phpMyAdmin.
  2. Search for the “correct” slug and replace it if required.
  3. Go to the Search:
  4. Search for east-sussex:
  5. Review the results:
  6. Adjust if you like by double clicking the field and changing the slug:

Using Better Search Replace

  1. After installing the Better Search Replace plugin, go to Tools > Better Search Replace:
  2. Let’s now search for the slug that we want to replace:
  3. You can now review where the slugs will be replaced:
  4. If all is OK, run the process, but un-tick the “Run as dry run” box.
  5. Once that is done, re-save WP Settings > Permalinks.
Posted on

Translation

Introduction | What you need to know
Translation Files | Core | Addons | Themes | Download
Translation process | Setup | Edit | PoEdit
More information | Resources | FAQ

Introduction

WordPress and GeoDirectory both are configured with English by default, but can easily be translated into other languages. In this document we will introduce the how translated strings are stored, edited, and loaded to a site to display a new translation.

The goal of this guide is not just to help you become familiar with translation. Once the new translations are setup in the GD site, you can edit and update your translation files any time. Once you start translating, and even changing the default text, you will probably find many ways to make the text ‘speak’ to your community of users.

What you need to know

  1. .po and .mo files are the standard method for storing “translated strings”.
  2. .po files are for doing translations.
  3. .mo files are for showing translations on your site.
  4. .po files can be edited with PoEdit, the free cross-platform desktop translation app.
  5. When you edit a .po file in PoEdit, and then save the file, PoEdit will also create/update a matching .mo file.
  6. Store BOTH the .po and the .mo files in the the proper site folder.
  7. GeoDirectory Core Translations are maintained at https://translate.wordpress.org/projects/wp-plugins/geodirectory, so go there if you want to download existing translations of GD Core.
  8. GeoDirectory Addon Translations are maintained at https://wpgeodirectory.com/translate/projects, so go there if you want to download existing translations of GD Addons.
  9. Finished translation files for plugins are stored in wp-content/languages/plugins/
  10. Finished translations for themes are stored in wp-content/languages/themes/

 

Core Translation Files

GeoDirectory Core plugin translations are maintained at https://translate.wordpress.org/projects/wp-plugins/geodirectory. If you are looking for existing translations of the GeoDirectory Core plugin in additional languages, you can go there to see which languages are available.

If your language is not currently available or at less than “100%” then consider joining the GeoDirectory translation team where members work together to make excellent, accurate translations available in every language. Visit the Translators Handbook to find out more.

GeoDirectory Core Languages Folder Location

Once you have completed your translation of GeoDirectory core plugin into a new language, the .po and .mo files must be transferred to your GD Site, usually by FTP. On your GD Site, the translation files for GeoDirectory core are stored in “wp-content/languages/plugins/”.

Use the following table to “check your work”. The most common reasons that a translation file won’t load is because it is named incorrectly or because it is stored in an improper folder.

Name .po/.mo folder path and file name (text domain)
GeoDirectory Core /wp-content/languages/plugins/geodirectory-en_US.mo

 

Addon Translation Files

GeoDirectory Addon translations are maintained https://wpgeodirectory.com/translate/projects. If you are looking for existing translations of addons you should go there to see if your desired language is available.

If your language is not currently available or at less than “100%” then consider joining the GeoDirectory translation team where members work together to make excellent, accurate translations available in every language. Visit the Translators Handbook to find out more.

GeoDirectory Addons Languages Folder Location

Translated files for GeoDirectory Addons are stored in “wp-content/languages/plugins/”. Use the following table to “check your work”. The most common reasons that a translation file won’t load is because it is incorrectly named or because it is stored in an improper folder.

Addon/Theme name .po/.mo folder path (text domain)
Advance Search Filters /wp-content/languages/plugins/geodiradvancesearch-en_US.mo
Ajax Duplicate Alert /wp-content/languages/plugins/geodir_duplicatealert-en_US.mo
BuddyPress Integration /wp-content/languages/plugins/gdbuddypress-en_US.mo
Claim Listing /wp-content/languages/plugins/geodirclaim-en_US.mo
Custom Google Maps /wp-content/languages/plugins/geodir_customgmaps-en_US.mo
Custom Post Types /wp-content/languages/plugins/geodir_custom_posts-en_US.mo
Event Manager /wp-content/languages/plugins/geodirevents-en_US.mo
Franchise Manager /wp-content/languages/plugins/geodir-franchise-en_US.mo
Location Manager /wp-content/languages/plugins/geodirlocation-en_US.mo
Markercluster /wp-content/languages/plugins/geodir_markercluster-en_US.mo
Payment Manager /wp-content/languages/plugins/geodir_payments-en_US.mo
Review Rating Manager /wp-content/languages/plugins/geodir_reviewratings-en_US.mo
Name /wp-content/languages/plugins/geodir_sagepay-en_US.mo
Social Importer /wp-content/languages/plugins/geodir_socialimporter-en_US.mo

 

Theme Translation Files

Only the default English translation is available for AyeCode’s GeoDirectory themes. You can find the default file inside the languages folder of the theme.

GeoDirectory Themes Language Folder Location

Translated files for GeoDirectory themes are stored in “wp-content/languages/themes/”. Use the following table to “check your work”. The most common reasons that a translation file won’t load is because it is incorrectly named or because it is stored in an improper folder.

Addon/Theme name .po/.mo folder path (text domain)
Directory Starter Theme /wp-content/languages/themes/directory-starter-en_US.mo
Supreme Directory Child Theme /wp-content/languages/themes/supreme-directory-en_US.mo

 

Download Existing Translations for a Plugin

Here we provide an example of how to download an existing translation.

In the example below, we will download an Italian translation of GeoDirectory Core, and then add the translation file to the GD site.

  1. Navigate to the GeoDirectory language project pages.
  2. Select the language and addon of your choice.
  3. Example: Italian:
  4. Select the language file you want:
  5. Scroll to the bottom of the page and Export the file (accept the defaults so you download the whole PO file):
  6. Load the file to the proper folder (See Translating Addons for more information).
    Change the file extension, if necessary, for your locale. Example: -it to -it_IT.
  7. Create the MO file using PoEdit or download from the same page where you downloaded the PO file:
  8. Review the translations on your site. If you find untranslated strings, continue to the next section for information about how to edit the translation files.

 

Translation Process

Setup New Language Translation Files on the Site

First, the translations need to be setup on the site. Here is the overview of that process:

  • Download an existing translation or create a new file. In either case, save the translation .po file to the desktop.
  • Open the file with PoEdit and select the new language.
  • Save the file with PoEdit on to the desktop with the new locale.
  • Find the .po and .mo files on the desktop.
  • Transfer the .mo and .po files via FTP to the proper site folder.

Edit an existing language translation

Once your translation files are setup, then you can edit them any time you want with this process:

  • Login to the site with FTP and navigate to the appropriate languages folder.
  • Download the appropriate .po file from the site folder, and save a backup copy in another location.
  • Open with PoEdit, Translate with PoEdit, Save with PoEdit.
  • Identify the new .po and .mo files in your local save location.
  • Transfer the .mo and .po files via FTP to the proper site folder.

 

Translating with PoEdit

This example is for translation of the core plugin. The process is the same for any plugin or theme, with the notable exception that the files are stored in the site in different folders.

  1. Download POedit and install the free program.
  2. Download the default translation. Each plugin or theme comes with English language .po and .mo files. Use FTP or cPanel to download the default language .po file to your local machine. You only need the .po file. PoEdit will create a new .mo file upon save.
  3. Open Poedit and select Create new translation:
  4. Navigate to the .po file and open it:
  5. Select the new language:
  6. Make sure to select exactly the same language you have at WP > Settings > General:
  7. Now save the file:
    1. Poedit will give you the correct extension, in our example that will be nl_BE.po.
    2. Make sure the filename matches the default translation filename. Example: geodirectory-nl_BE.po.
    3. PoEdit saves the .po and the .mo files: geodirectory-nl_BE.po and geodirectory-nl_BE.mo
    4. transfer BOTH the .po and the .mo files via FTP to the proper folder on the site.
    5. Save a backup of the files on your desktop and in your personal cloud, just in case of emergency.
  8. Translate the remaining strings. Now that the workflow is setup, you can Now translate any language string you want, and save the file once finished:
  9. When you are ready, upload both the .mo and .po file to the /wp-content/languages/plugins/ folder on the server.
    Create the folder if it does not exist yet:
  10. Go to your website and refresh to see your changes 🙂

 

Resources

  1.  GeoDirectory Addons Translation Project
  2. Translators Handbook

 

FAQ – Frequently Asked Questions about Translation

  • Can I change “Place Title” and “Place Description”?
  • To change Place Title and Place Description on the Add Listing page, you need to use the language file and look for %s Title and %s Description.
    %s refers to the singular name of the custom post type, which you can set using the Custom Post Types addon, or by translating Place and Places in the language file.
    For example to change Place Title to Business Name, you would translate %s Title to %s Name, and change Place to Business.
  • How do I translate the “New” and “Featured” banners.
  • To translate the “New” and “Featured” banners used for GD listings, you can copy and paste the blank images below, adjust them as required and upload to your website. Then add the following CSS:
    [css].geodir_new_listing {
    background: url(‘http://reference to your new image’) no-repeat scroll left top transparent;
    }
    ul li .geodir_featured_img {
    background: url(‘http://reference to your featured image’) no-repeat;
    }[/css]

    Right-click to download and save:

      

  • Translating the days in the Events Calendar
  • When adding the Events Calendar Widget, you will have 4 options for the format of the day:

    If you want to translate the days on the calendar, you will have to choose another option than the first option.
    In the translation file for the Events Manager, you can then translate the strings that match the option you have chosen.
Posted on

GD Translator’s Handbook

GeoDirectory Translator's Handbook
Welcome to our Translator’s Handbook. This is where we collect the resources we need to translate GeoDirectory into all the different languages of the world. My name is Ismi and I’m here to help.

Who translates? (Everyone!)
Find your Language Team
Setup
Say Hi/Bonjour/Selamat
Translate some strings
Request Validation
Become a PTE
GD Locale Topics
GD Lead Translators
Additional Resources

Who does translations? Everyone! All the plugin users together!

In 2017 WordPress translations changed completely. First there was a change in where translations are stored, and now the responsibility for who creates the translations has changed, too. Instead of plugin authors, it is now all of us, the plugin users and site managers and everyone together who are responsible for translating plugins into our own language.

It’s a big job, but luckily both WordPress.org and AyeCode are providing us with tools and support to help us get organized. Join us to reach the goal of making GeoDirectory available in 20+ languages in 2018! Read on to find out more about how to join us #polyglots to #makewordpress.

Find Your Language Translation Team on WordPress.org

Every language has a team. If you want to be a translator, you should go find out how to join the team for your language: https://make.wordpress.org/polyglots/teams/

Setup your accounts

Most translation team leaders are on WordPress slack. Here are the steps to quickly setup your WordPress and WordPress Slack accounts.

  1. Login/Register at http://wordpress.org
  2. Login/Register (same account) at https://translate.wordpress.org
  3. Visit https://make.wordpress.org/chat and use the same account to register for Slack
  4. Visit https://gravatar.com to set an image for your new
    @chat.wordpress.com address
  5. Visit https://make.wordpress.org/polyglots/teams/ and find your language, then click on “View Team”

Say Hi and ask to how to join your language team

Once you know where to find your language team, and you have all your accounts setup, it’s time to say hello to your language team.
Introduce yourself on #polyglots
Start with saying “Hi” in the #polyglots channel on WordPress Slack.

  1. Open WordPress Slack
  2. Click the + next to channel
  3. Search for #polyglots
  4. Join the channel
  5. Say “Hello” (or something like it). Introduce yourself, and mention which language team you want to join. For example: “Hello, everyone @here ! I am new, and want to join the language team. @ismiaini @alexrollin”

Say hi to your language team leaders
Next, you can message some of the leaders of the team, to let them know. Visit your language team page, or look through the requests or the GD Translations to find other WordPress users who have validated in the past. Then make a direct message in Slack to say hello to them also:

  1. Open WordPress Slack
  2. Click the plus next to Direct Message
  3. Search for the people from your translation team and add them to the message.
  4. Also add @ismiaini and @alexrollin to share the joy
  5. Enter a message and say “Hi” again and introduce yourself, like you did in the #polyglots channel.

Ask your team at these questions
There are, at least, two (2) questions that you want to ask your language team leaders before you submit a request for help with validation:

  1. “How do I join the team?”
  2. “Is there anything you can tell me before I make a request for validation?”

Note: Be nice to these folks, as they have worked hard at what they do and obviously care a great deal about translation into your own language. They are your new collaborators, and you are their new team member. Enjoy the opportunity to meet these new colleagues and to work together on this great project called WordPress.

Translate some strings

Visit the GeoDirectory page for your language: https://translate.wordpress.org/projects/wp-plugins/geodirectory
The best way to get started is to click on one of the incomplete projects and then click on “untranslated”. This gives you a list of strings that need translation. Double click and add a translation. Easy!

Request Validation

Once you have translated some strings, you can ask your language team for help with validation. You can make your request here: https://make.wordpress.org/polyglots/?resolved=unresolved

Here is a template you can use to make your request. All the users tagged in the request will receive a notification.

Hello #polyglots! I translated some strings with our project language team and we need your help with validation.

o fr_FR @MyUsername @ismiaini @alexrollin

Pleased to answer comments and questions below in the comments.

CAUTION: Your language team will be happier if you contact them by WordPress Slack to say hi, first, BEFORE you request help. Your team may also have additional suggestions or rules about joining their team. Be sure to ask “How do I join the team?” before you ask “Is there anything you can tell me before I make a request for validation?”.

What’s a PTE?

Once you translate some strings, the strings must be validated by someone who is a member of your language team. Remember the person you said “hi” to above? Someone like them. Once you join your language team, and then complete a translation for GeoDirectory, you can ask a leader of your language team to set you up as a PTE for GeoDirectory for your language. A “PTE”, which is an acronym for “Project Translation Editor”. PTEs can validate strings. PTEs are assigned by the WordPress language team to to projects in their language. For example, a person who translates GD into Russian would go and talk to the Russian team members and ask them to validate the new translations. Then, when they finish, the translation team might make them a PTE for the GeoDirectory Russian translation. Being a PTE means that your strings are automatically validated, and you can validate the contributions of others, too.

GD Translation Leads

Are you committed to keeping up GeoDirectory translations for your native language? Here’s the rundown of what goes with the territory:

  • Join the WordPress language team for your native language.
  • Complete and continuously update the translation of GeoDirectory core and readme.txt on WordPress.org for your langage.
  • Complete and continuously update the translations of the GD Addons here.
  • Follow your own WordPress language team’s guidelines for translations and collaboration with other translators.

One lead translator from each language will receive a GeoDirectory membership that will remain active as long as they remain a translation lead on the GD Translation Team.

GD Translation Topics

Join up with others here on GD that speak your language. Some languages have a forum topic they call “home”; if your language doesn’t have one, go ahead and create it in the transations forum.

Existing Locale Forum Topics

Locale (English) Locale (Native) WP Locale Team Topic
Indonesian Bahasa Indonesia id_ID https://wpgeodirectory.com/support/topic/indonesian-locale/
French (France) Français fr_FR https://wpgeodirectory.com/support/topic/french-locale/

Additional Resources

Posted on

Do you provide refunds?

If you are not satisfied with our products and services you should get your money back, it is as simple as that!

Ask for a refund within 30 days from your initial purchase here. You will get it, no questions asked.

Should you open a dispute, instead of asking for a refund, we will keep 50% of the disputed amount, for our time having to gather evidence and submit it.

It is a member’s responsibility to stop payments authorized through PayPal or Stripe. If you decide to stop the membership and discontinue using our Products, please remember to login to your PayPal and cancel the Authorization. (see instruction here for Paypal). For payment made through Stripe, you’ll need to contact us directly.

Posted on

Geo Travel – Genesis Child Theme – Overview


Introduction
Genesis Framework
Preparation
Home Page Setup
Widgets and Widget Areas
FAQ – Frequently Asked Questions

Introduction

The Geo Travel – Genesis Child Theme is a mobile responsive and HTML5 theme especially developed to optimize GD with Genesis Framework.

View the demo

Genesis Framework

Genesis Framework is premium theme, and one of the most popular and widely used theme frameworks. The Genesis Framework parent theme is required when you wish to use the GeoTravel Child theme.

To proceed with installation of the Geo Travel – Genesis Child Theme theme you will need your own copy of the Genesis Framework parent theme.

Get Genesis Framework Here: https://my.studiopress.com/themes/genesis/

Preparation

  1. Install BUT DO NOT ACTIVATE the Genesis Framework. Link: https://my.studiopress.com/themes/genesis/
  2. Download the Geo Travel – Genesis Child Theme from your download area. Link: https://wpgeodirectory.com/your-account/
  3. Upload the Geo Travel – Genesis Child Theme and activate it.
  4. You will need to enter your license so you are notified if the child theme needs updating:

Home Page Setup

Home Settings

GeoTravel Child theme works best when the WordPress Site’s Home page is set to a different page as “GD Home”, the home page of your GeoDirectory directory.

To set this up on your site, the same way the demo works:

  1. Go to GeoDirectory > Permalinks > GD Home and choose a page as your directory homepage. By default this is set to a page called “GD Home” but you can set it to any page you like.
  2. Save the settings
  3. Go to WordPress > Settings > Reading and choose a different page for the “Static Front Page” of your site.
  4. Save the settings
  5. Visit the site home page to see the changes.

Home Page Featured Area Setup

The following instructions will help you setup the background image and the upper featured area for the homepage to match the demo.

  1. Go to Appearance > Customize > Home Background and upload the background image for the homepage:
  2. Go to Appearance > Widgets.
  3. Add a text widget to the Home Featured Left widget area and add your custom text.
  4. Add the GD Search widget to the Home Featured Right widget area.

Home Page Widgets

GeoDirectory uses widgets to display listings. You can read more about all the widgets that are available here: https://wpgeodirectory.com/docs/widgets/ .

To setup your site to match the demo, add the following elements on your site.

Dummy Data

Add dummy data to populate the widgets on the home page. You can skip this if you already have listings on your site.

  1. Go to GeoDirectory > General > Dummy Data
  2. Adjust: Select 10 or more.
  3. Insert data
Latest Places

Add a GD Popular Post widget to the Home Top widget area.

  1. Go to Appearance > Appearance > Widgets
  2. Adjust: On the left side of the screen find the “GD Popular Post View widget.
  3. Adjust: Select the widget and choose to add to “Home Top“.
  4. Find the GD Home Top widget area on the right side and open the settings for the GD Popular Post View widget.
  5. Adjust: Title > “Latest %posttype_plural_label%“.
  6. Adjust: Sort by > “Latest“.
  7. Adjust: Number of posts > “5“.
  8. Adjust: Layout > “Grid View (5 Columns)“.
  9. Save settings
  10. Visit the site home page to see the changes.

Widgets and Widget Areas

The Geo Travel – Genesis Child Theme uses the following widget areas:

  1. The blue sections will show on all your site’s pages.
  2. The yellow sections are only for the home page. To see the Home page sections you must have a different pages for WordPress Front Page and GD Home Page. If they are the same page, only the GD template will be shown.
    Logo Header Right widget area
    Menu section
    Home Featured Right widget area Home Featured Left widget area
    Home Top widget area
    Home Middle widget area
    Home Bottom widget area
    Footer 1 widget area Footer 2 widget area Footer 3 widget area
     Copyright text
    Disclaimer widget area
  3. A Secondary and Primary Sidebar widget area used on all WP pages and posts, depending on the Genesis layout selected at Genesis > Theme Settings > Select Default Layout.
  4. An After Entry widget area that is used after the content of a WP post on the WP post pages.

FAQ – Frequently Asked Questions

Is the Genesis Framework really required?

Yes, the Geo Travel – Genesis Child theme won’t work without the Genesis Framework.

How do I change the footer area?

To change the footer text in the Geo Travel – Genesis Child theme, look for the following code in the functions.php file, and adjust as required.

[css]//* Add My Custom Footer Links[/css]

I added additional content to the GD Home page with a builder ,why doesn’t it show up?

The GD Home page content area will be overwritten by the GeoDirectory plugin when it renders the GD Home page. This will also effect your site home page, if you have your site home page set to the same page as “GD Home”.

Builders can be used on other WP Pages, but their content will be overwritten when used on the pages chosen in the GeoDirectory Permalinks settings.

Posted on

Translating GD Listings in a multilingual site

How do you add a listing in more than one language on your WPML – GeoDirectory site?

Let’s say we want to add an English and a Dutch version of the same listing. These are the steps required:

  1. Add the listing the normal way, yourself or user submission.
  2. Once that is done, login as administrator and navigate to the new listing in the backend.
  3. Once there, click the + sign to add a translation of the listing:
  4. This will open a new listing, and once there, click Overwrite with English content:
  5. Save the Dutch version of the listing. You will now have a listing with two language versions:
  6. Translate the Dutch version as required, or if this was a user submitted listing, notify your user, who now can log in to the Dutch version of your site, and will find his listing in his dashboard, ready for translation:
  7. Now your visitors will be able to switch languages for the listing while looking at the detail page.

Adding two different listings from the frontend will not link them together, even if using the same address. You need to create the listing in the other language in the backend for them to stay connected.

Posted on

Translating Custom Post Types

Translating Custom Post Types names

  1. If you only want to translate your CPT names (like Place and Places), follow the instructions here. Only the Multilingual Blog plugin is required then.
  2. But if you also want to translate the CPT slugs, you will need to keep reading below.

Translating Custom Post Types slugs

  1. Translate your CPT names (like Place and Places) as explained above.
  2. To translate your CPT slugs (like /places/ or /events/ etc), you will need WPML’s String Translation plugin, and the Translation Management plugin which are part of the Multilingual CMS plugin.
  3. Once the String Translation and Translation Management plugins are activated, go to WPML > Translation Management, and select the Multilingual Content Setup tab. and then select Custom posts slug translation options:

  4. Select and save Translate custom posts slugs (via WPML String Translation):

  5. Now scroll down the page to Custom posts, and select the CPTs to translate and add your translations before saving:
Posted on

Creating different Event types

On this page:

Introduction – Scenario – Preparation – User experience

Introduction

  1. You can create different Custom Post Types, but you can only have one Event Custom Post Type.
  2. This article explains how you can create different Event types, with the use of the Payments Manager.
  3. The options and idea explained below can also be used for other Custom Post Types.

Scenario

  1. We want our users to add Festivals and Markets, and Festival submissions can include the name of artists, and Market submissions can include details of the organisers.
  2. But we want to make it easy, so when they choose to add a Festival, they are not shown any Market specific fields.

Preparation

Categories

  1. Go to Events > Event Categories and add your categories:

Price packages

  1. Go to GD > Prices and Payments and create or edit Event price packages.
  2. We will create a Festivals and a Markets package:
  3. After creating the Festivals package, save it first.
  4. Then choose to edit again, and now you will be able to exclude all the Event categories that are not Festival categories:
  5. Repeat for the Markets package.

Custom fields

  1. Go to GD > Event Settings and create an Artists custom field.
  2. Make sure to restrict the custom field to the Festival package only:
  3. Repeat for the Markets only custom field.

User experience

  1. Now you can link direct to the packages like this if you like:
    1. Festivals: yoursite.com/add-listing/?listing_type=gd_event&package_id=2
    2. Markets: yoursite.com/add-listing/?listing_type=gd_event&package_id=3
  2. And your users can also select from the Add Listing page:
  3. If they choose the Festival package, then the festival categories will be the only ones available for selection:
  4. Only the Festival specific custom fields will be available too:
Posted on

The GD Search explained

On this page:

1. Custom Post Type selector 2. Category selector 3. “Search for” field 4. “Near” field 5. The “Near me” compass 6. Filtering with custom fields Adding a Select custom field to the search bar

Read Understanding navigation, searching and browsing … to understand the basic search function better.

1. Custom Post Type (CPT) selector

This selector will only be shown if you have more than one Custom Post Type.

 

 

 

 

  1. The CPT selector defaults to the current CPT of a Listings, detail or search page. For example on an Events category page, Events will be listed first in the selector.
  2. On a location page or any standard WP page or post, the order of the CPTs in the selector can be determined by changing the order at GD > Custom Post Types > Choose a CPT > Advance Mode tab > Order in post type list (Custom Post Types addon required).

2. Category selector

The categories drop down can be set up for each Custom Post Type and the Advanced Search addon is required.

  1. Activate the Advanced Search addon.
  2. Go to GD > Place (or other CPT) Settings > Custom Fields tab.
  3. Select Yes to include the categories drop down in the Advanced Search:
  4. Then go to the Advanced Search tab and click on the Category field on the left hand side, that will move it to the available fields on the right:
  5. Now open the Category field there, and select to Show in main search bar
    :
  6. The Search bar priority setting allows you to move the Category selector left or right in the main search bar.

3. “Search for” field

  1. GD will check the entry titles, description and taxonomies (tags and categories) of the listings.
  2. The search will not check custom fields or locations.
  3. The search will only search one Custom Post type at the time.
  4. With the Advanced Search addon, you can set this field to auto-suggest listings based on the title of the listings, see Search Autocompleter settings.
  5. You can change the default text at GD > Design > Search.

4. “Near” field

  1. When you enter a location in the Near field, GD will calculate the center of that location.
  2. GD then will look for all listings within an area with a default that match the Search for criteria.
  3. Your default search area is set at GD > General > Search.
  4. The default GD search is not an IN search, but a search NEAR THE CENTER OF.
    For example, assuming your search area is set to 40 square miles:

    1. If you enter World Trade Center, you will get listings around that building.
    2. If you enter United States, you will get listings somewhere around Buffalo in Kansas, because that is where Google situates the center of the United States.
    3. If you enter California, you will get listings somewhere in the Sierra National Forest.
  5. Be aware of some issues:
    1. If you enter a ZIP or a postcode, be aware that that postcode might be used by different countries in the world and might return results around the center of a city in a different country.
    2. A similar issue might occur for place names of cities in different countries.
    3. Please review Add location specific text to (Near) search for Google.
  6. Although the default search for this field is a NEAR THE CENTER OF search, with the Advanced Search addon, you can set this field to auto-suggest locations based on the title of the listings, see Near Autocompleter settings.
    Please note that if you have the Location Manager addon activated, the Near Autocompleter will start giving suggestions as your visitor starts searching, which if selected will search IN the location being entered (ie the city or region in the address of the listing) and will not search an area NEAR THE CENTER OF that location”
  7. You can change the default text at GD > Design > Search.

5. The “Near me” compass

  1. This compass will only show if you have the Advanced Search addon active.
  2. It allows for the search to be limited or expanded by a radius around the visitor’s current location (if Near me is ticked) or near the center of the location selection in the Near field (if Near me is not ticked):
  3. Also review the Geolocation settings.

6. Filtering with custom fields

  1. This will only work if you have the Advanced Search addon active.
  2. Create your custom fields at GD > Place (or other CPT) Settings > Custom Fields.
  3. Then navigate to the Custom fields tab and expand any custom field you would like to filter with search and tick the checkbox Include this field in filter:
  4. Then go to the Advanced Search tab and click on the custom field on the left hand side, that will move it to the available fields on the right:
  5. Now open the field by clicking on it, and select the settings:
  6. Now clicking on the Search cogwheel will open the custom filter:
  7. Now if your visitors click the search button in the example above, the results will return:
    1. Listings from the Places CPT only,
    2. that are in the Attractions category, and
    3. have farm in the title, description, category or tag of the listing, and
    4. are around the center of Amsterdam (depending on the radius set in the system), and
    5. will be filtered to only return those listings that have dogs.

Adding a Select custom field to the search bar

  1. Select custom fields can also be added to the search bar – but only Select, not Multiselect or any other, they can only be added to the Customized Search section as explained above.
  2. Follow steps 1 to 4 from 6. Filtering with custom fields above.
  3. Now open your Select custom field there, and select to Show in main search bar
    :
  4. That will add the Select custom field to the main search bar: