Getting Started issues.

[Adam]

I am trying to do the demo, http://buddycloud.com/get-started-javascript but the very first step of including the scripts fails for me.  I get an error about unexpected character because I am including the primus.js but the file pointed to, "https://demo.buddycloud.com/scripts/primus/primus.js" but when I look at the source for that file it is really an HTML file and not JS. I also created an account and tried using the the free hosted version but all of the links I am given for endpoints and the primus.js file all result in DNS lookup failures.

Is there some basic step I am missing or some other way to get started?

[Kamal Reddy]

Can someone reply to this, please ?? I am also facing the same problem..

[Steven Lloyd Watkin]

Hi yes, 

We've renamed the script to make it more obvious that its a buddycloud connector. See the example here: https://demo.buddycloud.org/api/demo.html

Basically you'll need to pull in /scripts/buddycloud.js and initialise a Buddycloud object.

I'll nudge Simon to get this corrected, thanks, Lloyd.

[Kamal Reddy]

Even this demo link has errors in console. 

[Steven Lloyd Watkin]

Apologies, the demo script isn't designed to be run on a subpath. The correct path to the javascript file would be /api/scripts/buddycloud.js, i.e. https://demo.buddycloud.org/api/scripts/buddycloud.js

--
http://buddycloud.org
---
You received this message because you are subscribed to a topic in the Google Groups "buddycloud-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/buddycloud-dev/KW8MKSzg0c4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to buddycloud-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tatjana Kleshnina]

This link works:

https://demo.buddycloud.org/api/scripts/buddycloud.js

But first example from http://buddycloud.com/get-started-javascript raises an error:

XMLHttpRequest cannot load .... No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

[Tatjana Kleshnina]

   And can you help, why server responses with 302?

1. 
   
2. Remote Address:
   5.9.67.253:443
3. Request URL:
   https://demo.buddycloud.com/socket.io/?EIO=3&transport=polling&t=1433250737853-0
4. Request Method:
   GET
5. Status Code:
   302 Found

On Monday, April 27, 2015 at 4:44:32 AM UTC+2, Adam wrote:

[Simon Tennant]

Hi Tatjana

I'm thinking that this redirect / 302 is because you are using .com instead or .org in the domain. 

I'm sorry about the URL issue - we're building a new instance of the buddycloud stack on SI that we can roll out that will fix some of these bad URL issues too. 

S. 

--
http://buddycloud.org
---
You received this message because you are subscribed to the Google Groups "buddycloud-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to buddycloud-de...@googlegroups.com.

[Tatjana Kleshnina]

Hi, Simon!

Thank you for the answer.

After changing to `org`, I get `200` in the answer, but I'm still getting CORS error:

XMLHttpRequest cannot load .... No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

Why server doesn't send Access-Control-Allow-Origin?

On Monday, April 27, 2015 at 4:44:32 AM UTC+2, Adam wrote: