That is because of jQuery's changes ..
jQuery.browser (http://api.jquery.com/jQuery.browser/)
Description: Contains flags for the useragent, read from navigator.userAgent.
This property was removed in jQuery 1.9 and is available only through the
jQuery.migrate plugin. Please try to use feature detection instead.
Those plugins (like autocomplete, for example) normally have version
dependencies to jQuery .. to ensure their functionality
-Stefan
On Thursday, September 26, 2013 at 2:50 PM, JMill wrote:
> I managed to get rid of the query error by playing jquery file in the
> velocity folder and adding line: "<script type="text/javascript"
> src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
> That has not solved the issues the console is showing a new error -
> "[13:42:55.181] TypeError: $.browser is undefined @
> http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90";.
> Any ideas?
>
>
> On Thu, Sep 26, 2013 at 1:12 PM, JMill <apprentice...@googlemail.com
> (mailto:apprentice...@googlemail.com)> wrote:
>
> > Do you know the directory the "#{url_root}" in <script
> > type="text/javascript" src="#{url_root}/js/lib/
> > jquery-1.7.2.min.js"></script> points too? and same for ""#{url_for_solr}"
> > <script type="text/javascript"
> > src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
> >
> >
> > On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
> > jlbetanco...@uci.cu (mailto:jlbetanco...@uci.cu)> wrote:
> >
> > > Try quering the core where the data has been imported, something like:
> > >
> > > http://localhost:8983/solr/suggestions/select?q=uc
> > >
> > > In the previous URL suggestions is the name I give to the core, so this
> > > should change, if you get results, then the problem could be the jquery
> > > dependency. I don't remember doing any change, as far as I know that js
> > > file is bundled with solr (at leat in 3.x) version perhaps you could
> > > change
> > > it the correct jquery version on solr 4.4, if you go into the admin panel
> > > (in solr 3.6):
> > >
> > > http://localhost:8983/solr/admin/schema.jsp
> > >
> > > And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
> > > loaded in solr 4.4 it should load a similar file, but perhaps a more
> > > recent
> > > version.
> > >
> > > Perhaps you could change that part to something like:
> > >
> > > <script type="text/javascript"
> > > src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
> > >
> > > Which is used at least on a solr 4.1 that I have laying aroud here
> > > somewhere.
> > >
> > > In any case you can test the suggestions using the URL that I suggest on
> > > the top of this mail, in that case you should be able to see the possible
> > > results, of course in a less fancy way.
> > >
> > > ----- Mensaje original -----
> > > De: "JMill" <apprentice...@googlemail.com
> > > (mailto:apprentice...@googlemail.com)>
> > > Para: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org)
> > > Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
> > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > columns)
> > >
> > > Could it be the jquery library that is the problem? I opened up
> > > solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
> > > the jquery library but I can't seem to find the directory referenced,
> > > line: <script type="text/javascript"
> > > src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
> > > "#{url_for_solr}" points to?
> > >
> > >
> > > On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> > > jlbetanco...@uci.cu (mailto:jlbetanco...@uci.cu)> wrote:
> > > > Perhaps this could be an issue, I know that this works perfectly in solr
> > >
> > > 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
> > > some tests, but what have been done in that core should work in solr 4.4,
> > > perhaps there is a setting that need some tweaking but it's impossible of
> > > knowing without checking the logs. In case that any incompatibility is
> > > present it should pop out on the logs.
> > > >
> > > > Regards,
> > > >
> > > > ----- Mensaje original -----
> > > > De: "JMill" <apprentice...@googlemail.com
> > > > (mailto:apprentice...@googlemail.com)>
> > > > Para: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org)
> > > > Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
> > > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > >
> > >
> > > columns)
> > > >
> > > > I simple query through admin (*:*) confirms the data is exists. The
> > > version
> > > > I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
> > > > wonder of this is the problem?
> > > >
> > > >
> > > > On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
> > > > jlbetanco...@uci.cu (mailto:jlbetanco...@uci.cu)> wrote:
> > > >
> > > > > The response does not show any error, can you confirm that the data is
> > > in
> > > > > solr? you should be able to see the numDoc stats in the admin UI.
> > > > > Which
> > > > > version of Solr are you using? I believe that the example was tested
> > > > > on
> > > > > Solr 3.x at least at the time I use it.
> > > > >
> > > > > Regards,
> > > > >
> > > > > ----- Mensaje original -----
> > > > > De: "JMill" <apprentice...@googlemail.com
> > > > > (mailto:apprentice...@googlemail.com)>
> > > > > Para: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org)
> > > > > Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
> > > > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > > >
> > > >
> > >
> > > columns)
> > > > >
> > > > > I followed the instructions, I am able to browse to "
> > > > > http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true"; but I am
> > > > >
> > > >
> > >
> > > not
> > > > > getting any suggestions (typed in c in Find Textbox).
> > > > >
> > > > > I wonder if loading the example data is the problem? The response I
> > > get
> > > > > after executing the script "feed-ac.sh (http://feed-ac.sh)" (step 3)
> > > > > is the following.
> > > > >
> > > > > user$ ./feed-ac.sh (http://feed-ac.sh)
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <response>
> > > > > <lst name="responseHeader"><int name="status">0</int><int
> > > > > name="QTime">2239</int></lst>
> > > > > </response>
> > > > >
> > > > > Are you able to confirm if this the expected response?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
> > > > > jlbetanco...@uci.cu (mailto:jlbetanco...@uci.cu)> wrote:
> > > > >
> > > > > > I've used a separated core for storing suggestions, based on what I
> > > see
> > > > > > in: https://github.com/cominvent/autocomplete. You can check the
> > > > >
> > > >
> > >
> > > blog
> > > > > > post on
> > > > > > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/
> > > > > > (http://www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/).
> > > > > > This is really flexible, on the downside it does not use the
> > > > > >
> > > > >
> > > >
> > >
> > > suggester
> > > > > > component su this are like regular queries against a separated core.
> > > > > >
> > > > > > Greetings!
> > > > > >
> > > > > > ----- Mensaje original -----
> > > > > > De: "Erick Erickson" <erickerick...@gmail.com
> > > > > > (mailto:erickerick...@gmail.com)>
> > > > > > Para: solr-user@lucene.apache.org
> > > > > > (mailto:solr-user@lucene.apache.org)
> > > > > > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> > > > > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > > > >
> > > > >
> > > > > columns)
> > > > > >
> > > > > > I've sometimes seen this handled by clever tokenizing. For "Bill
> > > Rogers",
> > > > > > index (untokenized) something like
> > > > > > Bill|Bill Rogers
> > > > > > Rogers|Bill Rogers
> > > > > >
> > > > > > Your suggester then is a simple term lookup (see TermsComponent)
> > > > > > which is quite fast. What you _don't_ get is autocorrect. But if you
> > > > > > use terms.prefix, you can also control whether it's whole word match
> > > > > > or not. To get whole-word in the above, you would set your prefix to
> > > > > > "Rogers|" for instance. Or you may want to leave off the "|" to see
> > > > > > more of an autocomplete-type response.
> > > > > >
> > > > > > Then, of course, when you display this you need to only display
> > > what's
> > > > > > after the "|" (or whatever delimiter you use).
> > > > > >
> > > > > > One other note, this will be case sensitive, so you probably want to
> > > > > > do casing yourself, index things like
> > > > > > rogers|Bill Rogers
> > > > > > and lowercase what you send in to terms component.
> > > > > >
> > > > > > Best,
> > > > > > Erick
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
> > >
> > >
> > > ________________________________________________________________________________________________
> > > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > > del 2014. Ver www.uci.cu (http://www.uci.cu)
> > >
> > >
> > > ________________________________________________________________________________________________
> > > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > > del 2014. Ver www.uci.cu (http://www.uci.cu)
> > >
> >
> >
>
>
>
