Skip to content

First pass at constant for forcing enable/disable of real time collab#11310

Open
aaronjorbin wants to merge 1 commit intoWordPress:trunkfrom
aaronjorbin:trac/64904
Open

First pass at constant for forcing enable/disable of real time collab#11310
aaronjorbin wants to merge 1 commit intoWordPress:trunkfrom
aaronjorbin:trac/64904

Conversation

@aaronjorbin
Copy link
Member

This is the start at adding a constant for forcing enable/disable for real time collab. Currently only includes UI changes

Trac ticket: https://core.trac.wordpress.org/ticket/64904

Use of AI Tools

AI assistance: Yes
Tool(s): Claude
Model(s): GPT-5.1
Used for: Initial code skeleton and test suggestions; final implementation and tests were reviewed and edited by me.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions
Copy link

github-actions bot commented Mar 19, 2026

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props jorbin, alecgeatches.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

<input name="wp_collaboration_enabled" type="checkbox" id="wp_collaboration_enabled" value="1" <?php checked( '1', (bool) get_option( 'wp_collaboration_enabled' ) ); ?> />
<?php _e( 'Enable real-time collaboration' ); ?>
</label>
<?php if ( defined ( 'FORCE_COLLABORATION_ENABLED' ) ) : ?>
Copy link

@alecgeatches alecgeatches Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about inverting this to WP_DISABLE_COLLABORATION? Just so the purpose is only disabling collaboration, but if it's WP_DISABLE_COLLABORATION === false it's still up to the site administrator.

I think for a host disabling collaboration could make sense, but define( 'FORCE_COLLABORATION_ENABLED', true ); is a bit odd to force-enable it, especially if there are "feature preview" issues.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noting that based on feedback it's been changed to WP_ALLOW_COLLABORATION and allows for the feature to be disallowed on an environment level.

@alecgeatches
Copy link

I added a modified version of this using WP_DISABLE_COLLABORATION instead as a only-turn-off constant in #11311.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants