Maxence1502
Member
Any update about the 2.3 compatibility ?
Thank you
Thank you

- Require StandardLib v1.21.0+
- XF2.3 support
- Replaces select2 library with a customized choices.js build from StandardLib
- php 8.4+ compatibility fixes
- Fix
multi-prefix-content-parent="XF:Thread"
being rendered as part of new thread HTML- Fixes for XenConcept's Project Manager
- Fix api support for projects
- Fix cleaning up prefix data when a prefix is deleted for...
Thanks very much for the update.Xon updated Multi Prefix with a new update entry:
2.14.5 - XenForo 2.3 support
Read the rest of this update entry...
choices.js
library and it's customizations in my StandardLib add-on, should also completely eliminate the "loading jank" that the previous versions had.choices.js
library doesn't quite have that as an option. For some reason it force enables search-as-you-type for multiple mode which multi-prefix uses. The previous select2
multi-prefix system had a similar issue.ie people like me. This caught me out this morning: I just typed the title in what now appeared to be a normal title text field, but then got kept getting an error when trying to post.To remove any confusion where people might type the title in the wrong box?
choices.js
) and v2.13.x (select2
) work the same for the input behavior. Both show "(no prefix)" and allow arbitrary text entry, and show 'no results found" for no matches.prefixes...
placeholder.I feel the same way. If I have one complaint and it really doesn't have anything to do with the addon. I wish there was a sort function on the prefix list in ACP.In the several years I've been using this addon, I have to say that this has never been a problem for me or my users. Most thread creation on my forum requires prefixes to post, so it's something regularly used by all members, and I've never mixed those two fields up or ever once had a member mention, privately or publicly, having an issue with it. Not to say no one ever has and didn't say anything about it, but if they did, they must have got used to it quickly. I'm guessing this is largely down to the thread title field being auto filled with "Thread title." Not trying to imply that other people's concerns aren't warranted, just saying that it probably won't turn out to be much of problem for most.![]()
Yes of course that makes perfect sense, and had that been the case here, I would probably not have had a problem.I'm guessing this is largely down to the thread title field being auto filled in with "Thread title.
LogicException: Attempted to set 'sv_prefix_ids' while a save was pending without forceSet in src/XF/Mvc/Entity/Entity.php at line 610
XF\Mvc\Entity\Entity->set() in src/XF/Mvc/Entity/Entity.php at line 582
XF\Mvc\Entity\Entity->__set() in src/addons/SV/MultiPrefix/XFRM/Service/ResourceItem/Edit.php at line 37
SV\MultiPrefix\XFRM\Service\ResourceItem\Edit->setPrefixIds() in src/addons/SV/MultiPrefix/XFRM/Service/ResourceItem/Edit.php at line 22
SV\MultiPrefix\XFRM\Service\ResourceItem\Edit->setPrefix() in src/addons/OzzModz/XFRMPrefixSync/Listener.php at line 185
OzzModz\XFRMPrefixSync\Listener::threadEntityPostSave() in src/XF/Extension.php at line 64
XF\Extension->fire() in src/XF.php at line 966
XF::fire() in src/XF/Mvc/Entity/Entity.php at line 1288
XF\Mvc\Entity\Entity->save() in src/XF/Mvc/Entity/Entity.php at line 1328
XF\Mvc\Entity\Entity->saveIfChanged() in src/addons/XFRM/Entity/ResourceItem.php at line 1433
XFRM\Entity\ResourceItem->updateCategoryRecord() in src/addons/XFRM/Entity/ResourceItem.php at line 1263
XFRM\Entity\ResourceItem->_postSave() in src/addons/CoderBeams/XFRMTitleMod/XFRM/Entity/ResourceItem.php at line 37
CoderBeams\XFRMTitleMod\XFRM\Entity\ResourceItem->_postSave() in src/XF/Mvc/Entity/Entity.php at line 1282
XF\Mvc\Entity\Entity->save() in src/addons/XFRM/Service/ResourceItem/Move.php at line 103
XFRM\Service\ResourceItem\Move->move() in src/addons/XFRM/Pub/Controller/ResourceItem.php at line 1385
XFRM\Pub\Controller\ResourceItem->actionMove() in src/addons/SV/MultiPrefix/XFRM/Pub/Controller/ResourceItem.php at line 110
SV\MultiPrefix\XFRM\Pub\Controller\ResourceItem->actionMove() in src/XF/Mvc/Dispatcher.php at line 352
XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 258
XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115
XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57
XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2485
XF\App->run() in src/XF.php at line 524
XF::runApp() in index.php at line 20
This looks to be a compatibility issue with @Ozzy47's OzzModz\XFRMPrefixSync add-on.When I try to move a resource from one category to another with just 1 prefix, I get the below error.
Code:LogicException: Attempted to set 'sv_prefix_ids' while a save was pending without forceSet in src/XF/Mvc/Entity/Entity.php at line 610 XF\Mvc\Entity\Entity->set() in src/XF/Mvc/Entity/Entity.php at line 582 XF\Mvc\Entity\Entity->__set() in src/addons/SV/MultiPrefix/XFRM/Service/ResourceItem/Edit.php at line 37 SV\MultiPrefix\XFRM\Service\ResourceItem\Edit->setPrefixIds() in src/addons/SV/MultiPrefix/XFRM/Service/ResourceItem/Edit.php at line 22 SV\MultiPrefix\XFRM\Service\ResourceItem\Edit->setPrefix() in src/addons/OzzModz/XFRMPrefixSync/Listener.php at line 185 OzzModz\XFRMPrefixSync\Listener::threadEntityPostSave() in src/XF/Extension.php at line 64 XF\Extension->fire() in src/XF.php at line 966 XF::fire() in src/XF/Mvc/Entity/Entity.php at line 1288 XF\Mvc\Entity\Entity->save() in src/XF/Mvc/Entity/Entity.php at line 1328 XF\Mvc\Entity\Entity->saveIfChanged() in src/addons/XFRM/Entity/ResourceItem.php at line 1433 XFRM\Entity\ResourceItem->updateCategoryRecord() in src/addons/XFRM/Entity/ResourceItem.php at line 1263 XFRM\Entity\ResourceItem->_postSave() in src/addons/CoderBeams/XFRMTitleMod/XFRM/Entity/ResourceItem.php at line 37 CoderBeams\XFRMTitleMod\XFRM\Entity\ResourceItem->_postSave() in src/XF/Mvc/Entity/Entity.php at line 1282 XF\Mvc\Entity\Entity->save() in src/addons/XFRM/Service/ResourceItem/Move.php at line 103 XFRM\Service\ResourceItem\Move->move() in src/addons/XFRM/Pub/Controller/ResourceItem.php at line 1385 XFRM\Pub\Controller\ResourceItem->actionMove() in src/addons/SV/MultiPrefix/XFRM/Pub/Controller/ResourceItem.php at line 110 SV\MultiPrefix\XFRM\Pub\Controller\ResourceItem->actionMove() in src/XF/Mvc/Dispatcher.php at line 352 XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 258 XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 115 XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 57 XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2485 XF\App->run() in src/XF.php at line 524 XF::runApp() in index.php at line 20
- Recommend StandardLib v1.21.5+
- Move multi-prefix style properties to "Multi Prefix" group
- Add "Close dropdown on select" style property (default: true).
This feature requires StandardLib v1.21.5+
Multiprefix is not supported or any prefix for that matter in Dragonbyte Social Groups.There isn't explicit support for them, but @DragonByte Tech might be able to answer on how dragonbyte social groups works with multiprefix
We use essential cookies to make this site work, and optional cookies to enhance your experience.