Multi Prefix

Multi Prefix [Paid] 1.8.16

No permission to buy ($20.00)
Overview FAQ Updates (66) Reviews (23) History Discussion
@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?
 
Steve F said:
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
Click to expand...
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.
 
  • Like
Reactions: Xon
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
/home/admin/public_html/library/XenES/Search/SourceHandler/ElasticSearch.php on line 1098

  1. XenES_Search_SourceHandler_ElasticSearch->_triggerFailedIndexError() inXenES/Search/SourceHandler/ElasticSearch.php at line 53
  2. XenES_Search_SourceHandler_ElasticSearch->insertIntoIndex() inXenForo/Search/Indexer.php at line 44
  3. XenForo_Search_Indexer->insertIntoIndex() in XenForo/Search/DataHandler/Thread.php at line 58
  4. XenForo_Search_DataHandler_Thread->_insertIntoIndex() inSV/MultiPrefix/XenForo/Search/DataHandler/Thread.php at line 12
  5. SV_MultiPrefix_XenForo_Search_DataHandler_Thread->_insertIntoIndex() inXenForo/Search/DataHandler/Abstract.php at line 275
  6. XenForo_Search_DataHandler_Abstract->insertIntoIndex() inXenForo/Search/DataHandler/Thread.php at line 119
  7. XenForo_Search_DataHandler_Thread->quickIndex() inXenForo/Search/DataHandler/Thread.php at line 101
  8. XenForo_Search_DataHandler_Thread->rebuildIndex() inXenForo/Deferred/SearchIndex.php at line 74
  9. XenForo_Deferred_SearchIndex->execute() in XenForo/Model/Deferred.php at line 295
  10. XenForo_Model_Deferred->runDeferred() in XenForo/Model/Deferred.php at line 429
  11. XenForo_Model_Deferred->_runInternal() in XenForo/Model/Deferred.php at line 374
  12. XenForo_Model_Deferred->run() in XenForo/ViewRenderer/Abstract.php at line 352
  13. XenForo_ViewRenderer_Abstract::hasManualDeferredToRun() inXenForo/ViewRenderer/Json.php at line 147
  14. XenForo_ViewRenderer_Json::_addDefaultParams() in XenForo/ViewRenderer/Json.php at line 185
  15. XenForo_ViewRenderer_Json::jsonEncodeForOutput() in XenForo/ViewRenderer/Json.phpat line 37
  16. XenForo_ViewRenderer_Json->renderRedirect() in XenForo/FrontController.php at line 617
  17. XenForo_FrontController->renderView() in XenForo/FrontController.php at line 158
  18. XenForo_FrontController->run() in /home/admin/public_html/admin.php at line 13
Click to expand...
 
@Moshe1010 can you try deleting the index via Elastic Search Configuration and then re-index instead of telling it to delete/index content?

Moshe1010 said:
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
Click to expand...
What is the actual error message? It should have an elastic search error message which I require to debug this.
 
Xon said:
@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.
Click to expand...
I have many of them, but I guess this is more relevent

[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
Click to expand...

I can rebuild my ES index only when the multiple prefix add-on is disabled. I've tried to hard-delete the index from the actual server, change its name, and also delete it from XF's ACP - same outcome to all of these methods. I also tried to re-install ES on my server until I saw a post of Mike saying it's a multi-prefix problem for someone else who had a similar problem few years ago.
 
Xon said:
What version of Elastic Search?

As this is working for me with Elastic Search 2.x :(


Cheers, will look into that soon.
Click to expand...
ES 2.4
I have 1.1M posts and it locks down after indexing 800K posts (or 40K threads, so it's not a timeout issue)
I use multiple prefixes a lot on my website. I would say there are at least 40K threads with multiple prefixes, some of them have 3-4 prefixes
 
  • Like
Reactions: Xon
In a node that only allows one prefix, could you disable multi-selection?
For example, I have a For Sale section with prefixes for WANTED, FOR SALE, SOLD.
In this node, which I have set to only allow one prefix, I'd like prefix selection to work exactly as vanilla xenForo, toggling between prefixes.
However, the add-on initially allows multiple selections, but then gives an error when the user tries to save the post. This confuses my users.

I asked about this several months ago and you said it would go on your to-do list.
Perhaps you've already taken care of this in a recent release?

Thank you,
Evan
 
You must log in or register to reply here.

Similar threads

mcatze
German translation for [SV] Multi Prefix [Paid]
Replies
0
Views
397
mcatze
mcatze
X
Multi Prefix [Paid]
30 31 32
Replies
637
Views
41K
Xon
X
Stuart Wright
Prefix Essentials featuring auto expiring prefixes and prefix filtering [Paid]
9 10 11
Replies
203
Views
15K
Stuart Wright
Stuart Wright
sbj
Add-on [Paid <50$] Marker/Tagging/Prefix
Replies
0
Views
749
sbj
sbj
Top Bottom