Skip to content
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

Social: Add connection management to the admin page #37120

Merged
merged 25 commits into from
May 6, 2024

Conversation

gmjuhasz
Copy link
Contributor

@gmjuhasz gmjuhasz commented Apr 29, 2024

Fixes https://github.com/Automattic/jetpack-reach/issues/294

Proposed changes:

  • Updated the backend so the connections return as an array, also populated the response with the needed attributes b6d9c52
  • Updated the store and frontend handlers to be able to handle the modified structure b47e440
  • Added the new ConnectionManagement component ece8d5f
  • Updated the get_profile_link function in base so it handles our new services too 312e2e4

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

https://github.com/Automattic/jetpack-reach/issues/294

Does this pull request change what data or activity we track or use?

No.

Testing instructions:

You can switch between the new and old UI with define( 'JETPACK_SOCIAL_USE_ADMIN_UI_V1', true ); in your wp-config file

  • Go to the social admin page
    • You should see the connection list under the main toggle
    • All connection should have their name retrieved after the test endpoint finishes
    • All connection should have the correct profile picture, or the default service icon if N/A
    • Hovering over the name should get a hyperlink to the service profile page. Not working for LinkedIn
    • Goto Jetpack Settings > Sharing
    • Confirm that the Connections list is displayed
  • Check that the connection toggles in the editor work as before

CleanShot 2024-04-29 at 17 39 05 png

Jetpack settings page
Screenshot 2024-05-02 at 2 50 24 PM

Social settings page
Screenshot 2024-05-02 at 2 50 49 PM

Copy link
Contributor

github-actions bot commented Apr 29, 2024

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.


Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.


Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

  • WordPress.com Simple releases happen daily.
  • WoA releases happen weekly.
  • Releases to self-hosted sites happen monthly. The next release is scheduled for May 7, 2024 (scheduled code freeze on May 6, 2024).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.


Social plugin:

  • Next scheduled release: June 4, 2024.
  • Scheduled code freeze: May 27, 2024.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Copy link
Contributor

github-actions bot commented Apr 29, 2024

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the add/social-connection-management-component branch.

  • To test on Simple, run the following command on your sandbox:

    bin/jetpack-downloader test jetpack add/social-connection-management-component
    

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@manzoorwanijk
Copy link
Member

@gmjuhasz I resolved the conflicts caused by my PR #37134

@gmjuhasz gmjuhasz marked this pull request as ready for review May 2, 2024 07:58
@gmjuhasz gmjuhasz requested a review from manzoorwanijk May 2, 2024 07:58
@github-actions github-actions bot added the [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ label May 2, 2024
@github-actions github-actions bot added the Admin Page React-powered dashboard under the Jetpack menu label May 2, 2024
@gmjuhasz gmjuhasz mentioned this pull request May 3, 2024
3 tasks
const isActive = this.props.getOptionValue( 'publicize' );
// Reload the page if Publicize is enabled.
if ( isActive && ! window.Initial_State.socialInitialState.is_publicize_enabled ) {
window.location.reload();
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems like a reasonable solution for now. We can work on making API calls for the initial state (if we want to) in the coming weeks.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, Sid created a task to work on the backend parts of it - https://github.com/Automattic/jetpack-reach/issues/310

@gmjuhasz gmjuhasz merged commit 8debc85 into trunk May 6, 2024
58 checks passed
@gmjuhasz gmjuhasz deleted the add/social-connection-management-component branch May 6, 2024 07:49
pkuliga pushed a commit that referenced this pull request May 9, 2024
* Prepare backend aggregation

* Update store to use new format

* Add component

* Update get_profile_link method

* changelog

* Revert "Prepare backend aggregation"

This reverts commit b6d9c52.

* Restore 'profile_link' prop

* Use feature flag

* Fixup versions

* Create get_initial_state helper in publicize and use it in Jetpack and Social

* Restore admin page hasConnection logic

* Fix the connection management for Jetpack and Social admin page

* Restore connectionRefreshPath

* Fix stylelints

* Fix the connection-test-results endpoint

* Fix PHP unit tests

* Replace deprecated method in tests

* Fix mocking for PHP 7

* Fix critical error

* No mocking needed now

* Set initial state only if publicize is enabled and setup

* Reload settings page if publicize is enabled

* Use connection package instead of Jetpack class

---------

Co-authored-by: Manzoor Wani <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin Page React-powered dashboard under the Jetpack menu [JS Package] Publicize Components [Package] Publicize [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Plugin] Social Issues about the Jetpack Social plugin RNA [Tests] Includes Tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants