I have this module setup identically on a dev box and a production box. Over the last couple weeks, it appears that the production instance is failing to work properly, probably due to higher amount of content.

- First, nothing was being indexed past 42%
- I had to up the max index number from 500 to 2000
- Re-indexing got content back into search, COMPLETELY IGNORING SEARCH CONFIG NODE TYPE SETTINGS
- Advanced search form 'Node types' checkboxes WON"T DISPLAY ON SEARCH RESULTS PAGE
- I installed Util and upped the weight of Search config, but that is having no effect.

I also notice there is almost no maintainer feedback on this module since spring/summer.

Since this functionality is not included in core, as it should be, it behooves the maintainers to be more accessible, here. If not, then perhaps it is time to put out a call for some help.

I see a lot of 'critical' bugs in this queue not being fixed, or even responded to. Sorry, but this just forces people like me to hack core to get search to work the way it should.

I hope these issues can be remedied, soon.

Thanks.

Comments

ccshannon’s picture

ccshannon commented
Status: Active » Closed (fixed)

Sorry if I sound shrill. I read this back and thought 'that isn't the tone I intended to convey'. Apologies.

I think I will kill this post because I found this #565232: little bug in validate function and also now see the call for maintainer help.