Tickets :: [#11355] Can't update DB schema with latest git

6.0.0-beta1

7/6/25

Summary	Can't update DB schema with latest git
Queue	Ansel
Queue Version	Git develop
Type	Bug
State	Not A Bug
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	thomas.jarosch (at) intra2net (dot) com
Created	08/15/2012 (4708 days ago)
Due
Updated	08/15/2012 (4708 days ago)
Assigned	08/15/2012 (4708 days ago)
Resolved	08/15/2012 (4708 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

08/15/2012 03:56:00 PM	Michael Rubinsky	Comment #6 State ⇒ Not A Bug	Reply to this comment
No idea, works fine for me.

08/15/2012 03:52:32 PM	Thomas Jarosch	Comment #5	Reply to this comment
Now I get a totally different error: "The Horde/Kolab integration engine does not support "ansel" Does that make more sense Only if you have kolab support enabled...otherwise, no. Yes, I do ;) I'm not keen on running ansel, I've just noticed the error. Probably I'll just remove it from my installation. I'm just wondering why it was able to update/create the database stuff initially.

08/15/2012 03:48:37 PM	Michael Rubinsky	Comment #4	Reply to this comment
[Show Quoted Text - 24 lines][Hide Quoted Text] Hi, the ansel DB schema is outdated at my installation so I tried to update it. It fails with this popup: "Class Content_Types_Manager does not exist" Nothing else is logged. Smells like the recent nag issue ~~#11346~~ Nope. Ansel has all the needed Autoloader paths set up in both the migrations and in the application init code (that was the cause of the Nag bug). Can you find out what migration is doing this and get a BT? Hmm, I just cleared all the Horde caches in /tmp, my browser cache and the PHP session directory to give it a clean start. Now I get a totally different error: "The Horde/Kolab integration engine does not support "ansel" Does that make more sense Only if you have kolab support enabled...otherwise, no.

08/15/2012 03:46:21 PM	Thomas Jarosch	Comment #3	Reply to this comment
[Show Quoted Text - 16 lines][Hide Quoted Text] Hi, the ansel DB schema is outdated at my installation so I tried to update it. It fails with this popup: "Class Content_Types_Manager does not exist" Nothing else is logged. Smells like the recent nag issue ~~#11346~~ Nope. Ansel has all the needed Autoloader paths set up in both the migrations and in the application init code (that was the cause of the Nag bug). Can you find out what migration is doing this and get a BT? Hmm, I just cleared all the Horde caches in /tmp, my browser cache and the PHP session directory to give it a clean start. Now I get a totally different error: "The Horde/Kolab integration engine does not support "ansel" Does that make more sense?

08/15/2012 03:31:11 PM	Michael Rubinsky	Comment #2 State ⇒ Feedback	Reply to this comment
[Show Quoted Text - 10 lines][Hide Quoted Text] Hi, the ansel DB schema is outdated at my installation so I tried to update it. It fails with this popup: "Class Content_Types_Manager does not exist" Nothing else is logged. Smells like the recent nag issue ~~#11346~~ Nope. Ansel has all the needed Autoloader paths set up in both the migrations and in the application init code (that was the cause of the Nag bug). Can you find out what migration is doing this and get a BT? Also, FWIW, a number of views in ansel in develop are broken. Haven't had time to convert to recent changes in imple code. Thomas

08/15/2012 02:58:19 PM	Thomas Jarosch	Assigned to Michael Rubinsky

08/15/2012 02:58:00 PM	Thomas Jarosch	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Can't update DB schema with latest git Queue ⇒ Ansel Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Hi, the ansel DB schema is outdated at my installation so I tried to update it. It fails with this popup: "Class Content_Types_Manager does not exist" Nothing else is logged. Smells like the recent nag issue ~~#11346~~ Thomas