Recently i have into the same issue. not usign createAndPublishObject though, but that shouldn' t be the problem.
in my case, the problem was that my content objects has some ezdate attributes, but i was not filling those attribs with any value. so, i was sending empty values to solr for those attrs and solr failed indexing those objects...
could this be the case?
the issue is reported and fixed by Paul at http://issues.ez.no/IssueView.php?Id=16365&activeItem=6
Thank you for the tip it can be the case here as my content class has multiple ezdate attributes and they are not mandatory. I am gonna try to fill those in to see what happens.
What i don't understand with ezfind is that it doesn't seems necessary to run indexation cronjobs, in fact when i publish content via the admin siteaccess objects are indexed even without cronjobs.
Does anybody know what those cronjobs are made for ?
Some other datatypes might give you the same problem. In the function addDocs in eZ find, ezsolrbase.php, check the string $updateResult. Solr will tell you there what the problem is.
As a solution, instead of filling al the date fields, you can also change the configuration in schema.xml, turning the date field into a text field within the dynamic field definitions, e.g:
Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.
Thanx a lot for this. I am running into multiple problems trying to run ezfind in production sites....usually small details making everything fall apart.
After content import i have a lot of warning and content indexation problems :
Undefined offset: 36760 in /$home/ezpublish-4.3.0_dev/extension/ezfind/search/plugins/ezsolr/ezsolr.php on line 814
Notice: PHP: E_NOTICE
Oct 05 2010 19:26:02
Undefined property: eZContentObject::$ClassID in /$home/ezpublish-4.3.0_dev/kernel/classes/ezpersistentobject.php on line 1224
Ending with hundreds of warning in my debug.
EZP is Great
You must be logged in to post messages in this topic!
