+ {/if}
-The domain name for your site, trimmed of any subdomains. For instance, beta.example.com becomes example.com. Typically only used in the Atom feed Template.
+#### `{avatar_image_width}`
-### `{url_title}`
+The width of the avatar image associated with the entry's author. Typically used as such:
-The human readable title used in the URL as a permalink.
+ {if avatar}
+

+ {/if}
-### `{url_title_path}`
+#### `{avatar_url}`
- {url_title_path='channel/archives'}
+The URL to the avatar image associated with the entry's author. Typically used as such:
-The URL to the specified template. The "url title" of the entry will be automatically added. For example, this:
+ {if avatar}
+

+ {/if}
-
permalink
+#### `{email}`
-Would be rendered like this:
+The author's raw email address.
-
permalink
+#### `{ip_address}`
-### `{username}`
+The IP address of the author when they posted the entry.
-The author's username.
+#### `{member_search_path}`
+
+ {member_search_path='search/results'}
-### `{week_date}`
+This variable is replaced by a URL that passes the author's member name to your search results Template. In this way, you can display all entries made by the author. You should specify the Template_Group/Template that you use to display search results. For example:
- {week_date format="%Y %m %d"}
+
View entries by this member
-The date that the week of the currently displayed entry started on, most commonly used in "weekly" scenarios with the [date_heading](#date_heading) variable pair.
+### `{profile_path}`
-This variable is affected by the [start_day=](#start_day) parameter. By default, the week date will fall on Sunday for the week of the entry. When `start_day="Monday"` is used, the week date will fall on Monday for the week of the entry. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
+ {profile_path='member'}
-## Conditional Tags
+DEPRECATED. The URL to the author of the current entry using [Legacy Member Profile Templates](member/profile-templates.md). The ID number of the author will be automatically added. Used in a link:
-[TOC=3 hide]
+
{author}
-Conditionals allow you to more precisely control your content.
+#### `{screen_name}`
-NOTE: **Note:** A more complete explanation of conditional control structures and operators can be found on the [Conditional Tags](templates/conditionals.md) page.
+The author's screen name, if it exists. This variable will not return anything if the author does not have a screen name defined.
-Here is an example that tests for the "summary" field being not empty
+#### `{signature}`
- {if summary != ""}
- The summary is not empty!
- {/if}
+DEPRECATED. The signature associated with the entry's author. Typically used as such:
-An alternate, shorthand syntax can accomplish the same thing
+ {if signature}
{signature}
{/if}
- {if summary}
- The summary is not empty!
+#### `{signature_image_height}`
+
+DEPRECATED. The height of the signature image associated with the entry's author. Typically used as such:
+
+ {if signature_image}
+

{/if}
-If only the variable name is in the conditional statement it tests for "not empty".
+#### `{signature_image_url}`
-Many of the single variables can be used in a conditional. You may always use the short name of one of your custom entry fields in a conditional. In addition, there are several unique conditionals.
+DEPRECATED. The URL to the signature image associated with the entry's author. Typically used as such:
-### `{if allow_comments}`
+ {if signature_image}
+

+ {/if}
- {if allow_comments} content {/if}
+#### `{signature_image_width}`
-This special conditional lets you conditionally display content if the current entry is set to allow comments. This conditional will return FALSE if commenting has expired.
+DEPRECATED. The width of the signature image associated with the entry's author. Typically used as such:
- {if allow_comments}
- ({comment_total})
Comments
+ {if signature_image}
+

{/if}
-Or you can display content if commenting is disabled:
+### `{username}`
- {if allow_comments == FALSE} content {/if}
+The author's username.
-### `{if avatar}`
+#### `{my_member_custom_field}`
- {if avatar} content {/if}
+Any of [custom profile fields](control-panel/member-manager.md#custom-member-fields) for entry's author can be accessed using the field's short name (as single tag or tag pair, whichever is supported by the [field type](/fieldtypes/overview.md))
-This special conditional lets you conditionally display content if the current entry's author has an avatar image specified.
+### Comment Variables
- {if avatar}
-

- {/if}
+[TOC=4]
-### `{if category_request}`
+#### `{comment_auto_path}`
- {if category_request} content {/if}
+This variable is replaced by the URL set in the **Comment Page URL** preference under `Developer --> Channels` in the channel's **Settings** tab. No entry id, URL Title, or other information is included; this is the exact URL from the preference.
-This special conditional lets you conditionally display content if the current tag is being displayed based on a category specified in the URL. For instance, if the URL being viewed were
that could trigger this conditional.
+#### `{comment_expiration_date}`
-### `{if count}`
+ {comment_expiration_date format="%Y %m %d"}
- {if count > 5} content {/if}
+The date on which commenting expires for this entry, if they do. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
-This conditional allows you to test against which number entry is being displayed. You could use this to apply different styles to the first entry or have the last 5 entries out of 10 be formatted differently.
+#### `{comment_entry_id_auto_path}`
-### `{if forum_topic}`
+This variable is replaced by the URL set in the **Comment Page URL** preference under `Developer --> Channels` in the channel's **Settings** tab. The ID number of the entry will be automatically added. For example, this:
- {if forum_topic} content {/if}
+
my entry
-You may use this conditional for displaying content when a forum topic has been associated with a channel entry. That option is only available if the Discussion Forum Module is installed. It will typically be used like so:
+Would be rendered like this:
- {if forum_topic}
-
Discuss this in our forums
- {/if}
+
my entry
-### `{if has_categories}`
+#### `{comment_subscriber_total}`
-Handy conditional for displaying markup or content based on whether or not the entry has been assigned any categories.
+Total number of subscribers to comments for a particular entry.
- {if has_categories}
-
Categories
+#### `{comment_total}`
-
- {categories}
- ...
- {/categories}
-
- {/if}
+The total number of comments for a particular entry.
-### `{if no_results}`
+#### `{comment_url_title_auto_path}`
- {if no_results} content {/if}
+This variable is replaced by the URL set in the **Comment Page URL** preference under `Developer --> Channels` in the channel's **Settings** tab. The URL Title of the entry will be automatically added. For example, this:
-You may use this conditional for displaying a message in the case when no entries are returned. The contents inside of the conditional will be displayed in cases where there are no results returned for the tag.
+
my entry
- {if no_results}
There are no entries available.
{/if}
+Would be rendered like this:
-Further, you may specify that another Template be shown in a case when there are no results. In order to do that, you must use the redirect=variable
+
my entry
- {if no_results} {redirect="channel/noresult"} {/if}
+#### `{recent_comment_date}`
-Lastly, if you want to simply display your 404 page (with 404 headers) when no entries are returned, simply use "404" as the template name.
+ {recent_comment_date format="%Y %m %d"}
- {if no_results} {redirect="404"} {/if}
+The date of the most recent comment associated with the entry. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
-NOTE: **Note:** If you have several nested tags, each one would need to include a `{if no_results}` pair to be parsed correctly.
+### Date variables
-For instance, if you have Grid field with `{if no_results}` block, the parent `{exp:channel:entries}` tag pair would need to include `{if no_results}` block as well.
-```
-{exp:channel:entries channel="blog"}
- {if no_results} No entries {/if}
- {my_grid_field}
- {if no_results} Grid is empty {/if}
- {my_grid_field:text}
- {/my_grid_field}
-{/exp:channel:entries}
-```
+[TOC=4]
-### `{if not_category_request}`
+#### `{edit_date}`
- {if not_category_request} content {/if}
+The date on which the entry was last edited. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
-This special conditional lets you conditionally display content if the current tag is _not_ being displayed based on a category specified in the URL. For instance, if the URL being viewed were
that would not trigger this conditional.
+#### `{entry_date}`
-### `{if not_forum_topic}`
+ {entry_date format="%Y %m %d"}
- {if not_forum_topic} content {/if}
+The date the entry was submitted. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
-You may use this conditional for displaying content when _no_ forum topic has been associated with a channel entry. That option is only available if the Discussion Forum Module is installed. It will typically be used like so:
+#### `{expiration_date}`
- {if not_forum_topic} There is no forum discussion available. {/if}
+ {expiration_date format="%Y %m %d"}
-### `{if signature_image}`
+The expiration date of the entry. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
- {if signature_image} content {/if}
+#### `{gmt_entry_date}`
-This special conditional lets you conditionally display content if the current entry's author has a signature image specified.
+ {gmt_entry_date format="%Y %m %d"}
- {if signature_image}
-

- {/if}
+The date the entry was submitted in GMT. This variable is **not** localized for each user's date settings. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
-### `{if sticky}`
+#### `{gmt_edit_date}`
- {if sticky == 'y'} content {/if}
+ {gmt_edit_date format="%Y %m %d"}
-You may test whether an entry is set to be "sticky". You may also test whether it is not "sticky".
+The date on which the entry was last edited in GMT. This variable is **not** localized for each user's date settings. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
- {if sticky == 'n'} content {/if}
+#### `{relative_date}`
-## Variable Pairs
+The amount of time that has passed between when the entry was submitted and the current time. The output is displayed in the format 1 day, 3 hours, 45 minutes. This variable is useful for displaying something such as "This entry was posted 1 day, 3 hours, 45 minutes ago."
-[TOC=3]
+#### `{week_date}`
-Variable pairs contain an opening and closing tag as well as content in-between. Example:
+ {week_date format="%Y %m %d"}
- {date_heading}
{entry_date format="%Y %m %d"}
{/date_heading}
+The date that the week of the currently displayed entry started on, most commonly used in "weekly" scenarios with the [date_heading](#date_heading) variable pair.
-The reason variable pairs have an opening and closing pair is because the information between the pairs can be shown or not shown if the criteria for each tag is met.
+This variable is affected by the [start_day=](#start_day) parameter. By default, the week date will fall on Sunday for the week of the entry. When `start_day="Monday"` is used, the week date will fall on Monday for the week of the entry. See [Date Variable Formatting](templates/date-variable-formatting.md) for more information.
-In the case of the "date_heading" pair, for example, it only appears at a certain interval that you set (hourly, daily, weekly, monthly, etc.). By using a pair of variables you can put HTML formatting between them that only gets shown when the interval is met. Otherwise, the chunk is not displayed.
+#### `{date_footer}`
-### `{date_footer}`
+This variable is intended to use as tag pair.
{date_footer display="daily"}
That's all from today!
{/date_footer}
@@ -1301,7 +1190,9 @@ If no parameter is specified it will default to "daily".
NOTE: **Note:** You can use as many date_footers as you want in the same tag. There is a bit of a performance hit, however, since date parsing is the most processor intensive. Read the caching section for information on improving performance.
-### `{date_heading}`
+#### `{date_heading}`
+
+This variable is intended to use as tag pair.
{date_heading}
{entry_date format="%Y %m %d"}
{/date_heading}
@@ -1327,7 +1218,7 @@ If no parameter is specified it will default to "daily".
NOTE: **Note:** You can use as many date_footers as you want in the same tag. There is a bit of a performance hit, however, since date parsing is the most processor intensive. Read the caching section for information on improving performance.
-### {categories}
+### Category Variables
[TOC=4]
@@ -1452,6 +1343,153 @@ All custom fields assigned to a category can be accessed using the "short name"
These are totally dynamic in that any field you create for your category will automatically be available by its "short name" as a variable.
+
+
+## Conditional Tags
+
+[TOC=3 hide]
+
+Conditionals allow you to more precisely control your content.
+
+NOTE: **Note:** A more complete explanation of conditional control structures and operators can be found on the [Conditional Tags](templates/conditionals.md) page.
+
+Here is an example that tests for the "summary" field being not empty
+
+ {if summary != ""}
+ The summary is not empty!
+ {/if}
+
+An alternate, shorthand syntax can accomplish the same thing
+
+ {if summary}
+ The summary is not empty!
+ {/if}
+
+If only the variable name is in the conditional statement it tests for "not empty".
+
+Many of the single variables can be used in a conditional. You may always use the short name of one of your custom entry fields in a conditional. In addition, there are several unique conditionals.
+
+### `{if allow_comments}`
+
+ {if allow_comments} content {/if}
+
+This special conditional lets you conditionally display content if the current entry is set to allow comments. This conditional will return FALSE if commenting has expired.
+
+ {if allow_comments}
+ ({comment_total})
Comments
+ {/if}
+
+Or you can display content if commenting is disabled:
+
+ {if allow_comments == FALSE} content {/if}
+
+### `{if avatar}`
+
+ {if avatar} content {/if}
+
+This special conditional lets you conditionally display content if the current entry's author has an avatar image specified.
+
+ {if avatar}
+

+ {/if}
+
+### `{if category_request}`
+
+ {if category_request} content {/if}
+
+This special conditional lets you conditionally display content if the current tag is being displayed based on a category specified in the URL. For instance, if the URL being viewed were
that could trigger this conditional.
+
+### `{if count}`
+
+ {if count > 5} content {/if}
+
+This conditional allows you to test against which number entry is being displayed. You could use this to apply different styles to the first entry or have the last 5 entries out of 10 be formatted differently.
+
+### `{if forum_topic}`
+
+ {if forum_topic} content {/if}
+
+You may use this conditional for displaying content when a forum topic has been associated with a channel entry. That option is only available if the Discussion Forum Module is installed. It will typically be used like so:
+
+ {if forum_topic}
+
Discuss this in our forums
+ {/if}
+
+### `{if has_categories}`
+
+Handy conditional for displaying markup or content based on whether or not the entry has been assigned any categories.
+
+ {if has_categories}
+
Categories
+
+
+ {categories}
+ ...
+ {/categories}
+
+ {/if}
+
+### `{if no_results}`
+
+ {if no_results} content {/if}
+
+You may use this conditional for displaying a message in the case when no entries are returned. The contents inside of the conditional will be displayed in cases where there are no results returned for the tag.
+
+ {if no_results}
There are no entries available.
{/if}
+
+Further, you may specify that another Template be shown in a case when there are no results. In order to do that, you must use the redirect=variable
+
+ {if no_results} {redirect="channel/noresult"} {/if}
+
+Lastly, if you want to simply display your 404 page (with 404 headers) when no entries are returned, simply use "404" as the template name.
+
+ {if no_results} {redirect="404"} {/if}
+
+NOTE: **Note:** If you have several nested tags, each one would need to include a `{if no_results}` pair to be parsed correctly.
+
+For instance, if you have Grid field with `{if no_results}` block, the parent `{exp:channel:entries}` tag pair would need to include `{if no_results}` block as well.
+```
+{exp:channel:entries channel="blog"}
+ {if no_results} No entries {/if}
+ {my_grid_field}
+ {if no_results} Grid is empty {/if}
+ {my_grid_field:text}
+ {/my_grid_field}
+{/exp:channel:entries}
+```
+
+### `{if not_category_request}`
+
+ {if not_category_request} content {/if}
+
+This special conditional lets you conditionally display content if the current tag is _not_ being displayed based on a category specified in the URL. For instance, if the URL being viewed were
that would not trigger this conditional.
+
+### `{if not_forum_topic}`
+
+ {if not_forum_topic} content {/if}
+
+You may use this conditional for displaying content when _no_ forum topic has been associated with a channel entry. That option is only available if the Discussion Forum Module is installed. It will typically be used like so:
+
+ {if not_forum_topic} There is no forum discussion available. {/if}
+
+### `{if signature_image}`
+
+ {if signature_image} content {/if}
+
+This special conditional lets you conditionally display content if the current entry's author has a signature image specified.
+
+ {if signature_image}
+

+ {/if}
+
+### `{if sticky}`
+
+ {if sticky == 'y'} content {/if}
+
+You may test whether an entry is set to be "sticky". You may also test whether it is not "sticky".
+
+ {if sticky == 'n'} content {/if}
+
## Pagination
The [Pagination](templates/pagination.md) feature allows you to create "next" and "previous" links between pages of entries.
diff --git a/docs/control-panel/channels.md b/docs/control-panel/channels.md
index c5e079300..5b7e813fa 100755
--- a/docs/control-panel/channels.md
+++ b/docs/control-panel/channels.md
@@ -51,6 +51,8 @@ The Fields tab contains the channel's field and field group assignments.
A channel can have any combination of fields and field groups assigned to it. You can also create fields and field groups on this tab, for a smooth workflow.
+
+
---
### Categories tab
diff --git a/docs/control-panel/create.md b/docs/control-panel/create.md
index c1e7a7a4e..bafa074e8 100755
--- a/docs/control-panel/create.md
+++ b/docs/control-panel/create.md
@@ -15,7 +15,7 @@
This is the area where you'll create content for your site by publishing new Entries to your Channels. If you have more than one Channel, moving your cursor over the Publish menu will show all of your Channels and allow you to select one.
-TIP: **Tip:** Site builders can customize the display of the Publish Page on a per Channel bases by creating a custom layout. Just go to the [Channel manager](control-panel/channels.md) and click 'layouts' to access the [Form layout](control-panel/channels.md#form-layouts).
+TIP: **Tip:** Site builders can customize the display of the Publish Page on a per Channel bases by creating a custom layout. Just go to the [Channel manager](control-panel/channels.md) and click 'layouts' to access the [Publish Layouts](control-panel/channels.md#publish-layouts).

@@ -39,15 +39,18 @@ NOTE: **Note:** If you let the system create your URL Title for you it will conv
### Entry Fields
-The names and types of entry fields displayed will be determined by what [Fields](control-panel/field-manager/field-manager-settings.md) you have defined for this channel. If an entry field is set to be "hidden" by default, it will have to be expanded by clicking on the field name before content can be entered.
+The names and types of entry custom fields displayed will be determined by what [Fields](/fieldtypes/overview.md) you have defined for this channel.
-### Save Revision
+If an entry field is set to be "hidden" by default, it will have to be expanded by clicking on the field name before content can be entered.
-Allows the content editor to force a revision save.
+The fields can be [conditionally hidden](control-panel/field-manager/conditional-fields.md).
-### Submit
+In order for the field to become available when publishing or editing entry, it needs to be assigned to the channel that holds the entry.
+
+This can be done in two ways:
+- assign custom field to a [Field Group](/control-panel/field-manager/field-manager-settings.md#createedit-field-group) which is associated to the Channel
+- assign field directly to channel by editing [Channel preferences](control-panel/channels.md#fields-tab)
-The Submit button allows you to save the entry and publish it to your site.
## Date Tab
diff --git a/docs/fieldtypes/overview.md b/docs/fieldtypes/overview.md
index 406d63a21..a0467835e 100755
--- a/docs/fieldtypes/overview.md
+++ b/docs/fieldtypes/overview.md
@@ -37,3 +37,5 @@ ExpressionEngine has the following built-in fieldtypes:
- [Value Slider](/fieldtypes/value-slider.md)
- [Toggle](/fieldtypes/toggle.md)
- [URL](/fieldtypes/url.md)
+
+Additionally, more fieldtypes are available in [ExpressionEngine Add-on Store](https://expressionengine.com/add-ons) as add-ons that can be [installed](add-ons/overview.md#installing-add-ons)
\ No newline at end of file