in the script updatesearchindexsolr.php, I've found the following lines (starting from line number 569):
protected function changeSiteAccessSetting( $siteaccess )
{
global $isQuiet;
$cli = eZCLI::instance();
if ( !file_exists( 'settings/siteaccess/' . $siteaccess ) )
{
if ( !$isQuiet )
$cli->notice( "Siteaccess $optionData does not exist, using default siteaccess" );
} }
It tests if the siteaccess exists under the settngs/siteaccess/ folder.But my siteaccess is under the extension/ folder.
The extension (relative to my website) is activated, and everything but ezfind works properly.
I thought that at runtime, the 'settings' folders of the activated extensions were kind of joined together...am I wrong? Is there a way to tell updatesearchindexsolr.php that it should look in the extension folder as well?
Where do I see how the update is called when a new content is added or a content is modified? Since that works, I should call the updatesearchindexsolr script in that same way.
Yes, this is a pain. One way around this is to add a symbolic link in settings/siteaccess/ to your extension siteaccess. I logged this as an issue last year - http://issues.ez.no/IssueView.php?Id=13850&activeItem=4