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

Redirecting despite settings #878

Closed
chrisaldrich opened this Issue Dec 25, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@chrisaldrich
Contributor

chrisaldrich commented Dec 25, 2016

From Manual:
Seconds to redirect user to source: 0 means no redirect. PressForward makes use of canonical URLs. If you would like to redirect your readers automatically to the items aggregated by the feed reader and published to your site, this setting will determine how long to wait before redirecting. The default setting is 0 seconds. The redirect setting can be manually overridden in the Edit Post page by editing the forwarding status in the publish box.

ISSUE:
I've got the "seconds to redirect" set to 1 and regardless of whether I have the per post override set to either "Forward" or "Don't forward" all posts want to forward to the canonical URL. This is disconcerting particularly for the posts that I don't want to forward, and when this happens I'm seeing the page not only forward to itself (and therefore refresh), but it does it every few seconds continually which makes the page terrifically hard to try to read. Is it possible that it's not checking for the "forward/don't forward" toggle somehow?

@AramZS

This comment has been minimized.

Show comment
Hide comment
@AramZS

AramZS Dec 26, 2016

Member

Thank you for this report, I'll look into it ASAP

Member

AramZS commented Dec 26, 2016

Thank you for this report, I'll look into it ASAP

@AramZS

This comment has been minimized.

Show comment
Hide comment
@AramZS

AramZS Jan 2, 2017

Member

This will be resolved in the upcoming patch!

Member

AramZS commented Jan 2, 2017

This will be resolved in the upcoming patch!

@AramZS AramZS added this to the 4.2.x patch milestone Feb 21, 2017

@chrisaldrich

This comment has been minimized.

Show comment
Hide comment
@chrisaldrich

chrisaldrich Feb 22, 2017

Contributor

I tested this quickly with 4.2.2 patch Release Candidate 1 and it does seemed to have fixed the issue.
Thanks AramZS!

Contributor

chrisaldrich commented Feb 22, 2017

I tested this quickly with 4.2.2 patch Release Candidate 1 and it does seemed to have fixed the issue.
Thanks AramZS!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment