Warning Improvements by Xon 2.11.6

[MentaL]

Right!
this one then for users with no active warnings then?

View attachment 321087

Right!
this one then for users with no active warnings then?

View attachment 321087

Im actually quite unsure now I think about it.

 

[unproperlypropagated]

Yeah i have a user with 2 warnings both expired but it's not getting promoted.
I don't think I understand these permissions.

I want to target users with no active warnings.

EDIT: I think i had to also select "Include expired" for some reason

 

[rdn]

Question about this feature:

Anonymize warnings and warning alerts as a particular user or as a generic 'Moderation Staff' (WarningStaff phrase).

Does this also anonymize the staff giving warning points via the DM/conversation created?

 

[Xon]

Yes, it does that by creation the conversation from the anonymized account rather than the staff who issued the warning

 

[rdn]

On the overview page, it says:

Does NOT change conversations.

I think it should be

Does NOT change old conversations.

or

Does NOT change old DMs.

 

[Xon]

On the overview page, it says:


I think it should be

or

I've updated the text a bit to be clear it is about existing conversations/direct messages

 

[rdn]

Is this intended or a bug?

sv_warning_view select radio is appearing on user changelogs?

Sample:

 

[Xon]

I forgot to release the version which stops that column being tracked by the change log. I'll release it on Monday

 

[Xon]

Xon updated Warning Improvements by Xon with a new update entry:

2.11.6 - Maintenance update

• Stop logging sv_warning_view changes to the user change log and purges these entries

Read the rest of this update entry...

 

[rdn]

Hi Xon, is it possible to disable the "Spoiler contents" and "Disable reactions" content action options when issuing warnings for all the moderators in the front end?

I tried doing this, but it doesn't work.

 

[Xon]

Hi Xon, is it possible to disable the "Spoiler contents" and "Disable reactions" content action options when issuing warnings for all the moderators in the front end?

I tried doing this, but it doesn't work.

View attachment 325991

There isn't a toggle to enable/disable this feature. You can disable the template modification Add "Disable reactions" at the end of "Content action" section to disable this feature when issuing a warning.

 

[Grumpy Squid]

We're getting this error from the addon in the ACP: Template error: [E_USER_WARNING] Method canViewWarningActions is not callable on the given object (SV\SearchImprovements\XF\Entity\User)

Any ideas?

 

[Xon]

Without seeing the template or the stack trace, impossible to tell.

Try ensuring no src/addons/SV/WarningImprovements/_output folder exists and then rebuild the add-on.

 

[Grumpy Squid]

_output was missing I rebuilt the add-on, but it did not fix the issue.

Here is the stack trace:

#0 [internal function]: XF\Template\Templater->handleTemplateError(512, '[E_USER_WARNING...', '/srv/www/forums...', 1277)
#1 src/XF/Template/Templater.php(1277): trigger_error('Method canViewW...', 512)
#2 internal_data/code_cache/templates/l1/s47/public/sv_warningimprovements_member_view_warning_actions.php(7): XF\Template\Templater->method(Object(SV\SearchImprovements\XF\Entity\User), 'canViewWarningA...', Array)
#3 src/XF/Template/Templater.php(1799): XF\Template\Templater->{closure}(Object(SV\StandardLib\XF\Template\Templater), Array, NULL)
#4 src/XF/Template/Templater.php(1873): XF\Template\Templater->renderTemplate('sv_warningimpro...', Array)
#5 internal_data/code_cache/templates/l1/s47/public/member_view.php(567): XF\Template\Templater->includeTemplate('public:sv_warni...', Array)
#6 src/XF/Template/Templater.php(1799): XF\Template\Templater->{closure}(Object(SV\StandardLib\XF\Template\Templater), Array, NULL)
#7 src/XF/Template/Template.php(24): XF\Template\Templater->renderTemplate('member_view', Array)
#8 src/XF/Mvc/Renderer/Html.php(50): XF\Template\Template->render()
#9 src/XF/Mvc/Dispatcher.php(471): XF\Mvc\Renderer\Html->renderView('XF:Member\\View', 'public:member_v...', Array)
#10 src/XF/Mvc/Dispatcher.php(453): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#11 src/XF/Mvc/Dispatcher.php(412): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#12 src/XF/Mvc/Dispatcher.php(66): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#13 src/XF/App.php(2824): XF\Mvc\Dispatcher->run()
#14 src/XF.php(806): XF\App->run()
#15 index.php(23): XF::runApp('XF\\Pub\\App')
#16 {main}

and the request state:

array(4) {
  ["url"] => string(38) "/index.php?members/USERNAME.291/page-9"
  ["referrer"] => bool(false)
  ["_GET"] => array(1) {
    ["members/baconfry_291/page-9"] => string(0) ""
  }
  ["_POST"] => array(0) {
  }
}

 

[Xon]

@Grumpy Squid does this happen on the stock theme? The member_view template should have a $user set and this template should only be rendered if the user exists