Hello,
I do not know whether this is a bug or not, but it could be. As far as I know we have followed the instructions for configuring shindig.
When I try to view the account's gadgets, they are unable to access the Config class functions.
Class 'Config' not found in
\drupal\sites\all\modules\shindig_integrator\shindig\php\src\common\sample\BasicBlobCrypter.php on line 54
I attempted to add an include to the BasicBlobCrypter before that line, and this created more errors having to do with 'Invald Config Key.'
I apologize if this is all due to ignorance. I did search around for answers but documentation on this new technology is rather light at the moment. If you are certain the module should be working, then at this point perhaps it would be best to start over and see if we can get different results. thank you
Comments
Comment #1
ramsharma2005 commentedHi,
I want to know which release of shindig are you using?
Currently it is supported shindig release 1.0.x-incubating. If you are using the same, please let me know.
Thanks
Comment #2
bob.hinrichs commentedThank you. I had grabbed the version recommended on the shindig site from trunk, which was not the correct version. Also, I note that I think you need to update your readme file, as it lists the 0.8.1-x branch as the version to download (unless I have the wrong version of your module somehow).
However, after ensuring that I have the latest shindig, and uninstalling/re-installing the shindig integrator module, the same error is occurring. I am able to add an application to the gallery, view the gallery, and add the application to my user's account. But when I click to view the account, the error occurs. It is a fatal error and results in a white screen. Does not log to drupal.
Fatal error: Class 'Config' not found in (...)drupal\sites\all\modules\shindig_integrator\shindig\php\src\common\sample\BasicBlobCrypter.php on line 52
thanks for your attention.
Here is a backtrace. It appears to be trying to get a configuration to get security keys. I have not created security keys using open ssl, and I haven't seen documentation relating to having to do that. However if there were the problem, I would expect a different output. The problem seems to be that it is did not include the Config.php file and so it does not have the class. The file is in the directory above. If I put in the require of Config.php before this line, then it responds with an 'Invalid Config Key' exception.
Comment #3
bob.hinrichs commentedOne more very important thing: the system is not finding some included files. When Config.php is calling 'include_once 'config/container.php';', it is not being included. Changing it to a require, I get this error: Failed opening required 'config/container.php' (include_path='.;C:\PHP5\includes;'). Perhaps the directory structure does not match, or we need to add to the include_path?
I did this and it removed some of the errors.
I had to add this line to shindig_integrator.module line 606 to get the Config to load (theme_add_gadget):
module_load_include('php', 'shindig_integrator', '/shindig/php/src/common/Config');
I also had to edit this in the container.php file:
'web_prefix' => '/sites/all/modules/shindig_integrator/shindig/php',
Though the errors are gone, the account view page just shows 'loading' graphics, so I think there are other problems, or these changes are not really solving the crux of the issue. There are javascript errors on that page. The first being 'gadgets.rpc is undefined'. My guess is that there are yet more paths that do not work.
Comment #4
bob.hinrichs commentedThe account view page javascript began working when I turned off javascript compression. So I assume this is reproducible.
The applications that I am trying seem to produce errors when they are interacting with the page. It is difficult to tell the source of the errors. My intuition tells me they are coming from the remote servers not getting all of the information they need.
Comment #5
ramsharma2005 commentedHi,
Thanks for bringing this up. It seems, all these issues are coming because of some directory strcuture changes made at the new Shindig branch. I had tested the module with shindig code available at http://svn.apache.org/repos/asf/incubator/shindig/branches/0.8.1-x/ location, earlier. But there is no branch available with this name now, I think some changes have been made in shindig release 1.0.x-incubating. There are some code updates as well...
I am analyzing the shindig code to make ShindigIntegartor compatible with shindig current release.
I will let you know as ShindigIntegrator will become shindig release 1.0.x-incubating compliance.
Thanks
Comment #6
ramsharma2005 commentedHi bob-hinrichs,
ShindigIntegrator is currently compliant with shindig code of 3 Dec 2008(revision:722552).
I am updating readme as well with same. Please let me know, if you are still facing issues.
We are contributing activity module for ShindigIntegrator as well very soon and working to make ShindigIntegrator shindig release 1.0.x-incubating compliant.
Thanks.
Comment #7
ramsharma2005 commentedHi bob-hinrichs,
I have made changes to make ShindigIntegrator shindig release 1.0.x-incubating compliant.
Please let me know, if there is any issue issue. Please checkout the latest branch.
Thanks
Comment #8
ramsharma2005 commentedResolved.