Closed (fixed)
Project:
Service Container
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
20 Mar 2015 at 14:36 UTC
Updated:
10 Jul 2015 at 12:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
santhoshabraham commentedComment #2
fabianx commentedI have not tested update.php, that is indeed a bug.
Can you try:
drush updb
instead?
Comment #3
santhoshabraham commentedI did little bit research, looks like service container need at least PHP >= 5.5. I'm running PHP 5.3. Is that cause the problem?
https://www.drupal.org/node/2443237
Comment #4
fabianx commentedIt should not be, I have tests working around PHP 5.3.
Comment #5
santhoshabraham commentedI upgraded to php 5.6. Still having same issue.
Comment #6
fabianx commentedSo does drush updb work? Or is it only update.php that breaks?
Comment #7
santhoshabraham commentedI tried drush updb, it works fine.
Comment #8
astringer commentedI am getting this error, also after an OpenLayers install. But I am getting the error in Views. It started as an ajax error:
This occurred when I tried to edit the view. I save the view and exited and now I cannot get back into the view -- the error appears.
Comment #9
fabianx commentedPlease give me as much information as you can in terms of how to reproduce. I will try to fix this ASAP.
Comment #10
astringer commentedI don't want to give it you from memory, so I'll need to reinstall the module. But I will get back to you.
Comment #11
m.stentaSteps to reproduce:
You will see:
Comment #12
formatC'vt commentedupdate.php doesn't call
service_container_init()try openlayers latest dev
Comment #13
fabianx commentedYes, I will need to see how I can get the service container registered during update.php
That will be fun! :)
Comment #14
robertwb commentedShould this be changed to "Postponed" since it maybe can be chalked up to the related problem with OpenLayers module? FWIW the new dev version of OL seemed to avoid this error (so far).
Comment #15
stevieb commentedI had the same issue ... I resolved it by running the update script before installing Openlayers and Service Container ... then everything works fine.
Comment #16
el_toro commentedHere's a quick hack that I used to get around this issue...
Comment #17
fabianx commentedThat is a pretty good idea!
There is one caveat however - this can only work if the container was build already - as trying to build it in hook_boot() would have bad consequences atm. (https://www.drupal.org/node/496170):
- I will take a look, thanks for your patch!
Comment #18
polHello,
In Openlayers, we've fixed the problem by adding two hooks:
See the original issues: #2446309: update.php produces fatal error and #2468057: "openlayers.manager" service definition does not exist.
Comment #19
fabianx commentedFixed, opened #2502543: [update.php] Fatal error: Call to a member function get() on a non-object as follow-up for the hook_boot() idea.
Comment #20
fabianx commentedComment #23
webengr commentedShould I go back to openlayers2 or try some of the patches, I am also as of 6/24 getting the error if I do a drush rr with all the latest dev
Error: Call to a member function get() on null in ............../sites/all/modules/service_container/lib/Drupal.php, line 52
Comment #24
fabianx commentedPlease try:
drush rr --no-cache-clear
Also see:
#2510798: Registry Rebuild does not rebuild classes loaded by Registry Autoload
Comment #25
webengr commentedI applied the beta updates that were dated 6/25 for openlayers and the service_container,
now the openlayers 3 is doing something and yes the "--no-cache-clear" also was required to rebuild the registry
So yes the 6/25 update made something work better, yes the drush rr does not work if it is allowed to clear cache.
In Fabian's words "Nice! So without clearing cache a registry rebuild is more successful, that gives hope"