Conversation
…k to the guide. Props birgire, azaozz. Merges [43263] to the 4.9 branch. Fixes #44057. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43264 602fd350-edb4-49c9-b593-d223f7449a82
… screen. Props ocean90, azaozz. Merges [43265] to the 4.9 branch. Fixes #44056. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43266 602fd350-edb4-49c9-b593-d223f7449a82
Props ocean90. Merges [43267] to the 4.9 branch. Fixes #44076. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43268 602fd350-edb4-49c9-b593-d223f7449a82
There doesn't appear to be any way for an attacker to introduce malicious input into the URL, unless a plugin is filtering the URL to add it, but it's better to be safe than sorry. Props birgire. Merges [43245] to the 4.9 branch. Fixes #44054. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43270 602fd350-edb4-49c9-b593-d223f7449a82
…ens. Props ianbelanger, subrataemfluence, desrosj. Merges [43251] to the 4.9 branch. Fixes #44026. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43271 602fd350-edb4-49c9-b593-d223f7449a82
…ordPress. Props fclaussen, azaozz. Merges [42981], [42982], [43243] to the 4.9 branch. Fixes #43491. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43272 602fd350-edb4-49c9-b593-d223f7449a82
…admin visits the Privacy Policy Guide screen. Props azaozz. Merges [43269] to the 4.9 branch. Fixes #44063. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43273 602fd350-edb4-49c9-b593-d223f7449a82
Previously, the link used absolute positioning, in order to stick it at the bottom of the page. That was done in order to create visual separation between it and the "action" links, like "Lost Your Password?" The absolute positioning can cause conflicts in some situations, though. For example, if extra text or error notices are added above the form, then the login link would be positioned on top of other elements. Switching to relative positioning with extra margins avoids those issues, while maintaining the visual separation between the "action" links and the privacy policy link. Props imath, melchoyce, desrosj, xkon, iandunn. Merges [43274] to the 4.9 branch. Fixes #44046. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43276 602fd350-edb4-49c9-b593-d223f7449a82
…Privacy_Policy_Content::notice()`. Props ocean90. Merges [43248] to the 4.9 branch. Fixes #44055. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43277 602fd350-edb4-49c9-b593-d223f7449a82
…screens. Props ianbelanger, azaozz. Merges [43279] to the 4.9 branch. Fixes #44093. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43280 602fd350-edb4-49c9-b593-d223f7449a82
…tools screens when text is long. Props audrasjb, ianbelanger. Merges [43278] to the 4.9 branch. Fixes #44092. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43281 602fd350-edb4-49c9-b593-d223f7449a82
Merges [43282] to the 4.9 branch. See #44092. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43283 602fd350-edb4-49c9-b593-d223f7449a82
Previously, personal data exports were stored in `wp-content/uploads/exports`, which is generic enough that it's likely there are existing folders with that name, either created by plugins or manually by administrators. If that folder were reused by Core, then `wp_privacy_delete_old_export_files()` would delete all of the existing files inside it, which is almost certainly not what the site owner wants or expects. To avoid that, the folder is being renamed to include a specific reference to Core, and a more verbose description of its purpose. With those factored in, it's very unlikely that there will be any conflicts with existing folders. The `wp_privacy_exports_dir()` and `wp_privacy_exports_url()` functions were introduced to provide a canonical source for the location, and the `wp_privacy_exports_dir` and `wp_privacy_exports_url` filters were introduced to allow plugins to customize it. Props johnjamesjacoby, allendav. Merges [43284] to the 4.9 branch. Fixes #44091. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43285 602fd350-edb4-49c9-b593-d223f7449a82
A user is required to have the `manage_privacy_options` capability in order to determine which page is set as the privacy policy (the `wp_page_for_privacy_policy`). Given that, it doesn't make sense to allow users without that capability to edit or delete the page. A similar situation exists with the `page_for_posts` and `page_on_front` options, but Editors are allowed to edit those pages. The reason that this situation is different is because it is more likely that an administrator will want to restrict modifications to the privacy policy, than it is that they will want to allow modifications. Modifications to the policy often require specialized knowledge of local laws, and can have implications for compliance with those laws. Props dlh, desrosj. Merges [43286] to the 4.9 branch. Fixes #44079. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43287 602fd350-edb4-49c9-b593-d223f7449a82
git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43288 602fd350-edb4-49c9-b593-d223f7449a82
git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43289 602fd350-edb4-49c9-b593-d223f7449a82
If a privacy policy has been set, then a link to it will automatically be shown in the footer. The element containing the "Proudly powered by WordPress" link was chosen for the new policy link, in order to minimize visual conflicts with custom CSS that was written before the new link existed. Unfortunately, some minor conflicts are expected and unavoidable. Adding this link is required as part of GDPR compliance, and the benefits outweigh the downsides. To further mitigate the conflicts, a new imprint class was added to the "Proudly powered..." link, in order to facilitate targeting each link invididually with custom styles. This was accidentally not backported to the `4.9` branch before the beta/RC phase, but there was a consensus that it is safe to do that this late in the release cycle. See https://wordpress.slack.com/archives/C02RQBWTW/p1526577643000132. See https://wordpress.slack.com/archives/C02RQBWTW/p1526580781000240. Props xkon, laurelfulford, birgire, azaozz, iandunn. Merges [43051] to the 4.9 branch. See #43715. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43294 602fd350-edb4-49c9-b593-d223f7449a82
…release Also, updates POT files for Twenty Ten and Twenty Eleven. Props earnjam, laurelfulford. Merges [43293] to the 4.9 branch. Fixes #43915. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43295 602fd350-edb4-49c9-b593-d223f7449a82
git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43296 602fd350-edb4-49c9-b593-d223f7449a82
git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43298 602fd350-edb4-49c9-b593-d223f7449a82
…p_privacy_generate_personal_data_export_file()`. `wp_mkdir_p()` returns `false` on error, not a `WP_Error` object. Props birgire. Merges [43299] to the 4.9 branch. Fixes #44158. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43300 602fd350-edb4-49c9-b593-d223f7449a82
There doesn't appear to be any way for an attacker to introduce malicious input into the URL, unless a plugin is filtering the URL to add it, but it's better to be safe than sorry. Props 1naveengiri, joyously. Merges [43290] to the 4.9 branch. Fixes #44115. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43301 602fd350-edb4-49c9-b593-d223f7449a82
The customizer has allowed HTML in sidebar descriptions since adding support for sidebars. This change ensures that basic HTML is also allowed for them in the widgets admin screen. Props flixos90. Merges [43275] to the 4.9 branch. Fixes #42608. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43302 602fd350-edb4-49c9-b593-d223f7449a82
…_privacy_personal_data_export_file`, `wp_privacy_personal_data_exporters`, and `wp_privacy_personal_data_erasers` hooks. Props birgire. Merges [43303] to the 4.9 branch. See #44125. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43305 602fd350-edb4-49c9-b593-d223f7449a82
Props desrosj, chetan200891. Merges [43304] to the 4.9 branch. See #44125. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43306 602fd350-edb4-49c9-b593-d223f7449a82
…ith_object_id`. When a term query using `fields=all_with_object_id` hits the cache, the cached `stdClass` objects must be converted to `WP_Term` objects. This was overlooked when `WP_Term_Query` was refactored to support object queries in [38667]. Merges [43313] to the 4.9 branch. Props dlh. Fixes #44221. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43314 602fd350-edb4-49c9-b593-d223f7449a82
…e data directory in place. Fixes #43982 Merges [43315] to the 4.9 branch. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43316 602fd350-edb4-49c9-b593-d223f7449a82
…rror` object in case the confirmation email has expired. Props itowhid06. Merges [43331] to the 4.9 branch. Fixes #44298. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43342 602fd350-edb4-49c9-b593-d223f7449a82
Props skoldin, subrataemfluence, ianbelanger, johnbillion. Merges [43317] and [43318] to the 4.9 branch. Fixes #44089. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43349 602fd350-edb4-49c9-b593-d223f7449a82
Props garetharnold, abdullahramzan. Merges [43350] to the 4.9 branch. Fixes #44166. git-svn-id: https://develop.svn.wordpress.org/branches/4.9@43351 602fd350-edb4-49c9-b593-d223f7449a82
Let Gutenberg shine with this simple, fast, and powerful theme. Initial development occurred on GitHub. See: https://github.com/WordPress/twentynineteen Props allancole, karmatosed, kjellr, yingling017, mrasharirfan, milana_cap, fabiankaegy, westonruter, aaronjorbin, netweb, b-07, khleomix, blowery, dereksmart, jasmussen, audrasjb, nielslange, mmaumio, dimadin, joyously, anevins12. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43808 602fd350-edb4-49c9-b593-d223f7449a82
After [43808], we can now make twentynineteen the default theme. Twentyseventeen has been a great default, but 5.0 and twentynineteen is guten. Fixes #45152. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43809 602fd350-edb4-49c9-b593-d223f7449a82
Adapts the response from `WP_oEmbed_Controller::get_proxy_item()` so that the response is correctly filtered and embeds work properly in JavaSccript editors. Introduces new `get_oembed_response_data_for_url()` function for preparing internal oEmbed responses. Props danielbachhuber, imath, swissspidy. Fixes #45142. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43810 602fd350-edb4-49c9-b593-d223f7449a82
Because the REST API allows meta keys to have empty values, the Custom Fields meta box should permit the same behavior. Props charlestonsw, soulseekah. Fixes #43559. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43811 602fd350-edb4-49c9-b593-d223f7449a82
Blocks are able to register styles that used in the editor and the frontend, or only in the editor. These functions ensure the correct styles are loaded in the correct place. See #45065. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43812 602fd350-edb4-49c9-b593-d223f7449a82
To avoid this being a vector for bypassing the filetypes that are allowed to be uploaded, this attribute is only allowed to be added without a value. Props kalpshit, arshidkv12, welcher, peterwilsoncc, marina_wp, pento. See #44724. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43813 602fd350-edb4-49c9-b593-d223f7449a82
The `add_theme_support()` inline docs now includes the features that the block editor adds. Props desrosj. See #45134. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43814 602fd350-edb4-49c9-b593-d223f7449a82
Change the default layout slightly, and tweak the HTML stored in `post_content`. Props matveb, karmatosed, joen, youknowriad, aduth, iseulde, pento, EphoxJames, mkaz, jnylen0, notnownikki, lonelyvegan, chopinbach, njpanderson, mimo84, intronic, westonruter, mcsf, dmsnell, afercia, paulwilde, mitogh, codebykat, mrahmadawais, kopepasah, circlecube, adamsilverstein, timmydcrawford, ephox-mogran, nbachiyski, JDGrimes, laurelfulford, Soean, mapk, sirjonathan, j-falk, ryelle, helen, netweb, lamosty, willybahuaud, maurobringolf, jorbin, spocke, androb, annaharrison, Afraithe, georgeh, matt, melchoyce, nitrajka, sirreal, babbardel, arush, martinlugton, iandunn, oyously, rileybrook, azaozz, folletto, ianstewart, johnpixle, clorith, joedolson, ipstenu, mrwweb, diegoliv, jeffpaul, lukecavanagh, shaunandrews, hugobaeta, jjj, mizejewski, buzztone, jdembowski, webdevmattcrom, GaryJones, jasonagnew, dd32, ieatwebsites, gma992, swissspidy, dixitadusara, ameeker, stagger-lee, jblz, nicbertino, rahmohn, vladanost, gziolo, lancewillett, lynneux, betsela, fuyuko, msdesign21, thrijith, chanthaboune, Cloud887, hblackett, vishalkakadiya, c-shultz, nfmohit, noisysocks, omarreiss, hedgefield, hideokamoto, mirucon, nosolosw, DannyCooper, burhandodhy, zebulan, benjamin_zekavica, danielbachhuber, jorgefilipecosta, ajitbohra, bph, ChrisVanPatten, dixitadusara, antpb, mikehaydon, jahvi, floriansimeth, Mathiu, amedina, diegoreymendez, etoledom, caxco93, yoavf, welcher, bobbingwide, jonsurrell, notlaura, ocean90, eliorivero, wpscholar, Shelob9, travislopes, earnjam, designsimply, johnwatkins0, dfangstrom, igorsch, jaswrks, daniloercoli, rianrietveld, dimadin, SergioEstevao, dlocc, tinkerbelly, schlessera, sumobi, kjellr, ireneyoast, hypest, tfrommen, intronic, johnny5, samikeijonen, bpayton, atimmer, Rahmon, tg-ephox, nerrad, talldan, Xyfi. See #45037. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43815 602fd350-edb4-49c9-b593-d223f7449a82
Props bordoni. See #45037. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43816 602fd350-edb4-49c9-b593-d223f7449a82
For the WordPress zip we need both the minified and non-minified files. This is because of `SCRIPT_DEBUG`. So in `grunt build` we need to do both `grunt webpack:prod` and `grunt webpack:dev`. Props bordoni. Fixes #45156. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43817 602fd350-edb4-49c9-b593-d223f7449a82
`wp-date` recently added the `datetimeAbbreviated` format, but the config wasn't sending it on page load. Fixes #45158. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43818 602fd350-edb4-49c9-b593-d223f7449a82
In PHP 7.3, the compact() function has been changed to issue an E_NOTICE level error if a passed string refers to an unset variable. In previous versions of PHP, this notice was silently skipped. The full RFC can be viewed here: https://wiki.php.net/rfc/compact This fixes all unit tested code that uses compact. Props desrosj. Fixes #44416. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43819 602fd350-edb4-49c9-b593-d223f7449a82
…olicy` to block content. Props desrosj, garrett-eclipse, danielbachhuber. Fixes #45151. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43820 602fd350-edb4-49c9-b593-d223f7449a82
…eteen. POT files are no longer required. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43821 602fd350-edb4-49c9-b593-d223f7449a82
git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43822 602fd350-edb4-49c9-b593-d223f7449a82
git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43823 602fd350-edb4-49c9-b593-d223f7449a82
Instead of requiring the packages individually this commit changes it so the packages are used from the packages repository (gutenberg). This is a solution that makes updating the packages easier, as long as we don't have a monorepo to manage both WordPress & the JavaScript packages together. Props youknowriad, gziolo, omarreiss, herregroen. See #45145. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43824 602fd350-edb4-49c9-b593-d223f7449a82
Adds the `wp_set_script_translations` function which registers translations for a JavaScript file. This function takes a handle, domain and optionally a path and ensures JavaScript translation files are loaded if they exist. Props atimmer, omarreiss, nerrad, swissspidy, ocean90. Fixes #45103. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43825 602fd350-edb4-49c9-b593-d223f7449a82
Props omarreiss. See #45145. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43826 602fd350-edb4-49c9-b593-d223f7449a82
…andbook from the descriptions for a variety of core conditional tag functions. These notations largely serve to direct consumers (of both the source and the parsed code reference) to extended information on individual and related conditional tags throughout WordPress. The changeset also standardizes corresponding DocBlock summaries to use third-person singular verbs. Notations have been added for the following functions: * comments_open() * email exists() * has_excerpt() * has_post_thumbnail() * has_tag() * in_category() * in_the_loop() * is_404() * is_active_sidebar() * is_active_widget() * is_admin() * is_admin_bar_showing() * is_archive() * is_attachment() * is_author() * is_blog_installed() * is_category() * is_comments_popup() * is_date() * is_day() * is_dynamic_sidebar() * is_feed() * is_front_page() * is_home() * is_local_attachment() * is_main_query * is_month() * is_multi_author * is_new_day() * is_page() * is_page_template() * is_paged() * is_plugin_active() * is_plugin_active_for_network() * is_plugin_inactive() * is_plugin_page() * is_post_type_archive() * is_preview() * is_rtl() * is_search() * is_single() * is_singular() * is_sticky() * is_tag() * is_tax() * is_taxonomy_hierarchical() * is_time() * is_trackback() * is_user_logged_in() * is_year() * pings_open() * post_type_exists() * taxonomy_exists() * term_exists() * username exists() * wp_attachment_is_image() * wp_script_is() Merges [42710] to the 5.0 branch. Props janalwin. Fixes #43254. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43827 602fd350-edb4-49c9-b593-d223f7449a82
`__DIR__` is not available in PHP 5.2.x. See #45103. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43828 602fd350-edb4-49c9-b593-d223f7449a82
…e media templates. Label elements should only be used for labelable elements. - `Uploaded By` and `Uploaded To` aren't form controls and shouldn't be associated with labels - changes the labels for media source, alternate sources, poster image, and tracks to solve a layout issue and explicitly associate the labels to their form fields (previously, the labels were wrapping also the Remove buttons) Merges [42444] to the 5.0 branch. Props Presskopp, afercia. Fixes #38759, #40468. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43829 602fd350-edb4-49c9-b593-d223f7449a82
…d callback. When `WP_DEBUG` is set, ensure that a static method callback is passed to `ReflectionMethod`, instead of `ReflectionFunction`. Props DrewAPicture. Fixes #45192. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43830 602fd350-edb4-49c9-b593-d223f7449a82
The inline script for `wp-date` incorrectly included a textdomain, and lacked translator comments. Props mukesh27. Fixes #45191, #45162. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43831 602fd350-edb4-49c9-b593-d223f7449a82
In PHP 7.3, the compact() function has been changed to issue an E_NOTICE level error if a passed string refers to an unset variable. In previous versions of PHP, this notice was silently skipped. The full RFC can be viewed here: https://wiki.php.net/rfc/compact By initializing these variables, they can be compacted. Previously [43819]. See #44416. Props desrosj. git-svn-id: https://develop.svn.wordpress.org/branches/5.0@43832 602fd350-edb4-49c9-b593-d223f7449a82
Member
|
This repository is just a synced version of git://develop.git.wordpress.org/, including branches and tags! Please do not send pull requests. Submit patches to https://core.trac.wordpress.org/ instead. |
Author
|
Thanks a lot. |
blitzy Bot
pushed a commit
to blitzy-research/wordpress-develop
that referenced
this pull request
Aug 8, 2026
…workstreams Addresses all 51 findings from code review o006 (34 numbered, 11 module, 6 security). Two of the six binding targets now pass and every unmet target improved; the four that remain short are documented against the AAP sections that exclude the work required to close them. Implemented, not merely disclosed: * wp-settings.php: defer the two admin-only files the plan mandates off the front-end path. wp-admin/includes/plugin.php is required only when a plugin is active or is_admin(); WP_Site_Health is instantiated only for admin, cron and WP-CLI. 6,533 lines stop being tokenized on every front-end request, and the Site Health class map entry stops being a zero-delta entry. (WordPress#13, A2) * capabilities.php: deliver the map_meta_cap() memoization the plan prescribes and the previous round withdrew. Branch-scoped to the four post arms, keyed on every input that can change the result including the post type's cap object, bypassed when a non-core map_meta_cap callback is present, and the filter still runs on every call. Measured -8.8% cold / -8.0% warm over 7/7 interleaved rounds. (WordPress#12) * autoload.php: is_readable() replaces file_exists() at both guards so an existing-but-unreadable file degrades instead of raising an uncatchable E_COMPILE_ERROR; the path-confinement pattern is anchored with \z so a value carrying a trailing newline cannot pass a guard advertised as canonical; CompileError is re-raised while any other Error is reported under WP_DEBUG through wp_trigger_error(). (WordPress#15, WordPress#16, WordPress#17, S2, S3) * formatting.php: scope the emoji gate to the front end, the only context the plan measured, pass the context to the filter, and restore trunk's $printed ordering. (WordPress#20, WordPress#21, C1) * script-loader.php: publish the documented one-line rollback for the Command Palette gate and name both consequences - wp.commands/wp.coreCommands undefined and the Ctrl+K button absent - in the predicate's docblock. (WordPress#18, WordPress#19, B1) * class-wp-object-cache.php: stop stats() emitting an advisory paragraph on the default path, so its public output matches trunk exactly. (WordPress#23, WordPress#22, D1) * Gruntfile.js: move verify:build-guards out of every production build into precommit and prerelease, and classify ENOENT at both host-php spawn sites. (WordPress#24, WordPress#25) * server-timing.php: refuse to serve the reset endpoint when the pre-existing unauthenticated clear-cache.php is provisioned beside it. (WordPress#29, S5) * admin.test.js / utils.js: collect JavaScript by Content-Type as well as by .js pathname, which was under-counting by ~99,019 gzipped bytes in both arms whenever CONCATENATE_SCRIPTS is active. (WordPress#30, WordPress#31) * generate-autoload-classmap.php: @return never on the fail-closed exit. Clears the one PHPStan error the file had. (WordPress#28) * build-guards.test.js: prettier-clean. (WordPress#33) New committed coverage for behaviour that shipped with none - 34 cases: tests/phpunit/tests/dependencies/commandPalette.php (7), tests/phpunit/tests/formatting/emojiGate.php (6), tests/phpunit/tests/cache/objectCacheGroupStats.php (8), tests/phpunit/tests/user/mapMetaCapMemoization.php (13). (B2, C2, D1) docs/performance-optimization-report.md rewritten against a fresh before/after pair captured under one interpreter regime with 40 samples per metric per scenario over 18 scenarios. Every stale artifact reference, blob id and digest is replaced; the ephemeral self-check machinery is replaced with in-tree re-runnable commands; the emoji, files-loaded, byte-size, PHPStan/PHPCS coverage and 216-construct claims are corrected; a Security invariants section records Gate 7 and findings S1, S4 and S6; and a before/after loading-flow diagram is added. (WordPress#1-WordPress#11, WordPress#14, WordPress#26, WordPress#27, WordPress#31, WordPress#32, WordPress#34, A1, A3, C3, H1, S1, S4, S6) Verification: PHPUnit 29,165 single-site and 29,957 multisite with 0 failures and 0 errors, warning and skip counts identical to the pre-change baseline; QUnit 456/456; E2E exit 0; performance suite 820 passed in both arms and compare-results.js exit 0; PHPStan exit 0 over 1,414 files; PHPCS exit 0; production and dev builds clean with no drift and build/ byte-identical to src/.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
18 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Is it possible to add "Checkmark" option on the "Appearance" > Menu?
That is very important to select multiple menu to delete or moving.
Kindly add this feature to the Wordpress 5.0