billybonks  
                
                  
                    August 4, 2015,  3:16pm
                   
                  1 
               
             
            
              Continuing the discussion from Problem Embedding Comments :
 
I’d like to use discourse comments in my ghost blog (using @eviltrout ’s instructions here ) – until recently, this has been working smoothly as expected. After re-importing my blog content with slightly different slugs, it started complaining that the X-Frame-Options header on discourse was set to ‘SAMEORIGIN’, preventing any x-site communication.
I followed the instructions here  and the error has since disappeared, only to be replaced by another.
In my developer console, I now see a 403 Forbidden error:
GET http://discourse.muselive.com/embed/comments?embed_url=http%3A%2F%2Fghost.muselive.com%2Falbum-number-7-on-its-way-1393155960%2F 403 (Forbidden) 
followed by:
Uncaught TypeError: Cannot read property 'forEach' of undefined
Uncaught TypeError: Cannot read property 'create' of undefined    discourse.muselive.com/assets/vendor-3c0b29078a0c6673dd5ae1991a1fc9a6.js:12
Could this be a problem with my ghost install or with discourse? Has anyone else come across this issue? Example page which doesn’t work here .
Any help would be appreciated - thanks.
 
 
similar issue as the linked topic, but none of the solutions seem to work
embed_urlhttp://discourse.unearthing.io/embed/comments?embed_url=http%3A%2F%2Funearthing.io%2Fnew-features-ember-2-0%2F 
post urlhttp://www.unearthing.io/new-features-ember-2-0/ 
Config
             
            
              
            
           
          
            
              
                billybonks  
              
                  
                    August 5, 2015,  4:55am
                   
                  2 
               
             
            
              It just seems to take a while to import. and imported the blog twice will test it further to see, whats the situation. it would be nice to have some visualisation as to what is going on
             
            
              
            
           
          
            
              
                fefrei  
              
                  
                    August 5, 2015,  7:42am
                   
                  3 
               
             
            
              A warning for this case (large backlog after import) is already being discussed here  
             
            
              
            
           
          
            
            
              This topic was automatically closed after 3230 days. New replies are no longer allowed.