Looser coupling of new plugins possible + WordPress plugin #72
Conversation
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
…rking form. Support for multiple wordpress intances.
…th the current time
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR enables plugins to define all of their own views, config, urls, forms etc without changing the core. This is done in a way that does not interfere with existing plugins so there are no BC breaks. Documentation of this functionality and a guide for writing plugins will need to be created but is not part of this PR.
Also included in this PR is a new WordPress plugin that uses a new CLA Toolkit Wordpress plugin (to be installed on the WordPress instance) that enables the integration by providing a read-only api. Documentation about the connection process is in progress.