Hi,
i know that this is minor, but there is a 503 error thrown when i (user1) logout of my offline site to test the solr search http://mydomain.de/user on the login frontpage. See attached picture. This will only affect admins or developers i guess.

Using drupal 6.16 on debian.

i have to click the OK Button (solr_ac_error.jpg) 3 times before the error popup goes away.

Big thank you for this great module

Comments

janusman’s picture

Status: Active » Postponed (maintainer needs more info)

When you say "offline site", do you mean the site is in "Maintenance Mode"? I'm guesing that putting the site in offline mode prevents access to menu paths (URLs) that require the "access content" permission, such as this one (which looks like normal behaviour).

Also, check if your anonymous user role has the "access content" and "search content" permissions.

pimok3000’s picture

Yes,
i mean the site is in Maintenance Mode. I have checked "access content" and "search content" permissions for anonymous user and both are allowed. Still the search results in a 503 error when being logged out.

janusman’s picture

Then, that is *completely normal*. You in fact should not have access to any page in a Drupal site in maintentance mode when you are not logged in.

This just leaves the question:: if your are logged out, why are you seeing a search form in the first place? Is that on the "Site is under maintenance" page itself?

pimok3000’s picture

Hi, by now i found out that the 503 Error is always related to issues when site is in offline mode like this for example:

http://drupal.org/node/445008#comment-1556282

So going to www.mydomain.se/user shows the user login eve in maintenance mode, which is good and as i think is intended to be exactly that way?!

And there i have enabled anon users to have the ability to search because i didn´t know that some modules don´t work flawlessly in offline mode. Of course you are right this really is minor and not the way it "should" be, but as there is the possibility to develop the whole site in offline mode (what i do)so i thought i´d save this issue for the after world, because it seems that i am not the only one wondering about 503 errors and not knowing that these are 100% offline issues.

janusman’s picture

Try this: in apachesolr_autocomplete.module, change this line in apachesolr_autocomplete_menu():

'access arguments' => array('access content'),

to this:

'access arguments' => array('search content'),

Then clear ALL of Drupal caches (admin/settings/performance), restart your browser, and try seeing if the error dissappears.