Changes have been made in Git for this ticket:

Check for, and throw exception if Content_Tagger class cannot be found 
from base.php. Temporary measure until Content_* system is better 
integrated with framework/autoloading etc...
Bug: 7936

http://git.horde.org/diff.php/kronolith/lib/Tagger.php?rt=horde-git&r1=048fd2907ef4ace8bce776d35fff2427ca173825&r2=9e178afdab63f394a5cdf393afabeed5d8a74b5c
http://git.horde.org/diff.php/kronolith/lib/base.php?rt=horde-git&r1=09ec72fad36cbb8f7d3b13531793d55bad790620&r2=9e178afdab63f394a5cdf393afabeed5d8a74b5c

Changes have been made in Git for this ticket:

Revert "Autoload Content." See Ticket: 7936 This reverts commit 
8925854973d1ba488b3f282f4f991d178bf2f52f.

http://git.horde.org/diff.php/kronolith/lib/base.php?rt=horde-git&r1=1ae2116e07c1d6fff4b20a7c9203f6eeb349c4db&r2=3d5cc54f92f2624a1ece227d44a94cf48f281257

Changes have been made in Git for this ticket:

Revert "Remove the requirement for a registry entry for content from 
the" See Ticket: 7936 This reverts commit 
85844520fcbb20506880dc41f29ec15d9ca65f53.

http://git.horde.org/diff.php/kronolith/lib/Tagger.php?rt=horde-git&r1=85844520fcbb20506880dc41f29ec15d9ca65f53&r2=3917c030a062a6e00f07960e6361cd01b497ec87

Changes have been made in Git for this ticket:

Check for, and throw exception if Content_Tagger class cannot be found 
from base.php. Temporary measure until Content_* system is better 
integrated with framework/autoloading etc...
Bug: 7936

http://git.horde.org/diff.php/kronolith/lib/Tagger.php?rt=horde-hatchery&r1=048fd2907ef4ace8bce776d35fff2427ca173825&r2=9e178afdab63f394a5cdf393afabeed5d8a74b5c
http://git.horde.org/diff.php/kronolith/lib/base.php?rt=horde-hatchery&r1=09ec72fad36cbb8f7d3b13531793d55bad790620&r2=9e178afdab63f394a5cdf393afabeed5d8a74b5c

From what I remember, the reason it isn't included more "officially" 
is that the Content stuff was supposed to be refactored into more of a 
framework library at one point, or at least have it more integrated 
with the rest of the libraries...but I will make a note of it 
somewhere else as well.

And at a minimum should exit gracefully if the registry entry doesn't 
exist instead of outputting a PHP fatal error message to the AJAX 
handler.

This needs to be documented somewhere besides the Tagger.php file 
(i.e. in registry.php or kronolith/docs/INSTALL).

Sure, though you can change 'status' to 'hidden' so it won't appear in 
the menu.

This works now, but is it correct?



$this->applications['content'] = array(

     'fileroot' => dirname(__FILE__) . '/../content',

     'name' => _("Content"),

     'status' => 'active',

);

Did you create a registry entry for content in config/registry.php?



If you need further help, please ask on the mailing list.

I still couldn't get it work, only with some patching...



kronolit/lib/Tagger.php:

require_once HORDE_BASE . '/content/lib/Users/Manager.php';

require_once HORDE_BASE . '/content/lib/Types/Manager.php';

require_once HORDE_BASE . '/content/lib/Objects/Manager.php';

require_once HORDE_BASE . '/content/lib/Tagger.php';



I see there's the autoloader, but doesn't work for me.

Reverted...

You both are right, this is probably due to my side-by-side checkout.

I'm sorry, I don't follow that.  In base.php the autoloader is 
configured to look in HORDE_BASE . '/content/lib' for Content_* 
libraries.  Content is in the hatchery, so it would not be present in 
HORDE_BASE for a standard out of the box checkout without either 
copying it or symlinking it into HORDE_BASE....or am I missing 
something?

No, it uses HORDE_BASE, which is different. I guess I haven't tried 
un-symlinking kronolith and just pointing the registry entry for it 
elsewhere lately, in combination with base.local.php.



Also, content is generally a library, yes, but it will need a registry 
entry so that the routes work for the web ui pieces of it.

No, the autoload configuration has been added to Kronolith which is in 
the same directory like content.

...well, not exactly out of the box, as the content directory will 
nowl need to be symlinked into the horde root.

This way it works out of the box with a regular checkout. This extra 
rule is no longer necessary once content is at a regular place that 
can be autoloaded. It's never supposed to be a standalone application, 
right? Then is should end up in the include_path, unless I am missing 
something.

Why are we hardcoding an assumption of content living in HORDE_BASE 
now? The registry method is much more flexible.

Please create separate tickets for different issues.

new error at the same place after copying content dirs to horde home.

kronolith db was newly initialized with the mysql script after we 
changed to the development code of kronolith, so I don't understand 
this...



Fatal error: Uncaught exception 'Horde_Db_Exception' with message 
'QUERY FAILED: No database selected SELECT type_id, type_name FROM 
`rampage_types` WHERE type_name IN ('calendar','event')' in 
/usr/share/php/Horde/Db/Adapter/Mysqli.php:299 Stack trace: #0 
/usr/share/php/Horde/Db/Adapter/Mysqli.php(217): 
Horde_Db_Adapter_Mysqli->execute('SELECT type_id,...', NULL, NULL) #1 
/usr/share/php/Horde/Db/Adapter/Abstract.php(391): 
Horde_Db_Adapter_Mysqli->selectAll('SELECT type_id,...', NULL, NULL) 
#2 /usr/share/horde/content/lib/Types/Manager.php(75): 
Horde_Db_Adapter_Abstract->selectAssoc('SELECT type_id,...') #3 
/usr/share/horde/kronolith/lib/Tagger.php(62): 
Content_Types_Manager->ensureTypes(Array) #4 
/usr/share/horde/kronolith/templates/panel.inc(28): 
Kronolith_Tagger->__construct() #5 
/usr/share/horde/kronolith/month.php(39): 
require('/usr/share/hord...') #6 
/usr/share/horde/kronolith/index.php(23): 
include('/usr/share/hord...') #7 {main} thrown in 
/usr/share/php/Horde/Db/Adapter/Mysqli.php on line 299

Content is autoloaded from kronolith/lib/base.php now.

That's ok, I saw this comment. But there's no content entry in 
horde/config/registry.php...



I'm sorry if I missed something...

There is a comment in the lib/Tagger.php file explaining what you need 
to do to ensure this can be autoloaded for the time being.

I receive the following error when changing to Calendar view:

Class 'Content_Users_Manager' not found in 
/usr/share/horde/kronolith/lib/Tagger.php on line 49



The error is below the displayed calendar.

Content_User_Manager as I can see is defined in the 
horde-hatchery/content clone, but there's no information where to 
include it manually...