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

Current release gives 'err is not defined' #42

Closed
jcoglan opened this issue May 24, 2012 · 5 comments
Closed

Current release gives 'err is not defined' #42

jcoglan opened this issue May 24, 2012 · 5 comments

Comments

@jcoglan
Copy link
Member

jcoglan commented May 24, 2012

I'm including https://github.com/unhosted/remoteStorage.js/raw/master/build/latest/remoteStorage.js on my page and calling this causes an error:

remoteStorage.getStorageInfo('jcoglan@localhost:4000', function(error, info) {
  console.log(error);
  console.log(info);
});

// -> Uncaught ReferenceError: err is not defined 
@jcoglan
Copy link
Member Author

jcoglan commented May 24, 2012

By the way, I'm using the express-storage server just for trying things out. If I run it on localhost:80 this error disappears and the call above seems to work.

@michielbdejong
Copy link
Member

thanks for the bug report, will fix asap!

On Thu, May 24, 2012 at 1:58 PM, James Coglan
reply@reply.github.com
wrote:

I'm including https://github.com/unhosted/remoteStorage.js/raw/master/build/latest/remoteStorage.js on my page and calling this causes an error:

remoteStorage.getStorageInfo('jcoglan@localhost:4000', function(error, info) {
 console.log(error);
 console.log(info);
});

// -> Uncaught ReferenceError: err is not defined

Reply to this email directly or view it on GitHub:
https://github.com/unhosted/remoteStorage.js/issues/42

@nilclass
Copy link
Member

Your problem with the port is due to this line, which doesn't allow a colon in the hostpart. I'm not sure, if webfinger is supposed to work on non-standard ports, but I don't think so. User-addresses are supposed to be like email addresses and those enforce a standard-port as well.

@jcoglan
Copy link
Member Author

jcoglan commented May 25, 2012

Fair enough. Makes local testing a tiny bit trickier but not a big deal.

@jcoglan jcoglan closed this as completed May 25, 2012
@nilclass
Copy link
Member

That's not the reason for that error message though, this fixes that: 62e280e

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

No branches or pull requests

3 participants