With the setting "Allow new terms" enabled, I still can't add new terms using Autocomplete Deluxe. When I type the new term, I don't get a message saying "The term '@term' will be added". Instead, the blue loading symbol keeps turning. When I click save, I get an error message saying that the referenced entity does not exist. It's as if the field was configured to not accept new terms through the node form, but that option is enabled.

I cannot reproduce this on https://simplytest.me/, though.

CommentFileSizeAuthor
#8 autocomplete_deluxe_8_1_0_beta1_fix_js_protocol_01.patch1004 bytesbrtamas
#4 autocomplete_url_relative-2935363-4.patch1.29 KBmkolar
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

yan created an issue. See original summary.

brooke_heaton’s picture

brooke_heaton CreditAttribution: brooke_heaton commented

Yep. Happens to me on Drupal 8.4. Same error.

mkolar’s picture

mkolar CreditAttribution: mkolar at Ciklum Western Europe for BurdaForward commented

we have same problem..

mkolar’s picture

mkolar CreditAttribution: mkolar at Ciklum Western Europe for BurdaForward commented
FileSize
autocomplete_url_relative-2935363-4.patch1.29 KB

This fixes my problem, Drupal which is behind load balancer which is https. I think this is somehow related to using of reverse proxy with https. Its not my cup of tea so dont know it deeply. This patch is sending relative url to the js and there is converted in javascript via Drupal.url.

extect’s picture

extect CreditAttribution: extect commented
Status: Active » Needs review

Make sure you have checked the option "Create referenced entities if they don't already exist" in the settings of your taxonomy (entity) reference field. This should solve your issue.

mkolar’s picture

mkolar CreditAttribution: mkolar as a volunteer commented

@extect this was checked of course. If i remember correctly this is an issue when you have client accessing load balancer via https and multiple nodes behind it without https.

brooke_heaton’s picture

brooke_heaton CreditAttribution: brooke_heaton commented

RE #5 - I think the field settings might want to check that, rather than the user. Just to fool proof the widget.

brtamas’s picture

brtamas CreditAttribution: brtamas at Integral Vision Ltd commented
FileSize
autocomplete_deluxe_8_1_0_beta1_fix_js_protocol_01.patch1004 bytes
daveiano’s picture

daveiano
Primary language German
CreditAttribution: daveiano as a volunteer commented

Patch from #4 works for me.

This also resolves a problem with mixed content for a HTTPS site for me.

quixxel’s picture

quixxel CreditAttribution: quixxel commented

Same here. Patches are not working for me.
Drupal 8.7.7

quixxel’s picture

quixxel CreditAttribution: quixxel commented

Anything new here?
It would be great to get this wonderfull module working as expected...

edwardchiapet’s picture

edwardchiapet
Location New York, NY
CreditAttribution: edwardchiapet at Mediacurrent commented

Thanks, everyone! @mkolar's patch works and will merge that into 8.x-1.x-dev.

A new release will be forthcoming that will include all the updates currently in 8.x-1.x-dev.

  • edwardchiapet committed 7f5495e on 8.x-1.x authored by brtamas 
    Issue #2935363 by mkolar, brtamas, brooke_heaton, yan, extect, daveiano...
edwardchiapet’s picture

edwardchiapet
Location New York, NY
CreditAttribution: edwardchiapet at Mediacurrent commented
Status: Needs review » Reviewed & tested by the community
edwardchiapet’s picture

edwardchiapet
Location New York, NY
CreditAttribution: edwardchiapet at Mediacurrent commented
Status: Reviewed & tested by the community » Fixed

  • edwardchiapet committed f687db2 on 8.x-1.x authored by brtamas 
    Issue #2935363 by mkolar, brtamas, edwardchiapet, yan, brooke_heaton,...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.