Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When I put in my site's address into the drupal garden's app, "Please wait" shows up and then disappears, but that's it. If I put in another site where I haven't installed the module, then it says, "There was an error connecting. The URL entered does not appear to be a Drupal site configured to support this application." So, my setup has made it past some sort of test, but I don't get any feedback about what is failing. I also don't have the foggiest clue how to get more information about what's going wrong.
Any suggestions?
Thanks,
-Joseph
Comments
Comment #1
DamienMcKennaRunning into the same problem with my site hosted at site5 using rc1 and the latest versions of all dependencies.
Comment #2
jtbayly CreditAttribution: jtbayly commentedOk, I'm going to switch this to a bug report since I'm not the only one seeing it.
Just out of curiosity does this app try to communicate with the site via anything other than port 80? If so, I could see that causing an issue like this.
My site is hosted on omega8.cc.
-Joseph
Comment #3
DamienMcKennaFYI dblog records the following error:
Notice: Undefined index: Auth in OAuthUtil::get_headers() (line 843 of oauth/lib/OAuth.php).
Comment #4
DamienMcKennaThe error is occurring in this part of the Oauth library:
It should be doing an isset($out['Auth']), but that's a symptom and not the core problem.
Comment #5
jprstoney CreditAttribution: jprstoney commentedGetting the same issue. Any further thoughts?
Comment #6
jtbayly CreditAttribution: jtbayly commentedUnfortunately, I just gave up.
-Joseph
Comment #7
jbrauer CreditAttribution: jbrauer commentedI had exactly the same symptoms, still do actually.
Every so often I try (say a few hours since the last attempt and I get "oauth/request_token" with a access denied error. It seems as though something in the Drupal Gardens app is caching this as it only shows up on my site once in a long while. On a whim the last time I tried a different name for the same server .net instead of .com and it worked.
Then I looked at cache_page and noticed these cache keys
http://www.example.net/mast/login?destination=/oauth/authorize[...]
http://www.example.net/oauth/request_token
http://www.example.com/oauth/request_token
Now a telling part of tis is that the site is set to only use example.me and example.com and .htaccess redirects to these. I never put a www in the Drupal Gardens app but somewhere along the line it was added before the page cache.
When I went back to the .com site same thing .. app flashes please wait and nothing. But the .net address worked fine.
Comment #8
jbrauer CreditAttribution: jbrauer commentedIt would appear that at least part of the challenge is for sites that are domainame.tld ... at least in Drupal Create (code) there is a function which appears to try to always add www if there is only one '.' in the site url.
Comment #9
jbrauer CreditAttribution: jbrauer commentedI confirmed that fixing the handling in the Drupal Create app allows it to work with urls that don't have three parts and ssl instead of requiring http connections.
https://github.com/acquia/drupal-create/pull/4
Marking this as needs review because I think the MASt module is fine here and that it's a problem on the Application side.
Comment #10
kylebrowning CreditAttribution: kylebrowning commentedThis was merged on the Drupal Create project, not sure what you want to do with this ticket, but nothing more needs to be done AFAIK.