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

Problem with Washington Post website #76

Open
scripting opened this Issue May 6, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@scripting
Copy link
Owner

scripting commented May 6, 2018

I don't know how to report a bug to the Washington Post website, so I'll try posting it here.

  1. I am a paying subscriber.

  2. I am able to access the site properly on my desktop Mac.

  3. I cannot access stories on my iPad.

  4. I was previously logged in on my iPad. Until Friday everything was working as expected. Then I was prompted to subscribe when I clicked on a link from Twitter to read an article. This happened repeatedly. I don't recall if it was just this article or others. (It was about how Trump isn't just a liar, he's a bullshitter, and how that's worse. Never actually got to read the article, but you can see why I was interested. I am obsessed with Trump. Trying to quit.)

  5. I tried logging off and logging back on. I use Amazon to log on. This is where I hit the error. There was a message from Amazon saying how the redirect URL was bad. I assume that's a bad configuration in your OAuth implementation? Just a guess. I would have copied and saved it, but that is ridiculously hard on an iPad. Thanks Apple. 🍎

  6. The problem persists. I am unable to read WP articles on my iPad. Since I do much of my WP reading on the iPad this is a major problem for me.

  7. Needless to say, but I'll say it anyway, if you're going to enforce a paywall, these kinds of errors, where you try to get an actual subscriber to pay is a reminder of how much we hated you before we went ahead and subscribed. And if paying doesn't get rid of the message, the hate is even greater. I can't help it. Fix the problem, and put some support people on Twitter, the same way the airlines do.

@dvodvo

This comment has been minimized.

Copy link

dvodvo commented May 6, 2018

loggin may not be the issue, but some corrupt cookie. try first another browser (your bug report did not indicate the usual necessary info). If that works, try clearing out cookies and cache; maybe it is a browser issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.