Unable to change/set Use an exisitng view -> AJAX errors [#2475687]

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: http://www.r-collectie.ugent.be/views/autocomplete
StatusText: OK
ResponseText: {"all_researchers_overview":"All-researchers-overview","free_storage_locations_biomat":"Free storage locations biomat","free_storage_locations_dna":"Free storage locations DNA","free_storage_locations_isolate":"Free storage locations isolate","free_storage_locations_primer":"Free storage locations primer","entityreference_view_widget_sample":"Entiy Reference View Widget Sample View"} Page execution time was 401.87 ms. Memory used at: devel_boot()=3.32 MB, devel_shutdown()=41.01 MB, PHP peak=41.25 MB.

http://www.r-collectie.ugent.be/views/autocomplete
gives empty page with []

So i think its because there are no custom JSON views yet.
But the nodes_autocomplete option does work so there is already at leased 1 valid JSON view
So there is something wrong here.

Comment	File	Size	Author
#14	http200-error-02.png	170.53 KB	mjrodriguez
#14	http200-error-01.png	205.53 KB	mjrodriguez
#7	jquery_update.png	17.96 KB	Dom.
#7	works_properly.png	3.86 KB	Dom.
#6	Schermafdruk van 2015-05-06 09:35:33.png	349.29 KB	ikeigenwijs
#6	Schermafdruk van 2015-05-06 09:35:16.png	365.42 KB	ikeigenwijs
#4	Schermafdruk van 2015-04-22 13:28:42.png	390.63 KB	ikeigenwijs
#4	json_view.txt	13.96 KB	ikeigenwijs

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Dom. CreditAttribution: Dom. commented 22 April 2015 at 08:02

Issue summary:

View changes

Hi !
http://www.r-collectie.ugent.be/views/autocomplete is a custom view you created yourself, it does not sound like one of the default view of this module. This views has to use the JSON Autocomplete output style and configure properly its settings. Can you confirm you did, and if yes, screenshot this ?

Comment #2

ikeigenwijs CreditAttribution: ikeigenwijs commented 22 April 2015 at 08:59

I added an extra view with display of the type JSON

The auto complete still fails and gives different AJAX errors.

Important to know its an Entity reference field.

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: http://www.r-collectie.ugent.be/views/autocomplete
StatusText: OK
ResponseText: [] Page execution time was 713.22 ms. Memory used at: devel_boot()=3.32 MB, devel_shutdown()=41.02 MB, PHP peak=41.5 MB.

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: http://www.r-collectie.ugent.be/views/autocomplete
StatusText: OK
ResponseText: {"usi_user_id":"USI_User_id","usi_zap_user_id":"USI_ZAP_User_id","usi_project_id":"USI_project_id","usi_collection_id":"USI_collection_id","all_collections_overview":"All-collections-overview","all_projects_overview":"All-projects-overview","all_researchers_overview":"All-researchers-overview","all_zaps_overview":"All-zaps-overview","all_faq_overview":"All-faq-overview","all_primers_overview":"All-primers-overview","all_dna_overview":"All-DNA-overview","all_biomats_overview":"All-biomats-overview","assign_r_numbers_to_isolates":"Assign R-numbers to isolates","field_collection_view":"field collection view","list_of_taxonomy_terms":"List of taxonomy terms","storage_locations_dna":"Storage locations DNA","storage_locations_isolate":"Storage locations isolate","storage_locations_primer":"Storage locations primer","storage_locations_biomat":"Storage locations biomat","free_storage_locations_biomat":"Free storage locations biomat","free_storage_locations_dna":"Free storage locations DNA","free_storage_locations_isolate":"Free storage locations isolate","free_storage_locations_primer":"Free storage locations primer","assign_storage_location_to_isolates":"Assign storage location to isolates","assign_storage_location_to_dna":"Assign storage location to DNA","assign_storage_location_to_biomats":"Assign storage location to BioMats","assign_storage_location_to_primers":"Assign storage location to primers","all_containers_overview_per_collection":"All-containers-overview-per-collection","modify_field_biomat":"Modify field BioMat","modify_field_dna":"Modify field DNA","modify_field_primer":"Modify field primer","modify_field_isolate":"Modify field isolate","modify_storage_location_biomat":"Modify storage location biomat","modify_storage_location_isolate":"Modify storage location isolate","modify_storage_location_primer":"Modify storage location primer","modify_storage_location_dna":"Modify storage location DNA","add_filter_tag_isolate":"Add filter tag isolate","add_filter_tag_dna":"Add filter tag DNA","add_filter_tag_biomat":"Add filter tag BioMat","add_filter_tag_primer":"Add filter tag primer","all_isolates_overview":"All-isolates-overview","link_isolate_to_biomat":"link-isolate-to-biomat","link_dna_to_isolate":"link-dna-to-isolate","storage_location_per_isolate":"Storage location per isolate","storage_location_per_dna":"Storage location per DNA","storage_location_per_primer":"Storage location per primer","storage_location_per_biomat":"Storage location per BioMat","search_storage_location_isolates":"Search storage location isolates","search_storage_location_dna":"Search storage location DNAs","search_storage_location_primers":"Search storage location primers","search_storage_location_biomats":"Search storage location BioMats","admin_views_comment":"Administration: Comments","admin_views_node":"Administration: Nodes","admin_views_taxonomy_term":"Administration: Taxonomy terms","admin_views_user":"Administration: Users","archive":"Archive","comments_recent":"Recent comments","entityreference_view_widget_sample":"Entiy Reference View Widget Sample View","feeds_log":"Feeds log","frontpage":"Front page","nodes_autocomplete":"nodes-autocomplete","popular":"Popular content","taxonomy_term":"Taxonomy term","tracker":"Tracker","users_autocomplete":"users-autocomplete","words_autocomplete":"words-autocomplete"} Page execution time was 560.21 ms. Memory used at: devel_boot()=3.32 MB, devel_shutdown()=41.02 MB, PHP peak=41.5 MB.

Comment #3

Dom. CreditAttribution: Dom. commented 22 April 2015 at 09:33

Please see comment #1 for expected details. Alternatively, you can export me your view.

Comment #4

ikeigenwijs CreditAttribution: ikeigenwijs commented 22 April 2015 at 11:43

File	Size
json_view.txt	13.96 KB
Schermafdruk van 2015-04-22 13:28:42.png	390.63 KB

I did not see your comment, i did not refresh until now.
So as answer to #1:
I did not make or configure a view that uses the http://www.r-collectie.ugent.be/views/autocomplete url
That came there from its own accord after installing this module

when i Start typing in the Use an existing view auto complete field on the settings page of the
admin/config/search/search_autocomplete/32/configure page

i directly get the AJAX error mentioned in #3
And there in responseText i see a list of view names

The exported view in attachment
the json display is not the first display of the view, maybe that is a problem?

Comment #5

Dom. CreditAttribution: Dom. commented 4 May 2015 at 18:53

Do you eventually use jquery update mod ule ? I have not been able to reproduce your issue yet.
Can you fully uninstall the module and reinstall it ?

Comment #6

ikeigenwijs CreditAttribution: ikeigenwijs commented 6 May 2015 at 07:35

File	Size
Schermafdruk van 2015-05-06 09:35:16.png	365.42 KB
Schermafdruk van 2015-05-06 09:35:33.png	349.29 KB

We do use Jquery update module.
with jquery version 1.10 configured.

I re installed with devel
Reconfigured a text field to auto search

Same issue and again the strange autocomplete url
2 consecutive errors
I made a screenshot of eatch.
Is there anything i can do to help debug?

Comment #7

Dom. CreditAttribution: Dom. commented 6 May 2015 at 08:15

File	Size
works_properly.png	3.86 KB
jquery_update.png	17.96 KB

Hi !
I'm sorry, still unable to reproduce with jQuery 1.10.

Comment #8

ikeigenwijs CreditAttribution: ikeigenwijs commented 6 May 2015 at 19:05

hmm, i could create an account and give you access to the site if that would help.
there is a large module list.
There are no messages in watchdog

Comment #9

ikeigenwijs CreditAttribution: ikeigenwijs commented 9 June 2015 at 14:55

@ Dom any ideas what else it could be or how i could debug.
i have profiler and xdebug on localhost

Comment #10

dakku CreditAttribution: dakku as a volunteer commented 15 July 2015 at 08:33

I was having the same issue last night. Switched back to 7.x-4.2 until i can debug and fix the issue.

Comment #11

Dom. CreditAttribution: Dom. commented 17 July 2015 at 15:15

Have you tried 4.6 ?

Comment #12

dakku CreditAttribution: dakku as a volunteer commented 17 July 2015 at 15:43

It was an issue when i had devel enabled. Turned devel off and we are good. no issue with module :)

seems like ikeigenwijs also has devel enabled. This is what he posed above

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: http://www.r-collectie.ugent.be/views/autocomplete
StatusText: OK
ResponseText: [] Page execution time was 713.22 ms. Memory used at: devel_boot()=3.32 MB, devel_shutdown()=41.02 MB, PHP peak=41.5 MB.

Comment #13

Dom. CreditAttribution: Dom. commented 17 July 2015 at 15:46

Status:

Active

» Closed (works as designed)

Oh... I missed that... Thanks a lot dakku !

Comment #14

mjrodriguez CreditAttribution: mjrodriguez commented 26 November 2015 at 14:40

Status:

Closed (works as designed)

» Active

File	Size
http200-error-01.png	205.53 KB
http200-error-02.png	170.53 KB

Hi!
I haven't installed devel and im getting a very similar issue:

Se produjo un error HTTP AJAX.
Código de Resultado HTTP: 200
A continuación se detalla la información de depuración.
Ruta: http://localhost/geba/?q=search/user
StatusText: OK
ResponseText: 

Buscar | GEBA

@import url("http://localhost/geba/modules/system/system.base.css?nyf97f");
@import url("http://localhost/geba/modules/system/system.menus.css?nyf97f"); ....

I feel it's so close to work... help?

Escriba las palabras clave. 
Search Results

waldemar

martin

As you can see, in the screen capture
First part
Last part

The error in the popup window appears everytime I press a key in the autocomplete field.
What bugs me is that, if you see the code, the correct results are there...

I installed the module as is, and it's not using any custom view.

The code for the form is:

            $form['socio'][0] = array(
                '#type' => 'textfield',
                '#id' => 'socio_0',
                '#title' => t('Player 1'),
                '#size' => 30,
                '#maxlength' => 60,
                '#autocomplete_path' => 'search/user',
                '#default_value' => $username,
              );

Comment #15

grahamvalue CreditAttribution: grahamvalue commented 4 April 2018 at 13:16

Hi,

Thanks for a great module!

Not sure if this is related.

By default, the autocomplete on the search page is configured to use the view "words_autocomplete" and the one on the search block is configured to "nodes_autocomplete".

However, both autocompletes behave exactly the same.
When the "nodes_autocomplete" view is modified, it affects both autocompletes.

Is that normal behavior?
What is the purpose of "words_autocomplete"?

Thanks again!

Comment #16

Dom. CreditAttribution: Dom. commented 19 October 2018 at 18:25

Status:

Active

» Closed (works as designed)

nodes_autocomplete is looking at node titles => you should just get nodes which title includes what you are looking for.
words_autocomplete work pretty like the search page looks for words within the content => you should get nodes containing your search within the body content.

Comment #17

grahamvalue CreditAttribution: grahamvalue commented 20 October 2018 at 21:22

Status:

Closed (works as designed)

» Active

Got that but it doesn't seem to work that way.

Please check the previous comment.

Both forms seem to work the same regardless of having different views set.

Words within the content are ignored during searches even when the search form is set to use the words view.

The search is always by title.

Can open a new issue if this problem is unrelated to this issue.

Thanks!

Comment #18

Dom. CreditAttribution: Dom. as a volunteer and commented 21 October 2018 at 09:33

Status:

Active

» Closed (cannot reproduce)

I am sorry, but I cannot reproduce using the latest 4.9 version.
I have two different views nodes-autocomplete and words-autocomplete that are perfectly separated. In words view the exposed filter is "body". In nodes view, the exposed filter is "title".

I have a node which title is "test" and content "foobar".

In the search autocomplete config page, if I set the "search block" to use the nodes view. When trying to enter "tes" in the search box, I get the "test" node appear. If I input "foo" I get nothing.
Then back to configuration, I now change "search block" to use "words" view. When trying to enter "tes" in the search box, I get nothing. If I input "foo" I get "is contained in : test".

Everything looks normal to me. If the issue persist, could you please open a new issue, and indicate a clear reproduction scenario ? I guess you messed up with the views, updating the wrong ones or using custom poorly configured views... ?