Skip to content

Thrive external source bug fixes #3852

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

Closed
kkartunov opened this issue Feb 7, 2020 · 9 comments
Closed

Thrive external source bug fixes #3852

kkartunov opened this issue Feb 7, 2020 · 9 comments
Assignees
Labels
Contentful-DEV Internal development operations for Contentful Prod Env Environment QA Pass
Milestone

Comments

@kkartunov
Copy link
Collaborator

  1. When the user searches an article on THRIVE and clicks on the details, if the article is on an external source(for instance the blog), the THRIVE content details is currently showing the page but should redirect to the link of the external article.

To reproduce type: "USING MEANINGFUL TYPOGRAPHY" in search bar in Thrive and click the result. Should be the blog article, not the articles detail page.

  1. Hitting the article details page directly, in this case, should also redirect to external source link.
    Example: https://www.topcoder.com/thrive/articles/Using%20Meaningful%20Typography%20in%20Your%20Design should redirect to https://www.topcoder.com/using-meaningful-typography-design/
@kkartunov kkartunov added the Contentful-DEV Internal development operations for Contentful label Feb 7, 2020
@kkartunov kkartunov self-assigned this Feb 7, 2020
kkartunov added a commit that referenced this issue Feb 10, 2020
@SathyaJayabal
Copy link
Collaborator

  1. clicking on article in search results does not open the article

  2. clicking on "view all results" does not open the search results"
    see attached video for reference
    thrive search.mov.zip

  3. Accessing the article by its link throws a file not found error
    https://www.beta-community-app-topcoder.com/thrive/articles/Using%20Meaningful%20Typography%20in%20Your%20Design

Screenshot 2020-02-11 at 3 35 02 PM

@SathyaJayabal SathyaJayabal added Beta Env Environment QA Fail QA verification on Dev has failed. Assignee to redo the fix. labels Feb 11, 2020
@SathyaJayabal
Copy link
Collaborator

@kkartunov
Copy link
Collaborator Author

@SathyaJayabal 1&2 are not in scope. For 3.your test url is wrong. Please, correct it and retry.

@SathyaJayabal
Copy link
Collaborator

@kkartunov , this is the bug description
When the user searches an article on THRIVE and clicks on the details, if the article is on an external source(for instance the blog), the THRIVE content details is currently showing the page but should redirect to the link of the external article.

How can #1 be out of scope ? Clicking on the details when you search on thrive does not work.

Let me know if I have misunderstood the bug.

@kkartunov
Copy link
Collaborator Author

@SathyaJayabal can you please verify 1.&2. again? It is all working for me in beta. See this video https://drive.google.com/file/d/17jkLoNdMdEAgfXEcBC7TfHgoOYJmp6ut/view

@SathyaJayabal
Copy link
Collaborator

@kkartunov , I am still getting the same issue.

@nithyaasworld @lakshmiathreya , can you please verify the above scenario?

@SathyaJayabal
Copy link
Collaborator

@kkartunov , I am marking this as QA pass with the video you have submitted.

@SathyaJayabal SathyaJayabal added QA Pass and removed QA Fail QA verification on Dev has failed. Assignee to redo the fix. labels Feb 11, 2020
@SathyaJayabal
Copy link
Collaborator

Verified on Beta (develop branch)

@SathyaJayabal SathyaJayabal added this to the 0.20.02 milestone Feb 12, 2020
@SathyaJayabal SathyaJayabal added Prod Env Environment and removed Beta Env Environment labels Feb 12, 2020
@SathyaJayabal
Copy link
Collaborator

verified in production
thrive search prod.mov.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contentful-DEV Internal development operations for Contentful Prod Env Environment QA Pass
Projects
None yet
Development

No branches or pull requests

2 participants