[#39717] - [4.2] Smart search indexer button does not always work in multilingual site
- Closed
- 28 Feb 2023
- Medium
- Build: 4.2-dev
- # 39717
Steps to reproduce the issue
- Set up a blank Joomla installation and install an additional language of your choice.
- Install multilingual sample data.
- Go to Smart Search > Index > and then click the "Index" button.
- If it works as expected, go to options, change something in the index settings, and then try again.
Expected result
Site is indexed.
Actual result
Frozen index modal which never errors out or succeeds. (I've left it for something like 15-20 minutes just in case.)
Not sure if the background indexing is okay and the modal just gets stuck.
Possibly related console error:
[Error] SyntaxError: JSON Parse error: Unrecognized token '<'
parse (indexer.min.js:1:2366)
onSuccess (indexer.min.js:1:2366)
(anonymous function) (core.min.js:1:6230)
Possibly related PHP notice:
PHP Deprecated: Locale::getPrimaryLanguage(): Passing null to parameter #1 ($locale) of type string is deprecated in /administrator/components/com_finder/src/Indexer/Helper.php on line 357
System information (as much as possible)
PHP 8.1
Joomla 4.2.6 and 4.2.7-RC2
Additional comments
Doesn't always happen, I haven't been able to pin down the conditions in which it happens vs it doesn't.
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
I've done that now and tried again, but not sure where to find the log.
No idea either - I would assume administrator/logs
You also get some more detailed info if you have debug on when running the index iirc
Found it.
This is what's logged within a few seconds after I clear the index and start from scratch:
2023-01-26T10:19:20+00:00 INFO ::1 - Starting the indexer
2023-01-26T10:19:20+00:00 INFO ::1 - Starting the indexer batch process
2023-01-26T10:19:20+00:00 INFO ::1 - Batch completed, peak memory usage: 6,291,456 bytes
So it appears that the index works fine, but something funky is happening with the modal as it's still frozen like in my screenshot above.
You also get some more detailed info if you have debug on when running the index iirc
Interesting! Will try that next.
Modal is still frozen with debug on, with additional frozen debug info haha:
I'm going to guess this is some kind of javascript error based on the error in the console.
From your error it's more likely the php warning to be honest. If you look in the network tab of dev tools
Filter by XHR requests to make life easier you should be able to see the raw response coming back from the server and which one isn't valid JSON. Sorry I've tried reproducing on my PHP 8.1 setup and can't seem to reproduce with error reporting on maximum :( otherwise would do it myself!
| Labels |
Added:
bug
|
||
@crystalenka Did you check this again?
| Labels |
Added:
Information Required
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-02-28 11:45:21 |
| Closed_By | ⇒ | Hackwar |
This stops the output from hard crashing but doesn't solve @crystalenka 's underlying root cause of some sort of php error so would still be good to get that info please Crystal!
have you tried "enable logging" in the finder component options. Might give some clues.