User Essentials [Paid] 4.5.8
- Thread starter Xon
- Start date
Is this still happening?
Nirjonadda
Well-known member
@Xon Getting lot of Server error log.
Code:
ErrorException: Fatal Error: Declaration of SV\UserEssentials\XF\Validator\Username::setupOptionDefaults() must be compatible with XF\Validator\Username::setupOptionDefaults(): void src/addons/SV/UserEssentials/XF/Validator/Username.php:70
Generated by: Unknown account Jul 17, 2024 at 2:40 AM
Stack trace
#0 [internal function]: XF::handleFatalError()
#1 {main}
Request state
array(4) {
["url"] => string(23) "/misc/validate-username"
["referrer"] => string(37) "/login/register"
["_GET"] => array(0) {
}
["_POST"] => array(0) {
}
}Xon updated User Essentials with a new update entry:
4.5.1 - Bugfix update
Read the rest of this update entry...
4.5.1 - Bugfix update
Read the rest of this update entry...
Joe Link
Well-known member
@Xon
Previously, members with a self-disable request could cancel it from the self-disable page. With XF2.3 and User Essentials 4.5.1, members with a pending self-disable request can only view the page with the "Your account is in the process of being disabled. If you would like to cancel this process, you can do it so from here" message. Since that phrase has a link to the self-disable page, I'm thinking this might be a bug.
Previously, members with a self-disable request could cancel it from the self-disable page. With XF2.3 and User Essentials 4.5.1, members with a pending self-disable request can only view the page with the "Your account is in the process of being disabled. If you would like to cancel this process, you can do it so from here" message. Since that phrase has a link to the self-disable page, I'm thinking this might be a bug.
Can you verify there are no template edits for this self-disable request templates?
Xon updated User Essentials with a new update entry:
4.5.2 - Bugfix update
Read the rest of this update entry...
4.5.2 - Bugfix update
Read the rest of this update entry...
Joe Link
Well-known member
@Xon
Still having this problem with 4.5.2 on both XF 2.2 and 2.3.
Here's how it (correctly) works with 4.5.0 and XF 2.2:
Step 1: Starting the disable process.
Step 2: Member is taken to the confirmation screen.
Step 3: Clicking the this page link takes them to
svUserEss_account_self_disable, where they can cancel the disable request.
Here's how it (doesn't) work with 4.5.2 on both XF 2.2 and 2.3.
Step 1: Starting the disable process.
Step 2: Member is taken to the confirmation screen.
Step 3: Clicking the this page link changes the URL to
domain.com/account/self-disable, but the data template is message_page and the same message is shown again. There's no way to view the page with the cancel button.
Alpha1
Well-known member
I'm getting this error when viewing any thread on version 4.5.2 on XF2.3, php7.3
Code:
ErrorException: [E_WARNING] Declaration of SV\UserEssentials\XF\Pub\Controller\Thread::finalizeThreadReply(XF\Service\Thread\Replier $replier) should be compatible with XF\Pub\Controller\ThreadController::finalizeThreadReply(XF\Service\Thread\ReplierService $replier) src/addons/SV/UserEssentials/XF/Pub/Controller/Thread.php:0
Generated by: Alfa Dec 31, 2024 at 1:34 PM
Stack trace
#0 src/vendor/composer/ClassLoader.php(576): XF::handlePhpError(2, '[E_WARNING] Dec...', '/home/nginx/dom...', 0, Array)
#1 src/vendor/composer/ClassLoader.php(576): include()
#2 src/vendor/composer/ClassLoader.php(427): Composer\Autoload\{closure}('/home/nginx/dom...')
#3 [internal function]: Composer\Autoload\ClassLoader->loadClass('SV\\UserEssentia...')
#4 src/XF.php(414): spl_autoload_call('SV\\UserEssentia...')
#5 [internal function]: XF::createAliasForClass('SV\\UserEssentia...')
#6 [internal function]: spl_autoload_call('SV\\UserEssentia...')
#7 src/XF/Extension.php(215): class_exists('SV\\UserEssentia...')
#8 src/XF/App.php(3385): XF\Extension->extendClass('XF\\Pub\\Controll...', NULL)
#9 src/XF/App.php(1854): XF\App->extendClass('XF\\Pub\\Controll...')
#10 src/XF/Container.php(233): XF\App->XF\{closure}('XF\\Pub\\Controll...', Array, Object(XF\Container))
#11 src/XF/App.php(3337): XF\Container->create('controller', 'XF:Thread', Array)
#12 src/XF/Mvc/Dispatcher.php(301): XF\App->controller('XF:Thread', Object(XF\Http\Request))
#13 src/XF/Mvc/Dispatcher.php(265): XF\Mvc\Dispatcher->dispatchClass('XF:Thread', 'index', Object(XF\Mvc\RouteMatch), NULL, NULL)
#14 src/XF/Mvc/Dispatcher.php(121): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), NULL, NULL)
#15 src/XF/Mvc/Dispatcher.php(63): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#16 src/XF/App.php(2826): XF\Mvc\Dispatcher->run()
#17 src/XF.php(806): XF\App->run()
#18 index.php(23): XF::runApp('XF\\Pub\\App')
#19 {main}
Request state
array(4) {
["url"] => string(47) "/threads/107444/"
["referrer"] => string(42) "..."
["_GET"] => array(1) {
["/107444/"] => string(0) ""
}
["_POST"] => array(0) {
}
}Your XF2.3 setup is in a broken state, and I'm unsure why. This should be working.
Can you open a ticket with XenForo to investigate why XF2.2 compatible add-on support is broken?
Alpha1
Well-known member
Will do. But could you please have a look at these resolved bug reports because I refer to errors with your addons in these and I have a hunch one of these may be related or at the cause:
Call to undefined method SV\ReportImprovements\XF\BbCode\Renderer\Html::vwSetParse r() src/addons/vw/vw/_core/instance/parser/renderer/xf2.php:192 - VaultWiki - Wiki for Forum Communities - Support
VaultWiki, Wiki addon for vBulletin forums. Licensing and support site.
www.vaultwiki.org
InvalidArgumentException: Unknown column vw_varname on XF:BbCode in src/XF/Mvc/Entity/Finder.php at line 1821 - VaultWiki - Wiki for Forum Communities - Support
VaultWiki, Wiki addon for vBulletin forums. Licensing and support site.
www.vaultwiki.org
Table 'xxx.vw_upgradelog' doesn't exist in src/XF/Db/AbstractStatement.php - VaultWiki - Wiki for Forum Communities - Support
VaultWiki, Wiki addon for vBulletin forums. Licensing and support site.
www.vaultwiki.org
Similar threads
