Not a bug Error during upgrade to 2.2: Error: Class 'Emojione\Client' not found

Affected version
2.2.0

Sim

Well-known member
Upgrading an XF 2.1.11 forum to XF 2.2.0, received the following error in the Server error log:

Code:
Error: Class 'Emojione\Client' not found src/XF/Str/EmojiFormatter.php:23
Generated by: Unknown account 30th Sep, 2020 at 1:06 PM
Stack trace
#0 src/XF/Str/Formatter.php(951): XF\Str\EmojiFormatter->__construct()
#1 src/XF/BbCode/Renderer/Html.php(389): XF\Str\Formatter->getEmojiFormatter()
#2 src/XF/BbCode/Renderer/Html.php(366): XF\BbCode\Renderer\Html->filterString()
#3 src/XF/BbCode/Traverser.php(65): XF\BbCode\Renderer\Html->renderString()
#4 src/XF/BbCode/Traverser.php(37): XF\BbCode\Traverser->renderSubTree()
#5 src/XF/BbCode/Traverser.php(20): XF\BbCode\Traverser->renderAst()
#6 src/XF/SubContainer/BbCode.php(219): XF\BbCode\Traverser->render()
#7 src/XF/Template/Templater.php(2038): XF\SubContainer\BbCode->render()
#8 [internal function]: XF\Template\Templater->fnBbCode()
#9 src/XF/Template/Templater.php(936): call_user_func_array()
#10 internal_data/code_cache/templates/l2/s2/public/post_macros.php(154): XF\Template\Templater->func()
#11 src/XF/Template/Templater.php(701): XF\Template\Templater->{closure}()
#12 internal_data/code_cache/templates/l2/s2/public/thread_view.php(535): XF\Template\Templater->callMacro()
#13 src/XF/Template/Templater.php(1315): XF\Template\Templater->{closure}()
#14 src/XF/Template/Template.php(24): XF\Template\Templater->renderTemplate()
#15 src/XF/Mvc/Renderer/Html.php(48): XF\Template\Template->render()
#16 src/XF/Mvc/Dispatcher.php(458): XF\Mvc\Renderer\Html->renderView()
#17 src/XF/Mvc/Dispatcher.php(440): XF\Mvc\Dispatcher->renderView()
#18 src/XF/Mvc/Dispatcher.php(400): XF\Mvc\Dispatcher->renderReply()
#19 src/XF/Mvc/Dispatcher.php(58): XF\Mvc\Dispatcher->render()
#20 src/XF/App.php(2191): XF\Mvc\Dispatcher->run()
#21 src/XF.php(391): XF\App->run()
#22 index.php(20): XF::runApp()
#23 {main}
 

Sim

Well-known member
Hmm ... thinking about it - I guess it is possible that this is a result of a visitor accessing a thread while the upgrade process was completing?

So just a point-in-time quirk during the upgrade process?
 
Top