Uncaught exception The service doctrine_extensions does not exist

[shefik]

Attempting to upgrade a site from Zikula 1.2.x to 1.3.5, throws the following uncaught exception. The problem is due to the Pages module, and the error exists in the current master repository.

---

Uncaught exception The service doctrine_extensions does not exist in /lib/Zikula/ServiceManager.php line, 142

0 /lib/util/ServiceUtil.php(69): Zikula_ServiceManager->getService('doctrine_extens...')

1 /modules/Pages/bootstrap.php(14): ServiceUtil::getService('doctrine_extens...')

2 /system/Extensions/lib/Extensions/Api/Admin.php(962): include_once('/mnt/stor1-wc1-...')

3 /system/Extensions/lib/Extensions/Api/Admin.php(1115): Extensions_Api_Admin->upgrade(Array)

4 [internal function]: Extensions_Api_Admin->upgradeall(Array)

5 /lib/util/ModUtil.php(1097): call_user_func(Array, Array)

6 /lib/util/ModUtil.php(1205): ModUtil::exec('Extensions', 'admin', 'upgradeall', Array, true, NULL)

7 /upgrade.php(324): ModUtil::apiFunc('Extensions', 'admin', 'upgradeall')

8 /upgrade.php(135): _upg_upgrademodules('', '')

9 {main}

[craigh]

you should not run the upgrade with modules in the module directory. remove modules. run upgrade. replace modules. upgrade modules as required.

[shefik]

But, all the other modules I have installed already don't have the same issue (even though a few of them make use of the same bootstrap of doctrine_extensions. So, why wouldn't those other modules fail?

[phaidon]

~~It is a core issue: https://github.com/zikula/core/issues/882~~

[craigh]

@phaidon - this should work in Core 1.3.5 which is what @shefik notes in this ticket. The Core issue is a 1.3.6 issue.

[ghost]

@phaidon this is not a 1.3.6 milestone issue, but 1.3.5 and it also seems like a non-bug as the upgrade instructions have not been followed.

[phaidon]

@drak @craigh

you are right.

[craigh]

Does Pages even use Doctrine extensions?

[craigh]

I experienced this issue just today but only when short urls are turned on. I'm still not sure why - but that would seem to indicate a core issue. I was able to properly install it (on Core 1.3.7) with shorturls off and then later when I turned shorturls on the problem was displayed.

@shefik - did you have shorturls enabled when you were upgrading?