adyp

That worked fantastically well – I doubled it to 16px and now it looks great, even the most squinty-eyed will be able to see that!

Thanks Paolo

I can only see an image ‘down-arrow.png’ in the images folder of the geodir_location_manager plugin – not an image called ‘downarrow-img.png’ – is that what I need to replace?

Is this sourced from a gallery somewhere of different coloured down arrows, where I can find a yellow one? And if so, won’t it just be over-written when Location Manager is next updated?

Thanks,
Adrian

Thanks Paolo,

I have tried adding

color: yellow;

to that CSS but it makes no change:

.geodir_location_tabs_head .geodir_location_tabs.gd-tab-active {
color: yellow;
}

Any ideas?

Hi Stiofan,

I genuinely am sorry this is causing friction – and do not want you to feel I am ‘punishing’ GD for not resolving this (my WP GD plugin review is the full 5 stars).

For me, an expectation is set in GD Documentation that is not delivered: the page https://wpgeodirectory.com/docs/useful-plugins/#logic sets out how to use the plugin Widget Logic to target widgets (and therefore functionality/content) based on location:

Will show the widget if the location is Queensland:
1

strtolower(geodir_get_current_location(array('echo' => false)))==strtolower('queensland')

… but this targeting based on location will not work with if the search is based on geolocation. It is therefore not correct to state in that documentation that “we know the [plugins] listed here all work without any conflict with GD” in the case of location logic.

This means I am unable to target widget functionality or content based on location if I want to make use of one of the main functions (geolocation) of a location-based directory. This is not an irrelevant issue with a multi-location based directory: it prohibits location-based advertisement slideshows/content unless you are willing to live without geolocation.

Now, perhaps if my expectation hadn’t been raised by the promise (location-based widgets) made in the documentation I might not have pursued this issue (although now location-based widgets is something that I want to achieve).

I realise that there are reasons for you wanting the ‘Near Me’ functionality to work the way it does, but I would have thought it could carry on working the way it does while also returning a variable/value for geolocated country location of the searcher that can be used in Widget Logic.

We differ in where we see the boundary between paid-for-customization and support to tidy up existing functionality – if I my expectations are too high that only reflects the high level of assistance that is usually provided on the forum (and you might want to add a caveat or two on the GD documentation on using location in Widget Logic – so as to avoid others traveling the frustrating path I am on with this).

Best wishes,
Adrian

For anyone who finds this thread looking to address this issue, here is how I resolved it:

Forced to choose between looking to grow/monetize my directory with country specific cross-promotions and adds using Widget Logic to display slideshows in appropriate country search results OR having geolocation (i.e., Search Near Me – in search bar or widget) – I had to ‘bite the bullet’ and stop visitors being geolocated and accessing geolocation search results.

To do this, I removed the Near Me widget fro my site and used the following additional css to remove the ‘Near Me’ option from search bar:

div.gd-advanced-s-menu-near {display: none;}

I had to do this because GD support does not stretch to showing how to display country specific widgets using Widget Logic on geolocated (Near Me) search result pages. It’s a shame doing without a key function like geolocation/Near Me searches, but promoting and monetizing the directory have to come first – and there is no way I can strike advertising or cross-promotion deals on a country-by-country basis when I cannot ensure the country-specific adds show for all searches relating to that country.
🙁

If anyone figures how to work Widget Logic to display widgets on geolocated search result pages (maybe with a Code Snippet), then perhaps they could post here?
Thanks

Thanks Stiofan,

I will spend some time looking at this, although I think it is a little outside my capabilities at the moment.

Adrian

Hi Stiofan,

There is no way i can think of that this would work with widget logic.

Please be patient with me, but this is the situation as I see it – please point out the flaw in my reasoning and I will leave it for now:

1. GD contains the coding to have the click of a button return visitor’s country based on geolocation data (if shared) – as happens with the cross-hairs button on the add-listing page DEMONSTRABLY TRUE;

2. Widget Logic is able to use country location to display or not display a widget based on country – this is what I am doing at the moment with widgets on the location pages displayed as a result of using the Location Selector (I have just coded Australia and UK when selected from Location Selector so far as a ‘proof of concept’ – the code for doing this is in GD documentation) DEMONSTRABLY TRUE;

3. If the same functionality (returning geolocated country) that the cross-hairs button demonstrated in 1. is added to the Near Me widget button (in addition to what it currently does) then Widget Logic will be able use that country data (as in 2.) to determine whether a widget appears on the /me page that the Near Me button loads. LOGICALLY TRUE).

I believe that this logic is water-tight. I would be happy to be shown otherwise – or where either of my first 2 premises are false!

Thanks,

Adrian