Benjamin Schmitz
Forum Replies Created
-
AuthorPosts
-
Yes, I’m aware of the options in Advanced Search. However, while we do want users to be geolocated on most of the pages, links to articles and forums we share on social media should take users to the link location without redirecting or asking for geolocation.
Thanks for the answer!
Thanks Stiofan!
This reply has been marked as private.Thanks Guust
This reply has been marked as private.Hi Guust,
I’m talking about share buttons, not “like” buttons. Those are two different features.
A good example of sharing buttons would be on your supreme directory demo.
https://wpgeo.directory/supreme-directory/places/united-states/pennsylvania/philadelphia/restaurants/buddakan/
The icons at the top section – facebook, twitter,google – below “heart” icon.Kor Chung,
That worked perfectly. Tested it both for the places and the events. Thanks you!!Thanks man, didn’t realize I need to customize listing-listview.php.
All done, working great. Thanks.January 12, 2017 at 11:58 am in reply to: Hiding "Import Details from Social" on single custom post type #341377Worked perfectly.
Didn’t know there is a shortcode available for add listing.December 28, 2016 at 2:53 pm in reply to: Location switcher slow response time – need assistance #331863It looks fine now. One question about the categories on location page. You have marked all the categories except one to not being visible on the map.
So in most cases, when the location page is loaded, there are only a few listings because of the map selection. However, when I tick to show another category, all I get are the pins on the map. The list of listings below the map is not refreshed/synced with that action.
Can something be done about it? So it refreshes based on the selected categories in the map?
This way, I don’t see any option to browse listings from the current region.
Thanks
December 23, 2016 at 5:12 pm in reply to: Location switcher slow response time – need assistance #329796This reply has been marked as private.December 23, 2016 at 5:10 pm in reply to: Location switcher slow response time – need assistance #329795Thanks for the fonts! Thought it was caching or something. Location switcher in the main menu, scrolling through the city tab works, but for the region it doesn’t. You can only see the first 5 regions and have to type in if you want to see Texas for example.
December 23, 2016 at 4:37 pm in reply to: Location switcher slow response time – need assistance #329781Also, the scroll on the location switch doesn’t work on most pages.
December 23, 2016 at 4:35 pm in reply to: Location switcher slow response time – need assistance #329761Thanks, I will give it a try. However, I do see that the CSS is broken now.. At least the fonts.. Can you please check on that? Thanks
December 23, 2016 at 9:18 am in reply to: Location switcher slow response time – need assistance #329617A few more things on SQL queries – There are a few slow queries on each action regarding search and locations. For example, the query for switching location
SELECT SQL_CALC_FOUND_ROWS PREFIXposts.*, PREFIXgeodir_gd_place_detail.* FROM PREFIXposts INNER JOIN PREFIXgeodir_gd_place_detail ON (PREFIXgeodir_gd_place_detail.post_id = PREFIXposts.ID) WHERE 1=1 AND ( PREFIXposts.post_status = 'publish' OR PREFIXposts.post_status = 'private' ) AND PREFIXposts.post_type = 'gd_place' AND post_locations LIKE '%,[california],%' GROUP BY PREFIXposts.ID ORDER BY PREFIXposts.post_date DESC, PREFIXposts.post_title ASC LIMIT 0, 5
which takes 0.6747sec to be executed and it’s considered slow. Could it be due to a usage LIKE query? Just for fun, I changed the query and used FULLTEXT search on this query and the query took 0.0002sec with the same results. That’s XXX times faster.
LIKE with wildcarding on the left side (IE: LIKE ‘%Search’) can not use an index (assuming one exists for the column), guaranteeing a table scan. LIKE ‘%Search’ and LIKE ‘%Search%’ can not use an index; LIKE ‘Search%’ can use an index as far as I know.
For location switcher, regions and cities are strictly defined values, right? Maybe I’m wrong about this, but why use LIKE if we know where and what to look for? Hope that makes some sort of sense..
For the advanced search.. The database get’s clogged just by typing in the search term. Disabling autocompleter definitely have an impact on performance in good a good way, but as I said above, ‘%Search%’ will always guarantee a full table scan, while ‘Search%’ can use an index.
But still, the fact that the query takes forever with autocompleter enabled, indicates there’s something wrong with it..
Thoughts?
-
AuthorPosts