Support archive

Conflict between Low Search and Entry Type

Keiron Lowe 6 May 2015 10:21 problem, active

I'm not sure which plugin is the issue, but Low Search and Entry Type don't seem to work well together. When they are both enabled I get errors on both the Publish/Edit and New Channel Field pages, it seems to be related to jQuery, so I tried enabling the jQuery module but it didn't fix the issue.

It looks like the control panel is requesting an file at '/index.php?S=fa7404b35bdd825d2331b40db76526fc&D=cp&C=javascript&M=load&package=low_search&file=EntryType' which is returning an error page saying jQuery cannot be found. Which then results in an error in the console saying 'Uncaught SyntaxError: Unexpected token >'

I get another error, which I believe is caused by the first error saying 'Uncaught ReferenceError: EntryTypeFieldSettings is not defined'.

As I said, I'm not sure which plugin is the issue, so I'm going to open an issue on the Entry Type github repo as well.

Cheers!

Replies

1. Stephen 6 May 2015 15:03

   I've just noticed this issue too with EE 2.9.3 and Low Search 4.2.0.
   
   I'm seeing the following error on Publish Pages that use the Category Field add-on in the Google Chrome web inspector (the Category Field add-on works fine and without any errors when Low Search is not installed):
   
   
Uncaught SyntaxError: Unexpected token <
Double-instantiating a context menu on an element
index.php?S=0108b8216907a0a82deaf27d2b867857&D=cp&C=javascript&M=load&package=low_search&file=categ...:1
garnish-0.1.js:206

   
   And this is causing a follow-on issue with the Category Field add-on:
   
   
Uncaught TypeError: $(...).categoryField is not a function
index.php?/cp/content_publish/entry_form&channel_id=3&S=0108b8216907a0a82deaf27d2b867857:2312

   
   Disabling the Low Search extension stops the error from happening.
   
   Thanks,
   
   Stephen

2. Low 6 May 2015 15:40

   Can you try enabling the extension and then running this query:
   
   

   UPDATE exp_extensions 
    SET enabled = 'n' 
    WHERE class = 'Low_search_ext' 
    AND method = 'custom_field_modify_data';

   
   
   Does that remove the error?

3. Stephen 6 May 2015 15:59

   Hi Low,
   
   Yes, that fixes it for me.
   
   Thanks,
   
   Stephen

4. Keiron Lowe 8 May 2015 09:38

   Thanks Low, that worked for me!

5. Low 8 May 2015 11:26

   OK. I'm thinking I need to remove that hook. The benefits don't weigh up to the down sides.