• Mentioned in [59628] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59627] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59626] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59625] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59624] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59623] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59622] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59618] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59615] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59614] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59613] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59612] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59611] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59610] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59609] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59608] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [59601] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Posted a reply to Classic Press, on the site WordPress.org Forums:
    Hi Tobias, ClassicPress retains full compatibility with the WordPress 4.9 branch, and the $wp_version variable…

  • Posted a reply to JavaScript error in v2.6.1, on the site WordPress.org Forums:
    You're welcome. In the meantime, users can add the following code to functions.php or a…

  • Created a topic, JavaScript error in v2.6.1, on the site WordPress.org Forums:
    Hi, Version 2.6.1 of this plugin is causing a JavaScr…

  • Mentioned in [51179] on WordPress SVN:
    Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests.

  • Mentioned in [51026] on WordPress SVN:
    REST API: Add support for modifying the term relation when querying posts.

  • Mentioned in [51000] on WordPress SVN:
    REST API: Update “object” strings to use the appropriate nouns.

  • Mentioned in [50823] on WordPress SVN:
    Docs: Correct the `aria-current` array key in the documentation for two widget filters.

  • Mentioned in [50157] on WordPress SVN:
    REST API: Allow for the posts endpoint include/exclude terms query to `include_children`.

  • Mentioned in [49635] on WordPress SVN:
    General: Rename the `wp_error_checked` action to `is_wp_error_instance` for clarity.

  • Mentioned in [49295] on WordPress SVN:
    REST API: Deprecate `WP_REST_Meta_Fields::register_field()`.

  • Mentioned in [48995] on WordPress SVN:
    Docs: Add a `@since` note about `adjacent_posts_rel_link_wp_head()` no longer being used in core.

  • Posted a reply to Where is My WordPress 5.5?, on the site WordPress.org Forums:
    This is incorrect. The ClassicPress migration plugin also allows converting back to WordPress via the…

  • Mentioned in [48657] on WordPress SVN:
    Upgrade/Install: Improve `wp_opcache_invalidate()` performance.

  • Mentioned in [48235] on WordPress SVN:
    Comments: Make `wp_update_comment()` return `false` instead of 0 for an invalid comment or post ID.

  • Mentioned in [48160] on WordPress SVN:
    Upgrade/Install: Invalidate OPcache for PHP files during updates.

  • Mentioned in [48154] on WordPress SVN:
    Comments: Allow `wp_update_comment()` to return `WP_Error()`.

  • Mentioned in [47559] on WordPress SVN:
    REST API: Handle parameter types consistently within set_param().

  • Mentioned in [47224] on WordPress SVN:
    REST API: Introduce selective link embedding.

  • Mentioned in [47171] on WordPress SVN:
    Database: Add `ANSI` to the list of incompatible SQL modes.

  • Closed ticket #41549 on Core Trac:
    REST API: Use `wp.apiRequest` helper in `wp.api` Backbone client

  • Created ticket #48377 on Core Trac:
    sql_mode ANSI is incompatible with WP in MySQL 5.7.5+

  • Mentioned in [46252] on WordPress SVN:
    REST API: Introduce date_floating property on status endpoint response objects.

  • Mentioned in [46249] on WordPress SVN:
    REST API: Pass "null" as the post date property to reset post to initial "floating" date value.

  • Mentioned in [44633] on WordPress SVN:
    Tests: Ensure meta keys are cleaned up after each test.