Update the add-on, that appears to be from a very old version.Hello. I am having problems with the addon on xf v2.2.13
- XF2.3.8 compatibility fix
- Adjust
Collect search DSL & debug statisticsso Log & show on search results only displays to members by defaults and not guests.
I just downloaded the update you uploaded and this was from after thatUpdate the add-on, that appears to be from a very old version.
Please post the actual stack trace and not a truncated screenshot of it, and when reporting please include what version of the add-on it is with.I just downloaded the update you uploaded and this was from after that
select content_type,field_value,addon_id
from xf_content_type_field
where field_name = 'search_handler_class' and content_type in ('conversation','conversation_message');
Please post the actual stack trace and not a truncated screenshot of it, and when reporting please include what version of the add-on it is with.
Do you have Conversation Improvements installed? Or did you uninstall it at some point.
Can you run this SQL query? I need to see the search types list for your site.
SQL:select content_type,field_value,addon_id from xf_content_type_field where field_name = 'search_handler_class' and content_type in ('conversation','conversation_message');
No rows.Please do a rebuild of the add-on, this should re-add the missing rowsI can however see that something like that exists
View attachment 332772
- Improve XF Cloud support
- Fix sorting by a custom elasticsearch field didn't work as expected when using
SearchOrderclass (ie Report Improvements and sorting reports by comment count)
indexing.index_time_in_millis and indexing.index_total the average is being computed very simply but it is using the XF number formatting which truncates the decimal places.{{ parens(phrase('xfes_x_milliseconds_average', {'time': number($esStats.indexing.index_time_in_millis / $esStats.indexing.index_total)})) }}
number() to include some decimal places.
- Require StandardLib v1.23.0+
- php 8.4+ compatibility fixes
- Fix Ticket's reply-count range search criteria into search page didn't work
- Ensure injecting participants search for Tickets keeps working if the macro syntax is updated
- Compatibility update for upcoming Content Ratings v2.9.0+
- Workaround "Maximum writeset size exceeded" SQL error when pruning search results
- Add
Maximum number of search/find new results for guestsoption
- Initialized to the same value as "Maximum number of search/find new results"
We use essential cookies to make this site work, and optional cookies to enhance your experience.