Daniel Kudwien

@mikmikmik You are saying that your custom post type must only be accessible for registered users. Then this case would be covered by setting appropriate permissions/callbacks - ideally when registering...

Closely related support thread with additional clues/pointers: https://wordpress.org/support/topic/conflict-with-woocommerce-77/ I've also experienced this issue myself. It seems like the PHP warnings are triggered when accessing a REST route that is not...

Nice! 👍 According to https://github.com/10up/action-wordpress-plugin-deploy#excluding-files-from-deployment we should include a `.distignore` file in this PR to exclude at minimum `/node_modules`, possibly more. Do you know of a command or tool to...

Thanks for taking the time to create a PR! Personally, I do not think we should make the functionality even more complex than it already is. There are dedicated plugins...

Duplicate of #3283 ?

@derekderaps As repositories are custom by design in Composer, this seems to be the only viable solution – at least for now. For the time being, this PR resolves https://www.drupal.org/project/drupal/issues/2873160...

2 of 3 builds on PHP 5.6 passed though. Could also have been a hiccup of the build platform. I do not see a button to re-test; any way to...

A completely different question would be whether drupal-composer/drupal-project still needs to support PHP 5.6 in the first place. In my opinion, attempting to support it is a complete waste of...

Note that `SHELL_PIPE=0` does not work for `wp db query`, because the db command is just a proxy to the mysql client. For the db commands, you need to pass...

@neural-oD Then you must be facing a different issue. Maybe your `wp-cli.phar` is wrapped into another shell script that is starting a new environment - losing the env variables that...