-
Notifications
You must be signed in to change notification settings - Fork 7
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
searching stopped working #8
Comments
You seem to be using a customized cosm-js in your fiddle, with a custom API endpoint which is the reason why it's not working. If you want to use that API endpoint, you can prepend http:// to make it work. If you use the original untouched cosm-js, it works as expected I believe. Let me know if it solves it. |
Ou, I'm sorry, I've changed cosm-js (when I was trying rly different things to find a solution) and didn't realize it will affect this fiddle also. I used the original again and now it should demonstrate my problem: http://jsfiddle.net/elerocks/pUeue/574/ - try repeatadly pressing the button and it gives you various results |
That fiddle is still using your custom cosm-js, try saving it so I can debug. Also, what browser are you using? |
yes, but only difference is, that api.cosm.com is replaced by its IP adress (they had some problems with it recently), that behavior was the same with original cosm-js. I'm using latest chrome and firefox. And another thing - this happens only with searching for fulltext ('q') values. If you search by owner, it seems to be ok. |
Hello,
lately I'm having trouble finding anything using cosmJS (cosm.feed.list). Either it finds 0 results or it just times out. It's propably fault on cosm side, but when cosmJS doesn't work, the hurl ( for example http://api.cosm.com/v2/feeds?user=xkocan00&tag=&q=&per_page=1&page=1&_=1361132779623?key=Ey0UIZkUZhAXtzzqYaPDooIm04GSAKxobUxnbkVhSkVVMD0g ) works. So my question is, whether you don't have this kind of problems or maybe even solution?
small fiddle ilustrating this problem : http://jsfiddle.net/elerocks/pUeue/565/
The text was updated successfully, but these errors were encountered: