Upcoming news and demo
This topic contains 17 replies, has 9 voices, and was last updated by Guust 10 years ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: caching, gd booster, varnish
-
AuthorPosts
-
November 25, 2014 at 7:03 pm #22593
Hi,
we just finished adding all the new stuff we developed in the past weeks on the official demo.
If you want to have a look and start testing, you can look here: http://wpgeo.directory
What’s new:
1) Multisite compatible
can’t really be tested there, but it is 🙂2) GeoLocation, advance search and autocompleter merged in 1 improved addon.
Autocompleter has been added to “Near” field. You can now search in a location different from the selected (no need to switch 1st).GeoLocation will take you to a page called : /location/me and it will show all listings around your position, in a radius defined by site admin. The GeoLocation can be triggered at 1st visit or disabled and triggered by the user via the “Share Location Button” (a new widget)
Clicking on the compass in the near field will show user defined radius and a “near me” checkbox. Enabling “near me” will show your position on the map. You can also move the position to a different place and search around it.
3) GD Booster taking GD from 30 something to 89 on Google pagespeed. 96 for user experience. http requests reduced by 70%. All internal CSS and JS that could be concatenated are merged in 2 files (1 css and 1 js obviously). It provides html page cache too, Gzip and enables browser caching.
4) New optimized queries. Home page queries have been reduced by 77% and memory usage by 50%.
Jeff is still working on Shrtcodes and probably he will have to change something because of the above.
We will start releasing all in beta 1st, to make sure that you can test it and report problems before we release them as new offical version.
Looking forward to hearing your feedback.
Thanks,
The Team
November 25, 2014 at 10:59 pm #22607Great news!
Looking forward to the multisite compatibility 🙂
November 26, 2014 at 5:28 am #22624Awesome News! Score for the home team!! Goo gle gonna love the GD Booster!
November 26, 2014 at 12:17 pm #22670And how about search on all CPT? Are you working on that?
November 26, 2014 at 3:40 pm #22696bugs
– when view location las vegas and comeback homepage then view any listing. breadcrumbs will be las vegas although you viewing listing in new york– when view a location and comeback homepage, browser always ask for share location, i think set this feature just asking for first time only. or you can make 1 option for GD auto set location for user when view listing
– I think location switcher you should make 1 search field suggest locations in site instead dropdown for country, state, city. it hard to change location. if you make this is a search suggest location it will easy to change location (look like yelp)
November 26, 2014 at 3:46 pm #22697And with plugin gd booster. I use w3 total cache to minify any script and css i want. Browser caching, i don’t use page cache on w3 because will have some bugs with location. i use w3 total cache and i have 96/100 score on webpagetest.org
– With me “I think new location plugin hard to use and not effective”
November 26, 2014 at 7:23 pm #22721Hi,
the 1st bug was due to GD-Booster, not multilocation and a quick tweak already solved it. Thanks for spotting it. (we didn’t test enough as logged out users.)
I think location switcher you should make 1 search field suggest location
This is how it works, the near field now allows to switch location too.
W3TC is not 100% compatible with GD and it will never be unless the plugin author starts tweaking his plugin to easily work with GD. Given that I doubt that will ever happen, we developed GD-Booster. If you wish to keep using w3tc instead, that’s your choice.
Thx
November 26, 2014 at 7:45 pm #22722we looked into it, but didn’t include it in this release.
The way CPT details are stored in the database (to avoid all the joins needed with the default wordpress db structure), doesn’t allow to perform a search on all CPTs without having to do 1 query for the main search and another query for each result, to get the info needed to order/sort them.
Example : for a search page with 10 results, we would need 11 queries.
That could be extremely slow and considering that this is the case for both search results and map results, we would avoid this.
Another option would be to create a new table (a big one) that would be the sum of all GD CPT tables used only in case someone wants to search in all CPT.
It will still be slower than a regular search, but probably a bit better than the 1st option.
In any case, this can only be worked on in the next batch of releases and now in the upcoming one, because in any case it would require a lot of extra code.
Thanks
November 27, 2014 at 11:45 am #22837Will GD Booster adversely affect my site if my host uses Varnish? Is it a separate and an optional plugin?
November 27, 2014 at 6:23 pm #22872Yes, it is an addon, if it doesn’t work correctly with your managed server you can avoid installing it.
Thx
December 2, 2014 at 3:39 am #23223where do we find GD Booster?
December 2, 2014 at 6:13 am #23227It is part of the beta, once extracted, you’ll find it as a plugin folder.
Once uploaded it is in your WP menu.December 2, 2014 at 10:39 am #23242When i upload and click activate,it show a fatal error.
Warning: require_once() [function.require-once]: Unable to access gd_upgrade.php in /home/xxx/plugins/geodir_gd_booster/geodir_gd_booster.php on line 49
Warning: require_once(gd_upgrade.php) [function.require-once]: failed to open stream: No such file or directory in /home/xxx/plugins/geodir_gd_booster/geodir_gd_booster.php on line 49
Should i wait for final release.
December 2, 2014 at 12:37 pm #23256@hirman
This is only beta, so we can fix all bugs like that. I guess you only get this when you activate the GD Booster?
What you get there is a warning only, and will be fixed in the final release.December 2, 2014 at 5:40 pm #23285Hi,
at the moment I would suggest to open file geodir_gd_booster.php, go to line 49 and change this:if ( is_admin() ){ require_once('gd_update.php'); }
to this
/*if ( is_admin() ){ require_once('gd_update.php'); }*/
This should remove the error. In any case this is a beta and autoupdate will not work until we release the official version.
Let us know,
Thx
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket