User talk:Cacycle/wikEd/Archive 008

BUG - WikiED is freezing

(Moved to page bottom. Cacycle (talk) 12:09, 29 July 2008 (UTC))

Enhancement Request - Customize URL conversion

Suppose you take these steps:

• Browse to internal MediaWiki site
• Copy name of MediaWiki page ("Foo Bar") to some HTML editor like Word
• Hyperlink the title "Foo Bar" to the URL of that page, giving (in our case) <<a href="http://wiki/index.php/Foo_Bar">Foo</a>
• Copy the hyperlinked word wikEd and hit [W]

Here is what I actually get in 0.9.44f:

[[index.php/Foo Bar|Foo Bar]]

Here is what I think I should get:

[[Foo Bar|Foo Bar]]

Or better yet, because the strings before and after the pipe are now identical:

[[Foo Bar]]

So is the URL conversion configurable - can I define what wikEd expects to see as the URL prefix?

Tom.ngo 11:13, 5 October 2007 (UTC)

WikEd hangs Firefox after search in long article

Using Firefox 3.0 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0) with all add-ons disabled, on Windows XP. Version of wikEd could not be determined: hovering over logo flashes some popup box for only a fraction of a second. Updated to last version with Shift-Reload. Only other script in use: Lupin's popups.js.

To reproduce the problem:

1. Go to [1]
2. Use WikEd's incremental search feature to search for "subtitle" (without the quotes). The first instance of the word will be highlighted.
3. Click on any other word in the edit box.
4. Firefox hangs; its CPU usage goes through the roof.

Cheers, AxelBoldt (talk) 02:33, 26 May 2008 (UTC)

When I use the same Firefox version (3.0 preview) with or without Popups gadget or using your monobook.js everything works fine for me - the logo popup works and I cannot reproduce your problem. Does it persist if you restart your browser / computer. Cacycle (talk) 03:58, 26 May 2008 (UTC)

Restarting the browser doesn't help, but rebooting sometimes does. I believe it has to do with Java: when I first go to a Java-heavy site and then to Wikipedia, the above happens. I'll check the bug reports for Firefox, maybe they screwed something up in the latest versions. Thanks, AxelBoldt (talk) 07:21, 26 May 2008 (UTC)

I've had the same thing occur on Ubuntu (using XP and Ubuntu) ffm 19:59, 2 June 2008 (UTC)

I also experience this slowdown – just open a page of around 100 KB with wikEd enabled and syntax highlighting on and Firefox hangs. Thanks Rjwilmsi 22:24, 4 July 2008 (UTC)

Alphabetical sorting

Is it possible to use wikEd to sort a list alphabetically? If not, do you know of a tool that will do this? --NigelG (or Ndsg) | Talk 17:52, 18 January 2008 (UTC)

It is not yet possible, but it is a good idea. You can sort lines in MS-WORD or in better text editors. Сасусlе 04:18, 31 January 2008 (UTC)

Thanks for the response. Yes, in practice I tend to use Word. What I had in mind was a quick way of getting lists such as bibliographies into alpha order. --NigelG (or Ndsg) | Talk 09:22, 31 January 2008 (UTC)

Added to 0.9.64g. Cacycle (talk) 02:51, 1 September 2008 (UTC)

This needs testing on long lists (over ~20 lines), and lists beginning with non alpha numerical characters (like bulleted lists, and lists with links. It doesn't work at all on my wiki - it re-sorts the list, but in some random order. Haven't tried it on wikipedia. --naught101 (talk) 07:01, 28 September 2008 (UTC)

Actually, after a second look, it appears that only lists with links ([ at the start) are screwed - bullets and numbered lists work fine.--naught101 (talk) 08:13, 28 September 2008 (UTC)

Ref tags again

Is there some way of omitting the "name" parameter in the <ref> tag? The problem is that the default <ref name=""> generates multiple references, as if "" were a real name. To get round this, I have to manually delete the "name" parameter. --NigelG (or Ndsg) | Talk 21:39, 20 January 2008 (UTC)

PS Something like Shift-Click would do the trick, I imagine. --NigelG (or Ndsg) | Talk 19:01, 21 January 2008 (UTC)

Implemented in 0.9.60. Сасусlе 04:16, 31 January 2008 (UTC)

Thanks for the speedy action: excellent! --NigelG (or Ndsg) | Talk 09:24, 31 January 2008 (UTC)

devmo/mdc support

Hey, I know I told you about how wikEd didn't work with cavendish. But, now my site uses devmo (and I occasionally use mdc). So could you support those skins?

Devmo edit page mdc edit page

Using wikEd 0.9.6f GM Firefox 3.0b4pre

Thanks,

onekopaka (talk) 03:26, 13 February 2008 (UTC)

Both skins / sites are already supported. If you have problems, please drop me note to fix it. :-) Сасусlе 03:32, 13 February 2008 (UTC)

I just tried it (having just fixed my wiki) and wikEd doesn't work in devmo or mdc skins. onekopaka (talk) 02:17, 8 March 2008 (UTC)

Devmo and Cavendish support has been fixed in 0.9.63d. Cacycle (talk) 02:25, 23 June 2008 (UTC)

Problem with diff in history page on :fr

Hi, some people on :fr have seen that there is a problem with diff display in history page. You can see an example here.

Text in left column :

• Il compose également pour d'autres notamment [[Ute Lemper]] avec qui il chantera '''"Parler d'amour'''" (n°22 au Top 50 en {{date||janvier|1994|en musique}}), [[Henri Salvador]], [[Enrico Macias]], [[Florent Pagny]] et [[Johnny Hallyday]] notamment.

In right column :

• Il compose également pour d'autres notamment [[Ute Lemper]] avec qui il chantera '''"Parler d'amour'''" (n°22 au Top 50 en {{date||janvier|1994|en musique}}), [[Henri Salvador]], [[Enrico Macias]], [[Florent Pagny]] , [[ Jane Birkin]] , [[Johnny Hallyday]] , [[ Juliette Greco]] , et [[ Liane Folie ]] notamment.

In fact, the following text should be highlight : , [[ Juliette Greco]] , et [[ Liane Folie ]]

People on :fr see that problem regulary when there is a modification before and after ]] in a paragraph.

Have you ever heard about this problem or is it specific on :fr ?

I precise that tests have been realised with Firefox and IE with windows and linux. It seems that it works correctly when wikEd is retire from monobook or gadget.

You can reply directly in original discussion here (if you want ).

Thanks Leag (talk) 09:51, 17 February 2008 (UTC)

This is an interference with the wikEdDiff function of making the links clickable. I will check the code to see if there is a simple fix. If not, I could make the links only clickable if the button is clicked. Thanks for notifying me, Сасусlе 01:43, 18 February 2008 (UTC)

Fixed in wikEdDiff.js 0.9.5b Cacycle (talk) 03:38, 13 July 2008 (UTC)

Feature request

Sort bulleted lists. When an item begins with a link that has a pipe, the pipe part should be what that item is sorted by. To make the sorting truly great, the sorting feature should recognize persons' names and sort items that begin with a name by the surname portion of the name (followed by the first name for continued sort order). The Transhumanist    14:46, 2 March 2008 (UTC)

The ts_sort_* functions in wikibits.js might be useful for that, especially since some wikipedias override them to make table sorting work correctly on their alphabets. --Tgr (talk) 10:46, 4 March 2008 (UTC)

Thanks for the suggestion. It is already on the list since a while, but it will definitely come. Сасусlе 17:22, 4 March 2008 (UTC)

Sorting has been added (0.9.64g), use the button. Cacycle (talk) 02:53, 1 September 2008 (UTC)

Bug: Searching/replacing newlines

Hallo, searching and/or an newline using the RegEx '\n' dosen't work - but clicking on "replace all" does work. Would it be possible to fix/enhance wikEd so, that you also can search/replace one by one? That's often needed to repair text copied form other documents... - Real cool plugin! --- 88.217.12.166 (talk) 12:49, 23 March 2008 (UTC)

I did some testing and it seems to be a Firefox bug, but I am still working on it. Сасусlе 12:40, 25 March 2008 (UTC)

Hyperlink conversion bug

First of all, congratulations for your work. Onto the bugs: Copying and pasting hyperlinks from a M$-Word document does not work properly, when the links point back to the wiki server that hosts the page being edited.

For example, assume we have just three words in a Word document: "one" "two" and "three". These are links that respectively point to:

1. http://happysheep.org/wiki/Main_Page
2. http://happysheep.org/wikidev/index.php/Main_Page
3. http://stupidcows.org/wiki/Main_Page

Copying/pasting these links with wikiEd in the wiki article that is at http://happysheep.org/wiki/Blah and then clicking the "wikify" button results in the following wikitext:

1. [../wiki/Main_Page one]
2. [../wikidev/index.php/Main_Page two]
3. [http://stupidcows.org/wiki/Main_Page three]

So there seems to be an effort to convert the links to relative (which fails in this context) - only the 3rd link is properly converted.

I'm using:

• M$-Word 2007 SP1
• Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13
• WikiEd 0.9.62c (April 6 2008)

Apapadop (talk) 14:12, 10 April 2008 (UTC)

Probably fixed in 0.9.62e. Please could you check? Thanks, Сасусlе 04:44, 11 April 2008 (UTC)

Hrmf, partly. Links #1 and #3 work, link #2 (same site name, different wiki instance) does not. Link #1 is converted to [[Main_Page|One]] which works, but seems to me less portable/stable than an absolute hyperlink. Link #2 is converted to [[wikidev/index.php/Main_Page|two]] which is broken. Link #3 is properly converted to an external full-URL hyperlink. I'd generally like to see the links kept absolute (i.e. the full URL). I believe it's a safer approach. Thanks for the input. Apapadop (talk) 16:20, 11 April 2008 (UTC)

Most probably fixed in 0.9.62f. Link #1 must be converted to a wikilink as the pasted html link is identical to pasted wikilinks from an article. Thanks, Сасусlе 06:23, 12 April 2008 (UTC)

Results with 0.9.62f:

1. [http://happysheep.org/w/wiki/Main_Page one]
2. [http://happysheep.org/w/wikidev/index.php/Main_Page two]
3. [http://stupidcows.org/wiki/Main_Page three]

So basically #1 and #2 are still broken, as they should have been

1. [http://happysheep.org/wiki/Main_Page one]
2. [http://happysheep.org/wikidev/index.php/Main_Page two]

or

1. [Main_Page|one]
2. [http://happysheep.org/wikidev/index.php/Main_Page two]

Please note that mediawiki URL rewrite rules are used to present a nicer URL, hence the physical path on the server is w/index.php?article=Main_Page while the URL presented is wiki/Main_Page. As WikiEd can not have knowledge of the rewrite rules of each site, it's safest to use the absolute URLs, as captured in the M$-Word hyperlink.

Also, pasting the clipboard to a wiki page belonding to another wiki instance on the same server (for instance http://happysheep.org/wikied/index.php/Sandbox) also returns erroneous results:

1. [http://happysheep.org/wikied/wiki/Main_Page one]
2. [http://happysheep.org/wikied/wikidev/index.php/Main_Page two]
3. [http://stupidcows.org/wiki/Main_Page three]

So, #1 basically hijacks the link, #2 is a 404 and #3 works. Apapadop (talk) 13:16, 14 April 2008 (UTC)

It would immensely help me to fix any remaining error if you could give me the links to your two wiki installations (you can email me). Thanks, Сасусlе 03:22, 26 April 2008 (UTC)

Can I take specific features from this?

I like the purple buttons for fixing dashes, line breaks, and capitalisation, but I don't think I need all of the other features attached to this. Is it possible to customise this gadget to just add those buttons to my toolbar like refTools does? --Arctic Gnome (talk • contribs) 03:17, 11 April 2008 (UTC)

You can minimize the button bars by clicking their handle. Сасусlе 04:13, 11 April 2008 (UTC)

But how do I add just the purple buttons without adding all the other buttons and the stuff that makes the editing window all colourful? In TW and Friendly, there is a page that clearly says "to add this feature, add this text", but I can't find an equivalent page for this gadget. --Arctic Gnome (talk • contribs) 04:20, 11 April 2008 (UTC)

It is not possible to use wikEd without certain buttons (such as the [T] button or the control buttons). I suggest that you try to use it for a while to get a feeling for it, many of the other formatting buttons are actually quite useful (e.g. because you do not have to select a word or a line). Сасусlе 04:43, 11 April 2008 (UTC)

Button don't work

• WikEd version 0.9.62g GM
• Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
• Error: [Exception... "Security Manager vetoed action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)" location: "JS frame :: https://wikiis..com/index.php?title=Accueil&action=edit :: anonymous :: line 0" data: no] Source File: https://wikiis..com/index.php?title=Accueil&action=edit Line: 0
• Windows XP SP2

• No user script in monobook.js but if I installed wikEd it in monobook.js and disable Greasemonkey the buttons work
• When clicking on on a button nothings happens except that I lose the cursor in the editing frame. Although, the keyboard shortcut work i.e. alt-shift-b

--Abrillon (talk) 23:27, 18 June 2008 (UTC)

All these problems are most probably caused by Firefox 3 using an outdated Greasemonkey version. It works fine for me using Firefox 3.0 and Greasemonkey 0.8.20080609.0. Please update your Greasemonkey add-on under https://addons.mozilla.org/en-US/firefox/addon/748. Cacycle (talk) 02:45, 19 June 2008 (UTC)

It seems to be a Firefox bug, see above. Cacycle (talk) 15:38, 22 June 2008 (UTC)

Firefox 3.0.x nightlies

Now that Firefox 3.0 is stable, the Mozilla folks have forked trunk to the 3.1 branch. Meanwhile, nightlies of the 3.0 branch (gecko 1.9.0) are now given a different codename, which apparently confuses WikiED. Since this is the stable branch, the nightly builds will not introduce any major changes. Thus, could you modify WikiED's code to accept the following user agent string:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1pre) Gecko/2008061905 GranParadiso/3.0.1pre
Thanks! --Dragon695 (talk) 03:13, 20 June 2008 (UTC)

Yes, as soon as I find the time. Cacycle (talk) 13:09, 20 June 2008 (UTC)

Added to 0.9.63. Cacycle (talk) 05:32, 21 June 2008 (UTC)

Bug: link color when link starts with "http://www.gui"

Whenever there's a URL that starts with "http://www.gui", only the "http://www.gu" portion of the URL shows up in bold red; the rest is just black. (Note that I just upgraded to Firefox 3 yesterday, and I'm just noticing this problem now.) --zenohockey (talk) 03:07, 21 June 2008 (UTC)

A similar problem: http://everything2.com/ is rendered with only "http://everyth" in red. --zenohockey (talk) 03:15, 21 June 2008 (UTC)

It is a Firefox 3.0 bug (see https://bugzilla.mozilla.org/show_bug.cgi?id=440926). Cacycle (talk) 04:22, 21 June 2008 (UTC)

I see... Thanks for reporting it, then. --zenohockey (talk) 18:44, 21 June 2008 (UTC)

Regex :fr

Hi, I'm sorry to write you again for the same problem but the regex typo fix doesn't work on :fr. The icon doesn't appear in the toolbar. Is there an error on my monobook.js ? Thanks Leag (talk) 11:32, 23 June 2008 (UTC)

It is probably a bug, I will fix this later. Cacycle (talk) 21:59, 23 June 2008 (UTC)

Thanks Leag (talk) 06:23, 24 June 2008 (UTC)

It is not a bug, you have to change the address customization into:

var wikEdRegExTypoFixURL = 'http://fr.wikipedia.org/w/index.php?title=Wikipédia:AutoWikiBrowser/Typos&action=raw';

I have corrected the customization page. Cacycle (talk) 03:34, 26 June 2008 (UTC)

Thanks a lot for these corrections, it works. I think on :fr we have to add var wikEdFixPunctFrench = true; to make RegExTypoFix working (but I'm not sure). Thanks again. Leag (talk) 06:56, 27 June 2008 (UTC)

wikEd Bug

Hi Cacycle, and first, let me thank you for your wonderful creation; it's helped me a ton. But, there is one minor bug. Whenever you use the fix spaces before punctuation button, it breaks <br>'s and images, since it spaces before the extension. Is there any way you could fix this? Please reply here, Thanks again!
Eu 21:37, 23 June 2008 (UTC)

Thanks for the suggestion, that is already on the feature wish list. It will come, but it might take a while as it is not trivial to implement (after all, it is done by regular expressions and not a wikicode parser). Cacycle (talk) 01:27, 27 June 2008 (UTC)

Somewhat alarming install behavior

I just had a very strange experience. I installed wikiEd a few days ago, and just now, upon navigating to a WP page from a Google results page, I was suddenly given the option to install the script, as if I had just clicked an install link for it... I had to rack my brain to remember I had chosen to install it a few days ago. I'm not sure what's up, but IMHO anything that asks users to trust a script after navigating to an arbitrary web page encourages unsafe behavior... if people start to get comfortable with suddenly seeing "install" screens as they surf the web, without having just then specifically asked to install the script, it opens up the door to all kinds of mischief. Just a thought.

Nice editor besides, though, thanks for your work. SteubenGlass (talk) 21:32, 26 June 2008 (UTC)

That is the auto-update mechanism under Greasemonkey. I will see if I can replace the installation window with a clickable link on an more informative popup. Unfortunately, the Greasemonkey install window does not (yet) show the installation URL. Thanks, Cacycle (talk) 01:24, 27 June 2008 (UTC)

Please see this Greasemonkey bug report. 03:49, 13 July 2008 (UTC)

Fixed in 0.9.64c with a short alert popup explaining the update and showing the download address. Cacycle (talk) 00:08, 20 July 2008 (UTC)

Request: Split screen editing

Today I was happily using wikEd (as I often do, with great delight) to edit a long wiki document and found myself scrolling up to compare information I was editing with information earlier in the document. I found that I was doing this a lot, and that I wish that I had a split screen bar that I could drag into the middle of the screen, like Microsoft Word and many text editors do, to split the editor into two panes so that I could look at the earlier information while entering in the newer information.

Here's to your good work on wikEd: thanks! Brion.finlay (talk) 22:23, 26 June 2008 (UTC)

Thanks for the suggestion, this would definitely be a nice feature to have. Unfortunately, this is probably beyond of what is possible in the limited time I can spend on this project and it would make the program too big and complex. However, if somebody finds an easy way to implement this, I would be happy to copy that solution into the main code. Cacycle (talk) 01:34, 27 June 2008 (UTC)

Epiphany

Latest wikEd 0.9.62g says "Browser not supported" when I use Epiphany (browser) 2.22.1.1 even though it is a browser using the Gecko-engine 1.9 by default. It worked before without problems. --Matthias M. (talk) 18:29, 9 June 2008 (UTC)

Okay with latest wikEd 0.9.63e G and/or 2.22.2 Epiphany this seems to be gone. Thanks for the fix, Cacycle or GNOME guys. --Matthias M. (talk) 08:34, 28 June 2008 (UTC)

Normal - not

When I paste text into an edit box with wikiEd on, it adds "Normal 0" in front of the pasted text, just a minor irritant, but what's happening? (Firefox 3, XP) jimfbleak (talk) 06:51, 29 June 2008 (UTC)

Not for me, please could you give me more infos (see the top of this page). Thanks, Cacycle (talk) 14:27, 29 June 2008 (UTC)

WikEd for Safari

OK, i finally decided to look back at my Safari changes to find a better way to fix the issue with the CSS. I think I have found a solution that is easy an unobtrusive but also works pretty good. This is the full diff of all changes to make wikEd work on Safari 3.1. It really isn't even that many changes, so I hope you will incorporate them soon. It still requires the skipbrowsertest option for safety, but I have few problems so far. --TheDJ (talk • contribs) 12:58, 1 July 2008 (UTC)

Thank you! I have added all your changes to the next release. Cacycle (talk) 03:00, 2 July 2008 (UTC)

I have one more error, though it's a bit rare apparently. There is this code:

var sel = WikEdGetSelection(); var range = sel.getRangeAt(sel.rangeCount - 1).cloneRange();

At times, sel.rangeCount will be 0 (There is no selection apparently?), and then getRangeAt() throws an error because of the negative value like it should. I can produce this consistently by hitting the "disable syntax highlighting" button, and then entering a searchterm. Every letter I try to enter there will then hit this error, and no searching while I type is occurring. I need to click on something in the editform (this creates a selectionrange I guess) to make it work again. I'm not really sure how that should be solved in the code. Guarding for the 0 value is easy of course, but I'm not sure if the code should bail, skip or fix that state when it encounters this. --TheDJ (talk • contribs) 13:46, 1 July 2008 (UTC)

I have added "if (obj.sel.rangeCount == 0) { obj.sel.collapse(wikEdFrameBody, 0); } " before all "(sel.rangeCount - 1)" lines. This should get rid of that error (which I cannot replicate in Firefox using your procedure). Cacycle (talk) 03:00, 2 July 2008 (UTC)

Confirmed to be working with that trick. Noticed btw, that somewhere in the code you have this comment: "workaround for Firefox 1.5 bug using: obj.sel.getRangeAt(obj.sel.rangeCount - 1).collapse(false);" Possibly that problem could have the same root cause as this one. ? --TheDJ (talk • contribs) 19:45, 3 July 2008 (UTC)

Fixed in wikEd 0.9.64. Thanks, Cacycle (talk) 03:44, 13 July 2008 (UTC)

Request: no boxes around pasted <pre> text

Currently, when copy-pasting text enclosed in <pre> tags, WikEd will insert "invisible" line breaks (i.e. it inserts in the textarea the box block-level elements like <pre> have). Is there any reasonable way to prevent the addition of those annoying 2+ linebreaks that will inevitably have to be deleted by hand? Circeus (talk) 17:10, 2 July 2008 (UTC)

As <pre> is a block level element, I do not really understand why you would not like to have the linebreaks. Can you give me an example to demonstrate your request?. Thanks, Cacycle (talk) 00:48, 3 July 2008 (UTC)

OK, I now understand the problem... I'll try to fix this. Cacycle (talk) 04:56, 3 July 2008 (UTC)

The issue is similar to the whitespace added by copy-pasting a header, but unlike with headers, the whitespace added by a <pre> teg can only be "converted" by using the "plain text" conversion, which is what creates the extra space. I don't normally use the "fix blank and empty lines" function (never have). Using it herewould still require using the "convert to plain text button" first (applying "fix blank lines" insert html <pre> tags), so it's still an annoying extra step either way. Circeus (talk) 18:22, 3 July 2008 (UTC)

Fixed in wikEd 0.9.64. Cacycle (talk) 03:43, 13 July 2008 (UTC)

"Punctuation and <ref>" fix button

Who thought it was an good idea to make this add a space after "<"? This will break any <nowiki>, <ref> or html tags in the article. (discussed above)

On the other end, something to fix punctuation/<ref> tags interaction (placing the tag after commas, colons, semicolons and periods, and stripping any spaces before the tag) would be an AMAZING addition. Circeus (talk) 18:28, 3 July 2008 (UTC)

Seamonkey not supported

It seems, that wikEd does not work with the Seamonkey Suite (Version. 1.10), which uses the same Gecko engine as do Firefox or similar browsers. --Goodgirl (talk) 07:27, 10 July 2008 (UTC)

I use Seamonkey 1.1.10 and it works fine for me :-) Cacycle (talk) 16:01, 10 July 2008 (UTC)

Do you think it might depend on the localization? I use a localized de-DE version. How does the script for the activation of wikEd determine, whether the browser is supported or not? Does it check the general.useragent.extra.seamonkey setting in about:config? I have set a value of “Mozilla 1.7.6” for compatibility with certain plug-ins. --Goodgirl (talk) 18:46, 10 July 2008 (UTC)

There we are: setting the general.useragent.extra.seamonkey value back to the default value of “SeaMonkey/1.1.10” did the trick, wikEd works. Is that a bug or a feature? *g* --Goodgirl (talk) 18:54, 10 July 2008 (UTC)

Feature request: Autocompletion

You should add autocompletion for template parameters. It would be a killer feature, to display a tooltip with a template's parameters whenever you type {{template|, and a tooltip with a parameter's description whenever you typed parameter=. It might be difficult to do so without some sort of standardized table on template pages with the parameters and descriptions, but it could be handcoded for the most popular templates like the cite templates.--Michael White^T·C 14:09, 11 July 2008 (UTC)

This would be a nice idea. Unfortunately, I cannot develop this as it is a bit off focus for wikEd. But I would be happy to make it compatible with wikEd if somebody creates this. Have you checked Lupin's Popups gadget, that might do exactly what you want. Cacycle (talk) 22:56, 13 July 2008 (UTC)

How do I completely disable wikEdDiff?

Resolved

How do I completely disable wikEdDiff when I'm using the wikEd gadget? It is messing with the default diff and so I've been missing a lot of things – it removes red highlighting, so I am often unaware that something has changed in a diff. I just realized this today after seeing a diff where one was missing half of a paragraph but it was not highlighted red. Viewing the diff with wikEd off or when logged out indeed shows it correctly. I've got "Toggle automatic improved diff view" off already but it does not help. For now, I have created a wrapper at User:Gary King/wikEd.js that removes wikEd from diff pages until this is resolved. Thanks in advance! Gary King (talk) 07:56, 12 July 2008 (UTC)

Hi Gary King, please could you provide a diff link so that I can try to fix this. Theoretically, you could disable wikEdDiff by putting the following line in your monobook.js: window.wikEdLoadDiff = false;, but right now this does not work for me. I will check into this later. 19:39, 12 July 2008 (UTC)

The diff is here. I was shocked when I discovered this. I don't want to imagine the countless diffs that did not appear correctly for me... Gary King (talk) 21:50, 12 July 2008 (UTC)

Great, I see the script has been updated. When will the gadget be updated, as I prefer using that? Gary King (talk) 02:26, 13 July 2008 (UTC)

Fixed in wikEdDiff.js 0.9.5b. I have also updated the gadget. Also, the above code to disable wikEdDiff now works again. Cacycle (talk) 03:41, 13 July 2008 (UTC)

Excellent – great work! I commend you on your quick response :) Gary King (talk) 03:46, 13 July 2008 (UTC)

Gadget is still problematic with same diff after a hard refresh. Gary King (talk) 03:48, 13 July 2008 (UTC)

That is a cache problem, open and refresh ("Reload" button) these links: [2], [3]. Cacycle (talk) 03:58, 13 July 2008 (UTC)

← Yes indeed fixed Gary King (talk) 03:31, 14 July 2008 (UTC)

Some css error messages in Firefox 3

Hello, Cacycle. During some days I remarked some css error message in my the error console of Firefox 3 on Windows XP. I use an own css file in my user pages. But I just found an error in the css code of wikEd.

// table edit // {{TABLE}}
			'.wikEdTableEdit':    'border: solid black; border-width: 1px 1px 0 0; background-image: url(\'' + wikEdImage['tableBG'] +  '\'); border: background-color: red; border-collapse: separate; border-spacing: 0;',
			'.wikEdTableEdit td': 'border: solid black; border-width: 0 0 1px 1px; background-color: white;',
			'.wikEdTableEdit th': 'border: solid black; border-width: 0 0 1px 1px; background-color: lightgrey; font-weight: bold;',
			'.wikEdTableEdit tr': 'background-color: lightgrey; font-weight: bold;',

The error is a : instead of ; between border and background-color in the line with '.wikEdTableEdit':.

I hope, that you can found this line in the very long code. Greetings --Tlustulimu (talk) 21:41, 13 July 2008 (UTC)

Thanks! Cacycle (talk) 22:25, 13 July 2008 (UTC)

Fixed in 0.9.64a. Cacycle (talk) 02:29, 14 July 2008 (UTC)

Thank you for the correction. Greetings --Tlustulimu (talk) 16:34, 16 July 2008 (UTC)

Bug report

I've had this occur across several versions of Firefox (1-3), and both Unix and Windows:

As you can see from my monobook page: User:The Evil Spartan/monobook.js, I have a junkload of things installed, one of which is clearly interfering; or possibly it is that I have the "view preview" preference installed. There is already another editing tool I had that I was trying out, though I'm not sure which it is. In any case, it completely wipes out the editing field so any previous text is gone.

In any case, the console reports the following error, which appears pertinent: Error: editHelp is null Source File: http://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-wikEd.js&action=raw&ctype=text/javascript Line: 2251

This isn't terribly surprising, viewing the surrounding code, as it looks like the code is just looking up span's and guessing that a certain one is correct, and that a certain child span will be the desired one. However, another Javascript which edits these spans will confuse it.

While I realize this is unpredictable, I too am a programmer, and understand this could and probably should be remedied. The Evil Spartan (talk) 22:05, 13 July 2008 (UTC)

Fixed in 0.9.64a. Cacycle (talk) 02:28, 14 July 2008 (UTC)

The problem remains, though the text is now slightly different:

Error: editHelp is null

Source File: http://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-wikEd.js&action=raw&ctype=text/javascript

Line: 2257

May I suggest changing line 2257 to read as following (changes in red):

while (editHelp!=null && editHelp.tagName != 'A');

As I'm sure you recognize, the problem is that the code is checking for does not check for nullness before dereferences its .tagName value. The Evil Spartan (talk) 05:55, 14 July 2008 (UTC)

I have fixed this in 0.9.64b, but you might run into other problems. You might as well just accept this incompatibility with another script that seems to completely remodel the page. You can try to add the following code to your monobook.js: var wikEdNoRearrange = true;. Cacycle (talk) 02:47, 15 July 2008 (UTC)

No, that fixed it, thanks. The Evil Spartan (talk) 08:17, 16 July 2008 (UTC)

Clicking on link in diff does not work with pipes

Resolved

 – Gary King (talk) 16:40, 15 July 2008 (UTC)

If there's a piped term like [[Example page|Example]] in a diff then yes it is clikable. But it leads to http://en.wikipedia.org/wiki/Example%20page%7CExample instead of http://en.wikipedia.org/wiki/Example%20page. Please fix? Gary King (talk) 03:30, 14 July 2008 (UTC)

Fixed in wikEdDiff 0.9.5c (reload [4] to clear server cache). Cacycle (talk) 03:17, 15 July 2008 (UTC)

Not fixed. Even worse now. This edit shows only "[[Example]]" in the right-pane when it should be "[[Example|testing]]" :( Gary King (talk) 04:06, 15 July 2008 (UTC)

... oops - fixed in 0.9.5d. Cacycle (talk) 13:12, 15 July 2008 (UTC)

Image issue in diff

In this problematic diff, check out the line that contains "Snowboarding Comparison.jpg". It should be [[Image:Snowboarding Comparison.jpg|thumb|''Final Fantasy VII: Snowboarding'': comparison of the [[PlayStation]] (left) and mobile versions]] on the right side, which is correct. The left side, however, is completely incorrect; it says [[Image:Snowboarding Comparison.jpg]] (left) and mobile versions.]] with wikEdDiff when it should actually say [[Image:Snowboarding Comparison.jpg|250px|thumb|''Final Fantasy VII: Snowboarding'': comparison of the [[PlayStation]] (left) and mobile versions.]]. Fix please? Thanks!

I don't know if I will keep reporting bugs or not. I've disabled wikEdDiff for now because I've been doing a lot of article work recently and am worried that these diffs are throwing me off sometimes. Gary King (talk) 07:15, 16 July 2008 (UTC)

Any luck on this? I was a bit struck after discovering this new bug when I posted it so I was a bit miffed, but I still think this should be fixed. Cheers. Gary King (talk) 04:06, 19 July 2008 (UTC)

I have fixed and improved the linkification in the current wikEdDiff 0.9.5e. Cacycle (talk) 20:48, 19 July 2008 (UTC)

Feature request: Semantic Forms support

WikiEd is not implemented when using Semantic Forms extension on MediaWiki. This extension replaces usual textarea with custom one called "free text". This is a sample of "free text" tag:

<textarea tabindex="12" id="input_16" name="free_text" rows="5" cols="80" class="createboxInput" ></textarea>

As you can see ID attribute changes depending on fields count in the form, so it can be identified only by name.

Is it realistic to hope for some features in WikiEd to support custom textareas? For example setting class on textarea would indicate that WikiEd should be used on it. - 78.59.146.170 (talk) 20:46, 12 June 2008 (UTC)

I will check what I can do for the next release. Cacycle (talk) 13:55, 13 June 2008 (UTC)

Added to 0.9.63a. Cacycle (talk) 06:10, 21 June 2008 (UTC)

Delete key loses everything I've written

Not the most important problem, I'm sure, but annoying nonetheless:

When wikEd is the active element on a page, pressing Delete removes letters, just as it should. But if the user has clicked on some other element on the page, wikEd is no longer active, and now the Delete signal goes to the browser. This means the same as pressing the Back button in the middle of writing: all the text is lost, and going Forward won't bring it back.

The difference between "remove the last letter" and "lose everything forever" seems a bit too much. Maybe wikEd could intercept the Delete signal going to the browser and show a dialog box before doing anything dramatic? Or, maybe wikEd could be shown as noticeably inactive when some other element has the focus?

I'm a happy user of wikEd 0.9.64b in the Finnish Wikipedia. My browser is Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; fi; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1.

85.77.229.64 (talk) 01:59, 19 July 2008 (UTC)

The "noticeably inactive" is an interesting suggesting. I don't think that wikEd can just intercept the delete key, so I don't think that's an option. But, I agree with you that this can be a real nuisance. Another suggestion is to just disable the delete key's feature of going back. Gary King (talk) 02:22, 19 July 2008 (UTC)

I don't really understand this and I do not have a Mac to try to replicate it. For Firefox 3.0 under Windows, the Delete key doesn't do anything if you push it on non-editable text. And even if you navigate back or forth you can still come back and continue to edit the page. Could this be a strange Firefox bug? If so, it should be fixed in Firefox, you could file a bug report on http://bugzilla.mozilla.org. Cacycle (talk) 04:03, 19 July 2008 (UTC)

I am on a Mac and it actually does not happen to me in Firefox, but it does on Safari. Gary King (talk) 04:06, 19 July 2008 (UTC)

Does the delete key do this with wikEd disabled (page top logo)? Cacycle (talk) 19:22, 19 July 2008 (UTC)

If you're asking me, then wikEd is automatically disabled in Safari, anyways, so it is already disabled; and yes, delete key still goes back in Safari. Gary King (talk) 22:58, 19 July 2008 (UTC)

It is beyond my understanding how developers could add such a stupid keybord shortcut! Here is a way to stop this annoying behavior in Firefox: http://kirk.blogspot.com/2007/10/fixing-annoying-delete-to-go-back-in.html. This does not fix the bug that the wikEd textarea is no longer editable after returning. I know that this was a known bug that had been fixed recently, at least for PC, please see https://bugzilla.mozilla.org/show_bug.cgi?id=416751. Cacycle (talk) 00:28, 20 July 2008 (UTC)

Oh, that is fantastic! Thank you very much, Cacycle! I sent feedback to Firefox developers. 85.77.250.221 (talk) 11:27, 22 July 2008 (UTC)

Text from Edittext template not getting inserted

I'm using WikiEd 0.9.64c in Firefox 2.0.0.16 on http://theaquariumwiki.com/ which I'm an Administrator.

I've noticed with WikiED that placing the caret on a blank line in the edit box and clicking on any of the quick-insert phrases causes the page to jump up and the caret disappears. Placing the caret at the end of an existing line and clicking on a phrase works however. Any clue to what's the matter? :-)

--Quatermass (talk) 12:29, 21 July 2008 (UTC)

The quick-insert links below the text edit box are not compatible with GreaseMonkey scripts (due to security issues). Please install wikEd as a gadget or as a sidewide or monobook.js user script as described on the installation pages. Cacycle (talk) 02:37, 22 July 2008 (UTC)

I have added page script support for the Greasemonkey version in 0.9.64d. The standard toolbar buttons and the insert links under the edit area are now functional. Cacycle (talk) 21:11, 26 July 2008 (UTC)

Request - wikilinking of dates

It would be nice if selecting a text like July 9 1792 and clicking on "Wiki link" button would produce [[July 9]] [[1792]] instead of [[July 9 1792]]. Of course, wikEd would have to recognize all four cases (MD/DM, comma/no comma). Should not be too difficult; the inverse operation would be slightly trickier, though... GregorB (talk) 16:41, 23 July 2008 (UTC)

I have to think about this. What complicates this is its language-dependency. I am not sure if the translators could create the required complex regular expression to make this work universally. Cacycle (talk) 13:23, 25 July 2008 (UTC)

Hadn't thought of this... Still, if it worked for English only, it would be an improvement... GregorB (talk) 18:58, 26 July 2008 (UTC)

Now that the Manual of Style had deprecated date wikilinking I don't think this should be added. Rjwilmsi 21:18, 15 September 2008 (UTC)

Jump to edit summary

Is there a way to make the cursor NOT always jump to the "edit summary" when you switch tabs, as it does it the default editor? A related question: is it possible to have the cursor not insert itself immediately into the edit box upon a "real" (non-ajax) preview load so that the page itself can be navigated without having to first click off to the side? — Skittleys (talk) 03:12, 24 July 2008 (UTC)

Which browser and installation method do you use (please see page top for the infos I need)? This does not happen under Windows with Firefox or SeaMonkey for me. Cacycle (talk) 00:33, 25 July 2008 (UTC)

CSS-Error in wikEd.user.js.

color: expression(parentElement.currentStyle.color) in User:Cacycle/wikEd.user.js 0.9.64c
causes CSS-Errors. If you want me to notice any response as soon as possible, then please use de:user talk:ParaDox.--ParaDox (talk) 00:16, 25 July 2008 (UTC)

Which browser do you use, what is the error message, when does it happen, does it break anything, and is it an incompatibility with another script? Cacycle (talk) 00:25, 25 July 2008 (UTC)

I use Firefox 2.0.0.16 and Greasemonkey 0.8.20080609.0. This DiffLink for example causes the following error six times:

Warning: Error in parsing value for property 'color'.  Declaration dropped.
Source File: http://de.wikipedia.org/w/index.php?title=Diskussion:Regenbogenfamilie&diff=48778058&oldid=48777056
Line: 0

I wouldn't say that anything breaks, but the error messages clutter up the Error Console. I do have quite a few Greasemonkey-Scripts and add-ons running, but when I disable wikEd completely, the errors disappear. To stop cluttering up the Error Console, I've twice removed (made to comments) the above highlighted style-code, which superficially has the same effect as disabling wikEd completely. As to incompatibility, hard to say and find out, but I'll try that, if you insist ;-)--ParaDox (talk) 01:23, 25 July 2008 (UTC)

Do you use Windows or Mac (please see the top of the page for the infos I need to fix this)?

It is actually a compatibility declaration for Internet Explorer, but I have never seen such an error message and I cannot reproduce this so far. Cacycle (talk) 02:21, 25 July 2008 (UTC)

OK, thanks. I use W2K as OS, and will do some tests to find a possible incompatibility with add-ons. --ParaDox (talk) 11:34, 25 July 2008 (UTC)

• wikEd Version 0.9.64c (July 19, 2008)

• Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16

I've tested the script with all add-ons and all “user.js” off (except for Greasemonkey and wikEd.user.js) and my monobook.css and monobook.js disabled (by logging out of Wikipedia), but all of that made no difference, the CSS-“Errors” still occured (it's not actually an JS-Error error, just a warning, I suppose).

The bottom line is: I no longer consider it to be a problem, since I've removed (made to comments) the above highlighted style-code, so no (more) fuss please, and thank you for all your efforts so far. I almost “love” wikDiff, and certainly wouldn't want to miss it – thanks very much for some very helpful and cool software.--ParaDox (de:user talk:ParaDox) 07:39, 26 July 2008 (UTC)

Thanks for your considerable efforts to pinpoint this issue. I will keep this in mind, maybe I will figure it out later or it will disappear when you update your browser. Cacycle (talk) 21:13, 26 July 2008 (UTC)

BUG - WikiED is freezing

My config -

• wikiEd: 0.9.64d
• Browser : Firefox 3.01
• GreaseMonkey 0.8.2
• Other Plugins None

When I want to edit a page , the text Field is not editable , Cursor is missing, by clicking on the disable or enable buttom Firefox freeze. No solution yet When I click to a button I get this error in the Jave Error Console

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLDocument.execCommand]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: https://wikiint.xxx.xxx.xx/zos-doc/index.php?title=User:Chris/monoblock.js&action=edit :: anonymous :: line 125" data: no] Source File: https://wikiint.xxx.xxx.xx/zos-doc/index.php?title=User:Chris/monoblock.js&action=edit Line: 125

The error seems to be caused by something on https://wikiint.xx.xxx.xx/zos-doc/index.php?title=User:Chris/monoblock.js, please check thereat line 125. For Greasemonkey you do not need anything on your monobook.js/monoblock.js page. Cacycle (talk) 12:09, 29 July 2008 (UTC)

The error is only on my PC , my friend can use Wikied without any problem for the same page , strange isn't it. And the monoblock.js seems to be empty I also get this message Warning: Unknown property 'word-wrap'. Declaration dropped.

Source File: http://static.ak.fbcdn.net/rsrc.php/pkg/72/113132/css/profile.css.pkg.php Line: 524

Ok I just uninstalled Microsoft .net 2.0 and the error message is now

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLTextAreaElement.selectionStart]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: https://wikiint.xxx.xxx.xx/zos-doc/skins/common/wikibits.js?42b :: mwSetupToolbar :: line 373" data: no] Source File: https://wikiint.xxx.xxx.xx/zos-doc/skins/common/wikibits.js?42b Line: 373 May you help me ? —Preceding unsigned comment added by 194.154.205.47 (talk) 13:31, 1 August 2008 (UTC)

I have the same problem!

• wikiEd: 0.9.64d
• Browser : Firefox 3.01
• GreaseMonkey 0.8.2 —Preceding unsigned comment added by 89.146.44.41 (talk) 07:27, 31 July 2008 (UTC)

Please could you any of you give me a wiki page that I can access where this happens. Please could you also tell me if there is anything on your User:Username/monobook.js page and what the complete browser id string and the complete wikEd id string is (or take the time to fill out the whole questionaire on top of this page, that would make things MUCH easier for me). Thanks, Cacycle (talk) 23:07, 1 August 2008 (UTC)

OK, I can actually reproduce this only with Firefox 3.01 and will check into it. Thanks for reporting, Cacycle (talk) 23:32, 1 August 2008 (UTC)

It has been fixed in version 0.9.64e (August 2, 2008), click here to update. Sorry for the problems, Cacycle (talk) 17:32, 2 August 2008 (UTC)

It is working for me now, sorry for the little information i provided, but i works like a charm now! Thank you for that! If there's is anything i can do, let me know!

Ok now it is working thank you very much —Preceding unsigned comment added by 194.154.205.47 (talk) 05:38, 4 August 2008 (UTC)

Wiked customization

I've got a suggestion: I've added my personal customization, but every time there's a new update (very frequently, which I like) I first have got to copy my customization part, install the new script and then add my part again.

A lot off hassle every time, so I came up with adding my customization in another userscript (lower and higher in the user.js tree). It didn't work, so maybe you can give a look at it. It would be a very useful feature for a lot off people I think.

ps. Keep your Recent Changes-part updated please.

Jeronevw (talk) 09:58, 3 August 2008 (UTC)

You can add the customization (or the loader for your customization) to your monobook.js or to site.js, wikEd will use it. Great page BTW. Cacycle (talk) 14:36, 3 August 2008 (UTC), Cacycle (talk) 14:43, 3 August 2008 (UTC)

I use it as a Userscript for GreaseMonkey. Do you have a solution for that?
If you want to use parts from my personal customization in Wiked?; you may (a little link to my own site would be appreciated: http://jervw.freehostia.com). If I'm correct, they work in the most common browsers. —Preceding undated comment was added at 16:56, 4 August 2008 (UTC)

You can add the customization to the wikis you edit as described in my previous reply. Please describe your usage in more detail if that answer does not work for you.

It would be great to have a wikEd custom buttons page, if you want you could start adding to User:Cacycle/wikEd_customization. Cacycle (talk) 01:56, 8 August 2008 (UTC)

Incorporating refToolbar functions

Hi there. I enjoy using wikEd, but I would find it much more useful if it incorporated the functions of the refToolbar script, which it is currently incompatible with. Have you considered doing something like that? – SJL 04:12, 6 August 2008 (UTC)

I will probably not add this to wikEd as it is highly specific for Wikipedia and especially the English Wikipedia. But after having a quick look at the code I think it would be relatively easy to make it compatible with wikEd, see User:Cacycle/wikEd#Making_scripts_compatible_with_wikEd. Alternatively, it could be added as a custom button function. Cacycle (talk) 01:43, 8 August 2008 (UTC)

List blanks spaces

Lists should not have a blank space in between entries since this causes the wiki software to believe the each entry is an individual list. WikiEd for some reason does not recognize that, and occasionally adds blanks spaces. See Wikipedia talk:Manual of Style#List formatting for details. ChyranandChloe (talk) 02:41, 8 August 2008 (UTC)

Please describe stepwise how to reproduce this problem. Thanks, Cacycle (talk) 13:11, 8 August 2008 (UTC)

It is not possible to automatically differentiate between intentional and accidental blank lines (i.e. two or one lists). Also, you must check your edits after using the purple buttons, one of your last edits had removed essential parts of the article (code tags). Cacycle (talk) 16:33, 8 August 2008 (UTC)

Thanks, I will see to that. ChyranandChloe (talk) 04:38, 9 August 2008 (UTC)

BUG - Linking

Note links in red.

I seem to be experiencing a bug in FF 3.0.1 in which wikEd is not linking hyperlinks properly. For instance, if I were to type in http://www.google.com/, it would work fine, but if I typed in http://www.microsoft.com, it would stop recognizing the link at the "i." It does this consistently, but with no other letter.

Browser: FF 3.0.1 (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1); Addons: all disabled; Windows XP SP2, and 2000 Pro.

I can't remember if this bug occurred in FF 2.5 or not.

Please let me know on my talk page if you need more information. Calebrw (talk) 18:19, 8 August 2008 (UTC)

It is a known Firefox 3 bug (see above) and I have already filed a Firefox bug (https://bugzilla.mozilla.org/show_bug.cgi?id=440926) but they have not done anything yet :-S Cacycle (talk) 18:48, 8 August 2008 (UTC)

Good to know. I signed myself up for getting a notice when it's fixed. Hopefully it will be soon. Calebrw (talk) 04:34, 10 August 2008 (UTC)

WikEd for other Wiki

Hi, I'm Michael. Thank so much for your creation!
I've got a problem: I work very often in an unofficial Wiki. I copied into my monobook.js this code from Italian Wikipedia:

// install Wikipedia:Monobook.js/WikEd.js/Descrizione
document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');

But it doesn't work. What do I have to do in order to import this script into other Wikis? - Airon^theKinslayer☮ 14:54, 9 August 2008 (UTC)
| PS: In Wikipedia it works perfectly :)

This should work - please could you answer the relevant questions from the orange box on top of this page. Thanks, Cacycle (talk) 15:33, 9 August 2008 (UTC)

Ops, I haven't seen it! So:

• My WikEd version: 0.9.64f (Do I have to upgrade it?)
• My browser id: Mozilla/5.0 (X11; U; Linux i686; it; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1
• Error console errors:
  • Errore: syntax error | File sorgente: http://it.wikipedia.org/w/index.php?action=raw&ctype=text/javascript&title=%3Aen%3AUser%3AIoeth%2Ffriendly.js | Riga: 1 | Codice sorgente: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  • Errore: syntax error | File sorgente: http://it.wikipedia.org/w/index.php?action=raw&ctype=text/javascript&title=%3Aen%3AUser%3AXytram%2Fwatchlistnotifier.js | Riga: 1 | Codice sorgente: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
• Plugins: Gmail Notifier 0.6.3.7 and Ubuntu Firefox Modification 0.5
  • Nothing changes if I disable plugins
• Other userscript: WikEd and another one that I don't know what it makes
• OS: Ubuntu 8.04 Hardy Heron
• The problem: In it.wiki WikEd works perfectly but if I import this code in another Wiki (not Wikimedia)

// install Wikipedia:Monobook.js/WikEd.js/Descrizione
document.write('<script type="text/javascript" src="'
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');

It doesn't work. Nothing happens.

I hope you are able to resolve this problem :) - Airon^theKinslayer☮ 17:54, 9 August 2008 (UTC)

I have to check the wiki where it does not work, please could you give me a link to it (you can email it to me). Cacycle (talk) 18:11, 9 August 2008 (UTC)

Here is the Wiki where I work - Airon^theKinslayer☮ 18:39, 9 August 2008 (UTC) —Preceding unsigned comment added by Mikethekinslayer (talk • contribs)

They don't have userscripts enabled, you have to use the Greasemonkey installation variant to use wikEd there. Cacycle (talk) 20:03, 9 August 2008 (UTC)

Bug – doubling of Template-Prefix @ diff-view

Hi Cacycle. I am using your great Gadget at dewiki an enwiki. Thanks a lot! As you may can see here, wikED is doubling of Template-Prefix of the included template as long as a user includes the namespace into the brackets. Maybe this is also „working“ with other namespaces. Bug discovered with „wikEd 0.9.64f G (August 2, 2008)“ at enwiki and „wikEd 0.9.61 (February 6, 2008)“ at dewiki. It's not a big bug, but you may want to be informed. With kind regards --M.L (talk) 23:59, 17 August 2008 (UTC)

It works fine for me on en though. Please could you provide more information (see the orange box on top of this page). Thansk, Cacycle (talk) 01:03, 18 August 2008 (UTC)

The doubling of the Template prefix 'only occurs at the link itself (http://en.wikipedia.org/wiki/Template:Template:wtf). I got Bug occurs at these systems:

• „Ubuntu 8.04 LTS“ with „Firefox 3.0.1“ („Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1“)
• „Windows 2000 Prof. 5.00.2195 SP4“ with „Firefox 3.0.1“ („Mozilla/5.0 (Windows; U; Windows NT 5.0; de; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1“)
• „Windows 2000 Prof. 5.00.2195 SP4“ with „IE 6.0.2800.1106“ („Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727“).

Both Firefox-Installations display the same error messages (german):

• Warnung: Unbekannte Eigenschaft 'word-wrap'. Deklaration ignoriert. Quelldatei: http://en.wikipedia.org/skins-1.5/common/diff.css?165 Zeile: 62
• Warnung: Unbekannte Eigenschaft 'column-count'. Deklaration ignoriert. Quelldatei: http://en.wikipedia.org/w/index.php?title=MediaWiki:Common.css&usemsgcache=yes&ctype=text%2Fcss&smaxage=2678400&action=raw&maxage=2678400&ts=20080818185529 Zeile: 53
• Warnung: Unbekannte Eigenschaft 'word-wrap'. Deklaration ignoriert. Quelldatei: http://en.wikipedia.org/w/index.php?title=MediaWiki:Common.css&usemsgcache=yes&ctype=text%2Fcss&smaxage=2678400&action=raw&maxage=2678400&ts=20080818185529 Zeile: 70
• Warnung: Fehler beim Verarbeiten des Wertes für Eigenschaft 'color'. Deklaration ignoriert. Quelldatei: http://en.wikipedia.org/w/index.php?title=Wikipedia%3ASandbox&diff=232580157&oldid=232578187 Zeile: 0
• Warnung: Fehler beim Verarbeiten des Wertes für Eigenschaft 'color'. Deklaration ignoriert. Quelldatei: http://en.wikipedia.org/w/index.php?title=Wikipedia%3ASandbox&diff=232580157&oldid=232578187 Zeile: 0
• Warnung: Fehler beim Verarbeiten des Wertes für Eigenschaft 'color'. Deklaration ignoriert. Quelldatei: http://en.wikipedia.org/w/index.php?title=Wikipedia%3ASandbox&diff=232580157&oldid=232578187 Zeile: 0

I have no monobook.js here at enwiki, an only activated wikED at the gadgets (at enwiki). --M.L (talk) 19:35, 18 August 2008 (UTC)

I have fixed this in wikEdDiff 0.9.5f, Shift-Reload this page to update. Thanks for notifying, Cacycle (talk) 01:25, 20 August 2008 (UTC)

Thank you! :) --M.L (talk) 01:17, 21 August 2008 (UTC)

Request: Warning if leaving page with unsaved changes

On MacOSX the key for 'move cursor to start of line' (Command-Left) is the same key as Firefox 'navigate back one page'. This is annoying as hell -- though Firefox is nice with standard text areas when you go back forward: the content is still there. Unfortunately when using WikEd this behaviour breaks, and any written content is LOST! What I'd love to see is when the browser trys to navigate away from a WikEd page that has unsaved content, WikEd alerts the user so they can cancel the accidental navigation, in the same way Gmail does if you try to close it without sending a half-written email. Glutnix (talk) 02:11, 24 August 2008 (UTC)

Is this the same as above? You should not lose anything when you navigate away from a page and come back (and you do not, at least under Windows). Try to pressure the Firefox developers to fix this bug under http://bugzilla.mozilla.org. Cacycle (talk) 21:25, 24 August 2008 (UTC)

Notepad++

Anyone know of any syntax highlighting add-ons for Notepad++ or SciTE? Thanks. SharkD (talk) 08:33, 24 August 2008 (UTC)

Firefox 3.1 support

Mozilla has introduced a new codename for the new release (currently in alpha 1): "Shiretoko".
Here the fully user agent string

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a1) Gecko/2008072310 Shiretoko/3.1a1

It would be nice, if you could add this to the the list of recognized firefox agent strings, along with bonecho, granparadiso... Thanks for this nice tool —Kaneiderdaniel (talk) 14:42, 27 August 2008 (UTC)

Thanks, I have added it to the latest release (0.9.64g). Cacycle (talk) 02:50, 1 September 2008 (UTC)

Request: Completion of interlinks

I would really aprecite some way to make it easier to create links to other existing pages. To be able to type "[[UniqueStartofpagename" and then press a shortcut key (or a button) to get the link automatically completed.

Is this possible, has it been considered? —Preceding unsigned comment added by Rojeras (talk • contribs) 10:43, 4 September 2008 (UTC)

Interesting idea! This also needs a server program to generate the suggestions, but one could hijack the search box mechanism. Cacycle (talk) 12:45, 4 September 2008 (UTC)

I am new to MediaWiki and wikEd (I am not even sure to get my signature in my posts here). But, I have seen you can get all existing page names through Special:Allpages. The names are also available in the TABLES table, but I am not sure i there is a way for wikEd to get access to it.

Regards, Lars Erik —Preceding unsigned comment added by Rojeras (talk • contribs) 12:51, 4 September 2008 (UTC)

Malay translation

Hi. This is a new translation for wikEd in Malay: User:Aviator/wikEd international ms.js. My user page is at ms:Pengguna:Aviator. Thank you for your great tool! Aviator (talk) 16:03, 6 September 2008 (UTC)

Thanks a lot! I have updated the language pages. Cacycle (talk) 17:43, 6 September 2008 (UTC)

Highlighting errors

Hello again. I have noted several minor problems with the colour-highlighting in the edit window, and thought that mentioning them here might help in some way, or at least result in satisfying my curiosity as to why they could not.

These are the ones I remember:

1. Paragraphs starting with a colon or bullet normally have a light-purple colour; if there are templates in these paragraphs, they break the colouring, and the part of the paragraph following the template appears white.
2. References also present problems: in a paragraph with several references, text between references often has the same colour as the references themselves. Citation templates are usually the cause of this effect.
3. External links should show the URL in red, but often only show a few letters thereof red and the rest black.
4. Links to mainspace pages with colons in the name appear as if they are to other namespaces. (I don't have high hopes for this one.)

PS: If you want non-administrators to "testify" in the Testimonials section of a protected page, why not transclude the section from another page? Waltham, The Duke of 01:14, 7 September 2008 (UTC)

I meant to read the "Bug reports" part before posting this, but forgot to. I use wikEd as a gadget; the version code is 0.9.64g G. My browser id is Mozilla/5.0 (Windows; U; Windows NT 5.1; el; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1. I'm not sure the add-ons are relevant; I remember having at least some of these problems before installing any add-ons. The same goes with scripts, to an even greater degree: I only have one, and have installed it relatively recently. My operating system is Microsoft XP. Waltham, The Duke of 01:21, 7 September 2008 (UTC)

Thanks for your report.

1. Their color should be grey and I could replicate this problem. Examples?

2. Will check this later

3. It is a known Firefox 3 bug but the developers do not seem to care. You can vote for this bug under https://bugzilla.mozilla.org/show_bug.cgi?id=440926.

4. Difficult to avoid as namespaces can have any name and therefore are indistinguishable from titles with colons

Ad PS: Isn't that the current setup?

Cacycle (talk) 04:34, 7 September 2008 (UTC)

You are welcome.

1. It is indeed grey; I must have been misled by the nearby purple of piped links. Anyway, {{template1}}, {{template2}}, and voila! No more colour.
2. Pending
3. I've heard of this Mozilla Bugzilla before; is it related to Bugzilla or Mozilla? I have a Bugzilla account, but I rarely use it, and feel pretty much lost in there.
4. Can't it recognise namespaces from the lack of a space after the colon? Or does this fall under the general treatment of spaces in MediaWiki (i.e. they can be inserted pretty much anywhere with little consequence)?

Oops. I had not noticed; I did not look at the sidebar, and there was no "edit" link at the section. I remember reading in the Signpost that the relevant bug had been solved and that an "edit" link would appear for editable transcluded sections of protected pages, and that was weeks ago. Still not active? Hm. Waltham, The Duke of 17:42, 7 September 2008 (UTC)

WikEd Light?

Hello, I recently tried using wikEd so that I could get the awesome Wikicode syntax highlighting feature. I had to abandon using wikEd, though, due to the terrible lag. Would there be any possibility of developing a wikEd Light that only has the Wikicode syntax highlighting feature and nothing else, or is the highlighting feature the main cause of the lag? Kaldari (talk) 16:10, 19 September 2008 (UTC)

There shouldn't be a terrible lag. On which pages do you experience this? Which operating system and browser do you use. Does it speed up if you disable highlighting ( button). Cacycle (talk) 23:27, 20 September 2008 (UTC)

breaking templates and weird control characters

Hi. Thanks for upgrading the script to work with Chrome. I'm not sure if has to do with last night's upgrade, or if it has to do with the fact that I exchanged the gadget for the script, but wikEd seems to be making changes to the text that break templates and such even when I don't ask it to make any changes. Also it's putting in

in at random places breaking headers and other formatting. Also, I thought the spelling correction was supposed to work like AWB, but it's trying to capitalize proper nouns that are part of URLs. Am I just doing things wrong, or is something up? Thanks! —Elipongo (Talk contribs) 11:57, 22 September 2008 (UTC)

Please could you describe where and when it happens so that I can try to replicate it. Otherwise I could not fix it. Thanks, Cacycle (talk) 13:47, 22 September 2008 (UTC)

Well here's one where all I did was write a comment at the bottom of the talk page and then highlighted only my own text to have it correct my own spelling diff. Then here all I did was change the defaultsort key, I didn't hit any buttons on wikEd, but it added space characters all over the place and broke the infobox diff. The <div></div> strangeness seems to have stopped as of now, I checked to see if it would do it again on revisions of pages where it did it before and couldn't reproduce it. Here's one where it's capitalizing proper nouns that happen to be embedded inside URLs diff. —Elipongo (Talk contribs) 17:03, 22 September 2008 (UTC)

Which browser do you use? Cacycle (talk) 23:10, 22 September 2008 (UTC)

Please see here: Wikipedia:Village_pump_(technical)#Bizarre_diffs. Cacycle (talk) 03:01, 23 September 2008 (UTC)

wikiEd bug

Let me tell you, wikiEd is the best script made for editing, but I frequently disable it because of the annoying issue that whenever I press back, forward, or otherwise navigate away from the page, all my changes are lost in an edit. This is extremely annoying especially after a huge edit and I get the "Wikimedia Foundation Error" and everything is gone. Is this a known issue (you didn't mention it though). I'm using Firefox 3.0.2 but this was a problem even on Firefox 2 , Windows Media center, and some non-intrusive scripts(?) on my monobook.js. Anything would be great, thanks -- penubag  (talk) 02:23, 25 September 2008 (UTC)

This is a browser bug. Interestingly, it does not happen if you push the back/forward button with your mouse. Unfortunately, there is not much wikEd can do against this. I will file a Firefox bug report. Cacycle (talk) 02:56, 25 September 2008 (UTC)

Too bad my mouse doesn't have extra buttons. Thanks for informing the devs at Firefox. -- penubag  (talk) 05:01, 25 September 2008 (UTC)

Interferes with spell checkers?

Perhaps I am just imagining this, but with wikEd turned on my squiggly-underlines don't appear. If I'm not imagining it, I'm not sure there's an easy way to get it back. Sadly I make more spelling mistakes than tag closure ones, so this is a dealbreaker for me. :-( Maury Markowitz (talk) 21:01, 3 October 2008 (UTC)

What browser do you use? It works fine for me with Firefox 3.0.1 and SeaMonkey 1.1.12. Cacycle (talk) 03:27, 4 October 2008 (UTC)

Chrome and Safari both show this problem. Maury Markowitz (talk) 14:18, 4 October 2008 (UTC)

I have submitted a WebKit bug report, please see https://bugs.webkit.org/show_bug.cgi?id=21384. Cacycle (talk) 15:32, 5 October 2008 (UTC)

Spell checking under wikEd works fine for me using Safari 3.1.2 under Windows. Are you sure you are using the current Safari version an have not disabled the spell checker manually (Edit > Spelling and Grammar > Check Spelling While Typing). Cacycle (talk) 00:29, 6 October 2008 (UTC)

Strip styles from "foreign" text

Try this...

• Open any article with wikEd.
• Copy some styled text from another source, like the large text header at the top of this page ("Editing User talk:...)
• Paste it into the editor.

Uggg. Is there some way the text styles can be ripped out? Maury Markowitz (talk) 21:03, 3 October 2008 (UTC)

Please check the wikEd help (you have to push the button). Cacycle (talk) 03:18, 4 October 2008 (UTC)

Since the styles have no effect on the actual article display, is there any reason this needs to be a "command"? Maury Markowitz (talk) 14:18, 4 October 2008 (UTC)

Please read the wikEd help. Thanks, Cacycle (talk) 15:57, 4 October 2008 (UTC)

I did. Am I missing something? Maury Markowitz (talk) 21:09, 5 October 2008 (UTC)

Please see User:Cacycle/wikEd_help#Updating_the_syntax_highlighting and User:Cacycle/wikEd_help#Automatic_syntax_highlighting. Cacycle (talk) 00:37, 6 October 2008 (UTC)

Minor bug

Open an article that has a ref-pointer somewhere, the things that look like "< ref name=somthing / >". Click behind the > and start typing... Maury Markowitz (talk) 21:05, 3 October 2008 (UTC)

Please provide more details (see the top of this page for an error reporting checklist). If this is about disappearing cursors, then Firefox is to blame. Cacycle (talk) 03:21, 4 October 2008 (UTC)

No, when you type it comes out in the style of "this is a ref". Maury Markowitz (talk) 14:18, 4 October 2008 (UTC)

Please read the wikEd help. Cacycle (talk) 15:57, 4 October 2008 (UTC)

Sorry, can you be more specific? Are you referring to the on-the-fly styling? If so, why isn't the style turned off after the >? Maury Markowitz (talk) 21:09, 5 October 2008 (UTC)

Please see User:Cacycle/wikEd_help#Updating_the_syntax_highlighting and User:Cacycle/wikEd_help#Automatic_syntax_highlighting. Cacycle (talk) 00:35, 6 October 2008 (UTC)

It is the same principle as in word processors (like Word), new text will inherit the styling of the existing text to the left. Cacycle (talk) 12:32, 6 October 2008 (UTC)

wiked.user.js, wikEdDiff

wiked.user.js, wikEdDiff: (http-)link-generation within diffs is broken by CSS-span

Hi Cacycle, the “http-link-generation” within diffs is broken (using Firefox 2.0.0.16) by

• <span class="diffchange diffchange-inline"> for example.

Perhaps you can fix that sometime. Best regards, --ParaDox (de:user talk:ParaDox) 04:35, 4 October 2008 (UTC)

wiked.user.js: wikEdDiff in a separate/stand-alone user.js

Hi Cacycle, I would find it extremely useful, if it were possible to have wikEdDiff in a separate/stand-alone Greasemonkey-„user.js“. I hardly ever use the wikEd-Editor itself, which is mainly because I've already got so many JS-scripts running that I need more urgently. Being at a point where lots of JS-scripts are slowing down my Firefox-browser too much, I'm forced to decide which scripts/modules are required least. Best regards, --ParaDox (de:user talk:ParaDox) 04:35, 4 October 2008 (UTC)

I will add the necessary code to wikEdDiff.js as soon as I find the time. You could also use wikEd as a gadget (check wikEd on the gadgets tab in your Wikipedia preferences). Cacycle (talk) 02:53, 6 October 2008 (UTC)

(a) Thx. (b) I know, but can't see any advantage in my case. --ParaDox (de:user talk:ParaDox) 04:09, 6 October 2008 (UTC)

See "#Are “wiked.user.js” and Firefox 2.0.0.17 incompatible?" below. --ParaDox (de:user talk:ParaDox) 11:40, 17 October 2008 (UTC)

Feature request: code folding

It would be great if wikiEd would implement code folding to, for example, hide and show the details of lengthy cite tags and other templates in articles. I think this feature would be extremely useful and would cause massive adoption of wikiEd.--Michael White^T·C 02:39, 6 October 2008 (UTC)

Real code folding or hiding would be overkill for wikEd, difficult to implement and confusing for many users. But you can already use the button to fade out ref tags. Cacycle (talk) 02:49, 6 October 2008 (UTC)

I'd love to have code folding, too. I'm doing a lot with Semantic MediaWiki, ParserFunctions, StringFunctions and the likes, and I sometimes end up with 5 closing }} - it would be extremely helpful if I could just press a small [-] button that appears on each opening double brackets and wikEd would hide everything between the double bracket pair (and the [-] would become a [+]). I understand that this would probably not be easy to implement, especially considering that there are also triple brackets etc. A scaled down version (without any hiding/folding going on) would be a change in colour / blinking of the double bracket pair once you hover over either the opening or the closing double brackets - so that you could easily find where one template/parser function call ends. What do you think, doable? --Patrick Nagel (talk) 07:14, 22 October 2008 (UTC)

Bug

The first is the external link where

/((http:\/\/|https:\/\/|ftp:\/\/|irc:\/\/|gopher:\/\/|news:|mailto:)[^\u0000\u0001\u0003-\u0020\!\"\$\'\(\)\*\,\<\>\[\\\]\^\`\{-\|\}\u007f-\uffff]*)/gi

should be

/((http:\/\/|https:\/\/|ftp:\/\/|irc:\/\/|gopher:\/\/|news:|mailto:)[^<>\[\]"\s\u0000-\u0020\u007f{|}]+)/g

The second is when enabling WikEd (w/o syntax highlighting) it removes the leading whitespace on the lines. — Dispenser 03:45, 13 October 2008 (UTC)

The first regexp is correct as far as I can see. Any problems are caused by a Firefox 3.0 bug, see the top of the page for a link to vote for this bug. I will check the second bug. Cacycle (talk) 04:14, 13 October 2008 (UTC)

• characters ' ` * $ ( ) : ! are all valid in external links characters [ ] < > " \n (space) and ASCII control characters are invalid
• The case insensitive flag should not be on

— Dispenser 13:41, 13 October 2008 (UTC)

Thanks, I will check the regExps for the next release. Cacycle (talk) 17:04, 25 October 2008 (UTC)

Fixed in 0.9.66. Cacycle (talk) 05:30, 14 November 2008 (UTC)

Are “wiked.user.js” and Firefox 2.0.0.17 incompatible?

Hi Cacycle,

since updating from Firefox 2.0.0.16-en-US to 2.0.0.17-en-US, Firefox displays a message box:

• after n seconds, depending on the setting in about:config = "dom.max_script_run_time" (max tried up till now: 90)
• "Warning: Unresponsive Script, bla bla bla", options: “Stop script” or “Continue”

My config:

• Windows 2000 SP4 etc.
• "wiked.user.js" Version 0.9.65a September 22, 2008
• browser-id = "Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.17) Gecko/20080829 Firefox/2.0.0.17"
• JS-Error-Console (all webpages including this one)
  • Error: key is not defined
  • Source File: http://en.wikipedia.org/wiki/User_talk:Cacycle/wikEd
  • Line: 184

The wikEd-script-freezing (during initialization as far as I can see/judge) remains, even when I:

• remove all add-ons except for Greasemonkey 0.8.20080609.0
• disable all other Greasemonkey-Scripts except for "wikEd (wiked.user.js)"
• logout of Wikipedia, so no “monobook.js” etc. is involved

Clueless now … Best regards, --ParaDox (de:user talk:ParaDox) 09:23, 17 October 2008 (UTC)

Well, seems pretty certain, that “wiked.user.js 0.9.65a” and “Firefox 2.0.0.17 en-US” are incompatible, since I've just download “Firefox 2.0.0.16 en-US” and reinstalled it, and everything works fine, including twenty add-ons and including “wiked.user.js” eleven “Greasemonkey-user.js”. So, then, just to be sure, I reinstalled 2.0.0.17 without changing anything else, and the wikEd-script-freezing returned :-(

Clueless again … Best regards, --ParaDox (de:user talk:ParaDox) 10:41, 17 October 2008 (UTC)

I'm happy to be able to say, that my attempt to extract wikEdDiff out of "wiked.user.js" seems to have worked fine, so that my "#wiked.user.js: wikEdDiff in a separate/stand-alone user.js"-request above is no longer urgent, perhaps even obsolete. And the fact that the wikEd-script-freezing-effect isn't within "wikEdDiff.user.js" makes me even happier, as I can now use the safer Firefox 2.0.0.17 in combination with "wikEdDiff.user.js" (0.9.5f August 19, 2008). Thanks very much again for a wonderful program :-)  Best regards, --ParaDox (de:user talk:ParaDox) 11:37, 17 October 2008 (UTC)

Although my attempt to extract wikEdDiff out of "wiked.user.js" has the effect of working under Firefox 2.0.0.17, my extracted standalone Version seems to be incompatible with some or all other Greasemonkey-Scripts. Most noticeable effect is, that inserted/deleted green/red are reversed in the wikEdDiff-result. When that happens, I (have to) disable all other GM-Scripts and restart Firefox to get my extracted wikEdDiff version to function as usual. So my need for a working stand-alone version seems fairly urgent to me, and definitely not obsolete. Best regards, --ParaDox (talk) 07:24, 21 October 2008 (UTC)

I have already spent some time to make wikEdDiff work as a GreaseMonkey script, but unfortunately, this is not a trivial task. I am quite busy these days, so it might take a while. Cacycle (talk) 12:53, 21 October 2008 (UTC)

Wonderful! I'd be extremely grateful/happy if you did it at all … perhaps until xmas … as an undeserved present? ;-)  --ParaDox (talk) 18:38, 21 October 2008 (UTC)

Parser function call handling

It seems to me that currently Parser function calls are not handled differently than normal template calls.

Example:

{{ urlencode:This is a test }}

leads to a page Urlencode:Template:This_is_a_test or

{{ #ifeq: {{ns:PAGENAME}} | Test | true | false }}

leads to a page Template:%23ifeq:_, saying Bad title.

Ideal would be if wikEd would recognise the parser functions (at least the built-in ones like 'ns' or 'urlencode', but preferably also those from the ParserFunctions and StringFunctions extension - and while we're at it also those of the Semantic MediaWiki extension ;) ). It could then link to the meta:Parser function page for built-in parser functions and to the Extension pages of the extensions the non-built-in parser functions belong to.

If this could even be configurable, like

parserFunction[0]='urlencode'; parserFunctionLink[0]='http://meta.wikimedia.org/wiki/Help:Parser_function';
parserFunction[1]='#ifeq'; parserFunctionLink[1]='http://meta.wikimedia.org/wiki/ParserFunctions';

that would be perfect. It would enable the wikEd user to tell wikEd which "template names" are actually parser functions, and where to link when encountering them. The mappings suggested above could then be provided as default configuration, and the user could add more on demand.

Alternatively, the CTRL-click-opens-template-page mechanism could just be disabled, so that template calls that are actually not template calls but parser function calls would not be CTRL-clickable.

--Patrick Nagel (talk) 07:56, 22 October 2008 (UTC)

Thanks for the suggestion. I will try to add this - it might take a while though... Cacycle (talk) 03:12, 23 October 2008 (UTC)

Added to 0.9.67. Cacycle (talk) 07:51, 16 November 2008 (UTC)

Interwiki Geman

Hi Cacyle,

since the page User:Cacycle/wikEd is blocked, I have to ask you this way to integrate there the interwiki-link to the german wikipedia: de:Wikipedia:Texteditor#wikEd. Thanks for the great tool!

Greets Carbenium (talk) 08:50, 22 October 2008 (UTC)

Thanks, I have added it. BTW, wikEd also works for Safari and Google Chrome, please could you add that to the German article? Thanks, Cacycle (talk) 03:11, 23 October 2008 (UTC)

wikEd

Hi, what I like best about wikEd is the improved version difference. Is there any way to use the diff without the rest of wikEd? Regards, --NEUROtiker (talk) 21:49, 25 October 2008 (UTC)

Sure, push the button on the right wikEd toolbar. Or are you talking about wikEdDiff? Cacycle (talk) 04:21, 26 October 2008 (UTC)

Yes I meant wikEdDiff. Thanks for the link! --NEUROtiker (talk) 13:36, 26 October 2008 (UTC)

WikEd for IE7Pro?

According to the web site. IE7Pro 2.4 has been released on Sep 24,2008. IE7Pro Web site

The web site also states that IE7Pro Script is to Internet Explorer7 as Greasemonkey is to Firefox. It lets you remix the Web via scripts.

For giggles, knowing it probably won't work, I tried to install the WikEd.user.js script into the IE7Pro user scripts area and test it out. I did go through and try and correct the few MSIE BrowserUnsupported lines.

I did learn the script has to have a certain naming convention so I changed it to WikEd.ieuser.js

I tried to edit a Wiki page and it still is the default Wiki editor, but now I saw an Error On Page alert.

I'm not sure if anyone is pursuing the IE7pro angle or if scripting is occurring for IE8. It looks like IE8 will use the same or similar framework as IE7Pro for user scripts.

I'd love to see WikEd for IE just because many corporate users are unable to install other browsers and are stuck with IE.

October 29, 2008, Mnbyers (Talk)

Yes it would be nice to have wikEd working under a future Internet Explorer version, but so far Microsoft for reasons unknown to me sticks to a completely non-standard and incompatible way of accessing selected text. wikEd will simply not work under IE until they fix their still crappy and incompatible browser (or somebody invests a lot of time and effort into wikEd). Cacycle (talk) 00:36, 1 November 2008 (UTC)

refTools

WikiEd and refTools seem to be incompatible. When I turn on wikiEd, the cite button stops appearing. --HughCharlesParker (talk - contribs) 01:21, 3 November 2008 (UTC)

I have compatibilized this script, see User talk:Mr.Z-man#refToolbar.js for wikEd. You should be able to use both as soon as Mr.Z-man puts it online and you do a Shift-Reload. Cacycle (talk) 04:02, 13 November 2008 (UTC)

Fantastic! Nja247 (talk • contribs) 07:21, 20 November 2008 (UTC)

WikEd + wgRawHTML + localpreview

When WikEd make a local preview, it send follwing AJAX-reguest:

  // make the ajax request
                    var formAction;
                    if (wikEdUpload == true) {
                        formAction = wikEdWikiGlobals['wgServer'] + wikEdWikiGlobals['wgScript'] + '?title=wikEdUploadPreview&action=submit';
                    }
                    else {
                        formAction = wikEdEditForm.action;
                    }
                    WikEdAjaxRequest('POST', formAction + '&live', 'Content-Type', 'multipart/form-data; boundary=' + boundary, postData, 'text/html', function(ajax) {
                        wikEdPreviewIsAjax = true;

Unfortunately, if $wgRawHTML=true; (this is true for our installations of MediaWiki, for example), then EditPage.php requires correct wpEditToken and wpEdittime, or else session_fail_preview_html happens:

        global $wgRawHtml;
        if( $wgRawHtml && !$this->mTokenOk ) {
            // Could be an offsite preview attempt. This is very unsafe if
            // HTML is enabled, as it could be an attack.
            return $wgOut->parse( "<div class='previewnote'>" .
                wfMsg( 'session_fail_preview_html' ) . "</div>" );
         }

Please, fix AJAX-request like that (this hack works):

  // make the ajax request
                    var formAction;
                    if (wikEdUpload == true) {
                        formAction = wikEdWikiGlobals['wgServer'] + wikEdWikiGlobals['wgScript'] + '?title=wikEdUploadPreview&action=submit';
                    }
                    else {
                        formAction = wikEdEditForm.action;
                    }
                    //!!! HACK BEGIN
                    editform=document.getElementsByName('editform')[0];
                    edittime=editform.wpEdittime.value;
                    token=encodeURIComponent(editform.wpEditToken.value);
                    formAction = formAction+'&wpEdittime='+edittime+'&wpEditToken='+token;
                    //--!!! HACK END
                    WikEdAjaxRequest('POST', formAction + '&live', 'Content-Type', 'multipart/form-data; boundary=' + boundary, postData, 'text/html', function(ajax) {
                        wikEdPreviewIsAjax = true;

--StasFomin (talk) 10:56, 12 November 2008 (UTC)

Will do this as soon as I find the time. Cacycle (talk) 13:30, 12 November 2008 (UTC)

Fixed, please could you check if it works? Thanks, Cacycle (talk) 05:29, 14 November 2008 (UTC)

0.9.67 does not work in zh.wikipeida with google chrome

possibly due to Chinese characters in the page title (i'm not very sure), the 0.9.67 seems not work in zh.wikipedia with google chrome. when i try to edit a page with wikied turned on, the editing area is blank. now i have switched back to 0.9.66 and no problem is found.

thank you for your attention!

--Johnson Lau (talk) 08:54, 17 November 2008 (UTC)

Same problem for the fr.wikipedia, but I don't know how downgrade to 0.9.66 version--Chandres (talk) 10:36, 17 November 2008 (UTC)

Sorry for that, please update to the fixed version 0.9.67b by a Shift-Reload. Cacycle (talk) 15:08, 17 November 2008 (UTC)

Thank you very much, works well now!--Chandres (talk) 15:19, 17 November 2008 (UTC)

It works now, thank you!--Johnson Lau (talk) 04:11, 18 November 2008 (UTC)

0.9.67a of Nov17 does not load properly in Safari

• Running Safari 3.2 (5525.26.21) on PPC/G5 Mac OS X 10.5.5
• Safari's Web Inspector reports an Undefined Value error (line 7886):

Undefined value
http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript (line 7886)

• I have no local scripts or add-ons running.
• Symptoms: the toolbar and edit window shows, but no text appears in the edit box; the icon in the top right shows a red X. If you reload the page, you can see the text appear in the edit box for a split-second, but then it disappears.
• Viktor Haag (talk) 14:31, 17 November 2008 (UTC)

Sorry for that, please update to the fixed version 0.9.67b by a Shift-Reload. Cacycle (talk) 15:08, 17 November 2008 (UTC)

Thanks for your responsiveness! Seems to be working now! Viktor Haag (talk) —Preceding undated comment was added at 18:37, 17 November 2008 (UTC).