Very interesting! I enabled J! debug mode on a few of my J! 4.4.2 test sites, used the smart search feature, and I see these errors, too!
I then compared with a J! 4.1.5 test site; I enabled J! debug mode and used the smart search module. There was no problem with doing that. Therefore something has changed between J! 4.1.x (at least) and J! 4.4.x. In my opinion, this is a bug and it should be reported to the J! development team. Unfortunately, the Issue Tracker is broken and I cannot report this error.
I then compared with a J! 4.1.5 test site; I enabled J! debug mode and used the smart search module. There was no problem with doing that. Therefore something has changed between J! 4.1.x (at least) and J! 4.4.x. In my opinion, this is a bug and it should be reported to the J! development team. Unfortunately, the Issue Tracker is broken and I cannot report this error.
Statistics: Posted by nacc — Sun Jan 14, 2024 12:25 am