Main menu

Video Post

This is an example of the Video Post Format:

Tip: for Vimeo videos please remember about using the HTTP (not HTTPS) protocol and the “www.” prefix.

Option files

Modification of administration panel content  in GavernWP is very easy – it is based on JSON files which include a list of options. Thanks to it, creating new options available in an administration panel is very easy.

Options files are in gavern/options catalog in a folder connected with a currently used language. In the catalog, you will find two main files groups:

  • tabs.json file – it includes a list of sections visible on the right side of an administration panel: meetgavern_wp-sidebar each section is described with a table in the form
    ["Basic", "options.basic", "enabled"]
    the first element of a table is a section name displayed in a panel, the second element is a file name without “.json” extension which stores a list of options available in a section given and the third value refers to whether a section given is visible in a panel. In this case, there will be a Basic tab displayed in a panel based on content of options.basic.json file.
  • options.*.json files – they include a list of options available in a section given – their names are strictly connected with the content of tabs.json file.

Each options.*.json file includes three main fields in an object stored:

  • groupname – it is a section title
  • groupdesc – it specifies a section description displayed directly under a  section title
  • fields – it includes a table of objects of fields displayed under the title and a section description

Each field defined by an object including the following fields:

  • name – it specifies an option name which will be connected with a particular field. There is a prefix added automatically to an option name which is a theme name (it is stored in a global variable – $tpl->name).
  • type– it specifies a field type. Standard fields are:
    • TextBlock – a field including a description text – it is not used for storing any option value
    • Text – the easiest text field allowing to insert short text values
    • RawText – pure, simple text without any formatting
    • Textarea – a text field used for inserting a greater number of text values
    • Select – a select field
    • Switcher – a checkbox restricted to two options: “Enabled” and “Disabled”
    • Media – a field allowing to choose images
    • WidthHeight – a field allowing to specify two values defining width and height (mostly used with a Media field)

These fields are defined in a gavern/form_elements/standard.php file and their code was derived from a GKFormInput field. It is worth remembering that files connected with options are parsed by a gavern/form.parser.php file. Additionally, you may create your own fields types in a gavern/form_elements catalog. In GavernWP, we have included the following fields types:

  • Menu – a field allowing to generate options connected with page’s menu – used in a Navigation section
  • ThemeStyle – a field allowing to choose page’s style – used at the beginning of a Basic section.

The description of creating your own fields types we will describe in the further part of this article.

  • label – it specifies a label text visible next to a field
  • tooltip – (optional) it allows to specify tooltip content which will appear after mousing over a label of a field given
  • default – default value of a field given
  • class – (optional) this field allows to specify CSS classes added to an element while generating it (if a field code supported such a functionality)
  • format – (optional) a field specifying a desired field content in the form of a regular expression. e.g. value: 
    specifies that a field given will be filled in correctly only when a user set as its value a sequence of capital or small letters from 2 to 5 symbols.
  • required – (optional) allows to specify whether filling in a particular field was required
  • visibility – (optional) specifies when a particular field is visible. Visibility rules are separated with commas and are created in FIELD_NAME=VALUE format – in the case of a few visibility rules, they are linked with AND operator. The value of  FIELD_NAME is a name without a prefix with a theme name. e.g.
    will cause that a field given will be visible when an option with option1 name will be set to 10 and, at the same time, an option2 option will have have value equals 20.
  • other – (optional) this field is used for storing additional values, e.g. in the case of a Select field, it is used for storing names and options values. This field is very useful when creating more advanced fields which may require additional configuration options.

After adding a new option, you have to remember about its support in the theme. Option value is loaded by using a get_option function of a schemata given:

get_option($tpl->name . '_OPTION_NAME', 'DEFAULT_VALUE');

when OPTION_NAME is an option name from a JSON file and DEFAULT_VALUE is default value of an option which will be used when a user does not specify a value of an option given. What is important, there is a “_” symbol which you cannot omit. A prefix with a theme name is added in order differentiate values of options of different themes.

Creating your own field types options

While creating a new field type, you have to start from creating a catalog compliant with a field name, e.g. CustomField in a gavern/form_elements catalog. Then, you have to create a config.json file in this catalog and fill it in according to the schemata below:

"name": "CustomField",
"description": "Example Custom Field",
"js": false,
"css": false,
"php": "customfield.php",
"class": "GKFormInputCustomField"

name, description, php i class fields have to include particular values; js and css fields are optional – they allow to specify whether a field given has to use additional CSS and JavaScript code (then, a name of files from a field catalog has to be set as a value). Also, you have to create a customfield.php file including a GKFormInputCustomField class derived after a GKFormInput class.

Also, a customfield.css file must include a safety code at the beginning:

// disable direct access to the file
defined('GAVERN_WP') or die('Access denied');

Each field class has to include at least one public method – output not loading any additional arguments. This method must return HTML code of a field given. Field properties froma JSON file are available as class fields, e.g. required is available as:


The second important public methid of each class of a form field is a getValue method which loads one argument – $default. Its use is optional and useful only when a value of a field given uses more than one field in the data base. Then, it is useful to overwrite this method – as an example we recommend a standard code of a WidthHeight field where overwritting a getValue method was used for storing values of two form fields in one main field created by a GKInputFormWidthHeight class.

The remaining class methods have to be created according to the needs of the author of a form  field given.

Social API settings

A section of options connected with Social API includes five groups of options:

  • options connected with sharing at Facebook
  • options connected with sharing on G+
  • options connected with sharing on Twitter
  • options connected with sharing on Pinterest
  • options allowing to switch on/off Social API on particular subpages.

Options connected with sharing are the equivalent of parameters available in online editors, used for creating buttons like:

The last group of options allows to specify where they will be displayed – thanks to Include/Exclude specified articles from Social API option, it is possible to switch off Social API completely or switch on/off this functionality only for chosen posts, subpages and categories.

We specify the list of posts, subpages and categories in three last options:


meetgavernwp_socialapias a sequence of ID, slug or the names of posts given, subpages or categories separated with comas, e.g. 


Advanced settings

An advanced settings section includes settings which are connected with different aspects of GavernWP framework work:


  • Widget rules  – it allows to switch on this mechanism. It is recommended to switch on this option in the case when there is no need to use widgets visible on a chosen subpages. Note that it will allow to optimize a little bit the speed of a website as operations of checking rules for each widget will not be made.
  • Custom Fields – it switches custom fields option, used to display additional information in the post.
  • Hidden Custom Post Fields – it specifies a list of the Custom Post Fields which will be always hidden. The names of fields should be separated by comma i.e. hidden1,hidden2,hidden3.
  • Google Analytics Tracking ID – The Google Analytics tracking code collects visitor’s data for your website and returns this data to Analytics where you can see it in reports. Enter your ID here.
  • Use Prefixfree script – Enable/Disable the usage of the Prefixfree script which causes that the CSS vendor prefixes are unnecessary.
  • Parse emoticons in the text widgets – it activates parsing emoticons to a graphic form in widgets.
  • Parse shortcodes in the text widgets – it activates parsing of Shortcodes in widgets.
  • Use Thickbox – it allows to switch on Thickbox  script for presenting images included in posts.
  • Value of variable $content_width this variable is used while creating thumbnails of images for posts, that’s why it has to be defined as an appropriate value – we recommend to set the value not bigger than the max. page’s width.
  • Excerpt length (in words) – specifies the value of the excerpt length used in the posts (the length is specified in words).
  • Use the override.css file – thanks to switching on this option, an override.css file will appear at the end of the list of CSS files which allows to overwrite theme’s CSS rules easily without interference in existing CSS code.
  • Add target blank to comments links – if this option is enabled, then every link in the comments text will open in a new browser tab.
  • Autolinking in comments – if this option is enabled, then every link in the comments text will be automatically changed into hyperlink
  • Enable support for Open Search – it allows to switch on support for  Open Search technology.
  • Enable support for Open Graph – it allows to switch on support for Open Graph  technology – after switching on this option, an additional metabox will appear on the page for editing posts: meetgavernwp_opengraph

Main back-end features

GavernWP has an advanced panel for managing theme’s options in an administration panel. These options have been divided into a few main groups:

  • Basic settings
  • Layout settings
  • Pages settings
  • Fonts settings
  • Navigation settings
  • Advanced settings
  • Shortcodes settings
  • Social API settings
  • Theme branding settings
  • Back-end branding settings
  • SEO settings

Also, some additional elements generated by a framework in an administration panel in some various places appear, namely:

  • Typography button
  • Widget rules
  • Open Graph metabox
  • GavernWP SEO settings metaboxes

It is also worth getting acquainted with a theme configuration with files use in JSON format:

  • Option files
  • Theme configuration

The ability of these files edition, gives a possibility of deep interference in websites work based on GaverWP.

Basic settings

Basic settings allow to specify basic parameters connected with the MeetGavern WP theme:


Theme color allows to choose a color version of a theme. Here, there may appear a few various fields depending on the conent of styles.json configuration file.

Style Switcher Display is an option allowing to switch a style-switcher after an option/options of choosing theme’s styles  – it is an element allowing for a website’s user to choose a theme style himself/herself.

Post sidebar informations option switches display of the post sidebar informations in the Meet Gavern WP theme.

The next option is connected with switching on breadcrumbs element on a website. There are the following options to choose from: Enabled, Disabled and Conditional rule – then, you have to set a rule using Conditional Tags and logic operators of PHP language in a Conditional rule field, e.g. a rule displaying a breadcrumbs element on the homepage and in the “Meet GavernWP” category will be in the following form:

is_homepage() || is_category('Meet GavernWP')

Social icons postition specifies the position of the social icons block.

Widget display on homepage option is useful when you want to place a widget instead of entries on the homepage – then  you have to switch it on mainbody widget position, place a widget needed which will replace a standard list of posts generated by WordPress.

Display author info allows to display information about its author under each post in the following form:

meetgavernwp_authorblockNext four options are using to include/exclude specific pages or categories from showing author block.
Include/Exclude mode specifies if the specified articles, categories will be included or excluded. Included/Excluded articles specifies the list of comma-separated article IDs/titles/slugs (i.e. 2,5,34,200 or post-title1,post-title2). Included/Excluded pages and Included/Excluded categories are similar, but they specify pages and categories.


SEO settings

GavernWP has SEO settings built – in which allow to overwrite WordPress standard SEO settings. After switching on “Use Gavern SEO settings” option, a lot of options connected with SEO will appear:

meetgavern-wp-settings1The first group of options is connected with page’s title:

  • Use blogname in title – this option allows to switch on showing a blogname in the title
  • Specify page title separator – it specifies a separator which is between a title description and a pages’s name
  • Set title description – it allows to specify page’s title description (the first part of a title – before a separator)
  • Set title blogname – it allows to specify page’s name (the second part of a title after a separator)

The remaining options allow to switch on advanced management of keywords and description metatags:


In the case of a homepage, these metatags values are specified in a SEO settings panel whereas in the case of subpages, there are two settings available for both metatags:

  • Disabled
  • Enabled (custom field in the post editor)

When you switch on these settings, under a posts editor two additional fields will appear:


If you fill them in, metatags used on one subpage with an entry will be created.

Fonts settings

One of the key elements which has influence on website’s look is an appropriate choice of fonts used for text presentation.

GavernWP allows to choose fonts easily which are assigned to CSS selectors specified by a user.

In order to simplify support for many fonts on one page, GavernWP supports groups of fonts – each group allows to assign a font given to selectors chosen by a user:


Groups of fonts are defined in a configuration file called fonts.json. Adding a new group of fonts is very easy – it is enough to define the next object of a form:

"full_name": "Full name of the fonts group",
"short_name": "short name of the fonts group using only alphanumeric characters",
"description": "Short description of the font family"

After adding such an object, in a table included in fonts.json file, you will see the next group of fonts to manage in an administration panel.

You have to specify three basic values for each group of fonts:

  •  a type of font used
  •  a font of a type given
  • selectors connected with a font given

Specifying of a font type is restricted to choosing one out of three fonts types:

    • Standard fonts – standard sets of fonts available on the majority of computers – you have to choose a font given from a list which is shown under the field of choosing a type of font: meetgavernwp_fonts2.jpg
    • Fonts Squirrel – fonts downloaded from Font Squirrel page – you have to download @font-face kit of a font given and place its content in fonts catalog.  It is very important to have a folder with the same name as a font name used in stylesheet.css file which is in a new catalog. If you prepare a catalog in this way, you will see a font given on the list to choose:  meetgavernwp_fonts3.jpg
    • Google Web Fonts – fonts from Google Web Fonts page; in this case, you have to specify the URL address of a font given:


  • Adobe Edge Fonts – fonts from Adobe Edge Web Fonts; in this case, you have to specify the URL address of a font given:meetgavernwp-fonts6


The last stage is specifying selectors connected with a font given:


After saving the settings, the results should be visible on the website immediately – it is not required to make any additional operations.

Main front-end features

Themes based on GavernWP framework have support for many useful solutions and technologies. The most important ones are:

  • Custom page styles – they extend functionality of standard subpages.
  • Typography – an advanced list of elements gives a possibility to enhance posts about various add ons.
  • Social API – it allows to add buttons for sharing posts in social network services very easily.
  • Open Graph – it allows to specify the way in which content shared on Facebook will be visible.
  • Threaded comments – they allow to make discussions under posts in a clear way.
  • Branding – it simplifies setting key elements of a website connected with its name or brand.
  • Color styles – thanks to color styles, it is possible to create many various color and stylistic versions of a theme.


Layout settings

Layout settings in a theme are connected with five main options:

meetgavernwp_layout.jpgThanks to a Page layout option, it is possible to specify a column position in page’s layout: on the left/right side or switch off showing a column completely (in this situation, you achieve the layout available via an additional subpage style – fullwidth).

A Theme width option specifies maximal page’s width – no matter what width a browser window has, page’s width will not exceed this value.

Column width is specified in per cents thanks to a Sidebar width option. Tablet width and Mobile width options allow to specify width of a browser window in pixels where css/tablet.css and css/mobile.css files are loaded.

In the case of tablet.css, modules which normally create four – column layout (max.), will appear in two – column layout which after loading a mobile.css file will change into one – column layout. Additionally, after loading a tablet.css file,a column moves under main content of a page given.

Note: all options from a Layout section are also in a live-preview editor which allows to adjust values of these options easily, thanks to a site live preview.


Hot links