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

Trackback: Force resending trackback/pingback #440

Closed
onli opened this issue Jan 12, 2017 · 3 comments
Closed

Trackback: Force resending trackback/pingback #440

onli opened this issue Jan 12, 2017 · 3 comments

Comments

@onli
Copy link
Member

onli commented Jan 12, 2017

The trackback-plugin offers some options for controlling trackbacks, like disabling sending them altogether or sending them to a specific URL. But it seems it misses a way to say "Resend trackback to this link" or "Resend trackback to all links in entry". Most user will never need it, but for debugging server issues it would be good to have this options.

It is possible that will need a core change to give the plugin the option to resend trackbacks that are already stored in the table serendipity_references.

@garvinhicking
Copy link
Member

You can do that with the plugin by removing all trackback links, saving, pasting in the old trackback links, saving again.

@onli
Copy link
Member Author

onli commented Jan 13, 2017

Good to know, thanks :) But a button to do it directly still would be helpful.

@yellowled yellowled added this to the 2.x.0 milestone Mar 8, 2017
@th-h th-h modified the milestones: Minor, 2.4 Aug 15, 2019
@th-h th-h removed the easy fix label Mar 23, 2020
onli added a commit to s9y/additional_plugins that referenced this issue May 28, 2020
See s9y/Serendipity#440. Relies on code added to the core during 2.4.0-alpha2
@onli
Copy link
Member Author

onli commented May 28, 2020

This is basically solved now. I added code to the core to skip the check whether the trackbacks are already sent, and the trackbacks-plugin now has a checkbox to enable that skip. But because of the core change I did not add the new version to spartacus, but to its own branch. To be merged after the next release. PR is in s9y/additional_plugins#116, so I think we don't need this issue anymore.

@onli onli closed this as completed May 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants