Also, in this case, you can put in that configuration file the following
option:
'extension_class_paths' => dirname(__FILE__).'/Shindig',
this way, you don't need to copy the PHP files from c:\wamp\www\partuza\Shindig
to the shindig tree - this should make the installation easier.
2008/8/14, Erel Segal <[EMAIL PROTECTED]>:
>
> P.S. maybe it would be easier to put the "local.php" configuration file in
> the Partuza SVN tree, and put the following content in
> shindig/php/config/local.php:
>
> <?php
> require(dirname(__FILE__).'/../../../partuza/local.php');
> ?>
>
> It is more natural to put Partuza's configuration in Partuza's svn tree -
> this way it will be automatically updated when Partuza is changed.
>
>
>
> 2008/8/14, Erel Segal <[EMAIL PROTECTED]>:
>>
>> I followed the Partuza installation guide on:
>> http://www.chabotc.com/guides/partuza_install/
>>
>> Under "Setting up Shindig for Partuza" it says:
>> " you need to copy the files you want to use to one of it's directories
>> it scans for PHP classes (i always prefer the shindig\php\src\socialdata
>> directory since it makes the most sense),"
>> However, there is currently no such directory.
>>
>> Later it says:
>> "First copy the 2 PHP files from c:\wamp\www\partuza\Shindig"
>> but there are 4 PHP files there.
>>
>> Later it says:
>> "edit shindig's configuration by opening the
>> c:\wamp\www\shindig\php\config.php file"
>> but currently the configuration is in
>> c:\wamp\www\shindig\php\config\local.php.
>>
>> Later it says:
>> "And change the *'handlers' => ''* configuration to read *'handlers' =>
>> 'PartuzaHandler',"
>> but currently there are other configuration options to use:
>> 'people_service' => 'PartuzaPeopleService',
>> 'activity_service' => '**Partuza**ActivitiesService',
>> 'app_data_service' => '**Partuza**AppDataService',
>> 'messages_service' => '**Partuza**MessagesService',
>>
>>
>> *
>>
>
>
