Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverting with the bot option should not trigger notifications #25

Open
ciencia opened this issue Jan 7, 2019 · 5 comments
Open

Reverting with the bot option should not trigger notifications #25

ciencia opened this issue Jan 7, 2019 · 5 comments

Comments

@ciencia
Copy link

ciencia commented Jan 7, 2019

When adding bot=1 to URL parameters on revert, it shouldn't send notifications to Discord. Or at least, allow it to be configurable.

@kulttuuri
Copy link
Owner

Could you explain the bot=1 parameter / revert more in-depth or link article that explains this? I'm not familiar with bot options myself on Mediawiki.

@kulttuuri
Copy link
Owner

Possibly duplicate with #35

@ciencia
Copy link
Author

ciencia commented May 18, 2019

Ah, sorry, I lost some notifications... You can revert pages adding bot=1 to the URL, and it will mark such rollback actions as bot (both the rollback and the edits being rollback). Even on Special:Contributions, it will propagate the bot=1 parameter to all rollback links. Useful for vandalism. This doesn't require the bot flag

See also https://www.mediawiki.org/wiki/Manual:Administrators#Rollback

When I did this, my rollbacks were triggering notiftications despite them being hidden by default from recent changes.

@kulttuuri
Copy link
Owner

I see. Will have a look at this!

@kulttuuri
Copy link
Owner

I've tried catching this parameter somehow, but no luck. The problem is that I could not find this parameter anywhere in the parameters passed to the $article, $revision etc... It's not also possible to check the query parameters or use MediaWiki's $wgRequest parameter because these parameters are being checked from the final URL, not the one you submit.

Leaving this thread open for someone else to tackle this, though...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants