Different views cache settingsAccelerator for WordPress

The purpose of that settings is to provide correct caching of some environment depended on views such as current language, device type, etc. But excluding user-dependent data that can be tuned in the related setting’s part.

settings-Views

General#

  • Separate by below criterias

    Enables cache separation.

Device types#

List of groups by a set of user-agents. Settings for each group:

  • Enable

    Enables current group.

  • Name and slug

    Unique group name. This name is used to generate a slug when saving, which is used to name the caching directory and when adding custom styles.

  • Agents

    Only pages’ requests having these strings in their user-agents will be included. If string begins with one of /~@;%`# it is interpreted as regular expression. Also, user-agent’s part can be compared by appending string with = or != and exact value (with logical ‘&’ operator as well) as in cookies below. E.g. !@\Wchrome/\d+\W@ & @(?:\W|^)safari/[\d\.]+(?:\W|$)@.

Compatibility#

List of groups by a set of user-agents, for which optimization will be performed in a compatible (sparing) mode. For example, the ‘Lite optimization’ group does not lazy load CSS and JS. And for ‘Lite optimization with minimum HTML size’ are not done inline yet images and styles to minimize HTML size. Settings for each group:

  • Enable

    Enables current group.

  • Agents

    Only pages’ requests having these strings in their user-agents will be included. If string begins with one of /~@;%`# it is interpreted as regular expression. Also, user-agent’s part can be compared by appending string with = or != and exact value (with logical ‘&’ operator as well) as in cookies below. E.g. !@\Wchrome/\d+\W@ & @(?:\W|^)safari/[\d\.]+(?:\W|$)@.

Parameters#

A list of grouped parameters such as arguments and cookies. Settings for each item:

  • Enable

    Enables current item.

  • Group name

    Unique group name.

  • Cookies

    Only pages’ requests having cookie names that begin with any of the specified strings will be included. If name begins with one of /~@;%`# it is interpreted as regular expression. Also, cookie’s value can be compared by appending name with = or != and exact value (with logical ‘&’ operator as well). E.g. @^cookie_1$@ = v1 & @^cookie_2$@ != v2 means that cookies cookie_1 and cookie_2 will be used only if cookie_1 equals to v1 and cookie_2 not equal to v2. Also, you can check the cookie for the absence or empty value by prepending name with !, for example, !@^cookie_1$@.

  • URI arguments

    Only pages’ URLs having arguments that begin with any of the specified strings will be included.

Leave a Reply