I too have tried solutions posted else where but to no avail. However, I just restarted the indexing ( I don't have root access so don't know if it was still running after it throws the error ) service, again and again and again till it finally finished.
Once indexed an article must be marked by the indexer as having been indexed. Restarting the service, it ignores what has been already indexed (though it still has to parse it but ignoring those indexed) and continues on until it throws another null error.
This was on nearly 7,000 articles.
If you can continue manually after if throws an error, why can't the developers just give an option to ignore the nulls?
via Joomla! http://ift.tt/1DNOIkD
Once indexed an article must be marked by the indexer as having been indexed. Restarting the service, it ignores what has been already indexed (though it still has to parse it but ignoring those indexed) and continues on until it throws another null error.
This was on nearly 7,000 articles.
If you can continue manually after if throws an error, why can't the developers just give an option to ignore the nulls?
Statistics: Posted by wickerbill — Fri Feb 06, 2015 8:23 pm
via Joomla! http://ift.tt/1DNOIkD
No comments:
Post a Comment