renderPreview($display_id, $args); } /** * Page callback to add a new view. */ function views_ui_add_page() { drupal_set_title(t('Add new view')); $view = entity_create('view', array()); return entity_get_form($view, 'add'); } /** * Converts a form element in the add view wizard to be AJAX-enabled. * * This function takes a form element and adds AJAX behaviors to it such that * changing it triggers another part of the form to update automatically. It * also adds a submit button to the form that appears next to the triggering * element and that duplicates its functionality for users who do not have * JavaScript enabled (the button is automatically hidden for users who do have * JavaScript). * * To use this function, call it directly from your form builder function * immediately after you have defined the form element that will serve as the * JavaScript trigger. Calling it elsewhere (such as in hook_form_alter()) may * mean that the non-JavaScript fallback button does not appear in the correct * place in the form. * * @param $wrapping_element * The element whose child will server as the AJAX trigger. For example, if * $form['some_wrapper']['triggering_element'] represents the element which * will trigger the AJAX behavior, you would pass $form['some_wrapper'] for * this parameter. * @param $trigger_key * The key within the wrapping element that identifies which of its children * serves as the AJAX trigger. In the above example, you would pass * 'triggering_element' for this parameter. * @param $refresh_parents * An array of parent keys that point to the part of the form that will be * refreshed by AJAX. For example, if triggering the AJAX behavior should * cause $form['dynamic_content']['section'] to be refreshed, you would pass * array('dynamic_content', 'section') for this parameter. */ function views_ui_add_ajax_trigger(&$wrapping_element, $trigger_key, $refresh_parents) { $seen_ids = &drupal_static(__FUNCTION__ . ':seen_ids', array()); $seen_buttons = &drupal_static(__FUNCTION__ . ':seen_buttons', array()); // Add the AJAX behavior to the triggering element. $triggering_element = &$wrapping_element[$trigger_key]; $triggering_element['#ajax']['callback'] = 'views_ui_ajax_update_form'; // We do not use drupal_html_id() to get an ID for the AJAX wrapper, because // it remembers IDs across AJAX requests (and won't reuse them), but in our // case we need to use the same ID from request to request so that the // wrapper can be recognized by the AJAX system and its content can be // dynamically updated. So instead, we will keep track of duplicate IDs // (within a single request) on our own, later in this function. $triggering_element['#ajax']['wrapper'] = 'edit-view-' . implode('-', $refresh_parents) . '-wrapper'; // Add a submit button for users who do not have JavaScript enabled. It // should be displayed next to the triggering element on the form. $button_key = $trigger_key . '_trigger_update'; $wrapping_element[$button_key] = array( '#type' => 'submit', // Hide this button when JavaScript is enabled. '#attributes' => array('class' => array('js-hide')), '#submit' => array('views_ui_nojs_submit'), // Add a process function to limit this button's validation errors to the // triggering element only. We have to do this in #process since until the // form API has added the #parents property to the triggering element for // us, we don't have any (easy) way to find out where its submitted values // will eventually appear in $form_state['values']. '#process' => array_merge(array('views_ui_add_limited_validation'), element_info_property('submit', '#process', array())), // Add an after-build function that inserts a wrapper around the region of // the form that needs to be refreshed by AJAX (so that the AJAX system can // detect and dynamically update it). This is done in #after_build because // it's a convenient place where we have automatic access to the complete // form array, but also to minimize the chance that the HTML we add will // get clobbered by code that runs after we have added it. '#after_build' => array_merge(element_info_property('submit', '#after_build', array()), array('views_ui_add_ajax_wrapper')), ); // Copy #weight and #access from the triggering element to the button, so // that the two elements will be displayed together. foreach (array('#weight', '#access') as $property) { if (isset($triggering_element[$property])) { $wrapping_element[$button_key][$property] = $triggering_element[$property]; } } // For easiest integration with the form API and the testing framework, we // always give the button a unique #value, rather than playing around with // #name. $button_title = !empty($triggering_element['#title']) ? $triggering_element['#title'] : $trigger_key; if (empty($seen_buttons[$button_title])) { $wrapping_element[$button_key]['#value'] = t('Update "@title" choice', array( '@title' => $button_title, )); $seen_buttons[$button_title] = 1; } else { $wrapping_element[$button_key]['#value'] = t('Update "@title" choice (@number)', array( '@title' => $button_title, '@number' => ++$seen_buttons[$button_title], )); } // Attach custom data to the triggering element and submit button, so we can // use it in both the process function and AJAX callback. $ajax_data = array( 'wrapper' => $triggering_element['#ajax']['wrapper'], 'trigger_key' => $trigger_key, 'refresh_parents' => $refresh_parents, // Keep track of duplicate wrappers so we don't add the same wrapper to the // page more than once. 'duplicate_wrapper' => !empty($seen_ids[$triggering_element['#ajax']['wrapper']]), ); $seen_ids[$triggering_element['#ajax']['wrapper']] = TRUE; $triggering_element['#views_ui_ajax_data'] = $ajax_data; $wrapping_element[$button_key]['#views_ui_ajax_data'] = $ajax_data; } /** * Processes a non-JavaScript fallback submit button to limit its validation errors. */ function views_ui_add_limited_validation($element, &$form_state) { // Retrieve the AJAX triggering element so we can determine its parents. (We // know it's at the same level of the complete form array as the submit // button, so all we have to do to find it is swap out the submit button's // last array parent.) $array_parents = $element['#array_parents']; array_pop($array_parents); $array_parents[] = $element['#views_ui_ajax_data']['trigger_key']; $ajax_triggering_element = drupal_array_get_nested_value($form_state['complete_form'], $array_parents); // Limit this button's validation to the AJAX triggering element, so it can // update the form for that change without requiring that the rest of the // form be filled out properly yet. $element['#limit_validation_errors'] = array($ajax_triggering_element['#parents']); // If we are in the process of a form submission and this is the button that // was clicked, the form API workflow in form_builder() will have already // copied it to $form_state['triggering_element'] before our #process // function is run. So we need to make the same modifications in $form_state // as we did to the element itself, to ensure that #limit_validation_errors // will actually be set in the correct place. if (!empty($form_state['triggering_element'])) { $clicked_button = &$form_state['triggering_element']; if ($clicked_button['#name'] == $element['#name'] && $clicked_button['#value'] == $element['#value']) { $clicked_button['#limit_validation_errors'] = $element['#limit_validation_errors']; } } return $element; } /** * After-build function that adds a wrapper to a form region (for AJAX refreshes). * * This function inserts a wrapper around the region of the form that needs to * be refreshed by AJAX, based on information stored in the corresponding * submit button form element. */ function views_ui_add_ajax_wrapper($element, &$form_state) { // Don't add the wrapper
if the same one was already inserted on this // form. if (empty($element['#views_ui_ajax_data']['duplicate_wrapper'])) { // Find the region of the complete form that needs to be refreshed by AJAX. // This was earlier stored in a property on the element. $complete_form = &$form_state['complete_form']; $refresh_parents = $element['#views_ui_ajax_data']['refresh_parents']; $refresh_element = drupal_array_get_nested_value($complete_form, $refresh_parents); // The HTML ID that AJAX expects was also stored in a property on the // element, so use that information to insert the wrapper
here. $id = $element['#views_ui_ajax_data']['wrapper']; $refresh_element += array( '#prefix' => '', '#suffix' => '', ); $refresh_element['#prefix'] = '
' . $refresh_element['#prefix']; $refresh_element['#suffix'] .= '
'; // Copy the element that needs to be refreshed back into the form, with our // modifications to it. drupal_array_set_nested_value($complete_form, $refresh_parents, $refresh_element); } return $element; } /** * Updates a part of the add view form via AJAX. * * @return * The part of the form that has changed. */ function views_ui_ajax_update_form($form, $form_state) { // The region that needs to be updated was stored in a property of the // triggering element by views_ui_add_ajax_trigger(), so all we have to do is // retrieve that here. return drupal_array_get_nested_value($form, $form_state['triggering_element']['#views_ui_ajax_data']['refresh_parents']); } /** * Non-Javascript fallback for updating the add view form. */ function views_ui_nojs_submit($form, &$form_state) { $form_state['rebuild'] = TRUE; } /** * Form element validation handler for a taxonomy autocomplete field. * * This allows a taxonomy autocomplete field to be validated outside the * standard Field API workflow, without passing in a complete field widget. * Instead, all that is required is that $element['#field_name'] contain the * name of the taxonomy autocomplete field that is being validated. * * This function is currently not used for validation directly, although it * could be. Instead, it is only used to store the term IDs and vocabulary name * in the element value, based on the tags that the user typed in. * * @see taxonomy_autocomplete_validate() */ function views_ui_taxonomy_autocomplete_validate($element, &$form_state) { $value = array(); if ($tags = $element['#value']) { // Get the machine names of the vocabularies we will search, keyed by the // vocabulary IDs. $field = field_info_field($element['#field_name']); $vocabularies = array(); if (!empty($field['settings']['allowed_values'])) { foreach ($field['settings']['allowed_values'] as $tree) { if ($vocabulary = taxonomy_vocabulary_machine_name_load($tree['vocabulary'])) { $vocabularies[$vocabulary->vid] = $tree['vocabulary']; } } } // Store the term ID of each (valid) tag that the user typed. $typed_terms = drupal_explode_tags($tags); foreach ($typed_terms as $typed_term) { if ($terms = entity_load_multiple_by_properties('taxonomy_term', array('name' => trim($typed_term), 'vid' => array_keys($vocabularies)))) { $term = array_pop($terms); $value['tids'][] = $term->tid; } } // Store the term IDs along with the name of the vocabulary. Currently // Views (as well as the Field UI) assumes that there will only be one // vocabulary, although technically the API allows there to be more than // one. if (!empty($value['tids'])) { $value['tids'] = array_unique($value['tids']); $value['vocabulary'] = array_pop($vocabularies); } } form_set_value($element, $value, $form_state); } /** * Page to delete a view. */ function views_ui_break_lock_confirm($form, &$form_state, ViewUI $view) { $form_state['view'] = &$view; $form = array(); if (empty($view->locked)) { $form['message']['#markup'] = t('There is no lock on view %name to break.', array('%name' => $view->get('name'))); return $form; } $cancel = drupal_container()->get('request')->query->get('cancel'); if (empty($cancel)) { $cancel = 'admin/structure/views/view/' . $view->get('name') . '/edit'; } $account = user_load($view->locked->owner); $form = confirm_form($form, t('Do you want to break the lock on view %name?', array('%name' => $view->get('name'))), $cancel, t('By breaking this lock, any unsaved changes made by !user will be lost.', array('!user' => theme('username', array('account' => $account)))), t('Break lock'), t('Cancel')); $form['actions']['submit']['#submit'][] = array($view, 'submitBreakLock'); return $form; } /** * Page callback for the Edit View page. */ function views_ui_edit_page(ViewUI $view, $display_id = NULL) { $view->displayID = $display_id; $build['edit'] = entity_get_form($view, 'edit'); $build['preview'] = entity_get_form($view, 'preview'); return $build; } /** * Page callback for rendering the preview form and the preview of the view. * * @param \Drupal\views_ui\ViewUI $view * The view UI object to preview. * @param string $display_id * The display ID to preview. * * @return array * The form array of the full preview form. */ function views_ui_build_preview(ViewUI $view, $display_id) { $view->displayID = $display_id; return entity_get_form($view, 'preview'); } /** * Move form elements into details for presentation purposes. * * Many views forms use #tree = TRUE to keep their values in a hierarchy for * easier storage. Moving the form elements into fieldsets during form building * would break up that hierarchy. Therefore, we wait until the pre_render stage, * where any changes we make affect presentation only and aren't reflected in * $form_state['values']. */ function views_ui_pre_render_add_fieldset_markup($form) { foreach (element_children($form) as $key) { $element = $form[$key]; // In our form builder functions, we added an arbitrary #fieldset property // to any element that belongs in a fieldset. If this form element has that // property, move it into its fieldset. if (isset($element['#fieldset']) && isset($form[$element['#fieldset']])) { $form[$element['#fieldset']][$key] = $element; // Remove the original element this duplicates. unset($form[$key]); } } return $form; } /** * Flattens the structure of an element containing the #flatten property. * * If a form element has #flatten = TRUE, then all of it's children * get moved to the same level as the element itself. * So $form['to_be_flattened'][$key] becomes $form[$key], and * $form['to_be_flattened'] gets unset. */ function views_ui_pre_render_flatten_data($form) { foreach (element_children($form) as $key) { $element = $form[$key]; if (!empty($element['#flatten'])) { foreach (element_children($element) as $child_key) { $form[$child_key] = $form[$key][$child_key]; } // All done, remove the now-empty parent. unset($form[$key]); } } return $form; } /** * Moves argument options into their place. * * When configuring the default argument behavior, almost each of the radio * buttons has its own fieldset shown bellow it when the radio button is * clicked. That fieldset is created through a custom form process callback. * Each element that has #argument_option defined and pointing to a default * behavior gets moved to the appropriate fieldset. * So if #argument_option is specified as 'default', the element is moved * to the 'default_options' fieldset. */ function views_ui_pre_render_move_argument_options($form) { foreach (element_children($form) as $key) { $element = $form[$key]; if (!empty($element['#argument_option'])) { $container_name = $element['#argument_option'] . '_options'; if (isset($form['no_argument']['default_action'][$container_name])) { $form['no_argument']['default_action'][$container_name][$key] = $element; } // Remove the original element this duplicates. unset($form[$key]); } } return $form; } /** * Add a