[#9686] - Joomla 3.5 stuck forever creating Index in Smart Search Component
- Closed
- 1 Apr 2016
- Medium
- Build: master
- # 9686
Steps to reproduce the issue
Go to Component Menu and select "Smart Search"
Click on "Index" button
The Smart Search Indexer overlay window appear...and stay forever
Opening the web inspector of the browser (I'm using Safari on El Capitain Mac Os X)I can read the JS error
SyntaxError: JSON Parse error: Unrecognized token '<'
parsejquery.min.js:4:16003
parseJSONjquery.min.js:4:16003
parseJSONjquery-migrate.min.js:1:2948
handleFailureindexer.js:65
jjquery.min.js:1:27314
fireWithjquery.min.js:1:28123
xjquery.min.js:4:22146
bjquery.min.js:4:26031
The LOG file
2016-03-31T12:30:16+00:00 INFO 127.0.0.1 - Starting the indexer
2016-03-31T12:30:17+00:00 INFO 127.0.0.1 - Starting the indexer batch process
only 2 lines...no errors, also if I set LOG to Development or Maximum (obviously, some lines of text more, like the query, but no errors)
Expected result
Joomla write content index
Actual result
Stuck forever on "Indexer Running"
System information (as much as possible)
iMac 10.11.3
Safari 9.0.3
Apache 2.2
PHP 5.6 (the same on 5.4)
Base Joomla 3.5 install with standard Example (Brochure English)
Additional comments
It's a new installation. No 3rd part extension.
Regards
Erik
From the error message, it looks like your PHP has been compiled without iconv support. I think you will have to ask your hosting company to install it for you.
can you check if iconv is installed ?
BOOM!
iconv not active was the problem.
I've activated this php extension from my web admin panel and now the indexing process is working.
Thank's for the support.
Great so can you close this issue that and record you test on the Pull Request?
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-04-01 08:40:16 |
| Closed_By | ⇒ | ErikDeMartiis |
You imply but you do not say if you *have not installed any 3rd party extensions ??
Unrecognized token '<'
the server responce is broken by some PHP error / warning / notice that breaks the JSON format of the server responce
you need to go to your browser and look at the server responce TEXT, which should reveal the real issue
See below an example of proper response using firefox and firebug, your browser has similar "Network" Tab to examine the server responce