Function/File Code Issue
"deprecated"
filter_xss_bad_protocol()
common.inc
 * @param $decode
 *   (deprecated) Whether to decode entities in the $string. Set to FALSE if the
 *   $string is in plain text, TRUE otherwise. Defaults to TRUE. This parameter
 *   is deprecated and will be removed in Drupal 8. To process a plain-text URI,
 *   call drupal_strip_dangerous_protocols() or check_url() instead.
Change record: https://www.drupal.org/node/2079005
drupal_realpath()
file.inc
 * @todo This function is deprecated, and should be removed wherever possible.
Change record: https://www.drupal.org/node/2418133
Entity::translations()
Entity.php
   * Returns the languages the entity is translated to.
   *
   * @todo: Remove once all entity types implement the entity field API. This
   * is deprecated by
   * TranslatableInterface::getTranslationLanguages().
Change record: https://www.drupal.org/node/1532946
hook_route_info()
system.api.php
 * @deprecated
 *   This mechanism for registering routes is temporary. It will be replaced
 *   by a more robust mechanism in the near future.  It is documented here
 *   only for completeness.
Completely gone. Like the @deprecated says, it was a scaffold.
user_uid_only_optional_to_arg()
user.module
 * Deprecated. Use %user_uid_optional instead.
 *
 * @todo D8: Remove.
Completely gone.
"D8"
LocalStream::getDirectoryPath()
LocalStream.php
   * @todo Review this method name in D8 per http://drupal.org/node/701358.
Still needs attention:
Ajax\FrameworkTest::testLazyLoad()
    // @todo D8: Add a drupal_css_defaults() helper function.
Gone.
UpgradePathTestBase::variable_set()
   * @todo Update for D8 configuration system.
UpgradePathTestBase no longer exists.
update_uninstall()
update.install
  // @todo D8: Convert to new state storage.
Uses state as of: #2175769: Fix incorrect variable_del in update_uninstall()
update_manager_install_form_submit()
update.manager.inc
    // @todo: Fix me in D8: We need a way to set multiple errors on the same
    // form element and have all of them appear!
Function is gone.
"Drupal 8"
ajax_pre_render_element()
ajax.inc
    // @todo Legacy support. Remove in Drupal 8.
    if (isset($settings['method']) && $settings['method'] == 'replace') {
      $settings['method'] = 'replaceWith';
    }
ajax.inc doesn't exist any more.
form_builder()
form.inc
      // @todo Legacy support. Remove in Drupal 8.
      $form_state['clicked_button'] = $form_state['triggering_element'];
#1812636: Remove deprecated $form_state['clicked_button']
Gone from form.inc.
drupal_rebuild_form()
form.inc
  // Caching is normally done in drupal_process_form(), but what needs to be
  // cached is the $form structure before it passes through form_builder(),
  // so we need to do it here.
  // @todo For Drupal 8, find a way to avoid this code duplication.
  if (empty($form_state['no_cache'])) {
    form_set_cache($form['#build_id'], $form, $form_state);
  }
Form elements are now subclasses of Drupal\Core\Render\Element\FormElement.
form_process_select()
form.inc
 *   - #empty_value: (optional) The value for the first default option, which is
 *     used to determine whether the user submitted a value or not.
 *     - If #required is TRUE, this defaults to '' (an empty string).
 *     - If #required is not TRUE and this value isn't set, then no extra option
 *       is added to the select control, leaving the control in a slightly
 *       illogical state, because there's no way for the user to select nothing,
 *       since all user agents automatically preselect the first available
 *       option. But people are used to this being the behavior of select
 *       controls.
 *       @todo Address the above issue in Drupal 8.
 *     - If #required is not TRUE and this value is set (most commonly to an
 *       empty string), then an extra option (see #empty_option above)
 *       representing a "non-selection" is added with this as its value.
Form elements are now subclasses of Drupal\Core\Render\Element\FormElement.
form_process_checkboxes()
form.inc
      // Integer 0 is not a valid #return_value, so use '0' instead.
      // @see form_type_checkbox_value().
      // @todo For Drupal 8, cast all integer keys to strings for consistency
      //   with form_process_radios().
      if ($key === 0) {
        $key = '0';
      }
Form elements are now subclasses of Drupal\Core\Render\Element\FormElement.
Database\Driver\sqlite\Install\Tasks
  /**
   * Minimum engine version.
   *
   * @todo Consider upping to 3.6.8 in Drupal 8 to get SAVEPOINT support.
   */
  public function minimumVersion() {
    return '3.3.7';
  }
From Drupal\Core\Database\Driver\sqlite\Install\Tasks:
  public function minimumVersion() {
    return '3.7.11';
  }
_field_form_state_parents()
field.form.inc
  // @todo Remove backwards compatibility in Drupal 8, and use a unique
  // $form_state['field'][...$parents...]['#fields'][$field_name] structure.
Function gone.
WebTestBase::curlExec()
    // TODO: Remove this for Drupal 8, since fixed in curl 7.20.0.
#2894723: @todo Fix WebTestBase::curlExec()
user_uid_optional_load()
user.module
 * @todo rethink the naming of this in Drupal 8.
Function is gone.
user_uid_optional_to_arg()
user.module
 * @todo rethink the naming of this in Drupal 8.
Function is gone.
user_comment_view()
user.module
    // @todo This alters and replaces the original object value, so a
    //   hypothetical process of loading, viewing, and saving will hijack the
    //   stored data. Consider renaming to $comment->signature_safe or similar
    //   here and elsewhere in Drupal 8.
    $comment->signature = check_markup($comment->signature, $comment->signature_format, '', TRUE);
Function removed by #1778178: Convert comments to the new Entity Field API

Comments

sun’s picture

Fixing the utterly ugly styling.

sun’s picture

Issue summary: View changes

Updated issue summary.

TR’s picture

Issue summary: View changes

Resolution of user_comment_view() issue.

andypost’s picture

Assigned: sun » Unassigned
dawehner’s picture

Berdir suggested this tag

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Mile23’s picture

Mile23’s picture

Issue summary: View changes

Made it through all of them. The only two outstanding are related to stream wrappers (see #7) and #2894723: @todo Fix WebTestBase::curlExec() which I just added.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Status: Active » Fixed
Issue tags: -

There is only one issue left to work on in this Meta, #2343491: Review and Redefine the Drupal 8 StreamWrapper API including error handling.

A common practice is close Metas when there is only one issue left, so I am changing this to fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.