Blaster Niceshot wrote: Just wanted to let you know that the code is functioning and that I am working on the script for this. So far, I have most of the external-to-internal conversion done, but I still need to create the internal-to-external conversion.
If you want see what I've written so far, you can look at my wikia.js on my test wiki.
Yippee!! :)
Thanks Blaster Niceshot! :) — SpikeToronto 10:16, January 23, 2017 (UTC)
HyperFlash Studios wrote: Interesting idea, I'll look into it.
Thanks! :)
I think it would be great if there were a script that would convert every local link in an article (or batch of articles) expressed as a full URL (e.g., http://dev.wikia.com/wiki/Board:Script_Suggestions) into proper wikilinks (e.g., [[Board:Script Suggestions]]).
Nerfmaster8 wrote: before anyone seriously considers making this, what's the actual point to wanting to move a category to main namespace?
@Nerf: It is not your job to police requests for scripts, nor require justification before others start a project that might interest them.
@Nerfie: I tried both MediaWiki:MassRedirect/code.1.js and MediaWiki:MassRename/code.js, and neither worked.
The Category namespace is peculiar in that normal methods of renaming/moving do not work, by design. The only existing script that comes close is MediaWiki:CategoryRenameAuto-update/code.js, which, after re-categorizing each of the pages populating a category, deletes the old category page, and recreates it in the Category namespace under the new name, albeit without any of the revision history.
I would like a script that – one at a time – moves a page from the Category namespace to mainspace along with its revision history. Essentially, it would be as if it were removing the Category: prefix from the name. Since it would work on a per-page basis, it would probably make sense for it to be on the Edit menu dropdown.
Thanks! :)
Okay. Well, I just tried it on my home wiki, and I could not get it to work.
This may be because MediaWiki:Custom-Filesource and MediaWiki:Filesource cannot both exist at the same time, and I did not want to delete the latter since I’d have no way to get it back.
Perhaps someone else can test this, because, if it works, it’d be better than adding yet another script to one’s home wiki.
No. It would just be pure text that gets input into each new file description page when a new file is uploaded.
If you go to MediaWiki:Filestatus you can see the default contents of that page.
If you upload an image to, for example, File:Test.jpg, you would see that text on that page after the upload. Therefore, anything on that MW page gets saved to the new file page. Hence why adding your category to that MW page should work.
But, there’s one catch: We can no longer edit that page. However, supposedly, if we create a new version of MediaWiki:Filestatus at MediaWiki:Custom-filestatus, it should override the text at MediaWiki:Filestatus and then work.
How can a script operate as a script if it is not on a page with a .js ending?
And, if it cannot, then I don’t understand the security risk (admittedly dumb here).
Whenever Special:Upload is used, the contents of MediaWiki:Filestatus are input to the related file description page that gets created.
You could just add [[Category:Images]] to the bottom of that page. This would, thenceforth, add that category to every image uploaded via Special:Upload.
P.S. You may have to do this by creating a new page at MediaWiki:Custom-filestatus since the real page – MediaWiki:Filestatus – is locked to us (i.e., not whitelisted).
DaNASCAT wrote: Hey there,
Catching up on this thread. For clarity, we have no issue approving a replacement as long as each edit to the replacement goes through JS Review. So if you were to build a script that relied on edits in, say, the Template namespace to change how/what the script does, then we would deny it. If any changes to psuedoGadgets scripts are in the MediaWiki namespace with .JS page endings, it will be fine.
Oh. You mean like Gadgets?
All scripts under gadgets are equally subject to JSReview since they are housed
… in the MediaWiki namespace with .JS page endings …Gee, seems to me like that condition is already satisfied … by Gadgets!
A personal-use script that causes the post-delete behavior of Special:Delete in the Oasis skin to behave as it does in the Monobook skin.
I’ve been emailing with Staff on this issue for a few weeks now.
For some reason, Staff are of the opinion that (a) there is no appreciable benefit from its use, and (b) it is a security risk (yes, that bogey man, again) despite the fact that scripts used by Gadgets are contained in pages with the .js filename extension, and therefore are all subject to JSReview.
Bottom line: Staff are implicitly saying that those of us on wikis who have Gadgets activated, or are seeking its activation, are not trustworthy.
So, it seems Gadgets may be yet one more exceptional tool that is to be lost to us as those ropes tying one hand behind our backs are made ever tighter.
Can you provide a screencap? I don’t see it atop pages in Oasis. Thanks! :)
