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

Pod page shows the wrong content #162

Closed
jschmid opened this issue May 27, 2015 · 7 comments
Closed

Pod page shows the wrong content #162

jschmid opened this issue May 27, 2015 · 7 comments
Labels

Comments

@jschmid
Copy link

jschmid commented May 27, 2015

Currently, if you look at the JCDialPad page, you will see the content of ABPadLockScreen.

screen shot 2015-05-27 at 09 33 23

This might be the result of a concurrency error in the page generation. Let me explain:

  • I did a search for keypad which yield two results, ABPadLockScreen and JCDialPad.
  • I opened in a new tab each pod's page. I opened them quickly.

I guess there is some problem in page generation and now that the page is cached you always see the wrong content.

@orta
Copy link
Member

orta commented May 28, 2015

Interesting, I've not seen this before. And re-parsing it doesn't seem to help.

@kylef kylef added the bug label May 28, 2015
@floere
Copy link
Member

floere commented Oct 18, 2015

@orta Any idea what the issue could be? Should we do a review? (Or, you could point me at some code for a review)

@kylef
Copy link
Contributor

kylef commented Oct 19, 2015

This may not be a code problem, considering there is no authentication on the API call from CocoaDocs to the CocoaDocs API it would be extremely simple for anyone to push content to any pod detail page.

To prove this, see https://cocoapods.org/pods/MFStoryboardPushSegue where I've pushed metadata for QueryKit to another of my pods without using any access tokens.

@floere
Copy link
Member

floere commented Oct 19, 2015

@kylef Good point. I assumed it was a code issue due to the reparsing not helping.

@kylef
Copy link
Contributor

kylef commented Oct 19, 2015

@floere Oh right, I went to the page and saw it was correct now, assuming the re-parse did succeed.

@floere
Copy link
Member

floere commented Oct 19, 2015

@kylef It's not correct, though.

@orta
Copy link
Member

orta commented Nov 5, 2017

Since then there's been authentication added to the request, and the process is simpler - closing.

@orta orta closed this as completed Nov 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants