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

Unofficial Sharing buttons don't point to the right URL when using "Page Links To" plugin #548

Open
richardmtl opened this issue May 15, 2014 · 6 comments
Labels
[Feature] Sharing Post sharing, sharing buttons Good For Community [Pri] Low [Type] Bug When a feature is broken and / or not performing as intended

Comments

@richardmtl
Copy link
Contributor

As reported in http://wordpress.org/support/topic/jetpack-sharing-module-issue-with-non-official-buttons?replies=6

If I use Jaquith's Page Links To plugin, and I try the unofficial sharing buttons, the sharing action doesn't work; I get a popup window with the Linked-to page, instead of a Facebook sharing dialogue that allows me to share the Linked-to page. However, it works as expected with the Official buttons: the shared URL is the linked-to URL. Also, as noted by the OP, other sharing plugins also work as expected, sharing the linked-to URL.

@jeherve
Copy link
Member

jeherve commented Aug 11, 2014

The Page Links To plugin changes the post permalink value thanks to the post_link filter that is applied to the permalink URL for a post prior to returning the processed url by the function get_permalink(). Jetpack uses get_permalink() to build the sharing pop up, so that popup is broken.

We should be able to fix the problem by adding the correct URL back to the sharing module thanks to the sharing_display_link filter (#), but to do so we need to find a way to get the original post link without using get_permalink().

Looking into this a bit more.

For reference:

@georgestephanis
Copy link
Member

If it's a single page, we could just do an add_query_arg() call without supplying the base URL, so it would just be added to current. The tricky bit is getting the links for archive pages.

Honestly, I'm unsure if it would be wisest to just call it a 'known issue' and 'wontfix' -- or whether we should change the urls we link to, to something like the super-raw /index.php?p=12345&share_to=facebook -- or whatever the specific args may be. Unsure.

@markjaquith -- your thoughts?

@samhotchkiss samhotchkiss modified the milestone: Needs Triage Aug 28, 2015
@jeherve jeherve modified the milestones: Community, Needs Triage Feb 15, 2016
@samhotchkiss samhotchkiss modified the milestones: Community, Not Currently Planned Feb 10, 2017
@stale
Copy link

stale bot commented Mar 12, 2019

This issue has been marked as stale. This happened because:

  • It has been inactive in the past 6 months.
  • It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

@stale stale bot added the [Status] Stale label Mar 12, 2019
@chickenn00dle
Copy link
Contributor

Looks like this issue still persists. Tested with JP 7.8

Adding steps to reproduce just for convenience:

  1. Install Page Links to plugin
  2. Ensure Jetpack is active and connected
  3. Create a Post or Page
  4. Check the Custom Permalink in Post/Page settings and enter any URL
  5. Go to Jetpack > Settings > Sharing > Sharing Buttons
  6. Make sure this option is toggled on and select "Configure Sharing Buttons"
  7. Select a button style other than "Official Buttons"
  8. Make sure the "Front Page, Archive Pages, and Search Results" button is selected for Show like and sharing buttons on
  9. Go to your homepage, and select any of the sharing buttons for the created post. You will get something like this:

Screen Shot 2019-10-24 at 17 48 18

@stale stale bot removed the [Status] Stale label Oct 24, 2019
@stale
Copy link

stale bot commented Apr 23, 2020

This issue has been marked as stale. This happened because:

  • It has been inactive in the past 6 months.
  • It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

@stale stale bot added the [Status] Stale label Apr 23, 2020
@kraftbj kraftbj removed this from the Not Currently Planned milestone Jan 26, 2021
@stale stale bot removed the [Status] Stale label Jan 26, 2021
@github-actions
Copy link
Contributor

This issue has been marked as stale. This happened because:

  • It has been inactive in the past 6 months.
  • It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

leogermani pushed a commit that referenced this issue Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Sharing Post sharing, sharing buttons Good For Community [Pri] Low [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Development

No branches or pull requests

7 participants