@Kephir and Mr. Stradivarius: Is it possible to alter the module so that it doesn't throw up a "Warning: this page (Wikipedia:Cascade-protected items) is not cascade-protected." message while on Wikipedia:Cascade-protected items? The actual content that is cascade protected is on Wikipedia:Cascade-protected items/content, which is transcluded on the previous page so that that page can be edited freely. Jo-Jo Eumerus (talk, contributions) 16:03, 16 March 2017 (UTC)
FYI, it looks like the expensive function count thing described in the comment as an "outrageous abuse of Scribunto API" was fixed in December 2014 with gerrit:178698. Anomie⚔ 13:02, 26 February 2019 (UTC)
@Mr. Stradivarius: According to 770715327, your (most recent) 2017 edit:
-- XXX: there seems to be no way to check for cascading protection using a
-- Scribunto API, so we have to use frame:preprocess with the
-- CASCADINGSOURCES parser function.
This is not true and was not true in 2017 when the edit was made. In fact, mw.title
objects have had a field named cascadingProtection
since gerrit:132730 by Jackmcbarn (talk · contribs) was merged on 2014-08-13 and released as part of MediaWiki 1.24 on 2014-11-26, only a few months after ((CASCADINGSOURCES))
was introduced in MediaWiki 1.23 on 2014-06-05.
Sadly, I only just recently added this to the English documentation: mw:Special:Diff/3921942/prev.
Also I believe "extaneous" is misspelled earlier in the same comment block. —Uzume (talk) 07:00, 22 June 2020 (UTC)
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please make these changes, per the above. Jackmcbarn (talk) 21:46, 26 July 2020 (UTC)