On September 8, 2006, Linden Lab released a news bulletin that revealed their Second Life database had been compromised and customer information, including encrypted passwords and users' real names, had likely been accessed.[140][141] However, it was later revealed that the hacker had in fact been focused on trying to cheat the in-world money system[142] and their access to personal information was believed incidental, although a full alert was still raised for safety's sake.
second life hack v2.7.1 password
In November 2006 controversy arose over a tool called CopyBot, developed as part of libsecondlife and was intended to allow users to legitimately back up their Second Life data. For a brief period, an unmodified CopyBot allowed any user to replicate SL items or avatars (although not scripts, which run only on the servers at Linden Lab). Later changes to the SecondLife protocols prevented unmodified copies of CopyBot from working. Nevertheless, the basic issue of users being able to duplicate content that is sent to them remains.
In second life anyone who owns a simulator and griefs others with alts or breaks the EULA/TOS nothing gets done. I know LL doesn't get involved in residentual disputes however when they are in clear violation of the TOS/CS they should deal with issues that come up.
A new release of WP-CLI is available as of today: WP-CLI v2.6.0. For this release, we had 57 contributors collaborate to get 311 pull requests merged. \ud83c\udf89\n\n\n\nThe pandemic is still controlling our daily lives, and as a side-effect we still notice a significant reduction in contributors to WP-CLI, probably due to the lack of in-person contributor days.\n\n\n\nAs always, big thanks to the WP-CLI sponsors that make the continued maintenance possible - even with a reduced number of contributors. \u2764\ufe0f\n\n\n\nApart from the numerous bug fixes that were included in this release, we also managed to snuggle in a few new features that add to the power or convenience of your CLI experience, so I want to spend a few paragraphs going over some of the noteworthy changes. As always, you can also skip directly to the\u00a0detailed changelog\u00a0if you prefer.\n\n\n\nPHP 8.1 Support\n\n\n\nWP-CLI now officially supports PHP 8.1. All commands are being extensively tested against PHP 8 and the actual development is currently being done on PHP 8.1 as well.\n\n\n\nHowever, keep in mind that PHP 8.1 support is not fully there for WordPress Core, and especially for a large part of plugins and themes. Due to the nature of the changes that PHP 8.1 brings about, it is very easy to break perfectly compatible WordPress Core or WP-CLI via the actions\/filters system. Keep this in mind when trying to diagnose PHP 8.1 compatibility issues and trying to deduce where the erroneous code is to be found.\n\n\n\nTabular data showing a timeline with supported PHP releases, with only 8.0 and 8.1 currently in active support.\n\n\n\nFor those of you who are not closely following the PHP release cycles, please be aware that only PHP 8.0 and 8.1 are currently actively supported versions. WP-CLI sticks with the WordPress Core PHP support policy (+ 1 year), which means we're still spending huge amounts of efforts to keep everything running all the way down to PHP 5.6 at the moment.\n\n\n\nIf you want to help the maintainers in their work, please ensure that all your sites run on the latest PHP versions, and nag your hosting providers to move everything over to the latest and greatest. WordPress will only bump the minimum version when the number of active sites on PHP 5.6 has dropped to an insignificant amount.\n\n\n\nNew commands for managing application passwords\n\n\n\nThe following commands were added to allow CLI users to create and manage WordPress application passwords:\n\n\n\nwp user application-password listwp user application-password getwp user application-password existswp user application-password updatewp user application-password record-usagewp user application-password createwp user application-password delete\n\n\n\nWP-CLI examples of creating a new application password and then listing all existing application passwords for that same user.\n\n\n\nAlthough you could technically already work with application passwords by directly controlling the WordPress user-meta table, this now provides a clean API that abstracts away the technical implementation. See the Application Passwords: Integration Guide to find out more about how to use them.\n\n\n\nNew global flag:\u00a0--context\n\n\n\nA new global flag --context=\u00a0was added which allows users to select the WordPress context in which WP-CLI is supposed to execute its command(s).\n\n\n\nOne of the main goals is to allow WP-CLI to run updates on premium plugins and themes without requiring any special setup. From our initial testing, this allows a large range of popular premium extensions to just work\u2122\ufe0f with WP-CLI in terms of their update procedures.\n\n\n\nPossible values for this flag with this initial release:\n\n\n\ncli: The context which has been the default before introduction of this flag. This is something in-between a frontend and an admin request, to get around some of the quirks of WordPress when running on the console.admin: A context that simulates running a command as if it would be executed in the administration backend. This is meant to be used to get around issues with plugins that limit functionality behind an\u00a0is_admin()\u00a0check.auto: Switches between\u00a0cli\u00a0and\u00a0admin\u00a0depending on which command is being used. For this initial release, all\u00a0wp plugin *\u00a0and\u00a0wp theme *\u00a0commands will use\u00a0admin, while all other commands will use\u00a0cli.frontend: [WIP] This does nothing yet.\n\n\n\nRoadmap: By default, the\u00a0--context\u00a0flag will be set to\u00a0cli\u00a0with this initial release (v2.6.0). With WP-CLI v2.7.0, the default will change to\u00a0auto. This gradual deployment will allow hosters and site owners to run tests on v2.6.0 by manually setting the context before the default behavior is changed.\n\n\n\nIf you want to use the future default of --context=auto right away in your present operations, you can do so by adding the necessary context: auto line to your global wp-cli.yml configuration file. Feel free to check the documentation on WP-CLI configuration files if this is new to you.\n\n\n\nWe also have a new hook to support this new global flag: before_registering_contexts.\u00a0This hook behaves like a filter with one argument:\u00a0array $contexts. When hooking into this hook, the callback should return (a potentially modified)\u00a0$contexts\u00a0value. This can be used to remove or override bundled contexts or add new ones.\n\n\n\nTo make this work, the hook functionality in WP-CLI (provided via\u00a0WP_CLI::do_hook()) was modified to return the first argument if arguments were provided.\n\n\n\nThanks to\u00a0Cloudways\u00a0for the special support and testing of this new flag with the goal of solving the \"premium updates problem\" for everyone.\n\n\n\nConfigurable WP-CLI cache settings\n\n\n\nThe WP-CLI file cache can now be configured via the following environment variables:\n\n\n\nWP_CLI_CACHE_DIR\u00a0- Directory in which to store the cached files. Default value:\u00a0\"$home\/.wp-cli\/cache\".WP_CLI_CACHE_EXPIRY\u00a0- Time after which cached files are automatically purged, in seconds. Default value:\u00a015552000\u00a0(6 months).WP_CLI_CACHE_MAX_SIZE\u00a0- Total size of the file cache after which older files are purged, in bytes. Default value:\u00a0314572800\u00a0(300 MB).\n\n\n\nThis not only allows you to fine-tune the WP-CLI cache behavior for the best balance between available storage and bandwidth usage, it could also be used to share cache storage between installations\/users (beware the security implications, though!).\n\n\n\nUse custom names\/locations for the wp-config.php file\n\n\n\nThe different config * commands now accept a new flag --config-file= that allow you point the different manipulations towards a custom location, that might not even fully adhere to conventions for the WordPress wp-config.php file.\n\n\n\nThis allows you for example to use the config set command for a configuration file outside of the WordPress document root (and parent folder).\n\n\n\nKeep in mind that you're on your own when it comes to making WordPress understand the structure and bootstrap correctly!\n\n\n\nGenerate a dotenv file from your existing wp-config.php file\n\n\n\nFor all the 12-factor app fans out there, WP-CLI has learnt a new format for its config list command: --format=dotenv. This will take the existing configuration key\/value pairs in your wp-config.php file and render them in a format that you can use in a .env file.\n\n\n\nWP-CLI example of list the contents of the wp-config.php file into a file in dotenv format and then showing the result.\n\n\n\nCombine with the previously mentioned --config-file to extract the dotenv file from an arbitrary location, even without a WordPress installation present.\n\n\n\nAllow plugin\/theme enumeration without forcing an update check\n\n\n\nPreviously, when you run plugin list or theme list, WP-CLI would automatically run a check in the background to see if updates are available. This is slow and expensive to do, and might not always be what is needed, especially in scripting scenarios.\n\n\n\nThis automatic check for updates can now be disabled for these two commands with the --skip-update-check flag. This can drastically speed up some scripts and make them more reliable.\n\n\n\nNew flag --strict for adapting the filtering of taxonomies by post type\n\n\n\nWhen retrieving taxonomies for a given post type, the old default behavior of WordPress (through the use of get_taxonomies()) is to only show those taxonomies that have as a sole associated post type the requested one. Taxonomies that have multiple associated post types, including the requested one, are not returned.\n\n\n\nWordPress had added a newer mechanism via get_object_taxonomies() that would return all taxonomies that are in some way associated with the requested post type, even if other post types are associated as well.\n\n\n\nWP-CLI now has a new --strict flag for the taxonomy list command that defines whether the strict filtering (the old default) should be used, or the more sensible inclusive approach should be used via --no-strict (or --strict=false).\n\n\n\nWe've opted to make this new, more sensible approach (i.e. --no-strict) the new default, so be mindful of that if you're using taxonomy list in a script somewhere.\n\n\n\nAnother round of improvements to the i18n * commands\n\n\n\nAs with all of the recent releases, the i18n * commands have received yet another round of overall improvements to keep in sync with the localisation requirements of WordPress Core.\n\n\n\nFrom new flags like --subtract-and-merge, --update-mo-files & --location and multiple improvements to the way Javascript syntax is parsed all the way up to the support for the new theme.json format, all your localization needs should be accounted for (at least for now).\n\n\n\nMake your to check out the detailed logs to find out more and play around with the new functionality when you get the chance!\n\n\n\nWith super admin permissions come super admin consequences!\n\n\n\nWP-CLI now mirrors the behavior of WordPress core and triggers various hooks when you grant or revoke the super admin status to users.\n\n\n\nThe following actions are being triggered now but the super-admin add & super-admin remove commands:\n\n\n\ngrant_super_admin\u00a0(before changes,\u00a0always\u00a0executed)granted_super_admin\u00a0(after changes, executed only on success)revoke_super_admin\u00a0(before changes,\u00a0always\u00a0executed)revoked_super_admin\u00a0(after changes, executed only on success)\n\n\n\nChanges to the default branches\n\n\n\nIn order to make the language used in the code and documentation of WP-CLI more inclusive, work has started to change the name of default branch across all repositories. From now on, the default branch name across the WP-CLI GitHub organization is main.\n\n\n\nThis change is currently a work in progress, as it unfortunately causes open pull requests to be automatically closed and often become unsalvageable. The current progress of this effort can be monitored here: wp-cli\/wp-cli#5598.\n\n\n\nKeep this in mind when you want to check out the latest development state of a repository or contribute by creating a PR!\n\n\n\nDetailed change log\n\n\n\nTo avoid too much noise in the list above, the following types of pull requests have been omitted:\n\n\n\nPRs that only bumped dependencies to their latest version.PRs that only fixed a typo in the documentation.PRs that add an allow-plugins rule to Composer\n\n\n\nwp-cli\/wp-cli-bundle\n\n\n\nDisable deployments on forks [#389]Deploy from main branch [#385]Revert usage of Mustache fork [#373]Use latest branch for Roave security advisories [#357]Add DEB build workflow [#345]Add RPM build workflow [#344]Switch to dev-master for wp-cli framework [#333]\n\n\n\nwp-cli\/wp-cli\n\n\n\nAdapt VERSION from 2.5.1-alpha to 2.6.0-alpha [#5605]Fix Composer stack tests [#5599]Detect and ignore BOMs [#5597]Check github.repository_owner in automerge workflow [#5591]Revert addition of the Mustache PHP 8.1 workaround and update dependency [#5590]Use Mustache work-around for PHP 8.1 compat [#5588]Use fork on schlessera for Mustache PHP 8.1 fix [#5587]Re-add subcommands on all composite commands that are overwritten [#5584]Fix default mysqli error reporting mode for PHP 8.1+ [#5582]Add --context flag [#5581]Make cache size and expiry configurable via environment variables [#5576]Updated default branch for roave\/security-advisories [#5575]Fix wrong variable name used in argument parsing [#5564]Fix regression that broke extending existing commands [#5563]Add a SECURITY.md file [#5562]Update credits [#5556]Pass in arguments to before_run_command hook [#5554]Change \"Fake Site\" site name to \"WordPress\" in core multisite-install command [#5552]Add missing docblocks [#5551]Make logger accessible and add colorization control to Quiet logger [#5549]Fix OOM issues when exporting to STDOUT [#5546]Allow WP_DEBUG_LOG to override the debug.log location [#5511]\n\n\n\nwp-cli\/handbook\n\n\n\nDocument the exec global parameter [#397]Provide example of optional positional arguments [#390]Added create table statement. [#389]\n\n\n\nwp-cli\/wp-cli.github.com\n\n\n\nUpdate\u00a0zh-cn\u00a0translation file [#422]Update build status badge [#416]Fix quick links anchors in German translation [#415]\n\n\n\nwp-cli\/cache-command\n\n\n\nAdd PHP 8.1 support [#72]\n\n\n\nwp-cli\/checksum-command\n\n\n\nAdd PHP 8.1 support [#89]\n\n\n\nwp-cli\/config-command\n\n\n\nAdd PHP 8.1 support [#135]Document special EOF anchor [#136]Add --config-file argument to process custom configuration files [#104]Add dotenv format option to config get command [#102]Escape values to avoid breaking them within single quotes [#95]Update the wp-config.php template [#139]\n\n\n\nwp-cli\/core-command\n\n\n\nUpdate download_package() function signature [#197]Support case-insensitive filesystems when pruning files after update [#196]Do not exit on error but pass on error [#193]\n\n\n\nwp-cli\/cron-command\n\n\n\nAdd PHP 8.1 support [#77]Adapt feature test to use HTTPS with example.com [#78]Promote a non-200 response from the cron spawn test to an error [#66]\n\n\n\nwp-cli\/db-command\n\n\n\nRefactor --defaults flag handling [#205]Adapt mysqldump message string to check for in tests [#201]Set 'utf8mb4' when exporting without '--default-character-set' option [#199]Add decimal numbers to wp db size [#163]Add --defaults flag to remaining commands [#206]Add PHP 8.1 support [#214]Fix table existence check in db columns [#210]Adapt feature test to use HTTPS with example.com [#216]Fix \"WP_DEBUG already defined\" test failure [#220]\n\n\n\nwp-cli\/embed-command\n\n\n\nAdd PHP 8.1 support [#65]\n\n\n\nwp-cli\/entity-command\n\n\n\nSupport PHP 8.1 [#331]Update example input to reflect example output [#326]Document default post type filtering for post list command [#321]Correct the home URL when listing sites [#312]Adapt http => https URLs [#339]Add application password commands [#330]Better error message when trying to delete super admin [#304]Recalculate menu order on insertion or deletion [#275]Add strict\/no-strict mode for taxonomy list [#256]\n\n\n\nwp-cli\/eval-command\n\n\n\nAdd PHP 8.1 support [#60]\n\n\n\nwp-cli\/export-command\n\n\n\nEnsure post attachment meta is exported correctly [#89]Only add needed user when filtering by --author [#88]Adapt tests [#87]Fix category, tag and term names missing in export [#86]Add the_title_export filter and cdata for item title to export [#77]Add PHP 8.1 support [#93]Adapt feature test to use HTTPS with example.com [#94]\n\n\n\nwp-cli\/extension-command\n\n\n\nFix test issues [#293]Fix incorrect examples [#290]Check for WP_Error on bulk updates [#294]Add support for PHP 8.1 [#306]Replace one-time-login with a sample plugin in the tests [#302]Add --skip-update-check flag to plugin list and theme list commands [#300]Ensure bundled themes don't interfere with update tests [#311]\n\n\n\nwp-cli\/i18n-command\n\n\n\nFix tests [#268]Add subtract-and-merge flag [#267]Use more inclusive language in argument description [#266]Add new --update-mo-files flag to make-json [#265]Add\u00a0new --location\u00a0flag to omit source code references [#264]Add ext-mbstring to list of suggested dependencies [#263]Prevent adding JS comments to multiple strings [#261]Fix string extraction when using template literals [#260]Update version constraint for mck89\/peast [#259]Fix plural extraction in JS [#258]Remove now unneeded workaround in JS scanner [#256]Extract strings for translation from theme.json [#254]Fix string extraction from block.json [#253]Add support to IterableCodeExtractor for symlinks. [#249]Add PHP 8.1 support [#293]Add new field to translate in theme.json [#292]Fix JS string extraction with unsupported argument type [#296]\n\n\n\nwp-cli\/import-command\n\n\n\nAdd PHP 8.1 support [#71]\n\n\n\nwp-cli\/language-command\n\n\n\nAdd PHP 8.1 support [#111]\n\n\n\nwp-cli\/maintenance-mode-command\n\n\n\nAdd PHP 8.1 support [#20]\n\n\n\nwp-cli\/media-command\n\n\n\nAdd PHP 8.1 support [#153]Add missing intermediate_image_sizes_advanced filter argument for WP 5.3+ [#150]\n\n\n\nwp-cli\/package-command\n\n\n\nOnly allow secure Composer versions [#144]Support PHP 8.1 [#143]Fetch default branch for GitHub packages [#146]Support common default development branches [#148]\n\n\n\nwp-cli\/php-cli-tools\n\n\n\nUpdate TTY checks [#145]\n\n\n\nwp-cli\/rewrite-command\n\n\n\nAdd PHP 8.1 support [#54]\n\n\n\nwp-cli\/role-command\n\n\n\nAdd PHP 8.1 support [#49]\n\n\n\nwp-cli\/scaffold-command\n\n\n\nFix testing on WordPress trunk version [#297]Ignore .github directory in .distignore [#295]Allow for diverging PHPUnit version specifics in tests [#304]Add PHP 8.1 support [#301]\n\n\n\nwp-cli\/search-replace-command\n\n\n\nFix offset handling when doing chunked replacements [#162]Add strict comparisons for color tests [#163]Add PHP 8.1 support [#166]Adapt feature test to use HTTPS with example.com [#167]\n\n\n\nwp-cli\/server-command\n\n\n\nAdd PHP 8.1 support [#72]\n\n\n\nwp-cli\/shell-command\n\n\n\nAdd PHP 8.1 support [#58]\n\n\n\nwp-cli\/super-admin-command\n\n\n\nAdd PHP 8.1 support [#48]Trigger core actions when granting or revoking super-admin permissions [#20]\n\n\n\nwp-cli\/widget-command\n\n\n\nAppend new widgets to the bottom of a sidebar [#52]Decouple tests from default theme widgets [#51]Add PHP 8.1 support [#53]\n\n\n\nwp-cli\/wp-config-transformer\n\n\n\nAdapt tests for polyfilled test case [#36]\n\n\n\nContributors\n\n\n\n@bgturner, @BhargavBhandari90, @CodeProKid, @connerbw, @dd32, @dh-programacion, @dlind1, @drzraf, @felixarntz, @gedex, @gitlost, @grappler, @greatislander, @herregroen, @imadphp, @janw-me, @jenkoian, @jmdodd, @johnbillion, @johnjago, @jrfnl, @kapilpaul, @KarlAustin, @l3ku, @localheinz, @matzeeable, @mbuxsoomro, @michaelzangl, @mircobabini, @mn7zDev, @mrkaluzny, @nickdaugherty, @Nikschavan, @oandregal, @ocean90, @pbiron, @pdaalder, @petruchek, @pmbaldha, @ponsfrilus, @ryotsun, @saz, @schlessera, @seatonjiang, @siliconforks, @skeltoac, @stefanpejcic, @stodorovic, @swissspidy, @tammelin, @thomasplevy, @Tug, @tyrann0us, @UVLabs, @wojsmol, @wpamitkumar, @yousan\n\n\n#release, #v2-6-0","contentFiltered":"A new release of WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http:\/\/wp-cli.org\/ https:\/\/make.wordpress.org\/cli\/ is available as of today: WP-CLI v2.6.0. For this release, we had 57 contributors collaborate to get 311 pull requests merged. \ud83c\udf89\n\n\n\nThe pandemic is still controlling our daily lives, and as a side-effect we still notice a significant reduction in contributors to WP-CLI, probably due to the lack of in-person contributor days.\n\n\n\nAs always, big thanks to the WP-CLI sponsors that make the continued maintenance possible \u2013 even with a reduced number of contributors. \u2764\ufe0f\n\n\n\nApart from the numerous bug fixes that were included in this release, we also managed to snuggle in a few new features that add to the power or convenience of your CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. experience, so I want to spend a few paragraphs going over some of the noteworthy changes. As always, you can also skip directly to the\u00a0detailed changelog\u00a0if you prefer.\n\n\n\nPHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http:\/\/php.net\/manual\/en\/intro-whatis.php. 8.1 Support\n\n\n\nWP-CLI now officially supports PHP 8.1. All commands are being extensively tested against PHP 8 and the actual development is currently being done on PHP 8.1 as well.\n\n\n\nHowever, keep in mind that PHP 8.1 support is not fully there for WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and especially for a large part of plugins and themes. Due to the nature of the changes that PHP 8.1 brings about, it is very easy to break perfectly compatible WordPress Core or WP-CLI via the actions\/filters system. Keep this in mind when trying to diagnose PHP 8.1 compatibility issues and trying to deduce where the erroneous code is to be found.\n\n\n\nTabular data showing a timeline with supported PHP releases, with only 8.0 and 8.1 currently in active support.For those of you who are not closely following the PHP release cycles, please be aware that only PHP 8.0 and 8.1 are currently actively supported versions. WP-CLI sticks with the WordPress Core PHP support policy (+ 1 year), which means we\u2019re still spending huge amounts of efforts to keep everything running all the way down to PHP 5.6 at the moment.\n\n\n\nIf you want to help the maintainers in their work, please ensure that all your sites run on the latest PHP versions, and nag your hosting providers to move everything over to the latest and greatest. WordPress will only bump the minimum version when the number of active sites on PHP 5.6 has dropped to an insignificant amount.\n\n\n\nNew commands for managing application passwords\n\n\n\nThe following commands were added to allow CLI users to create and manage WordPress application passwords:\n\n\n\nwp user application-password listwp user application-password getwp user application-password existswp user application-password updatewp user application-password record-usagewp user application-password createwp user application-password deleteWP-CLI examples of creating a new application password and then listing all existing application passwords for that same user.Although you could technically already work with application passwords by directly controlling the WordPress user-metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. table, this now provides a clean APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. that abstracts away the technical implementation. See the Application Passwords: Integration Guide to find out more about how to use them.\n\n\n\nNew global flag:\u00a0--context\n\n\n\nA new global flag --context=\u00a0was added which allows users to select the WordPress context in which WP-CLI is supposed to execute its command(s).\n\n\n\nOne of the main goals is to allow WP-CLI to run updates on premium plugins and themes without requiring any special setup. From our initial testing, this allows a large range of popular premium extensions to just work\u2122\ufe0f with WP-CLI in terms of their update procedures.\n\n\n\nPossible values for this flag with this initial release:\n\n\n\ncli: The context which has been the default before introduction of this flag. This is something in-between a frontend and an admin request, to get around some of the quirks of WordPress when running on the console.admin: A context that simulates running a command as if it would be executed in the administration backend. This is meant to be used to get around issues with plugins that limit functionality behind an\u00a0is_admin()\u00a0check.auto: Switches between\u00a0cli\u00a0and\u00a0admin\u00a0depending on which command is being used. For this initial release, all\u00a0wp plugin *\u00a0and\u00a0wp theme *\u00a0commands will use\u00a0admin, while all other commands will use\u00a0cli.frontend: [WIP] This does nothing yet.Roadmap: By default, the\u00a0--context\u00a0flag will be set to\u00a0cli\u00a0with this initial release (v2.6.0). With WP-CLI v2.7.0, the default will change to\u00a0auto. This gradual deployment will allow hosters and site owners to run tests on v2.6.0 by manually setting the context before the default behavior is changed.\n\n\n\nIf you want to use the future default of --context=auto right away in your present operations, you can do so by adding the necessary context: auto line to your global wp-cli.yml configuration file. Feel free to check the documentation on WP-CLI configuration files if this is new to you.\n\n\n\nWe also have a new hook to support this new global flag: before_registering_contexts.\u00a0This hook behaves like a filterFilter Filters are one of the two types of Hooks https:\/\/codex.wordpress.org\/Plugin_API\/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. with one argument:\u00a0array $contexts. When hooking into this hook, the callback should return (a potentially modified)\u00a0$contexts\u00a0value. This can be used to remove or override bundled contexts or add new ones.\n\n\n\nTo make this work, the hook functionality in WP-CLI (provided via\u00a0WP_CLI::do_hook()) was modified to return the first argument if arguments were provided.\n\n\n\nThanks to\u00a0Cloudways\u00a0for the special support and testing of this new flag with the goal of solving the \u201cpremium updates problem\u201d for everyone.\n\n\n\nConfigurable WP-CLI cache settings\n\n\n\nThe WP-CLI file cache can now be configured via the following environment variables:\n\n\n\nWP_CLI_CACHE_DIR\u00a0\u2013 Directory in which to store the cached files. Default value:\u00a0\"$home\/.wp-cli\/cache\".WP_CLI_CACHE_EXPIRY\u00a0\u2013 Time after which cached files are automatically purged, in seconds. Default value:\u00a015552000\u00a0(6 months).WP_CLI_CACHE_MAX_SIZE\u00a0\u2013 Total size of the file cache after which older files are purged, in bytes. Default value:\u00a0314572800\u00a0(300 MB).This not only allows you to fine-tune the WP-CLI cache behavior for the best balance between available storage and bandwidth usage, it could also be used to share cache storage between installations\/users (beware the security implications, though!).\n\n\n\nUse custom names\/locations for the wp-config.php file\n\n\n\nThe different config * commands now accept a new flag --config-file= that allow you point the different manipulations towards a custom location, that might not even fully adhere to conventions for the WordPress wp-config.php file.\n\n\n\nThis allows you for example to use the config set command for a configuration file outside of the WordPress document root (and parent folder).\n\n\n\nKeep in mind that you\u2019re on your own when it comes to making WordPress understand the structure and bootstrap correctly!\n\n\n\nGenerate a dotenv file from your existing wp-config.php file\n\n\n\nFor all the 12-factor app fans out there, WP-CLI has learnt a new format for its config list command: --format=dotenv. This will take the existing configuration key\/value pairs in your wp-config.php file and render them in a format that you can use in a .env file.\n\n\n\nWP-CLI example of list the contents of the wp-config.php file into a file in dotenv format and then showing the result.Combine with the previously mentioned --config-file to extract the dotenv file from an arbitrary location, even without a WordPress installation present.\n\n\n\nAllow pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party\/theme enumeration without forcing an update check\n\n\n\nPreviously, when you run plugin list or theme list, WP-CLI would automatically run a check in the background to see if updates are available. This is slow and expensive to do, and might not always be what is needed, especially in scripting scenarios.\n\n\n\nThis automatic check for updates can now be disabled for these two commands with the --skip-update-check flag. This can drastically speed up some scripts and make them more reliable.\n\n\n\nNew flag --strict for adapting the filtering of taxonomies by post type\n\n\n\nWhen retrieving taxonomies for a given post type, the old default behavior of WordPress (through the use of get_taxonomies()) is to only show those taxonomies that have as a sole associated post type the requested one. Taxonomies that have multiple associated post types, including the requested one, are not returned.\n\n\n\nWordPress had added a newer mechanism via get_object_taxonomies() that would return all taxonomies that are in some way associated with the requested post type, even if other post types are associated as well.\n\n\n\nWP-CLI now has a new --strict flag for the taxonomy list command that defines whether the strict filtering (the old default) should be used, or the more sensible inclusive approach should be used via --no-strict (or --strict=false).\n\n\n\nWe\u2019ve opted to make this new, more sensible approach (i.e. --no-strict) the new default, so be mindful of that if you\u2019re using taxonomy list in a script somewhere.\n\n\n\nAnother round of improvements to the i18n * commands\n\n\n\nAs with all of the recent releases, the i18n * commands have received yet another round of overall improvements to keep in sync with the localisation requirements of WordPress Core.\n\n\n\nFrom new flags like --subtract-and-merge, --update-mo-files & --location and multiple improvements to the way JavascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user\u2019s browser. https:\/\/www.javascript.com\/. syntax is parsed all the way up to the support for the new theme.json format, all your localization needs should be accounted for (at least for now).\n\n\n\nMake your to check out the detailed logs to find out more and play around with the new functionality when you get the chance!\n\n\n\nWith super admin permissions come super admin consequences!\n\n\n\nWP-CLI now mirrors the behavior of WordPress core and triggers various hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. when you grant or revoke the super admin status to users.\n\n\n\nThe following actions are being triggered now but the super-admin add & super-admin remove commands:\n\n\n\ngrant_super_admin\u00a0(before changes,\u00a0always\u00a0executed)granted_super_admin\u00a0(after changes, executed only on success)revoke_super_admin\u00a0(before changes,\u00a0always\u00a0executed)revoked_super_admin\u00a0(after changes, executed only on success)Changes to the default branches\n\n\n\nIn order to make the language used in the code and documentation of WP-CLI more inclusive, work has started to change the name of default branch across all repositories. From now on, the default branch name across the WP-CLI GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the \u2018pull request\u2019 where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https:\/\/github.com\/ organization is main.\n\n\n\nThis change is currently a work in progress, as it unfortunately causes open pull requests to be automatically closed and often become unsalvageable. The current progress of this effort can be monitored here: wp-cli\/wp-cli#5598.\n\n\n\nKeep this in mind when you want to check out the latest development state of a repository or contribute by creating a PR!\n\n\n\nDetailed change log\n\n\n\nTo avoid too much noise in the list above, the following types of pull requests have been omitted:\n\n\n\nPRs that only bumped dependencies to their latest version.PRs that only fixed a typo in the documentation.PRs that add an allow-plugins rule to Composerwp-cli\/wp-cli-bundle\n\n\n\nDisable deployments on forks [#389]DeployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. from main branch [#385]Revert usage of Mustache fork [#373]Use latest branch for Roave security advisories [#357]Add DEB build workflow [#345]Add RPM build workflow [#344]Switch to dev-master for wp-cli framework [#333]wp-cli\/wp-cli\n\n\n\nAdapt VERSION from 2.5.1-alpha to 2.6.0-alpha [#5605]Fix Composer stack tests [#5599]Detect and ignore BOMs [#5597]Check github.repository_owner in automerge workflow [#5591]Revert addition of the Mustache PHP 8.1 workaround and update dependency [#5590]Use Mustache work-around for PHP 8.1 compat [#5588]Use fork on schlessera for Mustache PHP 8.1 fix [#5587]Re-add subcommands on all composite commands that are overwritten [#5584]Fix default mysqli error reporting mode for PHP 8.1+ [#5582]Add --context flag [#5581]Make cache size and expiry configurable via environment variables [#5576]Updated default branch for roave\/security-advisories [#5575]Fix wrong variable name used in argument parsing [#5564]Fix regression that broke extending existing commands [#5563]Add a SECURITY.md file [#5562]Update credits [#5556]Pass in arguments to before_run_command hook [#5554]Change \u201cFake Site\u201d site name to \u201cWordPress\u201d in core multisite-install command [#5552]Add missing docblocks [#5551]Make logger accessible and add colorization control to Quiet logger [#5549]Fix OOM issues when exporting to STDOUT [#5546]Allow WP_DEBUG_LOG to override the debug.log location [#5511]wp-cli\/handbook\n\n\n\nDocument the exec global parameter [#397]Provide example of optional positional arguments [#390]Added create table statement. [#389]wp-cli\/wp-cli.github.com\n\n\n\nUpdate\u00a0zh-cn\u00a0translation file [#422]Update build status badge [#416]Fix quick links anchors in German translation [#415]wp-cli\/cache-command\n\n\n\nAdd PHP 8.1 support [#72]wp-cli\/checksum-command\n\n\n\nAdd PHP 8.1 support [#89]wp-cli\/config-command\n\n\n\nAdd PHP 8.1 support [#135]Document special EOF anchor [#136]Add --config-file argument to process custom configuration files [#104]Add dotenv format option to config get command [#102]Escape values to avoid breaking them within single quotes [#95]Update the wp-config.php template [#139]wp-cli\/core-command\n\n\n\nUpdate download_package() function signature [#197]Support case-insensitive filesystems when pruning files after update [#196]Do not exit on error but pass on error [#193]wp-cli\/cron-command\n\n\n\nAdd PHP 8.1 support [#77]Adapt feature test to use HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. with example.com [#78]Promote a non-200 response from the cron spawn test to an error [#66]wp-cli\/db-command\n\n\n\nRefactor --defaults flag handling [#205]Adapt mysqldump message string to check for in tests [#201]Set 'utf8mb4' when exporting without '--default-character-set' option [#199]Add decimal numbers to wp db size [#163]Add --defaults flag to remaining commands [#206]Add PHP 8.1 support [#214]Fix table existence check in db columns [#210]Adapt feature test to use HTTPS with example.com [#216]Fix \u201cWP_DEBUG already defined\u201d test failure [#220]wp-cli\/embed-command\n\n\n\nAdd PHP 8.1 support [#65]wp-cli\/entity-command\n\n\n\nSupport PHP 8.1 [#331]Update example input to reflect example output [#326]Document default post type filtering for post list command [#321]Correct the home URLURL A specific web address of a website or web page on the Internet, such as a website\u2019s URL http:\/\/www.wordpress.org when listing sites [#312]Adapt http => https URLs [#339]Add application password commands [#330]Better error message when trying to delete super admin [#304]Recalculate menu order on insertion or deletion [#275]Add strict\/no-strict mode for taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https:\/\/codex.wordpress.org\/Taxonomies#Default_Taxonomies. list [#256]wp-cli\/eval-command\n\n\n\nAdd PHP 8.1 support [#60]wp-cli\/export-command\n\n\n\nEnsure post attachment meta is exported correctly [#89]Only add needed user when filtering by --author [#88]Adapt tests [#87]Fix categoryCategory The 'category' taxonomy lets you group posts \/ content together that share a common bond. Categories are pre-defined and broad ranging., tag and term names missing in export [#86]Add the_title_export filter and cdata for item title to export [#77]Add PHP 8.1 support [#93]Adapt feature test to use HTTPS with example.com [#94]wp-cli\/extension-command\n\n\n\nFix test issues [#293]Fix incorrect examples [#290]Check for WP_Error on bulk updates [#294]Add support for PHP 8.1 [#306]Replace one-time-login with a sample plugin in the tests [#302]Add --skip-update-check flag to plugin list and theme list commands [#300]Ensure bundled themes don\u2019t interfere with update tests [#311]wp-cli\/i18n-command\n\n\n\nFix tests [#268]Add subtract-and-merge flag [#267]Use more inclusive language in argument description [#266]Add new --update-mo-files flag to make-json [#265]Add\u00a0new --location\u00a0flag to omit source code references [#264]Add ext-mbstring to list of suggested dependencies [#263]Prevent adding JS comments to multiple strings [#261]Fix string extraction when using template literals [#260]Update version constraint for mck89\/peast [#259]Fix plural extraction in JS [#258]Remove now unneeded workaround in JS scanner [#256]Extract strings for translation from theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. [#254]Fix string extraction from block.json [#253]Add support to IterableCodeExtractor for symlinks. [#249]Add PHP 8.1 support [#293]Add new field to translate in theme.json [#292]Fix JS string extraction with unsupported argument type [#296]wp-cli\/import-command\n\n\n\nAdd PHP 8.1 support [#71]wp-cli\/language-command\n\n\n\nAdd PHP 8.1 support [#111]wp-cli\/maintenance-mode-command\n\n\n\nAdd PHP 8.1 support [#20]wp-cli\/media-command\n\n\n\nAdd PHP 8.1 support [#153]Add missing intermediate_image_sizes_advanced filter argument for WP 5.3+ [#150]wp-cli\/package-command\n\n\n\nOnly allow secure Composer versions [#144]Support PHP 8.1 [#143]Fetch default branch for GitHub packages [#146]Support common default development branches [#148]wp-cli\/php-cli-tools\n\n\n\nUpdate TTY checks [#145]wp-cli\/rewrite-command\n\n\n\nAdd PHP 8.1 support [#54]wp-cli\/role-command\n\n\n\nAdd PHP 8.1 support [#49]wp-cli\/scaffold-command\n\n\n\nFix testing on WordPress trunk version [#297]Ignore .github directory in .distignore [#295]Allow for diverging PHPUnit version specifics in tests [#304]Add PHP 8.1 support [#301]wp-cli\/search-replace-command\n\n\n\nFix offset handling when doing chunked replacements [#162]Add strict comparisons for color tests [#163]Add PHP 8.1 support [#166]Adapt feature test to use HTTPS with example.com [#167]wp-cli\/server-command\n\n\n\nAdd PHP 8.1 support [#72]wp-cli\/shell-command\n\n\n\nAdd PHP 8.1 support [#58]wp-cli\/super-admin-command\n\n\n\nAdd PHP 8.1 support [#48]Trigger core actions when granting or revoking super-admin permissions [#20]wp-cli\/widget-command\n\n\n\nAppend new widgets to the bottom of a sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. [#52]Decouple tests from default theme widgets [#51]Add PHP 8.1 support [#53]wp-cli\/wp-config-transformer\n\n\n\nAdapt tests for polyfilled test case [#36]Contributors\n\n\n\n@bgturner, @BhargavBhandari90, @CodeProKid, @connerbw, @dd32, @dh-programacion, @dlind1, @drzraf, @felixarntz, @gedex, @gitlost, @grappler, @greatislander, @herregroen, @imadphp, @janw-me, @jenkoian, @jmdodd, @johnbillion, @johnjago, @jrfnl, @kapilpaul, @KarlAustin, @l3ku, @localheinz, @matzeeable, @mbuxsoomro, @michaelzangl, @mircobabini, @mn7zDev, @mrkaluzny, @nickdaugherty, @Nikschavan, @oandregal, @ocean90, @pbiron, @pdaalder, @petruchek, @pmbaldha, @ponsfrilus, @ryotsun, @saz, @schlessera, @seatonjiang, @siliconforks, @skeltoac, @stefanpejcic, @stodorovic, @swissspidy, @tammelin, @thomasplevy, @Tug, @tyrann0us, @UVLabs, @wojsmol, @wpamitkumar, @yousan\n#release, #v2-6-0Login to Reply","permalink":"https:\/\/make.wordpress.org\/cli\/2022\/01\/26\/wp-cli-v2-6-0-release-notes\/","unixtime":1643156189,"unixtimeModified":1643156195,"entryHeaderMeta":"","linkPages":"","footerEntryMeta":"","tagsRaw":"release, v2.6.0","tagsArray":["label":"release","count":13,"link":"https:\/\/make.wordpress.org\/cli\/tag\/release\/","label":"v2.6.0","count":1,"link":"https:\/\/make.wordpress.org\/cli\/tag\/v2-6-0\/"],"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2022%2F01%2F26%2Fwp-cli-v2-6-0-release-notes%2F&locale=en_US","hasPrevPost":false,"prevPostTitle":"","prevPostURL":"","hasNextPost":false,"nextPostTitle":"","nextPostURL":"","commentsOpen":true,"is_xpost":false,"editURL":null,"postActions":"Post ActionsLogin to ReplyScrollShortlink","comments":["type":"comment","id":"196","postID":"3505","postTitleRaw":"WP-CLI v2.6.0 Release Notes","cssClasses":"comment byuser comment-author-pmbaldha even thread-even depth-1","parentID":"0","contentRaw":"I am proud to be a contributor to WP-CLI v2.6.0! :trophy:\ufe0f :slightly_smiling_face:","contentFiltered":"I am proud to be a contributor to WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http:\/\/wp-cli.org\/ https:\/\/make.wordpress.org\/cli\/ v2.6.0! :trophy:\ufe0f :slightly_smiling_face:\n","permalink":"https:\/\/make.wordpress.org\/cli\/2022\/01\/26\/wp-cli-v2-6-0-release-notes\/#comment-196","unixtime":1643180454,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2022%2F01%2F26%2Fwp-cli-v2-6-0-release-notes%2F%23comment-196&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"Login to Reply","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":"1643180456","hasChildren":false,"userLogin":"pmbaldha","userNicename":"pmbaldha","type":"comment","id":"197","postID":"3505","postTitleRaw":"WP-CLI v2.6.0 Release Notes","cssClasses":"comment byuser comment-author-verygoode odd alt thread-odd thread-alt depth-1","parentID":"0","contentRaw":"Thanks, ya'll!","contentFiltered":"Thanks, ya\u2019ll!\n","permalink":"https:\/\/make.wordpress.org\/cli\/2022\/01\/26\/wp-cli-v2-6-0-release-notes\/#comment-197","unixtime":1643311620,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2022%2F01%2F26%2Fwp-cli-v2-6-0-release-notes%2F%23comment-197&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"Login to Reply","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":"1643311622","hasChildren":false,"userLogin":"verygoode","userNicename":"verygoode","type":"comment","id":"199","postID":"3505","postTitleRaw":"WP-CLI v2.6.0 Release Notes","cssClasses":"comment byuser comment-author-amirhosein441 even thread-even depth-1","parentID":"0","contentRaw":"Hello dear @schlessera.\nThanks for your efforts on WP-CLI.\nI used PHP 8.1.10 (cli)\nOS : WIN10\n\nwhen i want to use WP CLI for create config, with this command : \n[code] wp config create --dbname=wp --dbuser=root [\/code]\n\nI get this error :\n[code]'\"mysql --no-defaults --execute=\"' is not recognized as an internal or external command,\noperable program or batch file.[\/code]\n\nbut when i downgrade php to 7.4.30 (cli), everything work perfect.\n\ni think WP-CLI no compatibility full with php 8.1.\n\nis this issue solved soon ?\nthanks for your time","contentFiltered":"Hello dear @schlessera.\nThanks for your efforts on WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http:\/\/wp-cli.org\/ https:\/\/make.wordpress.org\/cli\/.\nI used PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http:\/\/php.net\/manual\/en\/intro-whatis.php. 8.1.10 (cli)\nOS : WIN10\nwhen i want to use WP CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. for create config, with this command :\n[code] wp config create \u2013dbname=wp \u2013dbuser=root [\/code]\nI get this error :\n[code]'\u201dmysqlMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https:\/\/www.mysql.com\/. \u2013no-defaults \u2013execute=\u201d\u2018 is not recognized as an internal or external command,\noperable program or batch file.[\/code]\nbut when i downgrade php to 7.4.30 (cli), everything work perfect.\ni think WP-CLI no compatibility full with php 8.1.\nis this issue solved soon ?\nthanks for your time\n","permalink":"https:\/\/make.wordpress.org\/cli\/2022\/01\/26\/wp-cli-v2-6-0-release-notes\/#comment-199","unixtime":1664893037,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcli%2F2022%2F01%2F26%2Fwp-cli-v2-6-0-release-notes%2F%23comment-199&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"Login to Reply","commentTrashedActions":"Untrash","mentions":["schlessera"],"mentionContext":"","commentCreated":"1664893037","hasChildren":false,"userLogin":"amirhosein441","userNicename":"amirhosein441"],"postFormat":"standard","postMeta":"isSticky":false,"postTerms":"category":["label":"Releases","count":19,"link":"https:\/\/make.wordpress.org\/cli\/category\/releases\/"],"post_tag":["label":"release","count":13,"link":"https:\/\/make.wordpress.org\/cli\/tag\/release\/","label":"v2.6.0","count":1,"link":"https:\/\/make.wordpress.org\/cli\/tag\/v2-6-0\/"],"post_format":[],"pluginData":[],"isPage":false,"mentions":[],"mentionContext":"","isTrashed":false,"userLogin":"schlessera","userNicename":"schlessera"}]Josepha10:56 pm on May 25, 2021Tags: make.wordpress.org/updates ( 10 ), p2-xpost ( 18 ) X-post: Experiment: A Public Channel for All Team RepsX-comment from +make.wordpress.org/updates: Comment on Experiment: A Public Channel for All Team Reps 2ff7e9595c
Comments