Content rating upgrade fails on VaultWiki

boardyogi

New Member
Hi

During upgrade to the latest version it fails with this error thrown.

Code:
LogicException: Content type vwattachedit must define an 'entity' value src/XF/App.php:2738

Generiert von: ... 8. November 2021 um 17:21

Stack-Trace

#0 src/addons/SV/ContentRatings/Job/ContentRatingData.php(50): XF\App->getContentTypeEntity('vwattachedit')
#1 src/XF/Job/Manager.php(260): SV\ContentRatings\Job\ContentRatingData->run(7.95378)
#2 src/XF/Job/Manager.php(202): XF\Job\Manager->runJobInternal(Array, 7.95378)
#3 src/XF/Job/Manager.php(118): XF\Job\Manager->runJobEntry(Array, 7.95378)
#4 src/XF/Admin/Controller/Tools.php(122): XF\Job\Manager->runByIds(Array, 8)
#5 src/XF/Mvc/Dispatcher.php(352): XF\Admin\Controller\Tools->actionRunJob(Object(XF\Mvc\ParameterBag))
#6 src/XF/Mvc/Dispatcher.php(259): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(XF\Admin\Controller\Tools), NULL)
#7 src/XF/Mvc/Dispatcher.php(115): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(XF\Admin\Controller\Tools), NULL)
#8 src/XF/Mvc/Dispatcher.php(57): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#9 src/XF/App.php(2345): XF\Mvc\Dispatcher->run()
#10 src/XF.php(512): XF\App->run()
#11 admin.php(13): XF::runApp('XF\\Admin\\App')
#12 {main}

Status der Anfrage

array(4) {
["url"] => string(31) "/xf2dev/admin.php?tools/run-job"
["referrer"] => string(54) "https://www.tt-board.eu/xf2dev/admin.php?tools/run-job"
["_GET"] => array(1) {
["tools/run-job"] => string(0) ""
}
["_POST"] => array(3) {
["_xfRedirect"] => string(89) "https://www.tt-board.eu/xf2dev/admin.php?add-ons/install-from-archive-complete&batch_id=8"
["_xfToken"] => string(8) "********"
["only_ids"] => string(144) "3050,3051,3052,3053,3054,3055,3056,3057,3058,3059,3060,3 061,3062,3063,3064,3065,3066,3067,3068,3069,3070,3071,307 2,3073,3074,3075,3076,3077,3078"
}

vaultwiki developer refers to you as he doesn't make use of the entity concept.
Interestingly, up to now both addons co-exists without any problems.

What has to be done?
 
@boardyogi can you post a ticket so I can share a build which might work-around the issue?

I believe this has been broken for a while. It is just someone kicked off a reactions rebuild (or deleted a reaction?) and now things are in a broken state.

If someone has implemented a content type used with the reaction system in XenForo, there really needs to be a linked Entity.
 
The add-on assumes if a reaction_handler_class exists there will be an entity for the thing, I'll add a workaround to discard those broken setup which should help for the vaultwiki add-on
 

Users who are viewing this thread

Back
Top