A page view is one that is accessible via URL meaning it can be linked to directly, and the view appears in the main content area.
In order to provide a page view, the 'Page View' setting must be checked; if unchecked, settings in this section will be ignored.
Some items in this list will be marked as advanced features, and require some understanding of Drupal to really 'get'. Don't worry if these descriptions don't make sense to you; feel free to ignore them.
- This is the Drupal URL from which the view is accessible, and is set just like URLs from in the menu; do not include the leading or trailing slash, and do not include http:// or your site's base URL in it. For example, if your site is http://www.example.com and you want your view to have the URL http://www.example.com/archive, then you simply enter 'archive' in the URL field.
The URL supports an option to rearrange the URL slightly and provide part of the URL as an argument. This is especially useful when views are created as tabs on the user profile. For example, the URL to a user's profile is user/UID -- if your drupal.org UID is 26979, then your profile will be located http://drupal.org/user/26979. If you have a view to display recent posts by a user, and that provides a menu tab, and you want that tab to appear on a user's profile page, the URL would have to look like this: http://drupal.org/user/26979/track -- in order to get this to work, you need to specify that number as an argument. You could specify that argument as user/$arg/track. By using $arg as a placeholder, Views will know that that section of the URL is an argument and will pass that through as the first argument to the View. See the section on Arguments for more detail.
- View Type
- Choose any of the types listed. (See the definitions page for more detail.) The type chosen is applicable only to Page Views; Block Views can have their own type.
- This is the title of the View, as displayed on the page. The title can use % substitution to include arguments in the view, if your view uses Arguments. (See the argument section for more). You may use %1 for the first argument, and %2 for the second argument, etc. For example, if you have a view which has 4 arguments: UID, Year, Month, Day and is meant to display blog entries, you might use the following title: Blog entries for %1 on %3 %4, %2 which would translate to Blog entries for USERNAME on MONTH DAY, YEAR.
- Use Pager
- If your view might return a lot of entries, you can (and almost certainly should) check this; it will use Drupal's built in paging system to return only the specified number of entries per page.
- Breadcrumb trail should not include Home Advanced Feature
- The breadcrumb trail is the line that informs the user where in the system a given page is; it is generally constructed from the menu tree or from taxonomy. This option will only very rarely be checked; in fact, in general only for the 'front page' view will the trail not include Home, and generally because that page is Home and doesn't need to link to itself.
- Nodes Per Page
- This option tells Views how many results to return on the page. If the pager option is not checked, then this is the maximum number of posts to display. You may enter 0 here for no limit.
- Provide Menu
- If checked, Views will create a menu entry for this tree, so that it may appear in the Navigation menu. The menu.module can be used to customize and/or rearrange this menu item. If not checked, all items in the menu field set will be ignored.
- Provide Menu as Tab Advanced Feature
- If checked, the menu will be provided as a 'tab' rather than a normal menu item. This means that instead of showing up in the navigation, it will show up as a menu tab, similar to the 'view' and 'edit' options on a post. There are two important considerations here: First, the URL to the view needs to have at least two portions, meaning it must be in the form of foo/bar (or foo/bar/baz) and can't simply be foo. This is because that the tab for foo/bar will show up on the URL foo. The second consideration is that tabs will only appear if there are at least 2 of them to choose from.
- Make Default Menu Tab Advanced Feature
- When creating a view (or more likely, multiple views) as a tab, you may need to set one of them as the default tab. For example, if you have two views, foo/bar and foo/baz, and you set foo/bar as the default menu tab, when you navigate to foo you will see the page for foo/bar, and foo will contain a tab that lets you also go to foo/baz.
- Tab Weight Advanced Feature
- If a view is set to be a menu tab, this option specifies the 'weight' of the tab. Lower numbers will appear more to the left. The default is 0, and if two tabs have the same weight they will be sorted alphabetically.
- Menu Title
- This is the name of the menu entry (or tab) that the View will have. It doesn't need to match the main title, (and should not if using % substitution in the title). You may not use % substitution in this title.
- The header will appear at the top of the view. It may be a short message describing the view; it may also be, if you have the proper permissions, PHP code that can run a snippet.
- The footer will appear at the bottom of the view. It may be a short message describing the view; it may also be, if you have the proper permissions, PHP code that can run a snippet.
- Empty Text
- The empty text will appear if the view returns no results. It may be a short message describing the view; it may also be, if you have the proper permissions, PHP code that can run a snippet. NOTE: If the view returns no results, the header and footer will not appear! If you want the header/footer to appear when a view returns no results, you need to duplicate it in the Empty Text!