|
views_handler_filter_term_node_tid_depth::query |
core/modules/taxonomy/views/views_handler_filter_term_node_tid_depth.inc |
Add this filter to the query. |
|
views_handler_filter_user_current::construct |
core/modules/user/views/views_handler_filter_user_current.inc |
Views handlers use a special construct function so that we can more easily
construct them with variable arguments. |
|
views_handler_filter_user_current::query |
core/modules/user/views/views_handler_filter_user_current.inc |
Add this filter to the query. |
|
views_handler_filter_user_name::accept_exposed_input |
core/modules/user/views/views_handler_filter_user_name.inc |
Check to see if input from the exposed filters should change
the behavior of this filter. |
|
views_handler_filter_user_name::admin_summary |
core/modules/user/views/views_handler_filter_user_name.inc |
Display the filter on the administrative summary |
|
views_handler_filter_user_name::exposed_validate |
core/modules/user/views/views_handler_filter_user_name.inc |
Validate the exposed handler form |
|
views_handler_filter_user_name::get_value_options |
core/modules/user/views/views_handler_filter_user_name.inc |
Child classes should be used to override this function and set the
'value options', unless 'options callback' is defined as a valid function
or static public method to generate these values. |
|
views_handler_filter_user_name::validate_user_strings |
core/modules/user/views/views_handler_filter_user_name.inc |
Validate the user string. Since this can come from either the form
or the exposed filter, this is abstracted out a bit so it can
handle the multiple input sources. |
|
views_handler_filter_user_name::value_form |
core/modules/user/views/views_handler_filter_user_name.inc |
Options form subform for setting options. |
|
views_handler_filter_user_name::value_submit |
core/modules/user/views/views_handler_filter_user_name.inc |
Perform any necessary changes to the form values prior to storage.
There is no need for this function to actually store the data. |
|
views_handler_filter_user_name::value_validate |
core/modules/user/views/views_handler_filter_user_name.inc |
Validate the options form. |
|
views_handler_filter_user_permissions::get_value_options |
core/modules/user/views/views_handler_filter_user_permissions.inc |
Child classes should be used to override this function and set the
'value options', unless 'options callback' is defined as a valid function
or static public method to generate these values. |
|
views_handler_filter_user_permissions::query |
core/modules/user/views/views_handler_filter_user_permissions.inc |
Add this filter to the query. |
|
views_handler_filter_user_roles::get_value_options |
core/modules/user/views/views_handler_filter_user_roles.inc |
Child classes should be used to override this function and set the
'value options', unless 'options callback' is defined as a valid function
or static public method to generate these values. |
|
views_handler_filter_user_roles::operators |
core/modules/user/views/views_handler_filter_user_roles.inc |
Override empty and not empty operator labels to be clearer for user roles. |
|
views_handler_filter_vocabulary::get_value_options |
core/modules/taxonomy/views/views_handler_filter_vocabulary.inc |
Child classes should be used to override this function and set the
'value options', unless 'options callback' is defined as a valid function
or static public method to generate these values. |
|
views_handler_relationship::init |
core/modules/views/handlers/views_handler_relationship.inc |
Init handler to let relationships live on tables other than
the table they operate on. |
|
views_handler_relationship::label |
core/modules/views/handlers/views_handler_relationship.inc |
Get this field's label. |
|
views_handler_relationship::options_form |
core/modules/views/handlers/views_handler_relationship.inc |
Default options form that provides the label widget that all fields
should have. |
|
views_handler_relationship::option_definition |
core/modules/views/handlers/views_handler_relationship.inc |
Information about options for all kinds of purposes will be held here.
@code
'option_name' => array( |
|
views_handler_relationship::query |
core/modules/views/handlers/views_handler_relationship.inc |
Called to implement a relationship in a query. |
|
views_handler_relationship::use_group_by |
core/modules/views/handlers/views_handler_relationship.inc |
You can't groupby a relationship. |
|
views_handler_relationship_broken::broken |
core/modules/views/handlers/views_handler_relationship.inc |
Determine if the handler is considered 'broken' |
|
views_handler_relationship_broken::ensure_my_table |
core/modules/views/handlers/views_handler_relationship.inc |
Ensure the main table for this handler is in the query. This is used
a lot. |
|
views_handler_relationship_broken::options_form |
core/modules/views/handlers/views_handler_relationship.inc |
Default options form that provides the label widget that all fields
should have. |
|
views_handler_relationship_broken::query |
core/modules/views/handlers/views_handler_relationship.inc |
Called to implement a relationship in a query. |
|
views_handler_relationship_broken::ui_name |
core/modules/views/handlers/views_handler_relationship.inc |
Return a string representing this handler's name in the UI. |
|
views_handler_relationship_entity_reverse::init |
core/modules/field/views/views_handler_relationship_entity_reverse.inc |
Init handler to let relationships live on tables other than
the table they operate on. |
|
views_handler_relationship_entity_reverse::query |
core/modules/field/views/views_handler_relationship_entity_reverse.inc |
Called to implement a relationship in a query. |
|
views_handler_relationship_groupwise_max::alter_subquery_condition |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
Recursive helper to add a namespace to conditions. |
|
views_handler_relationship_groupwise_max::condition_namespace |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
Helper function to namespace query pieces. |
|
views_handler_relationship_groupwise_max::get_temporary_view |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
Helper function to create a pseudo view. |
|
views_handler_relationship_groupwise_max::left_query |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
Generate a subquery given the user options, as set in the options.
These are passed in rather than picked up from the object because we
generate the subquery when the options are saved, rather than when the view
is run. This saves considerable time. |
|
views_handler_relationship_groupwise_max::options_form |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
Extends the relationship's basic options, allowing the user to pick
a sort and an order for it. |
|
views_handler_relationship_groupwise_max::options_form_submit |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
When the form is submitted, take sure to clear the subquery string cache. |
|
views_handler_relationship_groupwise_max::option_definition |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
Defines default values for options. |
|
views_handler_relationship_groupwise_max::query |
core/modules/views/handlers/views_handler_relationship_groupwise_max.inc |
Called to implement a relationship in a query.
This is mostly a copy of our parent's query() except for this bit with
the join class. |
|
views_handler_relationship_node_term_data::init |
core/modules/taxonomy/views/views_handler_relationship_node_term_data.inc |
Init handler to let relationships live on tables other than
the table they operate on. |
|
views_handler_relationship_node_term_data::options_form |
core/modules/taxonomy/views/views_handler_relationship_node_term_data.inc |
Default options form that provides the label widget that all fields
should have. |
|
views_handler_relationship_node_term_data::option_definition |
core/modules/taxonomy/views/views_handler_relationship_node_term_data.inc |
Information about options for all kinds of purposes will be held here.
@code
'option_name' => array( |
|
views_handler_relationship_node_term_data::query |
core/modules/taxonomy/views/views_handler_relationship_node_term_data.inc |
Called to implement a relationship in a query. |
|
views_handler_relationship_translation::options_form |
core/modules/translation/views/views_handler_relationship_translation.inc |
Add a translation selector. |
|
views_handler_relationship_translation::option_definition |
core/modules/translation/views/views_handler_relationship_translation.inc |
Information about options for all kinds of purposes will be held here.
@code
'option_name' => array( |
|
views_handler_relationship_translation::query |
core/modules/translation/views/views_handler_relationship_translation.inc |
Called to implement a relationship in a query. |
|
views_handler_sort::admin_summary |
core/modules/views/handlers/views_handler_sort.inc |
Display whether or not the sort order is ascending or descending |
|
views_handler_sort::can_expose |
core/modules/views/handlers/views_handler_sort.inc |
Determine if a sort can be exposed. |
|
views_handler_sort::expose_form |
core/modules/views/handlers/views_handler_sort.inc |
Form for exposed handler options. |
|
views_handler_sort::expose_options |
core/modules/views/handlers/views_handler_sort.inc |
Provide default options for exposed sorts. |
|
views_handler_sort::options_form |
core/modules/views/handlers/views_handler_sort.inc |
Basic options for all sort criteria |
|
views_handler_sort::options_submit |
core/modules/views/handlers/views_handler_sort.inc |
Simple submit handler |
