-
Notifications
You must be signed in to change notification settings - Fork 846
Explore new set of default modules #11631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: April 2, 2019. |
|
I'm going to leave a raw list of notes here of things I noticed when trying this out, which don't "fit the narrative", or which seems to pose an issue of some sort; Pre Set Up
Set Up
After Set Up
Settings*
|
|
Caution: This PR has changes that must be merged to WordPress.com |
337da31 to
11df884
Compare
|
I've rebased master to include the latest changes I introduced to auto activation as part of the module prioritization project (like widgets, widget-visibility and others) so changed files went from 16 to 11. I think this is good to go in the context of module prioritization. |
eliorivero
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐑
|
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: May 7, 2019. |














This introduces a new set of default modules to play with.
Context p1HpG7-6qm-p2
Testing instructions:
Since these only kick in for new sites, Jurassic.ninja is kinda the only way.
https://jurassic.ninja/create?jetpack-beta&branch=update/default-modules&wp-debug-log
Proposed changelog entry for your changes:
N/A for now