User talk:ClueBot NG/Warnings/FPReport
Protected edit request on 18 March 2014[edit]
 | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Shouldn't this be using a protocol relative URL (//tools.wmflabs.org/cluebot/?page=View&id=12345 instead of http://tools.wmflabs.org/cluebot/?page=View&id=12345)? — {{U|Technical 13}} (t • e • c) 16:04, 18 March 2014 (UTC)
- Support. However, "HTTPS security is compromised by http://www.google.com/recaptcha/api/challenge?k=6LfNb-kSAAAAAELmJplTPPM8Gz2-p4YA68vIMgq8". Could the tool's owner switch that link to protocol relative URL too (i.e. //www.google.com/recaptcha/api/challenge?k=6LfNb-kSAAAAAELmJplTPPM8Gz2-p4YA68vIMgq8? Chmarkine (talk) 02:45, 19 March 2014 (UTC)
Done. Chmarkine, if you want to change the recaptcha code, you should contact the appropriate member of the ClueBot NG team. — Mr. Stradivarius ♪ talk ♪ 12:05, 19 March 2014 (UTC)
- I don't really see why this is required - the page is not guaranteed to be behind https, it just happens to be currently (so urls may break). The only thing that should be forced to https is the login, which is bad anyway and should move to use oauth (which wasn't available at the time). Considering this change (on any decent browser at least), will actually cause confusion for people trying to report issues over https I don't really support the change in the current state, but on the other hand there are many things that need fixing and I don't specifically care enough about this issue. - Damian Zaremba (talk • contribs) 19:14, 19 March 2014 (UTC)
Protected edit request on 28 August 2017[edit]
| This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The link produced by the template leads to an error page. To repair the link, change "cluebot" in the URL to "cluebotng". --87.177.125.74 (talk) 21:10, 28 August 2017 (UTC)
Protected edit request on 19 April 2018[edit]
| This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
This link here I have found on the user page, and looking at the comments, it appears that the link from user talk pages saying "report it here" from the Warning1 page, but I've noticed from the ClueBot Commons page that False Positives are being reported there. //tools.wmflabs.org/cluebotng/?page=View&id={{urlencode:{{{1|12345}}}}} could be changed to something like https://en.wikipedia.org/w/index.php?title=User_talk:ClueBot_Commons§ion=new&veaction=editsource to report false positives from talk pages until the technical issue is fixed. Iggy (Swan) 18:48, 19 April 2018 (UTC) Iggy (Swan) 18:48, 19 April 2018 (UTC)
- No, sorry. These get subst'd into user talk pages, and we don't want to send them directly to the talk page editor interface without anything else describing what information at the very least is required. Honestly, at this point, we just need to fix the report interface, rather than updating people to post on the talk page, because the posts on the talk page are, for the most part, useless. -- Cobi(t|c|b) 21:38, 19 April 2018 (UTC)
Update URL[edit]
| This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change //tools.wmflabs.org/cluebotng/?page=View&id={{urlencode:{{{1|12345}}}}} to https://cluebotng.toolforge.org/?page=View&id={{urlencode:{{{1|12345}}}}} as the URL has changed and the protocol-relative bit isn't needed anymore since both Wikipedia and the interface are https only now
Thanks --Nintendofan885T&Cs apply 10:21, 3 September 2020 (UTC)
Done @Nintendofan885: let me know if any problems. — xaosflux Talk 14:32, 3 September 2020 (UTC)
