Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: low search indexes

Status Resolved
Add-on / Version Publisher Low Search 4.4.4
Severity
EE Version 2.11.3

Cameron Ross

Jul 18, 2017

Hi
Description:
There is an issue with the Publsher low search module
It doesn’t index all the values
I contacted low low search and they disabled the Publsher low search module and indexed and all values were indexed
But with the module enabled it only indexed (saved to index db table)  the first batch , 25 records
It doesn’t index the remaining batches


Detailed steps to reproduce the issue:

I have a channel called glossary and a collection for this channel

There are 450 entries

I build the collection it says 450 items) 

All is good

I run this and the result it returns only 25 results

SELECT * FROM `exp_low_search_indexes` where collection_id = 13

 

I think this why my search is not finding my titles

Any idea why the all 450 might not be added to the index table

Low search say that the first batch is only being indexed

 

#1

BoldMinded (Brian)

Cameron, I’m not sure why its not working, but this is a deprecated product since its for EE2. I’ll be working on porting it to EE3 in the coming weeks, and if I find anything that I can back port to the EE2 version then I’ll do so, but I won’t be looking into this for EE2 specifically.

#2

Cameron Ross

hmmmm not much help as we are using some of your other ad don extensions like the nav ee one and th low search

Both of these are not ready for ee 3 and so cant update until they are ready

So in the mean time we are stuck with a search that does work properly and the search is a huge part of the website

#3

BoldMinded (Brian)

Are you seeing any PHP errors in your log or in the ajax requests that LS is making when updating the indexes? If its stopping at a certain point it could be a memory or the execution time was reached. Perhaps try increasing max_execution_time and memory_limit in your php.ini to see if that makes a difference.

I could look into this but if I don’t spot the issue in 15-30 minutes then I may need to charge an hourly rate to fix it. I’m not trying to nickel and dime… just trying to move past EE2.

#4

Cameron Ross

Comment has been marked private.

#5

BoldMinded (Brian)

I wouldn’t be able to do anything without FTP access. I’d have to step through the code to see where its breaking down. Is this a site you could zip up and send a .sql dump with it so I can run it locally?

#6

BoldMinded (Brian)

I haven’t heard back in over a month, so closing this ticket. If you can provide the information requested just re-open the ticket and I’ll look into it.

Login to reply