Hi,

I have enabled this module in my website. Also I have configured this in vocabulary called "Role based access". Now I have field taxonomy field called Line of business. I getting the below attached js error while selecting the term on Line of business.

1. Role based access - Permission by term enabled
2. Line of business - Permission by term is not enabled with chosen enabled(Multi-value field)

How can we solve this issue?
Thanks

Comments

iyyappan.govind created an issue. See original summary.

iyyappan.govind’s picture

Priority: Normal » Major
iyyappan.govind’s picture

ccjjmartin’s picture

Version: 8.x-1.x-dev » 8.x-2.33

I agree that this bug a major problem with this module. It isn't actually caused by the autocomplete functionality though. After digging into this pretty deeply I found that the DomClient js is getting run twice, once for the taxonomy term reference field that I wanted to use permissions by term for and once for a taxonomy term reference field that I didn't want permissions by term to care about. The other term was using an inline entity reference field on the content types node form edit page and this module's JS was throwing a fit about it.

More details:
The JS is making a call out to the `/admin/permissions-by-term/access-info-by-content-type/{nodeType}` route and getting back all of the taxonomy term reference fields on a specific content type but this is where the issue really is. The gold standard here would be to have a site builder be able to configure which content types permissions by term is active for so that other vocabularies aren't forced to use certain compatible widgets.

Work around for now:
Change all of your taxonomy term reference field widgets into select lists or autocompletes, it is possible that checkboxes and radio buttons work too but I haven't tested this.

bstan’s picture

Our application ran into this issue. I created a patch based on the 3.1.x-dev branch and looks to be working