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

Premium content block: member can access the content after the first 24 hours #68506

Closed
Robertght opened this issue Oct 3, 2022 · 11 comments
Closed
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Earn [Feature Group] Customer Seller Experience The customer experience when purchasing services or products. [Feature] User Payments & Donations The configuration screens and tools for users to receive payments and donations on their sites. [Platform] Atomic [Platform] Simple Premium Content Controlling specific content for paying site visitors. [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts [Type] Bug When a feature is broken and / or not performing as intended

Comments

@Robertght
Copy link

Robertght commented Oct 3, 2022

Quick summary

We have someone who is unable to access their content in the first approx 24 hours after the subscription is renewed.

The user tried to log out/in and to clear the cache, but this didn't help:

I also tried using an incognito Chrome browser (no cookies), signed in again, and got the same result.
I have tried different browsers (Chrome, Safari)
This behaviour happens on the monthly anniversary of my subscription.

Other info:

I am based in Australia, so perhaps this is a timezone-related issue in your payment code.

cc @Automattic/ajax for further help

bcc @inaikem

Steps to reproduce

We cannot replicate the issue, however the user shared a video in the ticket

What you expected to happen

To be able to see the content after the renewal

What actually happened

It didn't work.

Context

5584857-zen

Please check the ticket with the video they shared.

Platform (Simple, Atomic, or both?)

Simple, Atomic

Theme-specific issue?

No

Browser, operating system and other notes

No response

Reproducibility

No response

Severity

No response

Available workarounds?

No response

Workaround details

No response

@Robertght Robertght added [Type] Bug When a feature is broken and / or not performing as intended Premium Content Controlling specific content for paying site visitors. User Report labels Oct 3, 2022
@github-actions
Copy link

github-actions bot commented Oct 3, 2022

Support References

This comment is automatically generated. Please do not edit it.

  • 5584857-zen
  • 5604470-zen

@Robertght
Copy link
Author

Robertght commented Oct 4, 2022

Another report in #5604470-zen

image

It's related to the above case.

@cuemarie
Copy link

cuemarie commented Oct 4, 2022

📌 SCRUBBING : RESULT

  • Tested on AT: Could Not Replicate on separate test site

📌 FINDINGS/SCREENSHOTS/VIDEO

  • For good measure, I tried replicating this issue on a test site with the same plugins installed, and the same theme installed as the user above.
  • The Login button was available right away after subscribing, and worked as expected.

Before Subscribing

Markup on 2022-10-04 at 13:40:43

Confirmation of Subscription

Markup on 2022-10-04 at 13:41:22

After Subscribing

Screen.Capture.on.2022-10-04.at.13-45-31.mp4

📌 ACTIONS

  • Marked as Triaged for Quality Squad review
  • Escalated here: p1664916725926879-slack-CJS75TX3R

@cuemarie cuemarie added the [Pri] High Address as soon as possible after BLOCKER issues label Oct 4, 2022
@rcrdortiz
Copy link
Contributor

I'll add this issue to team Ajax's board so that we can have a look as soon as possible.

@cuemarie
Copy link

Cross-posting this similar issue with Premium Content: #69427

The subscribers that are noted in that report cannot see premium content even after the first 24 hours, it seems, but wanted to note it here in case these issues have a shared underlying cause.

@artpi artpi added the Earn label Dec 21, 2022
@karenroldan karenroldan added [Feature Group] Customer Seller Experience The customer experience when purchasing services or products. [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature] User Payments & Donations The configuration screens and tools for users to receive payments and donations on their sites. labels Oct 6, 2023
@github-actions github-actions bot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label Oct 6, 2023
@karenroldan karenroldan moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Oct 6, 2023
@mmtr
Copy link
Member

mmtr commented Jul 24, 2024

Hey @Automattic/gold, this sounds like an issue you can help with. Do you mind taking it a look?

As part of pekYwv-4m6-p2, we’re trying to make sure every blocker/high priority issue on The One Board has an owner and clear next steps.

Thanks!

@lsl
Copy link
Contributor

lsl commented Aug 6, 2024

Cross-posting this similar issue with Premium Content: #69427

This does look related, added it to the board as well.

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Aug 6, 2024
@lsl lsl moved this from Triaged to Ready for Development in Automattic Prioritization: The One Board ™ Aug 6, 2024
@miksansegundo miksansegundo self-assigned this Aug 19, 2024
@miksansegundo miksansegundo moved this from Ready for Development to In Progress in Automattic Prioritization: The One Board ™ Aug 19, 2024
@miksansegundo miksansegundo removed their assignment Aug 20, 2024
@miksansegundo miksansegundo moved this from In Progress to Ready for Development in Automattic Prioritization: The One Board ™ Aug 20, 2024
@TimBroddin TimBroddin assigned TimBroddin and unassigned TimBroddin Aug 20, 2024
@TimBroddin
Copy link
Contributor

I tried reproducing this but failed. @Automattic/gold has more background in this area of the code, I think they're in the bets position to take a stab at this.

(cc @miksansegundo )

@millerf
Copy link
Contributor

millerf commented Aug 20, 2024

CC @pottedmeat You might be the one with latest knowledge about this.
We tried to fix this so many times I lost track.

@millerf
Copy link
Contributor

millerf commented Aug 21, 2024

This seems to be a duplicate of #80974
Can we close this @TimBroddin ?

@TimBroddin
Copy link
Contributor

Closed!

@github-project-automation github-project-automation bot moved this from Ready for Development to Done 🎉 in Automattic Prioritization: The One Board ™ Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Earn [Feature Group] Customer Seller Experience The customer experience when purchasing services or products. [Feature] User Payments & Donations The configuration screens and tools for users to receive payments and donations on their sites. [Platform] Atomic [Platform] Simple Premium Content Controlling specific content for paying site visitors. [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts [Type] Bug When a feature is broken and / or not performing as intended
Development

No branches or pull requests

10 participants