@Moshe1010 I'll have a look for any hardcoded terms, it should all be using phrases.
Can you provide a screenshot of where this is happening?
Can you provide a screenshot of where this is happening?
When you edit a title of a thread either through the thread itself of through the thread list :@Moshe1010 I'll have a look for any hardcoded terms, it should all be using phrases.
Can you provide a screenshot of where this is happening?
Thanks, found the unphrased text inside the javascript. Now to fix it & test.When you edit a title of a thread either through the thread itself of through the thread list :
https://drive.google.com/file/d/0B8Q8w4_vLThUV2VzTFhxejZWSVU/view?usp=drivesdk
- Add-on compatibility tweaks
- Prevent error when merging threads on forums with limits on prefixes
- Allow the phrase "prefixes" used in the front-end to be phraseable
- Correctly package javascript files
This issue is happening still. Want me to post on Atelier Aphelion @Xon so it can be tracked? I thought it had been fixed but it's showing up on TAZ now.Minor issue with the latest version.
If you have a custom CSS prefix defined the class for that is not added to the thread edit overlay title. It just appends noPrefix instead of my custom class 'cssPrefix' making it impossible to style.
View attachment 119010
View attachment 119011
With Multi Prefix disabled, it works as expected.
View attachment 119012
I think I've just missed this, cheers for bumping it.This issue is happening still. Want me to post on Atelier Aphelion @Xon so it can be tracked? I thought it had been fixed but it's showing up on TAZ now.
- Prevent error when moving thread/resources to a forum/category with a required prefixes > 1
/home/admin/public_html/library/XenES/Search/SourceHandler/ElasticSearch.php on line 1098
- XenES_Search_SourceHandler_ElasticSearch->_triggerFailedIndexError() inXenES/Search/SourceHandler/ElasticSearch.php at line 53
- XenES_Search_SourceHandler_ElasticSearch->insertIntoIndex() inXenForo/Search/Indexer.php at line 44
- XenForo_Search_Indexer->insertIntoIndex() in XenForo/Search/DataHandler/Thread.php at line 58
- XenForo_Search_DataHandler_Thread->_insertIntoIndex() inSV/MultiPrefix/XenForo/Search/DataHandler/Thread.php at line 12
- SV_MultiPrefix_XenForo_Search_DataHandler_Thread->_insertIntoIndex() inXenForo/Search/DataHandler/Abstract.php at line 275
- XenForo_Search_DataHandler_Abstract->insertIntoIndex() inXenForo/Search/DataHandler/Thread.php at line 119
- XenForo_Search_DataHandler_Thread->quickIndex() inXenForo/Search/DataHandler/Thread.php at line 101
- XenForo_Search_DataHandler_Thread->rebuildIndex() inXenForo/Deferred/SearchIndex.php at line 74
- XenForo_Deferred_SearchIndex->execute() in XenForo/Model/Deferred.php at line 295
- XenForo_Model_Deferred->runDeferred() in XenForo/Model/Deferred.php at line 429
- XenForo_Model_Deferred->_runInternal() in XenForo/Model/Deferred.php at line 374
- XenForo_Model_Deferred->run() in XenForo/ViewRenderer/Abstract.php at line 352
- XenForo_ViewRenderer_Abstract::hasManualDeferredToRun() inXenForo/ViewRenderer/Json.php at line 147
- XenForo_ViewRenderer_Json::_addDefaultParams() in XenForo/ViewRenderer/Json.php at line 185
- XenForo_ViewRenderer_Json::jsonEncodeForOutput() in XenForo/ViewRenderer/Json.phpat line 37
- XenForo_ViewRenderer_Json->renderRedirect() in XenForo/FrontController.php at line 617
- XenForo_FrontController->renderView() in XenForo/FrontController.php at line 158
- XenForo_FrontController->run() in /home/admin/public_html/admin.php at line 13
What is the actual error message? It should have an elastic search error message which I require to debug this.Hi since updating to the latest version, I can't seem to rebuild ElasticSearch index. I get the following error once I enable or disable the add-on
I have many of them, but I guess this is more relevent@Moshe1010 can you try deleting the index via Elastic Search Configuration and then re-index instead of telling it to delete/index content?
What is the actual error message? It should have an elastic search error message which I require to debug this.
[2016-09-20 15:00:52,142][DEBUG][action.bulk ] [Prowler] [lbs2016][0] failed to execute bulk item (index) index {[lbs2016][post][1148100], source[{"prefix":{"1":"7"},"node":7,"thread":84299,"title":"\u05e9\u05d0\u05dc\u05d4 \u05d1\u05e7\u05e9\u05e8 \u05dc\u05e8\u05db\u05d9\u05e9\u05ea \u05d7\u05d2\u05d5\u05e8\u05ea \u05d2\u05d1 \u05e2\u05dd \u05d7\u05d9\u05d1\u05d5\u05e8 \u05dc\u05de\u05e9\u05e7\u05d5\u05dc\u05d5\u05ea","message":"\u05d7\u05d1\u05e8\u05d9\u05dd \u05de\u05d9\u05e9\u05d4\u05d5 \u05d9\u05d5\u05d3\u05e2 \u05d0\u05e4\u05d4 \u05d0\u05e0\u05d9 \u05d9\u05db\u05d5\u05dc \u05dc\u05e7\u05e0\u05d5\u05ea \u05d1\u05d9\u05e8\u05d5\u05e9\u05dc\u05d9\u05dd \u05d7\u05d2\u05d5\u05e8\u05ea \u05d2\u05d1 \u05e2\u05dd \u05d4\u05e9\u05e8\u05e9\u05e8\u05ea \u05e9\u05d0\u05e0\u05d9 \u05d9\u05db\u05d5\u05dc \u05dc\u05d7\u05d1\u05e8 \u05dc\u05d4 \u05de\u05e9\u05e7\u05d5\u05dc\u05ea \u05d5\u05dc\u05e2\u05e9\u05d5\u05ea \u05e2\u05dc\u05d9\u05d5\u05ea \u05de\u05ea\u05d7 \u05d5\u05de\u05e7\u05d1\u05d9\u05dc\u05d9\u05dd \u05e2\u05dd \u05de\u05e9\u05e7\u05dc? \u05d1\u05d9\u05e8\u05e8\u05ea\u05d9 \u05d13 \u05de\u05e7\u05d5\u05de\u05d5\u05ea \u05d1\u05d9\u05e8\u05d5\u05e9\u05dc\u05d9\u05dd \u05d5\u05d0\u05e3 \u05d0\u05d7\u05d3 \u05de\u05d4\u05dd \u05dc\u05d0 \u05de\u05d5\u05db\u05e8 \u05d0\u05ea \u05d6\u05e0.. \u05de\u05d9\u05e9\u05d4\u05d5 \u05de\u05db\u05d9\u05e8?","date":1473154865,"user":20829,"discussion_id":84299}]}
MapperParsingException[failed to parse [prefix]]; nested: IllegalArgumentException[unknown property [1]];
at org.elasticsearch.index.mapper.FieldMapper.parse(FieldMapper.java:329)
at org.elasticsearch.index.mapper.DocumentParser.parseObjectOrField(DocumentParser.java:311)
at org.elasticsearch.index.mapper.DocumentParser.parseObject(DocumentParser.java:328)
at org.elasticsearch.index.mapper.DocumentParser.parseObject(DocumentParser.java:254)
at org.elasticsearch.index.mapper.DocumentParser.parseDocument(DocumentParser.java:124)
at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:309)
at org.elasticsearch.index.shard.IndexShard.prepareIndex(IndexShard.java:580)
at org.elasticsearch.index.shard.IndexShard.prepareIndexOnPrimary(IndexShard.java:559)
at org.elasticsearch.action.index.TransportIndexAction.prepareIndexOperationOnPrimary(TransportIndexAction.java:211)
at org.elasticsearch.action.index.TransportIndexAction.executeIndexRequestOnPrimary(TransportIndexAction.java:223)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation(TransportShardBulkAction.java:327)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:120)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:68)
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryPhase.doRun(TransportReplicationAction.java:648)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:279)
at org.elasticsearch.action.support.replication.TransportReplicationAction$PrimaryOperationTransportHandler.messageReceived(TransportReplicationAction.java:271)
at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:77)
at org.elasticsearch.transport.TransportService$4.doRun(TransportService.java:376)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: unknown property [1]
at org.elasticsearch.index.mapper.core.StringFieldMapper.parseCreateFieldForString(StringFieldMapper.java:366)
at org.elasticsearch.index.mapper.core.StringFieldMapper.parseCreateField(StringFieldMapper.java:315)
at org.elasticsearch.index.mapper.FieldMapper.parse(FieldMapper.java:321)
... 22 more
Cheers, will look into that soon.
ES 2.4What version of Elastic Search?
As this is working for me with Elastic Search 2.x
Cheers, will look into that soon.
This is related to the prefix id's being transformed into strings instead of integers when they are inserted into Elastic Search. This causes the ad-hoc mapping to transform them badly which doesn't mesh with existing content.
For Elastic Search, the index must be deleted and search re-indexed from scratch.
- Fix indexing & searching by prefix when XenForo Enhanced Search is installed
We use essential cookies to make this site work, and optional cookies to enhance your experience.