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

full-size image popup won't close #21

Open
durkie opened this issue Jun 3, 2016 · 5 comments
Open

full-size image popup won't close #21

durkie opened this issue Jun 3, 2016 · 5 comments

Comments

@durkie
Copy link
Collaborator

durkie commented Jun 3, 2016

If I click on an image I've uploaded of a tree to see the full size image, I'm unable to close that popup. It gives this error on opening the full-size image:

invariant.js:46 Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's `render` method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).

this is on OSX. also unable to zoom/pan the image and have to reload to get out.

@ThePlushEater
Copy link

Hmm.. I haven't checked on OSX Safari, I might need to change the way google use for image zoom in / out.

@ThePlushEater
Copy link

Check this bug with the current released version, and let me know if the same thing happens to you.

@durkie
Copy link
Collaborator Author

durkie commented Jun 9, 2016

@ThePlushEater
Copy link

I also checked the same error on the CJ FoodParent site, which I don't see in my site: http://foodparent.thecaptainwhale.com/tree/142?note=439. I think it is different version of npm issue or something related to compile.
See this thread: https://gist.github.com/jimfb/4faa6cbfb1ef476bd105

If you have time, try these solutions that people suggested, or if not, we will figure out together later, since I cannot which solution will work for you. The only concern that I have now is about the 20th filed testing. We don't want to have that error when we do the field testing.

@ThePlushEater
Copy link

I know you did clean build, but I want you to check about the below:

https://gist.github.com/jimfb/4faa6cbfb1ef476bd105
Multiple copies of React
Bower does a good job of deduplicating dependencies, but NPM does not. If you aren't doing anything (fancy) with refs, there is a good chance that the problem is not with your refs, but rather an issue with having multiple copies of React loaded into your project. Sometimes, when you pull in a third-party module via npm, you will get a duplicate copy of the dependency library, and this can create problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants