System Connect Status - Not Found

Same here, can it be a problem caused by Services 3.2, as described here: http://drupal.org/node/650776#comment-4895626 ?

Sorry for the delay. It appears the latest Services module changed up some stuff. When enabling the 'recommended version' of DrupalGap now, its Endpoint won't get set up properly. If you disable and uninstall the current DrupalGap module, then download the latest dev release for 7.x, then enable it, this problem should be taken care of.

Also be sure to visit the documentation and check out the troubleshooting section and the firefox poster tests to verify your Drupal site is set up properly: http://drupal.org/node/1603690

The poster Plugin says that its not found. But i'm very sure i've checked everything as described here: http://drupal.org/node/1603690

Please paste the URL you are trying to use with the Poster plugin here and I'll take a look.

www.famjam.org THX!

Using Firefox Poster and doing a POST with Content Type application/x-www-form-urlencoded to this url works:

http://www.famjam.org/drupalgap/system/connect.json

It looks like DrupalGap is setup correctly on your site.

P.S. I just released 7.x-1.2 which should fix any problems with the newest version of the Services module.

Don't know where this is gonna post now...so:

RE: http://drupal.org/node/1820552

I am having a similar endpoint definition problem for the DrupalGap 6.x-1.1 release as well.
In conjunction with Services 6.x-3.3.

Does the fix suggested in the above post (that is: If you disable and uninstall the current DrupalGap module, then download the latest dev release for 7.x, then enable it, this problem should be taken care of.) work for a 6.x-1.x-dev upgrade as well.

dmduke

If the cause of your problem is the same change in services which may or may not be and it would require similar changes in D6 as in D7 it is unlikely those have been committed since as you can see at the modules page the last release of 6.x-dev if of 2012-May-17.

Is there an error message regarding spyc on your status page?

Note: the documentation regarding spyc is currently outdated. See http://drupal.org/node/1349588 for more details.

Can you access: admin/structure/services/list/drupalgap/resources ?

If you manually disable, then re-enable the service resources at admin/structure/services/list/drupalgap/resources , does that fix the problem?

According to the module list in #10, here are my guesses at some modules that may be interfering with the Service Resource:

OAuth (I see you have this disabled, perhaps it needs to be uninstalled)
Redirect
Global Redirect
Boost
Memcahe

My advice would be to start a completely new D7 install in a localhost environment, get DrupalGap up and running first, then start enabling each of your modules one by one. That should reveal which one(s) is the problem.

I'd like to point out that using FireFox Poster to hit your System Connect URL with a clean URL results in this response:

FireFox Poster / POST / http://jungchristophe.fr/drupalgap/system/connect.json

<!-- Page cached by Boost @ 2013-01-15 03:22:16, expires @ 2013-01-15 04:22:16, lifetime 1 heure -->

@Tauph: Ah I think you updated your post after I started answering ;)

As Tyler pointed out the cause might be another module.

Have you tried and tested to create a normal services recource manually?

Here is some information regarding spyc and services.

(Note: Your issue seems not related to spyc)
It's been a while since I looked at it but this is as far as I remember the situation:
Aparently it is not actually required for REST services unless you want to use YAML. However you cannot activate the REST server in the current version when the spyc file is missing. Now in 7.x-3.3 the loading of the file changed and now uses libraries 2.x only so the old path (sites/all/modules/services/servers/rest_server/lib) wont work any more preventing rest_server module to be installed. If rest_server module had been installed before and libraries 2.x is present the module continues to run with the message on the status page about missing spyc. If libraries 2.x is not present the site will crash as with a undefined function call to libraries_load(). It's all a bit of a mess and the services documentation isn't helping either.

My patch (which I still need to finish but I'm writing my thesis currently) tries continues with the road the services maintainers took and only reads from libraries (sites/all/libraries/... not the old path) but updates the documentation to state this and makes spyc no requirement so rest server can be installed without it.

Hi
Global Redirect is the culprit here, any workaround?
Simone

Does Global Redirect allow you to add exceptions? If so, adding http://www.example.com/drupalgap/* would be a good start.

Unfortunately not, but that is what i asked in the GR issue queue

Here's an updated list of contrib modules known to cause problems with DrupalGap Services:

• Boost
• Global Redirect

I've changed this issue to a support request and have closed it for now.

After some hours of testing different setups, I can confirm, that BOOST and GLOBAL REDIRECT need to be - not only disabled but actually - uninstalled to allow drupalgap to connect.

I found a solution to remove the problem with global redirect enabled. It's not the final solution because I modified Global Redirect instead drupalgap ...

In the globalredirect.module file, in the globalredirect_init function, line 205, modifiy the next lines to get :

// If no alias was returned, the final check is to direct non-clean to
// clean - if clean is enabled
if ($settings['nonclean_to_clean'] && ((bool)variable_get('clean_url', 0)) && strpos(request_uri(), '?q=')) {
$res = explode("/",$current_path);
if (!($res[0] == "drupalgap")) {
globalredirect_goto($current_path, $options);
}
}

it works for me.

Disabling the 'Non-clean to Clean' to checkbox at admin/config/system/globalredirect allows DrupalGap to work with Global Redirect.

Any ideas how we can solve this cleanly?

I mean the functionality of global redirect is not bad and makes sense so what can we do?

See this issue for the Global Redirect fix: #1927336: Global Redirect Breaks Drupalgap