diff --git a/README.txt b/README.txt index 95c3805ea91571fba36bfcca6cad39b9bd67fd03..af47ce0bd14c7862d36101523381041bad4a93e6 100644 --- a/README.txt +++ b/README.txt @@ -1,4 +1,3 @@ -// $Id$ Welcome to Views 2. Please see the advanced help for more information. diff --git a/css/views-admin.css b/css/views-admin.css index 986c6bdbf489b68149b09303008d810f1c6e50cc..2a80ba996cef76b71574edc1df5556bbbd3be351 100644 --- a/css/views-admin.css +++ b/css/views-admin.css @@ -1,4 +1,3 @@ -/* $Id$ */ /* * Summary pad diff --git a/css/views-list-rtl.css b/css/views-list-rtl.css index c9452db14172f7543a6d5fde53380cba8a1808e0..1b62fc3fb33e47c3cfffd4908de4f7b886158de3 100644 --- a/css/views-list-rtl.css +++ b/css/views-list-rtl.css @@ -1,4 +1,3 @@ -/* $Id$ */ table.views-entry { clear: right; /* RTL */ diff --git a/css/views-list.css b/css/views-list.css index 27e849a396fbbaf36b096893ed29eb00857dfcde..73f0aa07cc887ac8af6c1fb714f9b801c6b6b6d3 100644 --- a/css/views-list.css +++ b/css/views-list.css @@ -1,4 +1,3 @@ -/* $Id$ */ table.views-entry { margin: 3px 0; diff --git a/css/views.css b/css/views.css index 812bc1566051e9a4ae0eaa6a3ad7098471b4ba7f..0a77a6cf4f82662309e506697555c3ea669a0f05 100644 --- a/css/views.css +++ b/css/views.css @@ -1,4 +1,3 @@ -/* $Id$ */ .views-exposed-form .views-exposed-widget { float: left; /* LTR */ padding: .5em 1em 0 0; /* LTR */ diff --git a/docs/docs.php b/docs/docs.php index 8114df7e908ddaa9197eb46bd8dd9aa9acb16eda..21912acd3ec2ef6c87c938ce534ba9bd4774dd3c 100644 --- a/docs/docs.php +++ b/docs/docs.php @@ -1,5 +1,4 @@ The views module allows administrators and site designers to create, manage, and display lists of content. Each list managed by the views module is known as a "view", and the output of a view is known as a "display". Displays are provided in either block or page form, and a single view may have multiple displays. Optional navigation aids, including a system path and menu item, can be set for each page-based display of a view. By default, views may be created that list content (a Node view type), content revisions (a Node revisions view type) or users (a User view type). A view may be restricted to members of specific user roles, and may be added, edited or deleted at the views administration page The "building block" design of the views system provides power and flexibility, allowing parameters to be specified only when needed. While an advanced view may use all of available parameters to create complex and highly interactive applications, a simple content listing may specify only a few options. All views rely on a conceptual framework that includes: diff --git a/help/analyze-theme.html b/help/analyze-theme.html index 0c5c3f19c70d0f8a5f6ff00fcaf7227a87da9e71..46bfbe8ce583103cb4a8be0650478e96f122206e 100644 --- a/help/analyze-theme.html +++ b/help/analyze-theme.html @@ -1,4 +1,3 @@ -
You may use any of the following possible theme files to modify individual parts of your view. In total, there are four parts to theming a view.
<?php -// $Id$ /** * This file is used to tell the views module about the new node_example table. diff --git a/help/api-handlers.html b/help/api-handlers.html index 00ce219d51def8ae2f235d89b0004bd9080b9e70..c463d899a52d81ac314d114f77a30ecd675cdc6b 100644 --- a/help/api-handlers.html +++ b/help/api-handlers.html @@ -1,4 +1,3 @@ - In Views, a handler is an object that is part of the view and is part of the query building flow. Handlers are objects; much of the time, the base handlers will work, but often you'll need to override the handler for something. One typical handler override will be views_handler_filter_operator_in which allows you to have a filter select from a list of options; you'll need to override this to provide your list. diff --git a/help/api-plugins.html b/help/api-plugins.html index ec20485c409b02db5478fd522d148a18642528d4..25fbffbe727bb6faec0fbd5c463f9f3d1bc88ca7 100644 --- a/help/api-plugins.html +++ b/help/api-plugins.html @@ -1,4 +1,3 @@ - In Views, a plugin is a bit like a handler, but plugins are not directly responsible for building the query. Instead, they are objects that are used to display the view or make other modifications. There are 6 types of plugins in Views: diff --git a/help/api-tables.html b/help/api-tables.html index 0cbbf41a682c1f7731ee2a8fe946a535b76fb8f5..483337e69f5bffb5e902db867ffeb7d0b62ef5a1 100644 --- a/help/api-tables.html +++ b/help/api-tables.html @@ -1,4 +1,3 @@ - Tables are described to Views via hook_views_data(), which returns an array of table information, keyed by the name of the table. For example, if your module is describing three tables, 'foo', 'bar' and 'baz', your array will look like this:$data = array( 'foo' => array( diff --git a/help/api-upgrading.html b/help/api-upgrading.html index 8ebf78267e228d8909be2ca141e7fb03f2b5c520..1447b209cb2254852d598b1a6e88f5a2005626f7 100644 --- a/help/api-upgrading.html +++ b/help/api-upgrading.html @@ -1,4 +1,3 @@ - In order to take advantage of the changes in Drupal 7, Views has gone through several API changes. Here's what you should know. diff --git a/help/api.html b/help/api.html index 08fc0d834f16c83624b2cd03a79dd5b611a275f3..6337e8be3493a41360177aa45dde31ced259c06d 100644 --- a/help/api.html +++ b/help/api.html @@ -1,4 +1,3 @@ - Views allows modules to describe their tables relationships to each other, as well as fields, filters, sort criteria and arguments via hook_views_data(). Whenever Views deems it necessary, this hook is called, the data aggregated together and cached. hook_views_data_alter() may also be used to modify existing data, changing other module's handlers or adding handlers to other module's tables. Views also allows modules to create new display types, style types, row styles, argument default handlers and argument validators via hook_views_handlers() and hook_views_plugins(). diff --git a/help/argument.html b/help/argument.html index 4280a0f0db1a46c888203a0a06b0f3255b0e8d60..c4bdf2b50ba550ea44f4cb3aff08e4196395deea 100644 --- a/help/argument.html +++ b/help/argument.html @@ -1,4 +1,3 @@ - Arguments are input. While they often come from the URL, they don't always so please don't be shocked when they don't. Each display type may have its own source for arguments. Block displays have no source of arguments at all; they cannot pull arguments from the URL, and often require use of the default argument PHP code in order to get arguments. The argument default plugins can be used to get arguments into a block view. See "Provide default", below. In general, arguments are used to filter the view, and in that sense they have a very close relationship to filters, but that isn't necessarily true for every argument. Arguments can be used for any purpose, really; the extent of what the argument does is up to the developer of the argument, but the arguments that come with Views are almost entirely filters. diff --git a/help/display-attachment.html b/help/display-attachment.html index 71b5ebf6448bba817667db6797abec733b7f5859..9963b25e129aba1fb48a45d7fa5627a7f9112e5e 100644 --- a/help/display-attachment.html +++ b/help/display-attachment.html @@ -1,2 +1 @@ - Attachment displays are 'attached' to another display in the same view. When the display is visited, the attached display will also be rendered and may be placed before, after or both before and after the original display. Attachment displays are often useful for displaying an argument summary view along with a page display that accepts arguments. This can be used to provide a kind of glossary. \ No newline at end of file diff --git a/help/display-block.html b/help/display-block.html index 63be273cd8f6a3c205b7f391cb88d88915222929..158cad07377b73b6e860caf2562e6784e33ccb9f 100644 --- a/help/display-block.html +++ b/help/display-block.html @@ -1,4 +1,3 @@ - Block displays will show up on your blocks administration page. Once a block display is created and saved, it can be enabled and positioned in your theme by visiting administer >> site building >> blocks and selecting it from the list. Blocks do not accept arguments from any source; the only way to get arguments to a block is to provide defaults to it, possibly via the PHP Code default setting. diff --git a/help/display-default.html b/help/display-default.html index 2903f68b70eb405511e47a5890baf11067c926ff..309690aaeb4a46dc31548836705b578fcdf677aa 100644 --- a/help/display-default.html +++ b/help/display-default.html @@ -1,4 +1,3 @@ - The default display is primarily a display to store settings, and isn't actually used anywhere within the Views system. It is possible for external programs to use the default display, but if they do they will (hopefully) tell you which display they will be working with. The default display is also a convenient display to use to embed into your site using PHP snippets; this is useful, for example, in node content, but this is something that should generally only be done by administrators. In general, you probably want to add either a page display or a block display. diff --git a/help/display-feed.html b/help/display-feed.html index 49e129f765e476fffcf668ee0b06436dff731d55..a5c0a65510810a016614c3771b1f24785606469e 100644 --- a/help/display-feed.html +++ b/help/display-feed.html @@ -1,2 +1 @@ - A feed display allows you to attach an RSS feed to a view. \ No newline at end of file diff --git a/help/display-page.html b/help/display-page.html index 5975646b4026494606b1145d310496ce3dc67ea7..a23c3a03b1a74e23e60efc09bd639dbf6b8a809a 100644 --- a/help/display-page.html +++ b/help/display-page.html @@ -1,4 +1,3 @@ - Page displays have a path and an optional menu component. Page displays will be the primary content for the page, meaning they will be displayed in the main content area when you visit the URL that corresponds to the path. Page displays take their arguments from the URL. You can embed arguments into the URL using %; in previous versions of Views, this was '$arg'. For example, 'node/%/foo' will accept URLs such as 'node/1/foo'. diff --git a/help/display.html b/help/display.html index ce1bc6c7178f2b272de43c1a89e16c50354f90be..5eca6fd9a50947835e8d29b5239d8c7f9dad2440 100644 --- a/help/display.html +++ b/help/display.html @@ -1,4 +1,3 @@ - Displays tell Views where the output should go. By adding a display to a View, you can have your view appear as a page, or as a block, or even as an attachment to a different display on the view. Each display can have its own settings, but when created, a display will take all of its basic settings from the default display which all Views must have. For most settings, there is an override button that will override that single setting for the current display. Overridden settings will have a mark in the summary for that display. All 'default display settings' are shown in the other displays in 'italic'. When you override a setting, then it is shown 'normal'. diff --git a/help/embed.html b/help/embed.html index b9e698ff38cd317c1186a010fc87bc1f92657010..e39fbf5cd232b98e32d258c5ef14d09877a6a8bd 100644 --- a/help/embed.html +++ b/help/embed.html @@ -1,4 +1,3 @@ - You can easily embed the results of a view into other parts of your site; either with code as a module, or in nodes or blocks as snippets. The easiest way is to use the function views_embed_view(): diff --git a/help/example-author-block.html b/help/example-author-block.html index 84f2b7a5caf82d4c2394a6076d36011df12676ed..1e802bcdf7ccbb89e109d2ccece90fa92e32ba3c 100644 --- a/help/example-author-block.html +++ b/help/example-author-block.html @@ -1,4 +1,3 @@ -In this example you will create a context-sensitive block that shows the titles of recent blog entries by an author when viewing one of their posts. This will demonstrate using Views arguments to dynamically filter a view's contents at display time.
Before working through this example, enable the Blog module and populate some entries from a few different users.
diff --git a/help/example-recent-stories.html b/help/example-recent-stories.html index 17313c24dad5a0849e867d268a5ebde6af63e50e..9e372d8391b20c0ee8a9620564e0aa6b3b22a4a3 100644 --- a/help/example-recent-stories.html +++ b/help/example-recent-stories.html @@ -1,4 +1,3 @@ - In this example you will create a list of nodes of the content type "story", to be shown in a block. Through this step-by-step process, you will become familiar with some basic steps in creating a view, and familiarize yourself with the Views User Interface.diff --git a/help/example-user-feed.html b/help/example-user-feed.html index d8d1d4f66023057dffb3032447989f57459036a9..3a9784f61c0276e83b339ea8b18f273fefb5faeb 100644 --- a/help/example-user-feed.html +++ b/help/example-user-feed.html @@ -1,4 +1,3 @@ -
In this example you will create a Feed display to show nodes by individual users, dynamically selected through the URL. You will become familiar with the Views 2 interface, as well as learn how to use an argument to pull in a user name and use it in a dynamically created path.
A feed is a data format that places your site's content into a file that can be read and displayed by news reader programs. When visiting a site, you may notice a small RSS transmission icon, whereby clicking on it, you can subscribe to the site's most recent content. This makes it easier for your visitors to keep up to date with your website. You can also use this format to aggregate information into other sites. For more information, please watch a video from Common Craft about RSS in plain English.
Note, Drupal automatically creates a feed for your website, but you may want to create feeds with specific information. In this case, a list per user.
diff --git a/help/example-users-by-role.html b/help/example-users-by-role.html index 6f50631344a7f8c2c915720df174088df781e774..f5228be3ba843a7088b5b454bce1d121cfcf281b 100644 --- a/help/example-users-by-role.html +++ b/help/example-users-by-role.html @@ -1,4 +1,3 @@ - In this example you will create a page view listing users on your site. Through this step-by-step process, you will become familiar with some basic steps in creating a view, and familiarize yourself with the Views User Interface.diff --git a/help/field.html b/help/field.html index b68ca317f8aca6d9f878ae261a02906457968cbc..e563176261b05aa59985d31da2fdde8a75a44ee9 100644 --- a/help/field.html +++ b/help/field.html @@ -1,4 +1,3 @@ - Fields are the individual pieces of data being displayed. Adding the fields Node: Title, Node: Type, and Node: Post date to a node view, for example, includes the title, content type and creation date in the displayed results). Fields may not appear on every display, because not all style plugins actually use fields. For example, the 'node' row plugin simply displays the node through Drupal's normal mechanisms, and fields are not involved. diff --git a/help/filter.html b/help/filter.html index 495076b247f1f3f32ff1c0a1f699a2f3f03071e3..b4cb5a05ade2584dab6ec876642995519f019311 100644 --- a/help/filter.html +++ b/help/filter.html @@ -1,4 +1,3 @@ - Filters are used to reduce the data set that Views provides. That is to say, without any filters applied, Views will return all of your content. You don't want that, so at least some filters must be used. Some very commonly used filters: diff --git a/help/getting-started.html b/help/getting-started.html index b31b9e2ed6e82d874535118552c77649e06a021f..c1848349cf7e7852ee898c1498d257d9b7e2df95 100644 --- a/help/getting-started.html +++ b/help/getting-started.html @@ -1,4 +1,3 @@ - For those new to Views, it can be a complex system that appears totally overwhelming. The good news is that the UI is designed to compartmentalize everything; this means that for the most part, you can ignore the parts you're not interested in. Start small and build your way up. Because of this, the edit UI can seem overwhelming at first, but there are really just a few things you have to know. The rest you can find through exploration. The Views Edit UI image, below, gives an overview of what you'll find on the edit UI. diff --git a/help/menu.html b/help/menu.html index 541ba29fd615a5b81f12097a008a58bdb14f218d..bb818a39b08d1f62c9f458e3a0a63a4e4d5ad027 100644 --- a/help/menu.html +++ b/help/menu.html @@ -1,4 +1,3 @@ - Page displays can hook into the Drupal menu system and provide menu links that will appear in the Navigation system as well as tabs that can be used to keep Views next to each other. For simple menu links, there is very little you need to do; simply select 'Normal menu entry' and fill in the text for the title. This will appear in the Navigation menu by default; you will need to visit the menu administration page to move this to another menu. diff --git a/help/new.html b/help/new.html index 69aafc0bf4a4b8813ce38307714ec156640b295f..f33bb8ff5537c0d0f35f530302be3e0fc5e9b11a 100644 --- a/help/new.html +++ b/help/new.html @@ -1,4 +1,3 @@ - Views 2 is the newest major release of Views and it is specifically coded for Drupal 6. Views 2 retains all of the core functionality of Views 1, together with a completely revamped user interface and a large set of new features which greatly expand upon the original feature-set of Views 1. This document is a side-by-side comparison of Views 1 versus Views 2 from a user's perspective, detailing the UI changes, some new ways to perform old tasks, the cool new features of Views 2 and how these features can be used to address some of the shortcomings of Views 1.
Admin interface
diff --git a/help/overrides.html b/help/overrides.html index 63f9c2236fc49287269eb25bb55ac9546d0a6c09..c6ff5310e640e6adaa1b969ba53ef94ecc077690 100644 --- a/help/overrides.html +++ b/help/overrides.html @@ -1,4 +1,3 @@ - If an item is using defaults then it is using values from the default display. IMPORTANT NOTE: If you modify this value, you are modifying the default display and thus modifying for all displays that are using default values. diff --git a/help/path.html b/help/path.html index c6bf05012390ab06bc8d96c48f916d482693dc0d..142534cba4da486d46e6732524d0ade6ab399eb4 100644 --- a/help/path.html +++ b/help/path.html @@ -1,4 +1,3 @@ - If a display has a path that means that it can be retrieved directly by calling a URL as a first class page on your Drupal site. Any items after the path will be passed into the view as arguments. For example, if the path is foo/bar and a user visits http://www.example.com/foo/bar/baz/beta, 'baz' and 'beta' will be given as arguments to the view. These can be handled by adding items to the arguments section. You may also use placeholders in your path to represent arguments that come in the middle. For example, the path node/%/someview would expect the first argument to be the second part of the path. For example, node/21/someview would have an argument of '21'. diff --git a/help/relationship.html b/help/relationship.html index f8449ed63563b8b2cbf74a1269e2304d0d5938a2..0f89184c8e621e5f375a7d43605d2e4248a4ff57 100644 --- a/help/relationship.html +++ b/help/relationship.html @@ -1,4 +1,3 @@ - Relationships allow you to expand the query to include objects other than the base query. This is actually made more difficult to understand by the fact that Views actually includes a few relationships by default, and doesn't tell you they're there. For historical reasons, it would be inconvenient to remove these default relationships. When relationships are present, all fields (including relationships) will gain a new form item to let you select which relationship they will use. They will default to using no relationship at all. The main example of the relationship that is there by default is the node --> user relationship; every node has an author, and if a node is in the query, the user who wrote that node is automatically made available. [Note: the author considers it an error that this relationship is automatic, but by the time it was realized this was in error, it was too late to change it.] diff --git a/help/sort.html b/help/sort.html index 673b4ad79867c53c96616abb2678fd8707d8fd43..9a5640fc1fe99070eb6b0f16c59d5653319a4b31 100644 --- a/help/sort.html +++ b/help/sort.html @@ -1,4 +1,3 @@ - Sort criteria determine what order the records are retrieved from the database and displayed in; generally, all you need to do is pick a field and choose ascending (1, 2, 3, 4) or descending (4, 3, 2, 1) and it will be done. If you have multiple sort criteria, the second (and later) items only come into play if the first item is the same. Different data types sort just a little bit differently from others: diff --git a/help/style-comment-rss.html b/help/style-comment-rss.html index 2b20df1d49ad30a8ce90d8927554ffa47e08fa50..c047ee726b6ad838b8704b14f09f602f504faf33 100644 --- a/help/style-comment-rss.html +++ b/help/style-comment-rss.html @@ -1,2 +1 @@ - This row style is only available to RSS styles. It produces XML necessary for an RSS feed for the comment. \ No newline at end of file diff --git a/help/style-fields.html b/help/style-fields.html index d9e397cb5b05111b41d73773bb5067d4b2fcaafd..0afde7a982eea44bad810a2942e9b52b8cd766e2 100644 --- a/help/style-fields.html +++ b/help/style-fields.html @@ -1,4 +1,3 @@ - The fields row style displays each field defined in the view, one after another. Each field defines its own output. By default, each field is put in a <div> unless it is selected to be inline. If it is inline, it is put in a <span>. Two items in <div>s will be displayed one after another, with the second one below the first. Two items in <span>s will be displayed on the same line. One item in a <span> next to <div>s is the same as two items in <div>s. This means that for the inline setting to do anything, at least two consecutive items must be set inline. diff --git a/help/style-grid.html b/help/style-grid.html index fbc305bc3fe0ecf0e76e63aeaa2a75a9edbe8bef..e3d00af082aa012fae4e765a8e3f76e45fe10e25 100644 --- a/help/style-grid.html +++ b/help/style-grid.html @@ -1,4 +1,3 @@ - The grid style will display each row of your view within a grid. You may customize the number of columns, though it defaults to 4. A grid looks like this:diff --git a/help/style-list.html b/help/style-list.html index 2b7514315a9910bab6a80447e62fe316e0c73a46..71fcfa43c98d73da3edae143c5d259f0e55f11f9 100644 --- a/help/style-list.html +++ b/help/style-list.html @@ -1,4 +1,3 @@ - The List view style will display every row of the view as part of an HTML list construct. For example:
- Row 1
diff --git a/help/style-node-rss.html b/help/style-node-rss.html index c869a311e537fdb31d2000e4bab6cb223cca8858..9cce41439e44b804f269538a27d51484a7694ca9 100644 --- a/help/style-node-rss.html +++ b/help/style-node-rss.html @@ -1,2 +1 @@ - This row style is only available to RSS styles. It produces XML necessary for an RSS feed for the node record. \ No newline at end of file diff --git a/help/style-node.html b/help/style-node.html index 19c8dab7eb6fb472037ce601a2ab05e29f2ccf10..c3a3e846402ef5c55ae8557701a3d75315f28ac6 100644 --- a/help/style-node.html +++ b/help/style-node.html @@ -1,4 +1,3 @@ - The node row style will display each item of the view through Drupal's standard node_view() function. Views has very little control over this output, except for the options you see. Instead, the output is run through the standard node template mechanism (typically node.tpl.php or a variant thereof) and any decisions about what is output may be done there. Views does add an extra 'suggestion' to the list of possible node templates: node--view--VIEWNAME.tpl.php -- you may use this to theme a node specifically for the view. This can be handy for creating very small teasers and the like. diff --git a/help/style-row.html b/help/style-row.html index be7ea0cecc3909b98661193fab5989a475ccce45..3eae5acdd19520f564f66274938bfa21c9c58d0c 100644 --- a/help/style-row.html +++ b/help/style-row.html @@ -1,4 +1,3 @@ - A row style is an individual style to display only an individual record within a view. For example, a node type view would display one node per row; a user type view would display one user per row. Some row styles use fields which means you select from the available fields to display; others do not; they are able to use the base type and create a display. Usually, row styles that do not use fields produce less efficient (slower) views, so bear this in mind when contemplating the performance of your site. \ No newline at end of file diff --git a/help/style-rss.html b/help/style-rss.html index 7f59e147869cca4e4d269a87bf373a33c52fd49a..0b18443672089dff460dc53e5a1fc1c0afa63fb2 100644 --- a/help/style-rss.html +++ b/help/style-rss.html @@ -1,4 +1,3 @@ - The RSS output style is only available for Feed display types. It will display the view as an RSS feed, which is a specialized XML output. This output is not user visible, but can be parsed by feed readers for aggregation. You may supply a description for the RSS feed; most feed readers will display this description along with the contents of the feed. You may also select to use the site's mission statement for the description. \ No newline at end of file diff --git a/help/style-summary-unformatted.html b/help/style-summary-unformatted.html index ecc29522534f14ac6db6620c8bc7283d905bcc12..258acf528cf9bb45f7f3b2d456a78f64b4e4a21d 100644 --- a/help/style-summary-unformatted.html +++ b/help/style-summary-unformatted.html @@ -1,4 +1,3 @@ - The unformatted summary style is only available for summary styles, which are when an argument has been set to provide a summary if it was not provided with a value. This summary provides the possible candidates for the argument one after another with no special formatting. If inline is selected, the summary items will be enclosed within <span> tags. Otherwise the items will be in <div> tags. You can also elect to display the number of matching records for the argument, plus change the number of items per page for the summary. This is often useful because summary views are often quite small, but other views quite space intensive. It is very common to have far more records available in the summary view than in the more normal view. \ No newline at end of file diff --git a/help/style-summary.html b/help/style-summary.html index 88b6923e25a6555fcf3e686a19aa44f0d5ce8ce1..f5b01ecf648a5a7da823e104215d153faa74a862 100644 --- a/help/style-summary.html +++ b/help/style-summary.html @@ -1,4 +1,3 @@ - The list summary style is only available for summary styles, which are when an argument has been set to provide a summary if it was not provided with a value. This summary provides a list of possible candidates for the argument in a standard HTML list. Like the normal list style, you may set this list to be ordered or not. You can also elect to display the number of matching records for the argument, plus change the number of items per page for the summary. This is often useful because summary views are often quite small, but other views quite space intensive. It is very common to have far more records available in the summary view than in the more normal view. \ No newline at end of file diff --git a/help/style-table.html b/help/style-table.html index 40c25a2c560e8ebda1223c4fadc4e341451e447a..b8ade8a352011f00f458a4ff599203872b2bc3ba 100644 --- a/help/style-table.html +++ b/help/style-table.html @@ -1,4 +1,3 @@ - The table style will display the View results as a table; each row of the table will correspond to a row from the view result. When setting the table options, each field in the view will be presented with some information next to each field: diff --git a/help/style-unformatted.html b/help/style-unformatted.html index ef03634282b40d8b64f74005406f02e1d9387b50..99fa3de7fa42a6aafe7accf6f9f2957350b73f0b 100644 --- a/help/style-unformatted.html +++ b/help/style-unformatted.html @@ -1,2 +1 @@ - The unformatted output style simply places each row of the view, one after another, with no additional formatting. diff --git a/help/style.html b/help/style.html index 91afab6a893eafcbf4b3aa5157dfb9c2825d3a81..01dffed3bdb95be70ed3c7db72c5b053bc10b54e 100644 --- a/help/style.html +++ b/help/style.html @@ -1,4 +1,3 @@ - The Views' style system is how you customize the output produced by your view. A view style is basically a smart theme template that processes the view data and then outputs it. All styles in Views can be overridden by placing copies of the templates in your theme directory and then modifying them. See the theme: information link available on all views to get hints for which templates a given view is using.diff --git a/help/theme-css.html b/help/theme-css.html index b7e0e69d58b3b0fb10c1f3ad89133c18dc32d5c0..8de1a0ab95da5a59cf7a8ff093b6100746462a61 100644 --- a/help/theme-css.html +++ b/help/theme-css.html @@ -1,4 +1,3 @@ - Views uses a wide array of CSS classes on all of its content to ensure that you can easily and accurately select exactly the content you need in order to manipulate it with CSS. Typically, every view is wrapped in a div with the name of the view as part of its class (for all these examples, we will assume the name of the view is myview), as well as the generic class 'view': diff --git a/help/updating.html b/help/updating.html index aade41e874e4fbf7f15aa6d3996b2f3a3cec7f18..844c46c773ffe7884f751ffb4dc583186b438c04 100644 --- a/help/updating.html +++ b/help/updating.html @@ -1,3 +1,2 @@ - TODO: This document needs to be fleshed out. diff --git a/help/upgrading.html b/help/upgrading.html index 03a88dee834cdb5c13b1f40a3a18c7625bfc2729..83314b104e89f0572b6a24605de2ca26c5b1cc4c 100644 --- a/help/upgrading.html +++ b/help/upgrading.html @@ -1,4 +1,3 @@ -;Updating templates
If you have theme files for node-view-$viewname of comment-view-$viewname you have diff --git a/help/using-theme.html b/help/using-theme.html index 8e53982da1d046313b1cf486bd4427fac3a5d2ad..80a032992940bf40bf50304d40b3569ff593833c 100644 --- a/help/using-theme.html +++ b/help/using-theme.html @@ -1,4 +1,3 @@ - Views theme templates are straightforward to use with the Drupal theming system. If you are unfamiliar with the theming system at all, you should probably at least read drupal.org theming documentation. That said, these are the important things you need to know:diff --git a/help/view-type.html b/help/view-type.html index e5ba2f10060a57508909f66e32f1f3b5c88e9089..bdb80fc0cdf99a0c953631cc20d4333bed451b07 100644 --- a/help/view-type.html +++ b/help/view-type.html @@ -1,4 +1,3 @@ -
The view type describes how this view is stored; Views is capable of having Views entirely in code that are not in the database. This allows modules to easily ship with Views built in, and it allows you to create a module to store your views for easy deployment between development and production servers.
diff --git a/help/views.help.ini b/help/views.help.ini index 24612968815dceae06068e57a16e2ce5d4dfffb2..a00f8a1ff0d8d4d05f138afe7d6284754b069787 100644 --- a/help/views.help.ini +++ b/help/views.help.ini @@ -1,4 +1,3 @@ -; $Id$ [advanced help settings] line break = TRUE diff --git a/includes/admin.inc b/includes/admin.inc index fa4150831d5dfbc145075dca277459753234ae1b..ae85dd43563c74a53805fe1bf76f97410991fba4 100644 --- a/includes/admin.inc +++ b/includes/admin.inc @@ -1,5 +1,4 @@