GeoDirectory SupportSearch Function Not Working in a WP install in a Subdirectory – GeoDirectory Support https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/feed Fri, 26 Dec 2025 13:40:47 +0000 http://bbpress.org/?v=2.5.14-6684 en-US https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3925 <![CDATA[Search Function Not Working in a WP install in a Subdirectory]]> https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3925 Tue, 10 Jun 2014 19:17:29 +0000 stars I have a fresh install of WP with the core GeoDirectory plugin installed, the URL to this install is http://www.mysite.com/alias-to-subfolder/

I load up the dummy info using the GeoDirectory backend and then try to search these dummie listings on the front end. What happens is that when I click search I get redirected to a URL that looks like this:

www.mysite.com/alias-to-subfolder?geodir_search=1&stype=gd_place&........... ( this is not the full URL, just giving an example)

If you notice the “/” between “/alias-to-subfolder” and the starting “?” is missing. If I manually add the “/” (“/alias-to-subfolder/?”) to the URL the search works fine.

If I load geodirectory into my root install of WP (www.mysite.com) it works fine. It seems that the search function assumes that GeoDirectory will be running in a root folder and not a sub-diretory/alias. is there an easy fix for this or do I need to go in and change code to fix this?

]]>
https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3931 <![CDATA[Reply To: Search Function Not Working in a WP install in a Subdirectory]]> https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3931 Tue, 10 Jun 2014 19:41:34 +0000 Paolo Thanks for reporting this, I flagged it for a developer to look at.
We’ll let you know asap.

]]>
https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3934 <![CDATA[Reply To: Search Function Not Working in a WP install in a Subdirectory]]> https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3934 Tue, 10 Jun 2014 19:44:34 +0000 stars Thanks for the quick response.

]]>
https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3936 <![CDATA[Reply To: Search Function Not Working in a WP install in a Subdirectory]]> https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3936 Tue, 10 Jun 2014 20:00:30 +0000 stars OK got a temporary fix.

if you look in listing-filter-form.php @ line 8 you will see:

<form class="listing_search" name="listing_search" action="<?php echo home_url();?>" method="get" >

I changed this to:

<form class="listing_search" name="listing_search" action="<?php echo home_url(), '/';?>" method="get" >

and that fixed this issue in this case

]]>
https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3959 <![CDATA[Reply To: Search Function Not Working in a WP install in a Subdirectory]]> https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3959 Tue, 10 Jun 2014 22:07:56 +0000 Guust Could you not just add a trailing slash to WP admin > Settings > general settings > WordPress Address (URL) ?
Ops, you can’t: WP will remove the / on saving …

]]>
https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3992 <![CDATA[Reply To: Search Function Not Working in a WP install in a Subdirectory]]> https://wpgeodirectory.com/support/topic/search-function-not-working-in-a-wp-install-in-a-subdirectory/#post-3992 Wed, 11 Jun 2014 15:12:26 +0000 stars Yeah that was my first thought but WP doesn’t like that. I have been testing my install with this change and so far its working fine.

]]>