GD Booster Add-on Overview

On this page

Introduction Installation Configuration Known issues

Introduction

Nothing drives away users like a slow-loading site. Here’s a total lightning rod for your directory! GD Booster incorporates some of the smartest caching, compression and minifying methods available today for WordPress to put a rocket under your GeoDirectory site.

Just activate the add-on and see your Google PageSpeed and load times improve dramatically. No technical knowledge is required. Simply check and uncheck options to add or subtract functionality.

With GD Booster on board, your GeoDirectory listings will never slow down your site, however many you add. Go on, add a million!

Important: this add-on must not be used with other third-party caching plugins.

Installation

  1. Visit wpgeodirectory.com ( Buy a subscription if Required )
  2. Navigate to My Account > Downloads ( Login if Required )
  3. Download Geodir Gd Booster zip file.
  4. Go to your WordPress site dashboard, Navigate to  Plugins > Add New > Upload Plugin
  5. Browse and Upload the zip file you downloaded from wpgeodirectory.com
  6. Activate the plugin.

Configuration

After plugin activation, navigate to GD Booster

To expand all setting groups

expand

To collapse all setting groups

collapse

To restore default settings

restore

To clear site cache

clear

Enable/Disable

1

To enable

  1. Check Yes, enable GD Booster!
  2. Scroll to bottom of the page
  3. Click Save All Changes

To disable

  1. Check No, disable.
  2. Scroll to bottom of the page
  3. Click Save All Changes

Notes

  1. Yes, enable notes in the source code so I can see it’s working (recommended).
    1. Screen Shot 2015-07-14 at 8.00.26 pm
  2. Yes, enable notes in the source code AND show debugging details (not recommended for production).
    1. This option adds debugging details in source code
    2. Not recommended for production
  3. No, I don’t want my source code to contain any of these notes.
    1. Disable notes and debugging details in source code

Plugin Deletion Safeguards

2

  1. Uninstall on Plugin Deletion; or Safeguard Options?
    1. Safeguard my options and the cache (recommended).
      1. if you want to keep GD Booster settings you can use this option.
    2. Yes, uninstall (completely erase) GD Booster on plugin deletion.
      1. if you want to completely uninstall GD Booster you can use this option.

Directory / Expiration Time

3

  1. Base Cache Directory (Must be Writable; e.g. Permissions 755 or Higher)
    1. This is where GD Booster will store the cached version of your site
    2. By default, this directory is created by GD Booster and the permissions are setup automatically.
    3. In most cases there is nothing more you need to do.
  2. Automatic Expiration Time (Max Age)
    1. If you don’t update your site much, you could set this to 6 months and optimize everything even further.
    2. A default value of 7 days (recommended); is a good conservative middle-ground.
    3. The value that you specify here MUST be compatible with PHP’s strtotime() function.
    4. Examples:
      1. 30 seconds
      2. 2 hours
      3. 7 days
      4. 6 months
      5. 1 year

Client-Side Cache

4

  1. Allow Double-Caching In The Client-Side Browser?
    1. No, prevent a client-side browser cache (safest option).
      1. Setting this to No is highly recommended when running a membership plugin like s2Member (as one example).
      2. In fact, many plugins like s2Member will send nocache_headers() on their own, so your configuration here will likely be overwritten when you run such plugins (which is better anyway).
      3. In short, if you run a membership plugin, you should NOT allow a client-side browser cache.
    2. Yes, I will allow a client-side browser cache of pages on the site.
      1. if users do NOT log in/out of your site, then this option will be better.

GET Requests

5

  1. Caching Enabled for GET (Query String) Requests?
    1. No, do NOT cache (or serve a cache file) when a query string is present.
      1. Always use this option. UNLESS, you’re using unfriendly Permalinks.
      2. In other words, if all of your URLs contain a query string (e.g. /?key=value); you’re using unfriendly Permalinks
      3. Ideally, you would refrain from doing this; and instead, update your Permalink options immediately; which also optimizes your site for search engines.
    2. Yes, I would like to cache URLs that contain a query string.
      1. if you really want to use unfriendly Permalinks, and ONLY if you’re using unfriendly Permalinks, you should use this option.

404 Requests

6

  1. Caching Enabled for 404 Requests?
    1. No, do NOT cache (or serve a cache file) for 404 requests.
      1. When this is set to No, GD Booster will ignore all 404 requests and no cache file will be served.
    2. Yes, I would like to cache the 404 page and serve the cached file for 404 requests.
      1. When this is set to Yes, GD Booster will cache the 404 page (see Creating an Error 404 Page) and then serve that single cache file to all future 404 requests.

RSS, RDF, and Atom Feeds

7

  1. Caching Enabled for RSS, RDF, Atom Feeds?
    1. No, do NOT cache (or serve a cache file) when displaying a feed.
      1. Always use this option, UNLESS, you’re sure that you want to cache your feeds.
    2. Yes, I would like to cache feed URLs.
      1. If you use a web feed management provider like Google® Feedburner and you set this option to Yes, you may experience delays in the detection of new posts
      2. This option affects all feeds served by WordPress, including the site feed, the site comment feed, post-specific comment feeds, author feeds, search feeds, and category and tag feeds.

GZIP Compression

8

  1. GZIP Compression (Optional; Highly Recommended)
    1. If you want to enable GZIP, create an .htaccess file in your WordPress® installation directory, and put the few lines in it.
    2. Alternatively, if you already have an .htaccess file, just add those lines to it, and that is all there is to it.
    3. GZIP is now enabled in the recommended way!
    4. Or, if your server is missing mod_deflate/mod_filter; open your php.ini file and add this line: zlib.output_compression = on

Theme/Plugin Developers

9

  1. Developing a Theme or Plugin for WordPress?
    1. In your PHP script, set: $_SERVER[‘GEODIR_GD_BOOSTER_ALLOWED’] = FALSE;
    2. or define(‘GEODIR_GD_BOOSTER_ALLOWED’, FALSE).
    3. GD Booster is also compatible with: define(‘DONOTCACHEPAGE’, TRUE).
    4. It does’t matter where or when you define one of these, because GD Booster is the last thing to run before script execution ends.
  2. Writing “Advanced Cache” Plugins Specifically for GD Booster
    1. Theme/plugin developers can take advantage of the GD Booster plugin architecture by creating PHP files inside this special directory: /wp-content/ac-plugins/.
    2. There is an example plugin file @ GitHub (please review it carefully and ask questions).
    3. If you develop a plugin for GD Booster, please share it with the community by publishing it in the plugins respository at WordPress.org.

JS/CSS Files Exclusion From Combines

10

  1. Excludes JS/CSS Files when combine in one file.
    1. Sometimes there are certain cases where a particular js/css file you don’t want to combine.
    2. Please enter file names per line to exclude;
    3. Example:
      1. autocomplete.js
      2. autocomplete.css
    4. OR for same file names use
      1. myplugin/js/script.js
      2. myplugin/css/style.css.
    5. Note: please remember that each file name must be per line.

Known Issues

  1. WordPress.com – GD Booster is not currently compatible with WordPress.com or any other host that does not allow the Write Access to the wp-content folder.
  2. GD Booster currently requires that a file called advanced-cache.php be placed inside the wp-content folder.