CZ Talk:Enhancing your editing with javascript extensions

Shouldn't this page be titled CZ:Enhancing your editing with javascript extensions ? There's a difference, after all. Anthony Argyriou 15:54, 28 June 2007 (CDT)

I thus defer. Stephen Ewen 15:59, 28 June 2007 (CDT)

Some of the popups functionality seems to be broken, I think since the MediaWiki upgrade. Anthony Argyriou 11:02, 15 October 2007 (CDT)

Yep, it's probably not a big thing to fix. Anyone wanna try? :-)  —Stephen Ewen (Talk) 11:17, 15 October 2007 (CDT)

Has anyone tried to fix this? I can still not get the popups to work on FireFox unless the link it to an anchor on the same page (such as to a reference). In addition to the usual version of popups.js at http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js], there is also a version mentioned by User_talk:ZachPruckowski at User:Nicholas_Kaye-Smith/popups.js, but it does not work for me either. Also, CZ:Enhancing your editing with javascript extensions recommends creating a Pinkwich5.js file, which is identical to the monobook.js recommended by the original Lupin script. - Robert Badgett 21:19, 21 June 2008 (CDT)

I agree Robert, it sure would be nice if someone could get this to work for us. --D. Matt Innis 21:45, 21 June 2008 (CDT)

The popups script does not work due to a change in the server configuration. The exact setting is the system which rewrites URL's in a "search engine friendly style. It should be a relatively simple fix by the technical team and a bug report has been submitted but no response has been received. Derek Harkness 00:22, 22 June 2008 (CDT)

I think I got it to work a few days ago by changing the scripts to reflect the URL change (diff). I intended to ask somebody to test it, but I didn't get around to it.

New instructions: copy this revision of my Pinkwich5.js to your Pinkwich5.js file. Try it out, let me know if it works, and I'll change the instructions here (or, even better, change the instructions yourself and save me some work!). -- Jitse Niesen 07:41, 22 June 2008 (CDT)

It works! This is great work. I will fix the instructions. Ok if:

1. I tell users to put the js call in [[Special:Mypage/monobook.js]] to be consistent with WP rather than to encourage an differently named js file?

2. Ok that I edited Template:Navpop to call your js rather than WP's http://en.wikipedia.org/w/index.php?title=User:Lupin/popups.js?

If all ok, I will edit our instructions to tell users to put "{{Navpop}}" in their [[Special:Mypage/monobook.js]].

Bob - Robert Badgett 20:24, 23 June 2008 (CDT)

You can't use monobook.js. This web site doesn't use the monobook skin. The .js file must match the name of the skin that you are using, which for most people will be the Pinkwich5 skin so the file should be called pinkwich5.js. Derek Harkness 21:59, 23 June 2008 (CDT)

Curious, my login is working fine with the call to the js file coming from [[Special:Mypage/monobook.js]].____

Presumable you are using the monobook skin (which looks like wikipedia) rather than the new skin. Derek Harkness 04:39, 24 June 2008 (CDT)

It does not look like WP. Please remind me how I tell which skin I am using. Robert Badgett 09:19, 24 June 2008 (CDT)

Bob, go to Special:Preferences and click on the Skin tab. The option that is selected is the skin that you are using. -- Jitse Niesen 11:37, 24 June 2008 (CDT)

That explains it. Thanks - Robert Badgett 11:54, 24 June 2008 (CDT)

Jitse, I've added your code to my pinkwich5.js and it all seems to be working. Derek Harkness 21:59, 23 June 2008 (CDT)

Navpop template

Can installing navpops just be a checkbox on Special:Preferences?

If not, I made Template:Navpop. However, does anybody see why it does not substitute text when added to your Pinkwich5.js?

Bob - Robert Badgett 11:54, 24 June 2008 (CDT)