I need to roll out some patches on the Dev wiki. There's a few security patches I need to roll out, and schema needs to be rewritten to survive the death of verbatim. I understand you still have edit permissions on there. If I give you updated code, would you be willing to publish updates on there?
I am aware of the recent events that took place on Dev Wiki. Seeing this, I believe they could be the cause of none of the scripts my global.js working. Would it be possible to find out which script(s) are causing this so it/they can be removed?
As far as I'm aware, simply protecting a number of files will not cause any problems. Have you tried looking in your js console to see if there are any specific errors there? Due to the nature of how you load all your scripts, one script being faulty would not cause the others to fail.
Hey cqm, I hope you don't mind me posting this here, since it seems a bit off topic for the dev wiki highlighted thread, and ProtectSite means I currently can't edit your talk page there.
I don't have a list of which scripts were affected specifically to hand, but there was nothing too harmful added to the scripts during the short time they were vandalised. However, I do not know the nature of the two sites you mentioned, so it may be worthwhile running a scan if you were one of the users affected by the changes.
for some odd reason it won't let me leave a comment so i'll just tell you here. ozuzanna made a massprotect script, works fairly well; would save you the time though would need expansion to include codeeditor rights.
i left you a talk page message regarding a deletion, not sure if you ever approved it. i'll just keep updating my instructions on a test wiki and if needed, have someone perform a full copy-replace.
I did indeed see Ozuzanna's script, but I didn't want to pick it apart to figure out how to make the protection level loading automatic. Either way, I'm making two clicks per protection at the moment so it's not too bad :)
Cqm wrote: I did indeed see Ozuzanna's script, but I didn't want to pick it apart to figure out how to make the protection level loading automatic. Either way, I'm making two clicks per protection at the moment so it's not too bad :)
like i said, it was made for general use (so sysop) so it didn't have the codeeditor option but besides that all that is needed is a list inputed and select the protect time (first option).
one possibility besides requiring peer review is to simply have people create scripts on a test wiki, confirm it works then transfer + lock it. before transfer, also have installation instructions avaliable. this would make dev wiki be more of a closed wiki. best thing is to lock scripts once made or only allow codeeditors to edit.
I read the discussion over the dev wiki and headed to the codeeditor page, in order to request one, but since the entire wiki is locked, i'm unable to make new requests there, so i'm contacting you here.
So, i would like to make a request for codeeditor rights for the dev wiki, if i may. I read the criteria, and i believe i fulfill it- i have had experience with CSS and JS coding (i've made quite a few codes for the dev wiki in the past)- and i'm willing to keep creating new codes and maintenancing my existing work for those who are interested in them.