identity

One other thing I just noticed though is that if you select one of the suggested locations (e.g., In: Some City) the h1/title on the search page includes the search term, but not the location. The results are filtered by that location though.

If you type in a specific address location, rather than selecting one of the suggested cities, that location is included in the h1/title (based on my programmatic pattern at least).

Explore %%search_term%% %%search_near%%

Don’t know if that is specifically a bug or just a quirk 😉

Cheers

Stiofan,

Always a pleasure. Super impressed with the changes over the years and exciting to dive back in and resurrect my project!

And as always, appreciate your time and further detail. I totally understand everything is a balancing act, and speed as we know has become critically important for many reasons.

All in all, I do like the way a lot of this is handled and what is most critical is that someone backing out of a listing doesn’t have location changed and the result set doesn’t change on them. I’m sure I can play around a little more with the configuration and setup to get something I’m happy with.

I like that you are using TripAdvisor as a bit of a benchmark as I think they’ve done an amazing job and probably the gold standard above Yelp, AirBnB, etc.

Thanks for pointing out the location icon… I’d really like to request/recommend that instead of that, a more prominent indicator for clearing could be made, perhaps with the clearing indicator to the right of the location name (https://fontawesome.com/icons/times-circle?style=regular), perhaps like this:

!Chicago x

One thing I think TA does that also helps with this is the breadcrumbs and forcing the user to select a location even upon entering into any of the categories.

I know Yoast or other 3rd party tools can be used for breadcrumbs to duplicate that, and the “location force” is also mixed…for a large site like TA, totally makes sense, maybe not so much on a hyper-local.

Thanks as always for listening. I know you take the feedback and recommendations into consideration and work them in when possible.

Cheers

Alex,

Right, understand. Not to harp on it, but I think this is a key UX area, so please indulge…

My view is that this is a passive interaction at best, and one which the user may not even be aware of. In either case, I think the main issue here is specifically the passive nature of this.

For a large geo area, maybe this isn’t such an issue….one could assume that if I click on a listing for restaurants in California that I then want to see listings in California only. But for hyper-local sites where various cities might be contained within “reasonable consideration” distance, this could be very impactful.

In both cases of archive links (both Archive URLs and Archive URLs on Details Page; see *Note below) set or disabled, as a user, things happen that I may not specifically be expecting, wanting, or again, even be aware of.

Examples (4 primary use cases):

Archive links enabled, user not changing location:
– Click Restaurants (All locations)
– Click a listing (Location passively changed to Seattle)
– Click Fine Dining category link/icon from listing (Seattle)
– Go to Fine Dining category and view listings only for Seattle
{would consider this an unexpected user experience…we assume the user wanted to limit listings by Seattle}
– Click to homepage or non-GD page (Location passively changed to All locations)
– Click into Bars category (All locations)
– Click into a listing (Location passively changed to Redmond)
= Location changes are being made on the behalf of the user, which they may or may not expect, want, or even be aware of).

Archive links enabled, user actively changing location:
– Click Restaurants (All locations)
– Selects Seattle
– Redirects to Seattle location page
– Clicks Restaurants again (Seattle)
– Click a listing (Seattle)
– Click Fine Dining category link/icon from listing (Seattle)
– Go to Fine Dining category and view listings only for Seattle
{would consider this an expected user experience…user wanted to limit listings by Seattle}
– Click to homepage or non-GD page (Location passively changed to All locations)
– Click into Bars category (All locations)
– Click into a listing (Location passively changed to Redmond)
{unknown expectations…user may expect or understand location reset, or may have expected to still be limited to Seattle}
= Location changes are being made on the behalf of the user, which they may or may not expect, want, or even be aware of).

Archive links set to disable, user not changing location:
– Click Restaurants (All locations)
– Click a listing (All locations)
– Click Fine Dining category link/icon from listing (All locations)
– Go to Fine Dining category and view listings for all locations
{would consider this an expected user experience…user has not actively limited location nor has it been changed}
– Click to homepage or non-GD page (All locations)
– Click into Bars category (All locations)
– Click into a listing (All locations)
= Location changes are not being made on the behalf of the user, which is what they would most likely expect).

Archive links disabled, user actively changing location:
– Click Restaurants (All locations)
– Selects Seattle
– Redirects to Seattle location page
– Clicks Restaurants again (All locations)
– Click a listing (All locations)
– Click Fine Dining category link/icon from listing (All locations)
– Go to Fine Dining category and view listings for All locations
{would consider this an unexpected user experience…user wanted to limit listings by Seattle, which became reset}
– Click to homepage or non-GD page (All locations)
– Click into Bars category (All locations)
– Click into a listing (All locations)
{unknown expectations…user may expect or understand location reset, or may have expected to be limited to Seattle}
= Location changes are being made on the behalf of the user, which they may or may not expect, want, or even be aware of).
* Note: this example does change a little bit if Archive URLs are enabled, but Detail page disabled; but a passive change again happens clicking to Fine Dining from the listing.

In all examples, there are passive changes being made, perhaps with lesser extent on the Archive URLs enabled and only Detail Page disabled, but still points where potentially unexpected changes are being made.

I think users can understand that navigating away from the directory pages (ie to homepage or non-directory page) could/would/might reset location. What I think most users would consider unexpected is location being changed passively “on their behalf” in the various examples above.

I don’t know of any other sites that operate in this way.

Cheers

Thanks Alex,

It would be nice if a “clear” or “everywhere” (like in V1) option could be added to the Location Changer for usability.

Can you detail the affect of the “adding location” as you mentioned above. I know the option and had it set to City, but now I’m not entirely sure I understand the impact and function of that option.

Thanks!

Thanks Naveen.

Understand and hopefully it can be added sometime down the road as I’m sure it would prove beneficial to the UX.

Cheers

FYI,

I was able to get PHP Compatibility Checker running now as well and nearly all plugins were marked as okay with 7.3 (main GD, GD Google Analytics, Invoicing, and Ninja Forms timed out unfortunately).

GD Event Manager did come back with these errors though:

geodir_event_manager/includes/class-geodir-event-api.php
————————————————————————————————————————
FOUND 2 ERRORS AFFECTING 2 LINES
————————————————————————————————————————
283 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
292 | ERROR | Extension ‘mysql_’ is deprecated since PHP 5.5 and removed since PHP 7.0; Use mysqli instead
————————————————————————————————————————

Cheers