I can't explain it.
Fatal error: Cannot access empty property in /home/mothersclick/web/public/html/sites/all/modules/contrib/apachesolr/SolrPhpClient/Apache/Solr/Response.php on line 225

happens on our QA server, but not on my local. I am sure its a config error, I just don't what that error is. Any ideas are appreciated.

The property isn't empty, i print_r() it and it clearly has the data. Im really confused...

Comments

JacobSingh’s picture

JacobSingh commented

I'm guessing it has something to do with the multi-site stuff.

One non-documented but pretty important bug / feature is that we create all documents with a hash of your domain name, so if you wanted to combine the indexes of two sites, you could do so.

The problem is, if you change the domain name, it screws up. We actually need to provide someway to allow the user to override the default hash so that this doesn't happen.

try re-indexing on a separate "QA" instance of Solr, and it should fix it.

Let me know what you find out.

Best,
Jacob

Scott Reynolds’s picture

Scott Reynolds commented

So ok I see what your saying.

But this is a fresh index, isn't migrated from anywhere nor shared with anyone. Furthermore, I noticed there is a way to provide a default hash 

  if (!($hash = variable_get('apachesolr_site_hash', FALSE))) {

but even providing a default hash didn't seem to work...

JacobSingh’s picture

JacobSingh commented

Hi Scott,

I looked at the line, and it appears you are trying to access some property that doesn't exist... not sure what is going on. Try getting a backtrace. Do you use xdebug? This would probably help identify what part of apachesolr.module is calling for it.

Best,
J

pwolanin’s picture

pwolanin commented

Could be that the schema.xml or solrconfig.xml is not up to date on the Solr server?

Checkout the HEAD of the CVS DRUPAL-6--1 branch and try that code - you'll need to re-index all content after putting the new xml files on the server.

Scott Reynolds’s picture

Scott Reynolds commented

Ya im closing this. I am not seeing it on our new QA servers. Its terribly strange. Can't reproduce it anywhere. Its a configuration problem. Not sure how I managed to pull that off...

Scott Reynolds’s picture

Scott Reynolds commented
Status: Active » Closed (fixed)
abqaria’s picture

abqaria commented

i just installed acquia search for drupal 6

my site is not completely indexed yet

i get same error

Fatal error: Cannot access empty property in /var/www/vhosts/i-bloggers.com/httpdocs/sites/all/modules/apachesolr/SolrPhpClient/Apache/Solr/Response.php on line 239

i have only one site running on this ip and instance

aangel’s picture

aangel commented

Me too, new install, latest of everything.

cfennell’s picture

cfennell commented

I'm in the process of upgrading my site from D5-D6, and while my new D6 instance on my test machine works just fine, it fails in the same way that Scott describes on my QA instance. I ran a fresh index on the QA server, no dice. I'm kind of at a loss as to what to try next. I'm running PHP 5.1.6 on RHEL5, 6.x-1.x-dev w/ the -r22 solr client on the QA server (with the JSON Pecl extension enabled), fwiw.

cfennell’s picture

cfennell commented

Er, 6.x-2.x-dev, that is.

cfennell’s picture

cfennell commented

Ok, found my problem: http://drupal.org/node/465528#comment-1903476

I had a "Filter by Organic Group" block enabled on a machine running the PECL JSON extension in lieu of PHP 5.2's native support. See the comment above for more information about the differing JSON handling behavior of PHP 5.2, the Zend JSON class and (I can now confirm) the PECL extension.

Gah, RHEL is making me crazy w/it's crummy support for PHP.