[ 
https://issues.apache.org/jira/browse/SOLR-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921517#comment-13921517
 ] 

Shawn Heisey commented on SOLR-5816:
------------------------------------

[~uchandra1],

Even without looking deeper, I can almost guarantee you that this is not a Solr 
problem, and certainly not one that requires opening a bug without discussion 
on the mailing list.  I see no evidence that you have attempted to do this.

Your first support contact should be for the Wordpress plugin.  The next 
support contact should be for the PHP Solr Client that the Wordpress plugin 
uses.

https://wordpress.org/plugins/advanced-search-by-my-solr-server/
http://code.google.com/p/solr-php-client/

Finally ... since you did not block access to your Solr server from the 
Internet, I was able to get into its admin UI and look at the Logging tab.  
Here's the error message in the most recent log entry:

org.apache.solr.common.SolrException: undefined field: "post_content_str"

The plugin is trying to query Solr using a field called post_content_str, but 
this field does not exist in your schema.  The solrconfig.xml and schema.xml 
look like they are unchanged from the example defaults.  The Wordpress plugin 
probably comes with new config and schema files, as well as instructions on 
installing them.  You haven't done that step.

I see that you have a post on the support forum for the Wordpress plugin.  As 
of right now, that post is only seven hours old.  They are the ones that will 
be able to help you with this problem.


> SOLR fetal error Fatal error: Uncaught exception 
> 'Apache_Solr_HttpTransportException' with message ''400' Status: Bad Request' 
> in 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/SolrPhpClient/Apache/Solr/Service.php:353
>  Stack trace
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5816
>                 URL: https://issues.apache.org/jira/browse/SOLR-5816
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - php
>    Affects Versions: 4.6
>         Environment: Live Server on wordpress application
> My SOLR Url:http://localhost:8085/solr/#/
> My Siteurl:http://108.166.87.229/AAB/?s=%242.25+and+under+1
>            Reporter: Umesh Chandra
>              Labels: Error, Fetal
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> My SOLR Url:http://108.166.87.229:8983/solr
> My Siteurl:http://108.166.87.229/AAB/?s=%242.25+and+under+1
> Fatal error: Uncaught exception 'Apache_Solr_HttpTransportException' with 
> message ''400' Status: Bad Request' in 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/SolrPhpClient/Apache/Solr/Service.php:353
>  Stack trace: #0 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/SolrPhpClient/Apache/Solr/Service.php(1241):
>  Apache_Solr_Service->_sendRawGet('http://localhos...') #1 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/solr.class.inc.php(126):
>  Apache_Solr_Service->search('$2.25 and under...', 0, '100', Array) #2 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/advanced-search-by-my-solr-server.inc.php(398):
>  Mss_Solr->search('$2.25 and under...', 0, '100', Array) #3 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/advanced-search-by-my-solr-server.php(745):
>  mss_query('$2.25 and under...', 0, '100', Array, '', Array) #4 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/template/mss_search.php(21):
>  in 
> /var/www/html/AAB/wp-content/plugins/advanced-search-by-my-solr-server/SolrPhpClient/Apache/Solr/Service.php
>  on line 353



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to