User talk:Cacycle/wikEd/Archive 007

ref tags

Hi. Id like to see block highlighting <ref>inbetween ref tags </ref>. I think that would make dealing with these a bit easier, though now I just realised that conjoined tags would probably show a contiguous highlight color... Dunno how to deal with that. -Stevertigo 19:25, 11 August 2007 (UTC)

Making scripts compatible with wikEd

Note that the method described under #Making scripts compatible with wikEd only works as long as you don't try to do anything with selections. Otherwise it will fail badly: even a supposedly fail-safe test like

if(typeof(document.getElementById('wpTextbox1').selectionStart) != 'undefined')

will result in an exception being thrown. (WikEd 0.9.38a, Firefox 2.0.0.6/Win) This is probably a Firefox bug, but it would be nice to see some documentation of WikEdGetText so one can write truly WikEd-compatible scripts. --Tgr 16:19, 20 August 2007 (UTC)

More generally, functions to get/replace the various kinds of text WikEd can handle (whole, selection, focusline etc.) would be nice. Piecing things together from the button handling code has a bad effect on one's sanity. :-) --Tgr 18:51, 20 August 2007 (UTC)

If I understand you correctly, you want to maintain (= copy) the selection from the iframe to the copied text in the textarea. That's not an easy task and would need some hacking - although some helper functions are probably already hidden in the wikEd code. I will check that.

The wikEd text fragments to manipulate would probably only make sense if you want to write an iframe handling wikEd extension.

What are you working on, maybe I could help better when I now what you are up to :-) Cacycle 23:22, 20 August 2007 (UTC)

You could try something like the following (completely untested and not complete):

// get selection range
    var sel = wikEdFrameWindow.getSelection();
    var rangeSelection = sel.getRangeAt(sel.rangeCount - 1);

// get the selection start node and offset
    var startNode = range.startContainer;
    var startNodeOffset = range.startOffset;

// get the selection end node and offset
    var endNode = range.endContainer;
    var endNodeOffset = range.endOffset;
    
// create a before-selection range
    var rangeBefore = document.createRange();
    rangeBefore.setStartBefore(wikEdFrameBody.firstChild);
    rangeBefore.setEnd(startNode, startNodeOffset); // should be one before!
    
// create an after-selection range
    var rangeAfter = document.createRange();
    rangeAfter.setStart(endNode, endNodeOffset); // should be one after!
    rangeAfter.setEndAfter(wikEdFrameBody.lastChild);

// create document fragments for plaintext conversion
    var fragmentBefore = rangeBefore.cloneContents();
    var fragmentSelection = rangeSelection.cloneContents();
    var fragmentAfter = rangeAfter.cloneContents();
    
// get innerHTML
    var objBefore = {};
    WikEdGetInnerHTML(objBefore, fragmentBefore); 
    objBefore.html = obj.html.replace(/(<br\b[^>]*>)\n* */g, '$1');

// textify so that no html formatting is submitted
    WikEdTextify(objBefore);
    objBefore.plain = objBefore.plain.replace(/&nbsp;/g, ' ');
    objBefore.plain = objBefore.plain.replace(/&lt;/g, '<');
    objBefore.plain = objBefore.plain.replace(/&gt;/g, '>');
    objBefore.plain = objBefore.plain.replace(/&amp;/g, '&');

// ... same for other two ranges

// copy to textarea
    wikEdTextarea.value = objBefore.plain + objSelection.plain + objAfter.plain;
    
// ... set selection, calculate from string lengths

// remember frame scroll position
    wikEdFrameScrollTop = wikEdFrameBody.scrollTop;

Cacycle 02:50, 21 August 2007 (UTC)

Thanks, but I just needed a way to read and replace the selected text; i think that (together with inserting text at the cursor) is a far more frequent task. I eventually ended up with something like this (mostly copy-and-pasted blindly from the WikEd code; I apologise if seeing it causes any emotional or esthetic harm :) :

var ciWikEdObj;
var ciTextRange;

function getSelection() {
      if (typeof(wikEdUseWikEd) != 'undefined' && wikEdUseWikEd == true) {
         ciWikEdObj = {};
	      ciWikEdObj.changed = {};
         WikEdGetText(ciWikEdObj, 'selection');
         ciWikEdObj.changed = ciWikEdObj.selection;
         var selection = ciWikEdObj.selection.plain;
      } else {
         var textarea = document.editform.wpTextbox1;
         if (document.selection && document.selection.createRange) { // IE, Opera
            textarea.focus();
            ciTextRange = document.selection.createRange();
            if(!is_opera) { // workaround for the inconsistent handling of trailing newlines in IE 
               var l = ciTextRange.text.length;
               while(ciTextRange.text.length == l) {
                  ciTextRange.moveEnd('character', -1);
               }
               ciTextRange.moveEnd('character', 1);
            }
            var selection = ciTextRange.text;
         } else if(textarea.selectionStart || textarea.selectionStart == '0') { // Gecko-based
            var selection = textarea.value.substring(textarea.selectionStart, textarea.selectionEnd);
         }
      }
      return selection;
}

function replaceSelection(text) {
      if (typeof(wikEdUseWikEd) != 'undefined' && wikEdUseWikEd == true) {
         ciWikEdObj.changed.plain = text;
         ciWikEdObj.changed.keepSel = true;
         wikEdLastVersion = null;
         ciWikEdObj.html = ciWikEdObj.changed.plain;
         if (wikEdHighlightSyntax == true) {
            WikEdHighlightSyntax(ciWikEdObj);
         } else {
            ciWikEdObj.html = ciWikEdObj.html.replace(/(\t)/g, '<span class="wikEdTabPlain">$1</span><!--wikEdTabPlain-->');
         }
         ciWikEdObj.sel.removeAllRanges();
         ciWikEdObj.sel.addRange(ciWikEdObj.changed.range);
         WikEdFrameExecCommand('inserthtml', ciWikEdObj.html);
         wikEdFrameDOMCache = null;
         wikEdFrameWindow.focus();
         if (wikEdHighlightSyntax == true) {
            WikEdFollowLinks();
         }
      } else {
         var textarea = document.editform.wpTextbox1;
         textarea.focus();
         if (document.selection && document.selection.createRange) { // IE, Opera
            if (document.documentElement && document.documentElement.scrollTop) {
               var winScroll = document.documentElement.scrollTop
            } else if (document.body) {
               var winScroll = document.body.scrollTop;
            }
            ciTextRange.text = text;
            if (document.documentElement && document.documentElement.scrollTop) {
               document.documentElement.scrollTop = winScroll;
            } else if (document.body){ 
               document.body.scrollTop = winScroll;
            }
         } else if(textarea.selectionStart || textarea.selectionStart == '0') { // Gecko-based
            var textScroll = textarea.scrollTop;
            var selStart = textarea.selectionStart;
            textarea.value = textarea.value.substring(0, selStart)
                           + text
                           + textarea.value.substring(textarea.selectionEnd, textarea.value.length);
            textarea.selectionStart = textarea.selectionEnd = selStart + text.length;
            textarea.scrollTop = textScroll;
         }
}

What i meant with the last paragraph is that it would be nice to have more API-type functions like WikEdUpdateTextarea/WikEdUpdateFrame in WikEd; specifically one to read/replace selection. (And more generally, i would really like to see scripts like WikEd or Lupin's navpopup to evolve in a developement framework direction. I think MediaWiki developement didn't scale with the community, and it's one of the worst bottlenecks right now; moving more of the new feature developement process to the javascript level would be very good, as that is much more scaleable... okay, I'll stop ranting now :)

--Tgr 18:20, 31 August 2007 (UTC)

Customizing:Edit_Toolbar

In our present mediawiki site, we have removed the old monobook.php file which is the default file you have when installing mediawiki and have uploaded a new monobook.php file with table format instead of div. In the previous monobook (i.e the default one)...there are many style sheets, li tags, javascripts etc that has been used, which is not used in our present design. If we use the previous stylesheet, javascript, etc.. the design gets changed. When we click "edit" on any of the articles, we do not have any edit toolbar configured. We want to add the Edit toolbar. Does anyone have any experience and success with customizing the Edit Toolbar?.......Please help.

<?php print Skin::makeGlobalVariablesScript( $this->data ); ?>

before this line: (line 53)

CODE <?php if($this->data['jsvarurl' ]) { ?><script type="text/javascript" src="<?php $this->text('jsvarurl' ) ?>"></script><?php } ?>

I used this code but unfortunately I am getting a javascript error(i.e.Object expected in line no. 570)..... please help —Preceding unsigned comment added by Gbozz (talk • contribs) 09:30, 19 November 2007 (UTC)

Colors

Hello

Very nice Tool! For daily use the colors are a bit extreme. For e.g. bold and red is to much. Maybe take an example on Notepad++. I think color codes can be found in config. --84.156.70.189 20:22, 4 December 2007 (UTC)

Firefox 3 (dev release)

When running this in Firefox (well, Swiftfox actually) 3.0b2pre (current latest version), it breaks. The edit box turns light blue. It is possible to add text, but old text is not displayed, and I think it might get overwritten if I save. When running it in Firefox (not Swiftfox) 2(.0.0.10 or so) it doesn't have any problems. Swiftfox uses the same extensions as Firefox, but many are disabled as being incompatible. I use Swiftfox for RC patrol, but often I have to warn users, and it's annoying to have to open the talk page in a new tab just to look at past warnings, so I've disabled wikEd for now. --Thinboy00 @921, i.e. 21:06, 15 December 2007 (UTC)

Please could you provide more information, filling out the bug report form on top of this page would definitely help me to get a better idea of your problem and the possible cause. Does the wikEd logo on top of the page have a red cross, indicating a loading error. Which error message do you see on the Javascript error console? Thanks, Сасусlе 00:14, 16 December 2007 (UTC)

I have the same problem. wikiEd 0.9.56. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2, no error console errors at all. This is the only userscript in monobook.js. The icon shows a loading error. Have not yet tested extention errors. Will test that after posting and will provide information shortly. Tacvek (talk) 22:18, 4 January 2008 (UTC)

I have verified that it is not the add-ons. I've noticed somebody else found an error with Venkman. I will see what further I can discover like that. Tacvek (talk) 22:24, 4 January 2008 (UTC)

Ok. As the other poster has mentioned the error is from the line

this.styleElement.appendChild(document.createTextNode()); // Saari 3 fix

The exact error is "Node cannot be used in a document other than the one in which it was created", which is correct. this.styleElement is set as a node from contextObj. However that line of code appends a node created from document. Since contextObj might not be document that is the problem. I suspect that using contextObj on that line rather than document would fix the problem. (Although other problems may still exist.) Tacvek (talk) 22:53, 4 January 2008 (UTC)

Fixed the Safari 3 fix in 0.9.57. Сасусlе 02:24, 5 January 2008 (UTC)

Ok. It seems to work now in Firefox 3 beta 2. Tacvek (talk) 20:57, 5 January 2008 (UTC)

Oh, hmm... while it sometimes works, it seems to be breaking if certain text is included in relevant page section (such as a category tag), there is some form of RegEx problem. There is an error in the error console. Under debugging i see the error can occur many times in one page load. One such error: Error ``invalid range in character class'' [x-] in file ``[../index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript]'', line 6905, character 0. Tacvek (talk) 21:29, 5 January 2008 (UTC)

Please give me an example article or text. Сасусlе 22:19, 5 January 2008 (UTC)

Sorry for the late reply, I only now noticed your reply. For a test page, I just picked one at rondom from the front page. For example: Quneitra. I am now using Firefox 3 Beta 3, and can edit this page just fine with wikEd, but editing that (or any page at all using cataegory tags) breaks with the ``invalid range in character class'' error. I'm pretty sure other things will break wikEd also (same basic bug) but the category tags are the first thing I've identified as a problem. Tacvek (talk) 01:21, 17 February 2008 (UTC)

See below under Swiftfox broken. It is a Firefox 3 bug that has already been filed, see Bug 416933. Сасусlе 07:01, 17 February 2008 (UTC)

Problem with Wikicities:c:ChristianMusic:MediaWiki:Edittools

It is just too bulky. Any suggestions? I don't know CSS or JS well enough. I also would like to allow users that install wikEd to turn off or hide the default edit tools. (However, it would help if wikEd could replace all of the edit cools including special characters. At the ChristianMusic wiki, ♥, ▲, and ▼ all tend to have special meanings to templates. My version of Edittools provides a handy way to enter them. Perhaps when wikEd is active, if you could autohide Edittools, that would help. Will (Talk - contribs) 03:27, 16 December 2007 (UTC)

Support for source tags

Could you please add support for <syntaxhighlight lang=""> tags? They're used for stuff like JavaScript syntax highlighting, but the wikEd preview doesn't render them properly, and it highlights them as an invalid tag.

Example:

// This is an example script.
document.write('Notice how wikEd highlights the tags wrong in the edit box.');
/* wikEd preview renders this code without the syntax highlighting. */

I'm not sure how long these have been in use, as I didn't know about them until recently, but it'd be nice to have wikEd support these. Thanks, Pyrospirit (talk · contribs) 20:53, 16 December 2007 (UTC)

Sure, as soon as I find the time - Сасусlе 23:43, 19 December 2007 (UTC)

Added to 0.9.58. Сасусlе 17:26, 13 January 2008 (UTC)

Swiftfox broken

This is a relisting of my previous bug, with much more info:

• WikEd version 0.9.56
• Browser ID Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2007121618 Firefox/3.0b3pre (Swiftfox)
• Errors: First to last. Note: First two appear before wikEd toolbar appears.
  • Warning: Unknown property 'column-count'. Declaration dropped. Source File: http://en.wikipedia.org/w/index.php?title=MediaWiki:Common.css&usemsgcache=yes&action=raw&ctype=text/css&smaxage=2678400 Line: 52
  • Warning: Unknown property 'word-wrap'. Declaration dropped. Source File: http://en.wikipedia.org/w/index.php?title=MediaWiki:Common.css&usemsgcache=yes&action=raw&ctype=text/css&smaxage=2678400 Line: 69
  • Warning: Error in parsing value for property 'white-space'. Declaration dropped. Source File: http://en.wikipedia.org/w/index.php?title=User:Thinboy00&action=edit Line: 130
  • Warning: Expected color but found 'auto'. Error in parsing value for property 'border'. Declaration dropped. Source File: http://en.wikipedia.org/w/index.php?title=User:Thinboy00&action=edit Line: 46
  • Ibid Line 49
  • Ibid Line 52
• Addons are irrelevant as every single addon that I have enabled in this browser is also enabled in Firefox 2(.0.0.10 or something) and Firefox 2 also has several addons enabled that I don't have in Swiftfox. However it's a short list so:
  • Adblock Plus- disabled on *.wiki*.org as Wikimedia is advert-free
  • All-in-One Sidebar
  • ChatZilla (not installed when the problem first appeared)
  • DOM Inspector
  • NoScript (disabled on en.wikipedia.org)
  • ProfileSwitcher
  • Session Manager
  • Several others are wholly disabled due to incompatibility with Swiftfox/Minefield
• Other scripts may be irrelevant as above, but all I have is Twinkle
• OS Ubuntu Gusty Gibbon 7.10
• Problem is as follows:

WikEd toolbar loads, icon in corner has a red "X". Page text is loaded but suppressed when wikEd toolbar becomes visible. Similarly, text field (editing box only, not edit summary) loads with BG color of white, but when wikEd loads, color changes to match monobook baby blue. Text typed into edit field is of a larger size and different font.

• Reproduce as follows (unfortunately requires installation of Ubuntu, and a compatible processor, in order to fully emulate my experiences):

1. After installing Ubuntu, don't mess with which browser to use by default (I did not attempt to go this far back, I went as far as 3)
2. Install wikEd
3. Install Swiftfox Pentium-m version for Debian/Ubuntu
4. Enable wikEd
5. Attempt to edit any page

I'm not sure if this works on other OS's (Swiftfox installs differently), and I know that Ubuntu is obscure. I'd like to point out that Swiftfox passes the Acid2 test on my machine, hinting at a lack of problems with the rendering engine. The issue continues even after a manual complete removal and subsequent (re)installation via Synaptic package manager. --Thinboy00 @149, i.e. 02:34, 20 December 2007 (UTC)

The listed errors are all css errors, are there no JavaScript errors? There should be, because only a real JavaScript error could stop the wikEd setup, leaving the red cross logo in place. Сасусlе 18:01, 20 December 2007 (UTC)

I took a screen shot. Would you like me to email it to you (I don't think it's appropriate for commons or wikipedia, because it's useless everywhere but here)? I'm not sure if Special:Emailuser supports attachments, though. Oh, and Happy Holidays. --Thinboy00 @734, i.e. 16:36, 22 December 2007 (UTC)

Thanks for your effort. The easiest way would be to select "Errors" in the error console and to copy and paste entries (Ctrl-C works for error messages) which have wikEd.js in their file name. Сасусlе 17:58, 22 December 2007 (UTC)

(outdent) No I think you don't understand. I took a screenshot of what it looks like when it's broken, not of the error console. I copied and pasted all of the error messages verbatim, clearing the console immediately before testing. You already have all of the errors above. --Thinboy00 @200, i.e. 03:47, 10 January 2008 (UTC)

What you pasted were the console "Warnings", not the "Errors" (or "All"). I need to see the errors to be able to help you, the screenshot is not that important. Сасусlе 12:45, 10 January 2008 (UTC)

Oh, sorry, I didn't realize that... Swiftfox uses a weird UI... here's the error you're looking for:

Error: invalid range in character class

Source file: http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript&dontcountme=s

Line: 6994

Hope this helps, because it's the only non-css error I could find. --Thinboy00 @893, i.e. 20:25, 13 January 2008 (UTC)

I have tested it under Minefield/3.0b3pre and it works fine. The error is caused by a RegExp containing Unicode characters:

var regExp = new RegExp('\\s*[\\w À-ÖØ-öø-\\u0220\\u0222-\\u0233ΆΈΉΊΌΎΏΑ-ΡΣ-ώ\\u0400-\\u0481\\u048a-\\u04ce\\u04d0-\\u04f5\\u04f8\\u04f9\\-]+\\s*:\\s*' + wikEdText['wikicode Category'] + '\\s*:', 'i');

My guess is that this is a real bug in FireFox Swiftfox related to Unicode and I suggest to file a bug report on bugzilla.mozilla.org. Unfortunately, I cannot track the error down without an Ubuntu/Swiftfox installation. I will save a version with a slightly rearranged regular expression under the version number 0.9.58e, maybe that helps, please report back after Shift-Reload. Сасусlе 22:38, 13 January 2008 (UTC)

I've had the same problem with the invalid range in character class in my installation of Firefox 3.0b2 on Windows XP. Not exactly sure why, though. I'm using this with a gadget installation (version 0.9.61f) at my website's wiki (MediaWiki 1.11.1), and can edit the Main Page fine, but trying to edit something like my Help:Posting Guidelines page produces the problem. It's really quite odd, although I did get to looking and do notice that pages without categories don't seem to have issues. Hmm... --Raenis (talk) 11:17, 10 February 2008 (UTC)

The code in question is now in line 7066 and is executed when highlighting rangescategory tags. Would you mind tracking the problem down by removing single ranges (of the form "\\u048a-\\u04ce") and testing if this prevents the error. Thanks in advance, Сасусlе 16:46, 10 February 2008 (UTC)

After removing the ranges you mentioned, the problem still persists. I did, however, manage to get it to work earlier today by changing the regex to the following:

var regExp = new RegExp('\\s*[\\w\\- \\u0401-\\u0481\\u0490-\\u04cc\\u04d0-\\u04f5\\u04f8\\u04f9]+\\s*:\\s*' + wikEdText['wikicode Category'] + '\\s*:', 'i');

However, I'm not exactly sure how much this limits the internationalization of the gadget, though. My wiki is pretty much english only so that doesn't affect me personally, but I too would like to see that it works well for everyone. --Raenis (talk) 22:13, 10 February 2008 (UTC)

That's interesting. It would be a big help if you could try to figure out which character or range causes the problems. Thanks in advance, Сасусlе 22:47, 10 February 2008 (UTC)

Alright, I had more time to test several different possibilities of what was causing the problem and the issue seems to be related to a single character range in the class, that range being:

Ø-ö

The rest of the regex is intact as it originally was. I also tried converting the starting and ending characters of that range to their Unicode equivalents, but the problem persisted. Hope that helps. --Raenis (talk) 18:40, 11 February 2008 (UTC)

The critical range is between Þ-ß. I have filed a Mozilla bug report, let's hope they will fix it soon. Thanks again, Сасусlе 03:52, 12 February 2008 (UTC)

Wikia has a new forum system

It supports some wiki syntax (but no HTML that I tried). It is based on BBCode. You can see two forums here and here. It would be great if you could find a way to get wikEd working with that system. Currently, wikEd is unavailable. Will (Talk - contribs) 04:24, 20 December 2007 (UTC)

Almost forgot. Wiki-style links out of posts work. But users can't link to any forum pages with internal links. That is why I used external links. Will (Talk - contribs) 04:26, 20 December 2007 (UTC)

That is currently not possible, but might be an interesting direction for development in the long run. Сасусlе 18:09, 20 December 2007 (UTC)

I should also note that wikEd is not available when I upload images. However, if I edit an image, wikEd works. Will (Talk - contribs) 06:41, 22 December 2007 (UTC)

Upload page support has been added in version 0.9.58. Сасусlе 06:20, 16 January 2008 (UTC)

Firefox 3b2 loading error

In using the version direct linked 0.9.56 on Firefox 3b2, the editing window shows up, but the text doesn't load into it, and the buttons don't respond. The little enabler button on the top right says "loading error" and can be disabled by clicking.

in the javascript debugger, venkmann says the error is at line

this.styleElement.appendChild(document.createTextNode()); // Safari 3 fix

and

apparently ie7 isn't supported either?

Benjamin Fleischer

Fixed in 0.9.57. IE7 is not yet supported, please see wikEd dev and wikEd dev talk. Сасусlе 02:23, 5 January 2008 (UTC)

Help

Hello. I am currently using Firefox 2.0.0.11. Whenever I edit a page, the WikEd logo appears, but is grey. Clicking on it does nothing. I hovered over it, and it said:

Browser not supported - wikEd 0.9.56 (December 12, 2007)

Is it not supported? Or is their some other issue?

Thanks! -Billy-talk 18:43, 31 December 2007 (UTC)

Also, whenever I log out, it works again (I also have it install in Greasemonkey). -Billy-talk 18:54, 31 December 2007 (UTC)

What's your browser id (see the top of this page). You might have changed this id to something else. Сасусlе 17:28, 2 January 2008 (UTC)

I'm getting the same message with a newer version\date and I'm using IE7 -- JRV 8.15.3.139 (talk) 21:51, 9 April 2008 (UTC)

insertTags not reverted

WikEd replaces inserTags() with wikEdInsertTagsOriginal() when loaded, but does not change it back when unloaded through the icon, thus clicking the edit toolbar will result in errors. --Tgr (talk) 16:26, 2 January 2008 (UTC)

Fixed in 0.9.57. Thanks, Сасусlе 02:20, 5 January 2008 (UTC)

Extending selected text

First of all, thank you once more for creating this excellent tool: it's a pleasure to use it!

I'm using FF2. When I select text & then expand the selection, the selection always extends beyond the final word to include any following space and/or punctuation. For example, if I select this in the first line of this post by clicking on the word, & then expand the selection to include the words excellent tool, the selection includes the colon and space (: ) as well. Is it possible to override this behaviour in WikEd so that the selection stops at a word boundary (as in eg Word)?

Please forgive me if you've already answered this question. --NigelG (or Ndsg) | Talk 15:46, 11 January 2008 (UTC)

Thanks :-) Sorry, that behavior is controlled by Firefox, wikEd has no influence on it. I think it is a feature, not a bug. It makes some sense to move the trailing space together with the word if you are shuffling words around and want to keep them evenly spaced. Сасусlе 23:31, 11 January 2008 (UTC)

You're right: sometimes it's just what you want, other times it's annoying! Anyway, I rather suspected it was a feature of FF, not wE. Thanks for setting the record straight. --NigelG (or Ndsg) | Talk 15:42, 12 January 2008 (UTC)

Regex in Find

I can't get this to work. Could you please explain exactly how I would search for mast, must or most? I assumed I should type m[aou]st in the search box; but it doesn't seem to find anything. I've been clicking on the little binoculars: is that right? Could this be a conflict with other software? --NigelG (or Ndsg) | Talk 21:38, 17 January 2008 (UTC)

Oops, it is broken. I'll fix it later today. You have to select the /R/ button. Сасусlе 23:02, 17 January 2008 (UTC)

Fixed in 0.9.59. Сасусlе 04:45, 18 January 2008 (UTC)

Thanks for the speedy & effective action! wikEd is wonderful—thanks again for all your hard work. --NigelG (or Ndsg) | Talk 11:24, 18 January 2008 (UTC)

Are there any known problems with using wikEd in Linux and Firefox?

I now have a Ubuntu 7.10 installation with Firefox 2.0.0.6 (Ubuntu comes with an out of date version of Firefox). Are there any known problems with this combination? wikEd is not working here. Will (Talk - contribs) 07:06, 21 January 2008 (UTC)

Please could you fill out the bug report form from the top of the page. Thanks, Сасусlе 15:28, 21 January 2008 (UTC)

Never mind. It was a Firefox extension called NoScript. I didn't realize it was blocking scripts from Wikipedia's server. Sorry. Will (Talk - contribs) 06:58, 22 January 2008 (UTC)

German Wikipedia Gadget

Hello,

i tried to use wikEd in the German wikipedia. It should be available as gadget, but if i enable it, I see the small error symbol on the upper right corner of the webpage which says "Loading error - wikEd {wikEdProgramVersion} ({wikEdProgramDate}) Click to disable".

My firefox reports me this JS errors:

wikEdProgramVersion is not defined
[Break on this error] var version = wikEdProgramVersion;

de:Benutzer:habakuk-- 217.229.48.3 (talk) 13:23, 22 January 2008 (UTC)

Thanks habakuk, somebody has made a small mistake during the last version update. I have notified the German Wikipedians and it will hopefully be fixed soon. You might have to Shift-Reload to get the corrected version. Thanks, Сасусlе 04:19, 23 January 2008 (UTC)

It has been fixed. Сасусlе 02:15, 24 January 2008 (UTC)

copying from PDFs with formatting

Hi - I've been using wikEd at Appropedia to port HTML content that we have the permission to use. Word docs seem to work too. Fantastic tool.

However, we haven't yet figured out how to copy and paste PDFs as formatted text - it only pastes as plain text (no matter what program or edit box it's pasted into). Just wondered if you happened to have come across this, or have any ideas about this. Much appreciated. --Chriswaterguy talk 03:32, 29 January 2008 (UTC)

I do not think that it is possible to copy and paste formatted text from pdf files. Adobe Acrobat has an export function, but the results are not much better than pasting unformatted text (although links and colors are preserved). Сасусlе 04:15, 31 January 2008 (UTC)

Request: Add BonEcho to the userAgent regex

WikEd version:	0.9.60 GM
User agent string:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071204 BonEcho/2.0.0.11

BonEcho is the development version of Firefox. Because of the different name WikEd refuses to work ("Browser version not supported"). On every update of WikEd I've to fix the userAgent Regex (Line 1174 in the Greasemonkey version) to look like this:

var agent = navigator.userAgent.match(/(Firefox|Netscape|SeaMonkey|IceWeasel|IceCat|Minefield|BonEcho)\W+(\d+\.\d+)/i);

Could you please add BonEcho to the Regex permanently so I don't have to fix that on every update? Thank you. —Preceding unsigned comment added by Tblue468 (talk • contribs) 14:35, 3 February 2008 (UTC)

Added to current version 0.9.60a. Сасусlе 02:24, 6 February 2008 (UTC)

Bravo!

Tremendous effort Cacycle. Keep up the good work. Riddell ☎ 16:35, 3 February 2008 (UTC)

Non-breaking space

It would be very useful to have a button for the NBSP ( ). I know there isn't much space on the toolbar, but one solution might be to have Subscript and Superscript on the same button, with Superscript using Shift-click (intuitive!). --NigelG (or Ndsg) | Talk 18:48, 5 February 2008 (UTC)

You can make your own custom button. There is also a &nbsp; link in the specialchars insert box below the edit field. Сасусlе 05:23, 10 February 2008 (UTC)

Thanks: I knew about the insert box—it's just that it's not that convenient to use. I think I'll try making a custom button instead. --NigelG (or Ndsg) | Talk 00:44, 11 February 2008 (UTC)

wikEd and my user JavaScript

Hi,

I am developing a user script in the German Wikipedia which does typographic corrections like automatically inserting fancy quotes when you type ".

At the moment, this does not work with wikEd because the script reacts to the textbox' onKeyPress event. For the moment, I'd like to disable my script when the wikEd editor is active.

• Is there a possibility to reliably determine whether wikEd is active or not? My script may be loaded any time, even when the wikEd script is not yet active.

Use if (typeof(wikEdUseWikEd) != 'undefined') { if (wikEdUseWikEd == false) { your-code } } to test if you have the classsical textarea displayed. Сасусlе 21:09, 6 February 2008 (UTC)

The problem is that I want to show or hide my script's "user interface" (currently only a checkbox) depending on whether wikEd is active. So I need to know if it's active right at startup.

The wikEd setup is, as far as I see, done in the function wikEdSetup() which is called by an event listener when the page is loaded. So what I'd have to do is to ensure that my init function gets called after the wikEd init function, so that the wikEdUseWikEd variable is set. Is there a way to do that? -- de:Jowereit, 21:50, 6 February 2008 (UTC)

I have added the function hooks wikEdSetupHook, wikEdOnHook, wikEdOffHook, wikEdTextareaHook, and wikEdFrameHook to the new version 0.9.61. Add your function to any of these by wikEdSetupHook.push(YourFunction);. See line 894 for more details. You probably want to use wikEdSetupHook (check wikEdUseWiked if the textarea or the frame is in place), wikEdTextareaHook, and wikEdFrameHook. Сасусlе 02:56, 7 February 2008 (UTC)

Wow - thank you very much, it works like a charm now. Keep up the good work! -- de:Jowereit, 21:50, 6 February 2008 (UTC) —Preceding unsigned comment added by 217.228.220.119 (talk)

• Can I somehow react to wikEd being enabled/disabled via the button in the personal toolbar? I want to reenable my script when wikEd is disabled.

It is probably better to check wikEdUseWikEd, but you can always add your own event listener to that button (line 1346, WikEdAddEventListener(wikEdLogo, 'click', WikEdMainSwitch, true);), but I am not sure about the order in which they will be called. Сасусlе 21:09, 6 February 2008 (UTC)

This would be the same problem as above: to add an event listener, the toolbar button must already exist, so I'd have to add the listener after wikEdSetup() has been called. -- de:Jowereit, 21:50, 6 February 2008 (UTC)

• Since I ultimately want my script to work with wikEd too, can I somehow capture the key that is pressed and replace it with another character? E. g. at the moment, when the " key is pressed, I manually insert „ or “ and then return false; to prevent the original character from being inserted. Is something similar possible with wikEd?

Use WikEdFrameExecCommand('inserthtml', string); to insert the character, see http://developer.mozilla.org/en/docs/Midas. Сасусlе 21:09, 6 February 2008 (UTC)

OK, thank you for the link! -- de:Jowereit, 21:50, 6 February 2008 (UTC)

It is a bit more complicated to get the plain text and your caret position in it: after running WikEdParseDOM(obj, wikEdFrameBody); you have the plain text in obj.plain and the caret position in obj.plainFocus. Сасусlе 02:40, 7 February 2008 (UTC)

Thanks in advance,
de:Jowereit, 16:53, 6 February 2008 (UTC)

You could also add your replacement as a purple wikEd button, see User:Cacycle/wikEd_customization#Custom_buttons. Сасусlе 21:09, 6 February 2008 (UTC)

This would be a button that takes the existing text and fixes all fancy quotes etc. in it? That would be possible as an additional option, but my existing script does the replacement right when the key is pressed (as normal word processors do, BTW), and I'd like to keep that functionality with wikEd, if it's possible. -- de:Jowereit, 21:50, 6 February 2008 (UTC)

My Word (processors) don't do this, it is the very first thing I turn off because I find it so highly annoying :-) Сасусlе 02:40, 7 February 2008 (UTC)

wikEdStrangeSpaces

(Moved from User talk:Cacycle)

I was glancing over the wikEd code, and noticed the code for non-breaking space was given as '31' - is this correct? the decimal for non-breaking space is actually 160. Also, in control characters, you have:

       '25': 'end of medium',
       '25': 'substitute',

and everything after that, up to 30, are off by one. I'd fix it myself, but don't want to mess around in code i'm not familiar with. —Random832 18:22, 6 February 2008 (UTC)

Thanks, I will check and correct that. Сасусlе 19:41, 6 February 2008 (UTC)

Fixed in 0.9.61e. Сасусlе 05:18, 10 February 2008 (UTC)

Greasemonkey version with customization for JS

I set up the Greasemonkey version and I tryed to customizing my personal settings in Monobook.js, but I couldn't (I followed the instruction).

When I install JavaScript version (as a user script) and customized it same as above (I set Greasemonkey extension off), that had no problem. Please help me ― 韓斌/Yes0song (談笑 筆跡 다지모) 14:34, 7 February 2008 (UTC)

You have to add the customization to the top of the installed Greasemonkey user script (click Manage user scripts -> Edit). Remember that these settings will be overwritten when you update the script. Сасусlе 17:28, 7 February 2008 (UTC)

I understand how to customizing the Greasemonkey version, now. Thank you for your answer. However, I suggest a new idea to you. It is that you will make the new version of wikEd Greasemonkey edition checks and uses the wikEd custom settings written in User:Username/monobook.js (or modern.js, etc.) located in the processing wiki. If my idea will be applied in the new version of wikEd Greasemonkey edition, users can customizing every each wikis. Therefore, I strongly hope this idea to be accept. ― 韓斌/Yes0song (談笑 筆跡 다지모) 16:08, 9 February 2008 (UTC)

You would get exactly what you want if you put the short wikEd installation code below your customizations on every wiki's monobook.js as monobook-installed wikEd takes precedence over the Greasemonkey installation. Сасусlе 17:24, 9 February 2008 (UTC)

Sicilian translation for wikEd

I've finsched the sicilian translation for Wiked. --Meloscn (talk) 21:16, 7 February 2008 (UTC)

Thanks :-) Сасусlе 04:05, 8 February 2008 (UTC)

IE7 Support

Hi, I would like wikiEd to be supported by Internet Explorer, particularly Internet Explorer 7--Troop350 (talk) 20:50, 7 February 2008 (UTC)

Please see wikEd dev and wikEd dev talk if you want to help. The problem is that MS IE is way behind in terms of supported features and standards conformity. It is a major annoyance for web developers to program for this browser and requires a good deal of IE-specific duplicate code that bloats the program and costs time to develop and maintain. However, I would be happy to add the needed changes and would gladly assist anybody trying to push this forward. Сасусlе 17:11, 10 February 2008 (UTC)

Option to make ctrl+click case sensitive.

Does this already exist? It's a bit annoying to use WikEd on Wiktionary and constantly have to go through the redirection routine (if it wasn't implemented server-side as a workaround, very few links would actually get where they are supposed to). Circeus (talk) 20:34, 9 February 2008 (UTC)

Please could you give me an example. Thanks, Сасусlе 21:36, 9 February 2008 (UTC)

Links like a or b are sent directly (by the script, not MediaWiki) to A and B instead of their proper targets. If there happens to be two entries, the link is outright incorrect. Having an option (or even a bit of script) for the css page would be very helpful. Circeus (talk) 22:12, 9 February 2008 (UTC)

I will check that. What do you mean by "css page"? Сасусlе 05:15, 10 February 2008 (UTC)

Link uppercasing fixed in 0.9.61f. Сасусlе 05:42, 10 February 2008 (UTC)

Sorry, I meant the monobook.js page (or whichever the user uses.). Circeus (talk) 01:01, 11 February 2008 (UTC)

Awesome. Circeus (talk) 01:10, 11 February 2008 (UTC)

Coding question

Little question, simply out of curiosity: what is the purpose of this edit, doesn't window.myVar=something have exactly the same meaning as myVar=something ? I might be wrong, but for a script that's designed for only one browser WikEd seems to have a lot of unnecessary extra code. / AlexSm 22:53, 9 February 2008 (UTC)

It's for Greasemonkey support, see User:Cacycle/wikEd_development#Greasemonkey-compatibility. The mentioned edit was a test and has been reverted. I had to fix compatibility of multiple parallel installations (i.e. Greasemonkey, gadget, user script) and the problem was caused by variable declarations without testing if they were already initialized. Сасусlе 05:14, 10 February 2008 (UTC)

I do not think that there is much unnecessary extra code (beside "simple" coding style and comments), feel free to discuss specific parts here. Сасусlе 05:55, 10 February 2008 (UTC)

Wiki's Without Internet Connection Section Missing

I run my WikiEd install as a "wiki without internet connection" for security reasons. I came to get the latest updates to the code but that section is gone now. (Though there are still 1 reference and 1 dead link to it on the page.)

Can this section come back?--Vaccano (talk) 17:48, 12 February 2008 (UTC)

The section has been moved to User:Cacycle/wikEd_installation. Сасусlе 21:53, 12 February 2008 (UTC)

Syntax highlighting

Is it possible to just enable syntax highlighting and disable everything else. That's all I'm interested in. Perhaps separate that section of code from the rest of WikEd and create a separate script with that? Mahanga^Talk 21:59, 17 February 2008 (UTC)

Add the following code to your monobook.js page (it has essentially the same effect as pushing the button):

var wikEdUseWikEdPreset = false;

I will not maintain a stripped version (and you might find out after a while that the buttons can be quite useful - see wikEd help for a short how-to). Сасусlе 22:34, 17 February 2008 (UTC)

new CSS-Bug?

I've only been using wikEd as Gadget for a few days, but the following error seems new since today (and vanishes when I turn wikEd off in WP-preferences):

• Warning: Expected color but found 'auto'. Error in parsing value for property 'border'. Declaration dropped.
• Line: 46, 49, 52

--ParaDox (talk) 14:37, 20 February 2008 (UTC) (de:User:ParaDox)

Thanks. This has already been fixed and the warnings will disappear with the next update of the German gadget page to the current version (any admin can do that). Сасусlе 03:15, 21 February 2008 (UTC)

System Requirements Revision

In the system requirements section, it should state, resolution of 1024 x 768, not 786. Since the article is protected, perhaps a sysop could fix it. 71.194.57.163 (talk) 07:04, 25 February 2008 (UTC)

Changed, thanks. Сасусlе 13:41, 25 February 2008 (UTC)

Top of page

Is there a way to make wikEd not scroll down to the toolbar of edit window? Thanks for a great tool. Libcub (talk) 07:06, 25 February 2008 (UTC)

Add the following line to your User:Libcub/monobook.js page:

var wikEdScrollToEdit = false;

Сасусlе 02:17, 12 March 2008 (UTC)

Extending selection by words

In other Firefox text boxes (I'm using Firefox version 2.0.0.12), I can extend the selection a word at a time by using Ctrl+Shift+arrow. That isn't working for me in wikEd. Any chance that can be added/fixed? I rely on that feature a lot. Thanks, Libcub (talk) 07:09, 25 February 2008 (UTC)

This works for me under FF 2.0.0.12 and Seamonkey, so it might be caused by another extension. Cacycle 13:40, 25 February 2008 (UTC)

You were right--it was the Firefox extension NextPlease. Thanks for pointing me in the right direction! Libcub (talk) 05:49, 27 February 2008 (UTC)

Error

I want to use wikEd only (so, not the old one as well), but it don't have a signature button, can you put one on. Plus, I can't create pages or edit blank pages/sections, it dont work. P.S. Does the edit summary history forget stuff over time? --[[123Pie|Talk]] 17:23, 25 February 2008 (UTC)

Found the source of prob. --[[123Pie|Talk]] 18:16, 25 February 2008 (UTC)

The summary history keeps the last 10 entries and can be deleted by pushing the button. The values are stored in cookies with a 30 day life span. A signature button has to be added as a custom button (see customization section) in order to keep the user interface small. Сасусlе 05:03, 26 February 2008 (UTC)

But the customized wikEd only works for one page. --[[123Pie|Talk]] 17:30, 26 February 2008 (UTC)

All sorted. I could not find out how to make a sig button can somebody do it for me. --{{SUBST:123Pie|Talk}} 17:42, 26 February 2008 (UTC)

Error in IE7

IE7 says Access denied at line 8685 of wikEd.js (request.open(requestMethod, requestUrl, true);). By the way, have you thought of using a javascript framework (jQuery, for example)? It would solve most of the browser-dependency issues. --Tgr (talk) 10:22, 4 March 2008 (UTC)

Many of the tricky DOM manipulations of wikEd are probably beyond a framework, however, I have not checked them yet. Сасусlе 17:26, 4 March 2008 (UTC)

Love the app, but big problem

(Moved from User_talk:Cacycle/wikEd_help)

Hi- this is really cool, but I can't seem to click into an empty text field to create a page. Can't tab in, either. A similar (but less problematic) thing happens with existing articles -- if I click below the last line of text, the cursor also does not show up in the box (or allow me to type.) I have to click within the existing text.

It's sort of a dealbreaker for me, since I create a lot of redirects and stubs. Unless there's an easy fix? I'll be back to check this out regardless, since there are so many advantages to the tool! (It's the text/syntax coloring that I like the most.) -Pete (talk) 01:42, 8 March 2008 (UTC)

You are probably using Firefox for Mac as other users have reported similar problems. These are annoying Firefox bugs, not wikEd bugs. I am sorry that I cannot help you as I do not have a Mac so that I cannot try to find workarounds for these long known browser bugs. You might want to file a bugzilla.mozilla.org bug report. Сасусlе 04:48, 8 March 2008 (UTC)

Arg! Okay, thanks for the explanation. Nice to know I won't have such problems when I'm using Windows FF. I just tried it in Camino, which is a Mac-specific Firefox variant, and is a much more refined app; but the editor isn't enabled. Any chance that's just a variable that could easily be changed to say "use with Camino" as well as "use with Firefox?" I'll try to file that bug report, haven't done that before, so it's probably about time I learn how. -Pete (talk) 06:11, 11 March 2008 (UTC)

SVGA with 800px

hi Cacycle - well done piece of art - in fact, there is a problem with lesser-than-XGA-resolution, as the 4 default-toolbars won't fit, causing the 4th to break to new line - now space below gets short.. ;) - any chance You let me switch off one of the bars (in fact I'd prefer the "fix .."-bar) - think it would just need one customation-variable (or you add x-toggles..) besides that, I'm happy - greetings from de:WP --W!B: (talk) 02:19, 10 March 2008 (UTC)

Thanks :-) You can minimize the toolbars by clicking their handle, see User:Cacycle/wikEd_help#Collapsing_button_bars. Сасусlе 01:15, 12 March 2008 (UTC)

hey fine, big usability.. i'd never have found that myself - maybe You add an "help"-button, linking to that page?- or did You already, and I missed it too?  ;) - greetings --W!B: (talk) 07:55, 12 March 2008 (UTC)

Yes, there is a wikEd help link under the edit box :-) Сасусlе 06:46, 6 April 2008 (UTC)

Works with modern skin ?

There is a new skin that can be selected, "Modern". Does wikEd work with it? ffm 16:30, 10 March 2008 (UTC)

Modern support has already been added, please report any problems here. Сасусlе 02:18, 11 March 2008 (UTC)

Using it right now, works wonders (thanks for all your work!). Just a question, will it ever be possible to modify the prefs using the gadget version? The Userprefs page states that that is not possible ATM. ffm 01:23, 12 March 2008 (UTC)

Yes, wikEd run as a gadget is fully customizable from your monobook.js page. This might be different for other gadgets. Сасусlе 02:07, 12 March 2008 (UTC)

Fix punctuation (French)

Correct when editing a text in english, the Fix punctuation button is quite inaccurate when editing a text in French. In this language, several punctuation characters must be preceded by a space! It is the case for ":;!?»". It would be fine to get an easy way to inactivate or suppress this button when working in French. Ptyxs (talk) 17:35, 10 March 2008 (UTC)

There is a configuration setting that allows you to do this:

monobook.js:

var wikEdFixPunctSpace = ' ';

Greasemonkey:

window.wikEdFixPunctSpace = ' ';

Сасусlе 01:35, 12 March 2008 (UTC)

Well, when I put this line in the customization section of my Greasemonkey wicked.user.js, wikED just stops working completely (its interface is no longer visible) Ptyxs (talk) 08:36, 14 March 2008 (UTC)

Sorry, see the corrections above. Сасусlе 02:46, 15 March 2008 (UTC)

OK, but this does not really solve the problem, as this button then converts something like bonjour, comment vas-tu? c'est moi: Jules into bonjour , comment vas-tu? c'est moi : Jules whereas the intended result should be bonjour, comment vas-tu ? c'est moi : Jules (errors: a space before comma and no space before question mark). For the time being it should be better, it seems to me, to completely inactivate or suppress the button (how?) when working on French data. Of course the best thing should be for the button to know that a space must be suppressed in French before some punctuation caracters and added before some other punctuation caracters. Ptyxs (talk) 06:59, 15 March 2008 (UTC)

Fixed in 0.9.62. Please add "window.wikEdFixPunctFrench = true;" to your customization settings (e.g. in your /monoook.js).Сасусlе 06:42, 6 April 2008 (UTC)

Fix Unicode

So far I believed that a "Unicode character representation" was an object like U+0061, representing LATIN SMALL LETTER A, but it doesn't seem the Fix Unicode button modifies in any way the string U+0061. So could you please explain what you mean by 'Fix Unicode character representation', is it possible to get an example? Thanks. Ptyxs (talk) 17:56, 10 March 2008 (UTC)

See User:Cacycle/wikEd_help#Fix_buttons. It converts &deg;, &#192;, or &#x0b0 into the actual character ° if there is IE6 support for it. Сасусlе 02:18, 11 March 2008 (UTC)

I have also fixed some bugs in 0.9.61g so that &#192; is now actually converted. Сасусlе 01:42, 12 March 2008 (UTC)

OK, anyway my browser is not IE6 but Firefox... Ptyxs (talk) 08:48, 14 March 2008 (UTC)

Romanian Wiked

I translated Wiked in Romanian (I started the translation some months ago but I finished it only now). I saved it at User:Roamataa/wikEd international ro.js. Please check if everything's ok and maybe you'll integrate it together with the other translations. If any other modification necessary, please let me know. --R O ^{A M A T A A} | msg  16:24, 12 March 2008 (UTC)

Hi Roamataa, thanks a lot! I have added the translation to the list. I have also made some minor updates (e.g. 'wikEdRef title' - please could you translate that). Сасусlе 02:28, 13 March 2008 (UTC)

Done. If any other modification needed in future, please let me a message on my talk page. --R O ^{A M A T A A} | msg  09:53, 13 March 2008 (UTC)

Macro for find / replace routines?

Hi. Is it possible to imbed macros for find / replace routines? E.g.

Find "xxyz" Replace with "xyz"
Find "wikipdeia" Replace with "wikipedia"
Find "- " Replace with "#"
etc. etc. all "jobs" are done one after the other by clicking 1 button. --Subfader (talk) 23:06, 14 March 2008 (UTC)

You can enable the button to fix common typos using AutoWikiBrowser RegExTypoFix rules and you can make your own rule page. For both settings see the top of the configuration setting list (User:Cacycle/wikEd_customization#Customization examples). Сасусlе 02:51, 15 March 2008 (UTC)

Thanks a lot bro --Subfader (talk) 14:48, 15 March 2008 (UTC)

Ah no... this is too much effort. I simply want to include a button (for all users) to replace some standard things. --Subfader (talk) 15:47, 16 March 2008 (UTC)

Greasemonkey script localisation

As far as I know the Greasemonkey script for wikED is downloadable from http://en.wikipedia.org/w/index.php?action=raw&ctype=text/javascript&title=User:Cacycle/wikEd.user.js But this is the english version (english help for the buttons). How is it possible to localise this script (I am specially interested in the French localisation) so that the help displayed for the buttons is in another language? Ptyxs (talk) 07:15, 15 March 2008 (UTC)

You have to paste the localization code to the top of the Greasemonkey script and replace "wikEdText = {" with "window.wikEdText = {". If you are interested, you could maintain a French language version on Wikipedia so that others can use this too. Сасусlе 00:35, 16 March 2008 (UTC)

Bug with Firefox 3 Beta 4

• wikEd version: 0.9.6.1i G(March 11, 2008)
• Browser id: Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4
• Console errors:
  Error: invalid range in character class
  File: http://en.wikipedia.org/w/index.php?title=MediaWiki:Gadget-wikEd.js&action=raw&ctype=text/javascript
  Row: 7089
• Browser add-ons: none
• User scripts on monobook.js: none
• Operating system: Windows XP SP2
• Description: "Loading error" (appearing on WikED logo) with many pages. The edit window remains blank.
• Steps to reproduce: edit a page containing a [[Category: ]] tag., i.e. http://en.wikipedia.org/w/index.php?title=Alaska_Democratic_caucuses%2C_2008&action=edit

With Firefox 3 Beta 4, installed with cleaned profile and application data folder. With Firefox 2 everything OK. --Subver (talk) 18:44, 15 March 2008 (UTC)

Please see above #Firefox 3 (dev release) and #Firefox 3b2 loading error. Also see the Mozilla bug report Сасусlе 16:09, 16 March 2008 (UTC)

Thanks, it seems now works with the last nightly. Another issue: it seems that only with Greasemonkey bundle, the signature button (standard bar)doesn't work when WikEd is enabled. --Subver (talk) 20:18, 25 March 2008 (UTC)

Cursor position from standard toolbar

I noticed that when you use a button from the standard toolbar, the cursor is placed at the end of the code, instead of the desired place. E.g.
'''|Bold text''' - clicking the Bold button in the standard toolbar with WikEd disabled
'''Bold text'''| - clicking the Bold button in the standard toolbar with WikEd enabled --Subfader (talk) 15:07, 16 March 2008 (UTC)

I have added text selection for sample text added by the standard toolbar buttons in wikEd 0.9.62g. wikEd actually improves the standard toolbar buttons by autoselecting the word under the cursor and I have kept the selection at the end for these. Сасусlе 04:26, 26 April 2008 (UTC)

Wikify

The wikify function replaces two empty rows by one. But I use 2 rows between text and the next heading (I disabled Editsection links) :/ Can you tell me a quick patch I could add on common.js? Thanks. --129.233.53.55 (talk) 11:53, 17 March 2008 (UTC)

More than one empty line is against Wikipedia style conventions and wiked therefore does not support that. Сасусlе 03:52, 4 April 2008 (UTC)

Redirects

Pray tell me, is there a specific reason why the redirect button creates an all-lowercase tag? The standard form which is seen in almost all redirects is uppercase ("#REDIRECT"), and "#redirect" looks pretty strange. I suppose I can adjust wikEd so that in my case the button produces an uppercase tag, but I just thought I'd ask (and I also find the inconsistency mildly annoying).

By the way, there's a typo on the main page, but I cannot fix it because the page is protected (it is the fourth word of the "How to use it" section). How you expect us to write a favourable review of wikEd on a protected page, only She knows. :-) Waltham, The Duke of 14:41, 18 March 2008 (UTC)

There is no reason for the redirect tag to be uppercase and I prefer the lowercase version :-) Сасусlе 20:25, 18 March 2008 (UTC)

There is no technical reason, true, but it is overwhelmingly common usage, and I prefer standardisation. Anyway, thanks.

PS: You still haven't corrected the typo. :-) Waltham, The Duke of 02:21, 19 March 2008 (UTC)

Fixed in 0.9.62. Сасусlе 06:39, 6 April 2008 (UTC)

Text selection with wikEd

Hi, I am developing a user script which suggests fixing some formatting issues while editing. I'd like to make it compatible with wikEd when it is enabled, so I need a way to mark wikitext between two given offsets. Can you recommend a solution? --Cameltrader (talk) 08:43, 25 March 2008 (UTC)

It is possible, but I have to dive into the code to tell you how exactly. I will do that tonight or tomorrow. Сасусlе 13:29, 25 March 2008 (UTC)

I am in no hurry, I usually do the coding during the weekends. Thanks very much. --Cameltrader (talk) 14:32, 25 March 2008 (UTC)

Hi Сасусlе, I looked at User:Cacycle/wikEd#Making scripts compatible with wikEd, and while I'm not good with JS objects and prototyping, maybe it could be possible to make wikEd transparent to other editing scripts, by pretending that your iframe is wpTextbox1, and redefining most setters and getters, like wpTextbox1.value= and so on? —AlexSm 15:25, 25 March 2008 (UTC)

Unfortunately, this wouldn't work in IE. --Cameltrader (talk) 15:43, 25 March 2008 (UTC)

Just checking, do you already have a clue about my initial question? --Cameltrader (talk) 10:26, 30 March 2008 (UTC)

Sorry, I am quite busy (and I think I had anwered that, might got lost somehow...). This is the way to go: run WikEdParseDOM(obj, wikEdFrameBody); on an empty object. After that, obj.plain contains the plain text, obj.plainNode contains the text node refs, obj.plainStart contains the plainNode start text positions. Then do something similar to the cosde starting with line 4992 ("// select the find") to set a range and select the text. It can now be changed similar to line 4645 ("// replace the selection with changed text"). That way your changes would end up in the edit (undo/redo) history. If you bypass the browser's rich text editor interface and change the edit frame directly, you will erase the edit (undo/redo) history. In general, automatic changes could interfere with user actions (especially when slow - and the method above is relatively slow). Generally I do not like it if my text gets changed without me knowing it... Сасусlе 03:49, 4 April 2008 (UTC)

See also above under User_talk:Cacycle/wikEd#wikEd_and_my_user_JavaScript. Сасусlе 04:13, 6 April 2008 (UTC)

Also, in order to add the changes, you have to move the focus/cursor and reset it after the addition. This might interfere with user input. Сасусlе 01:01, 7 April 2008 (UTC)

null dereference in wikEdDiff.js

The linkification step in wikEdDiff.js leads to null dereferences under some circumstances.

• wikEd version: 0.9.61i
• wikEdDiff version: 0.9.4h
• Mediawiki 1.7
• affected browsers: Internet Explorer
• error message: Line 512, column 4, wikEdDiffWikiGlobals.wgArticlePath is null or not an object.
• fix: add a null check around the block of line 504-513:
  • if ((wikEdDiffWikiGlobals['wgServer'] != null) && (wikEdDiffWikiGlobals['wgArticlePath'] != null)) {
  • ...
  • }
• other details: So far I have only experienced this for one page in our wiki, so I think the real problem is located somewhere else in the code. But with this workaround at least you get the diff output, instead of some lines containing only "undefined". —Preceding unsigned comment added by 213.68.15.100 (talk) 13:23, 25 March 2008 (UTC)

Thanks. Please could you give me a link to reproduce that error. Сасусlе 13:30, 25 March 2008 (UTC)

Added to wikEdDiff 0.9.5a. Сасусlе 01:22, 7 April 2008 (UTC)

Local Installation Problem

I tried installing wikEd on a local intranet wiki without Internet connection. I followed the instructions but could not get it to work, it does not show up at all. Looking at the page source, I find something like this (when installed using the user's monobook.js): <head>...<script type="text/javascript" src="/mediawiki/index.php?title=User:Ah/monobook.js&amp;action=raw&amp;ctype=text/javascript&amp;dontcountme=s"></script> </head>

Where do these escaped ampersands come from? If I enter the URL manually in the browser without them, the script shows up correctly. When installed via Mediawiki:Common.js, nothing shows up in the page source at all. I have set both $wgUseSiteJs and $wgAllowUserJs to true. I am using Debian Etch and mediawiki 1.7 (from the etch package), with only an LDAP-Auth-Extension installed. Browser is Mozilla Firefox 2.0.0.12/Windows. --Andreas DE (talk) 09:45, 26 March 2008 (UTC)

The code from the source is correct, the same amp's show up for Wikipedia. Have you checked for error messages in your browser's error console? Сасусlе 04:08, 27 March 2008 (UTC)

Firefox' error console shows "Invalid range in character class" two times for each page, but without any further hints where the error occurs. --Andreas DE (talk) 09:08, 31 March 2008 (UTC)

That was an error with earlier Firefox 3.0 beta versions and has been fixed since, so try it with a newer or older browser version. Сасусlе 03:02, 4 April 2008 (UTC)

I have the same "Invalid range in character class" error, once for each loaded page on a local install, using Firefox 2.0.0.14/Windows. 21:30, 9 May 2008 (EEST) —Preceding unsigned comment added by 193.138.194.29 (talk)

Internet explorer alternative

What a great tool. Is there an alternative tool for Internet Explorer? Some of my coworkers still have not made the switch. Also, is there a way to install the (German) translation sitewide on our internal wiki? --Liface (talk) 13:02, 27 March 2008 (UTC)

1. There is no alternative for wikEd on IE :-) There is work in progress to make wikEd IE compatible, see wikEd dev, but the most difficult part is still ahead of us. Maybe the upcoming versions of IE will support standards... Сасусlе 16:37, 27 March 2008 (UTC)
2. Just paste the translation installation code above the wikEd installation code. Сасусlе 16:32, 27 March 2008 (UTC)

WikEd_case - Toggle

This function has a little bugs

• Ampersands: & becomes &Amp; which is displayed as such "&Amp;" on the page after saving :/
• whith apostrophes:
  

YOU CAN'T DO >> you can't do >> You Can'T Do
Would be good if the standards would be considered like won't don't couldn't can't or all genetives:
CASE'S BUG >> case's bug >> Case'S Bug
Maybe via Find all ('t ) or ('s )? --Subfader (talk) 10:37, 2 April 2008 (UTC)

I will fix that with the next release. Thanks, Сасусlе 03:00, 4 April 2008 (UTC)

Fixed in 0.9.62. Сасусlе 06:38, 6 April 2008 (UTC)

Works for ' but still buggy when it's european(?) ´ or ` --77.135.30.91 (talk) 16:21, 25 May 2008 (UTC)

I will add the "’" apostrophes. Are there actually words containing grave accent and acute accent? Cacycle (talk) 01:13, 26 May 2008 (UTC)

Can't tell, but I copy-paste text a lot from other websites and those are often used instead of '. Note that ’ is used often as well. --Subfader (talk) 06:56, 28 May 2008 (UTC)

On variables defaulting to true

// exclude identical sequence starts and endings from change marking
window.wDiffWordDiff = window.wDiffWordDiff || true;

// enable recursive diff to resolve problematic sequences
window.wDiffRecursiveDiff = window.wDiffRecursiveDiff || true;

// enable block move display
window.wDiffShowBlockMoves = window.wDiffShowBlockMoves || true;

Do you see the problem in the logic here? --Random832 (contribs) 16:33, 3 April 2008 (UTC)

Sure - which dimwit did code that? Сасусlе 02:40, 4 April 2008 (UTC)

Fixed in 0.9.62 / 0.9.5 / 0.9.5. Сасусlе 06:37, 6 April 2008 (UTC)

Slow

I've had this in my monobook.js for a long time now, but only use it rarely because of the slowdown it causes.

1. Is there a way to make it default to "off"? Whenever I log into Wikipedia on another computer, it defaults to on and 99% of the time I have to click the button to turn it off.
2. Does it run faster if installed as a Gadget or Greasemonkey script? — Omegatron 01:05, 4 April 2008 (UTC)

1. var wikEdDisabledPreset = true; disables wikEd completely (top logo click). If you just want to disable the time consuming syntax highlighting try the same with wikEdHighlightSyntaxPreset ( button) or wikEdUseWikEdPreset ( button)
2. That should not make any difference. Time consuming steps on long articles are syntax highlighting, whole text edit buttons, and regexp searches. Turning off syntax highlighting should do the trick in most cases.

Сасусlе 02:59, 4 April 2008 (UTC)

wikiEd toggles browser crash because of the Unicode character ranges

This may be similar (or identical to User_talk:Cacycle/wikEd#Swiftfox_broken). I couldn't find your bugzilla report.

This expression:

p2.match(/^\s*(([\w À-ÖØ-öø-\u0220\u0222-\u0233ΆΈΉΊΌΎΏΑ-ΡΣ-ώ\u0400-\u0481\u048a-\u04ce\u04d0-\u04f5\u04f8\u04f9\-]*\s*:)*)\s*([^\|]+)/);

triggers an assertion in the debug build of Mozilla-base browsers (I am using seamonkey).

There is something wrong with the ordering of the Unicode codepoints in the character range.

I have prepared a simplified testcase demonstrating what's wrong.

I am using a debug build - that means normal users should not experience the crash. But those expressions may not work as wanted anyway.

Since the crash is really a Mozilla bug, I have filed it on the bugzilla.

// version info
window.wikEdProgramVersion = window.wikEdProgramVersion || '0.9.61i';
window.wikEdProgramDate    = window.wikEdProgramDate    || 'March 11, 2008';

All other details are in the Bugzilla.

Maybe re-ordering characters in regular expressions will help?

 « Saper // @talk »  16:31, 5 April 2008 (UTC)

The bug I had filed is already fixed (at least for Firefox), see https://bugzilla.mozilla.org/show_bug.cgi?id=416933. Сасусlе 20:28, 5 April 2008 (UTC)

Spanish Wikipedia

Hi,

Can i use this Script on the Spanish Wikipedia. If i cant i offer u my help for making work it on Wiki_Es.

Greetings. —Preceding unsigned comment added by Ssthormess (talk • contribs) 00:22, 6 April 2008 (UTC)

Yes, see User:Cacycle/wikEd#Complete_version for the wikEd installation and User:Cacycle/wikEd_international for how to create and install a translation. Your help in creating a still missing Spanish translation would be greatly appreciated. Сасусlе 03:05, 6 April 2008 (UTC)

Bug 6 Apr 2008

My Firefox Firebug says that "wikEdNoRearrange is not defined" for the expression if (wikiEdNoRearrange != false) {. Please review your last correction of code. Thank you. Vinhtantran (talk) 06:16, 6 April 2008 (UTC)

It seems that you didn't initiate this variable in your code. I initiated it in my js and it works now. You should do it if you don't want everyone to DIY. Vinhtantran (talk) 06:24, 6 April 2008 (UTC)

It is already fixed, please shift-reload to update. Thanks, Сасусlе 06:35, 6 April 2008 (UTC)

Custom table button

Hey, i love this userscript and i'm using it all the time (personal wiki). I'm even so far that i'm making a custom button: add custom table. When clicked a div pops-up to select how many cells a new table must be when inserted. All works except for the last step, putting the code into the frame. I only want the new table inserted at the cursor position so i used the following code at my last function:

    WikEdGetText(obj, 'cursor');
    console.log(obj.changed);
    obj.changed = obj.cursor;
    obj.changed.plain = "hoi";

Where "hoi" is changed in the new code. The problem is only that the obj isn't available anymore. Can you give me an example on how to use this when another function is called by the first function. Jeronevw (talk) 13:48, 6 April 2008 (UTC)

The obj in the anonymous functions of the event handlers seem to be local. You should do the whole wikEd frame handling in the same function. The rich text editor of Firefox/Mozilla already has actually a table editor, just paste a html table and you can insert/delete ros and columns, I am actually working on utilizing this build-in functionality for wikEd. Сасусlе 17:49, 6 April 2008 (UTC)

I was a freed that you were going to say that; one function. Well theres nothing to do about it then adjusting it.
I put my script online so you could check how it's suppose to work: [1] and the code atm: here. It's just a matter of time for me to get it also to work for WikEd.
ps: the online page works in FF2, IE7 and Opera9. Jeronevw (talk) 19:01, 6 April 2008 (UTC)

Maybe you want to help me with this code, because i personally want it finished. ATM i get the range/selection of the text, but i can't do the last part; putting the new text into the page. Even in Firebug console i see the 'range' with the new text, but it isn't displayed on the page. The current code i have now can you find here: Jeronevw (talk) 10:55, 7 April 2008 (UTC)

Follow the example under User:Cacycle/wikEd_customization#Custom buttons, that should definitely work. Сасусlе 12:49, 7 April 2008 (UTC)

Just to let you know i solved it: User:Jeronevw/wiked addon. The code isn't clean yet, but it does its job. Jeronevw (talk) 14:46, 7 April 2008 (UTC)

Ok, cleaned up code and made it multilangual (2 words). Got only one bug to fix: page gets selected when image is clicked. And need to add one feature: selected lines should be added into table. Jeronevw (talk) 21:43, 7 April 2008 (UTC)

Spanish translation

Hi, I've made a spanish translation. You can find it in http://es.wikipedia.org/wiki/Usuario:Krusher/wikEd_international_es.js --es:Ususario:Krusher —Preceding unsigned comment added by 217.125.73.234 (talk) 10:02, 9 April 2008 (UTC)

Thank you very much! Please could you register an username at the English Wikipedia and create the translation page as described under User:Cacycle/wikEd_international#Translation_guide so that both you and I can make changes and updates. Thanks in advance, Сасусlе 04:48, 11 April 2008 (UTC)

Done. You can find it on User:Axelei/wikEd_international_es.js. (User Krusher was taken on English wikipedia) --Axelei (talk) 13:19, 13 April 2008 (UTC)

It's not on my Gadgets selection anymore..

It's disappeared from my preferences section.

Not sure where to look for information about this..

Thanks, Drum guy (talk) 22:01, 9 April 2008 (UTC)

I'm curious about this, too. Was it removed because some problems were found with it? Maybe compatibility issues with some browsers? Gary King (talk) 22:15, 9 April 2008 (UTC)

Why, it seems to have vanished altogether! The toolbars, the mark-up, the small window... The entire tool is gone. Where is the manager, or a legal representative thereof? I wish to speak to a person of authority. Waltham, The Duke of 23:25, 9 April 2008 (UTC)

It has just returned. What has happened? We may never know... Waltham, The Duke of 05:21, 10 April 2008 (UTC)

Yeah, it's back for me too. I guess this is just one of the times we realise we're just at the receiving end of every whim of the Wikipedia Cabal. Thanks, Drum guy (talk) 14:23, 10 April 2008 (UTC)

See Wikipedia talk:Gadget#wikEd no longer available as a gadget? for an explanation (kind of...). Сасусlе 00:36, 11 April 2008 (UTC)

Page Caching

OK, I admin over at [lyricwiki.org] and I need some help with modifying wikEd to return the native editor's page caching. What I mean, is that with the native, I can type some lines, hit the back button, and then forward, and the page is as it was, just before hitting 'back'. WikEd right now will revert the same page to the first time I loaded the page. Thanks so much.
King_Nee1114 (talk page • contributions • deletions) 19:59, 15 April 2008 (UTC) / lyricwiki user page

PS One other thing since I am here. It would also be nice to be able to output the page title at the top. ie: Editing Modest Mouse —Preceding unsigned comment added by Kingnee1114 (talk • contribs) 20:13, 15 April 2008 (UTC)

This is a known and highly annoying Firefox bug that has been filed for a while now, check https://bugzilla.mozilla.org/show_bug.cgi?id=416751. Сасусlе 03:13, 16 April 2008 (UTC)

Thanks. With that mozilla bug, it looks like it's out of your hands.

King_Nee1114 (talk page • contributions • deletions) 14:47, 16 April 2008 (UTC)

HTML to Wiki converter

I would like to recreate the wikicode for http://en.wikipedia.org/wiki/Special:SpecialPages.

In Firefox, I used Ctrl+U to see the page source.

Then I copied and pasted the page source into WikEd and clicked on [W].

It didn't work. All the content was still in HTML, and all the links were broken. The pipe characters were all missing, and there's an extra string of text between the page name and the piped text in each link.

I posted a message on WP:VPT asking for the location of the wikitext for that page, and someone told me it was hardwired into the software. That's when I resorted to the page source and trying to convert it.

I've been looking for a converter that can handle this, (yours is the 4th I've tried), but I still haven't found one.

The Transhumanist 22:26, 16 April 2008 (UTC)

It works for me. You have to copy and paste the content from the actual page, not the html code. Сасусlе 03:22, 17 April 2008 (UTC)

The wikicode fragments for that page can be found on Special:AllMessages if you search for the respective text. Сасусlе 03:27, 17 April 2008 (UTC)

Dutch translation and /!\ custom button bug

Hey, still love this script, so I've made a Dutch (nl-NL / Nederlands) translation.

Also I'm very busy creating my own custom buttons, but I found a bug when using obj.cursor, while I don't add anything, e.g. obj.changed.plain=""; or obj.changed.plain=obj.changed.plain;. What happens is that where the cursor stands wikEd removes one character to the left (backspace). || Jeronevw (talk) 13:32, 17 April 2008 (UTC). ps. I'm working on a custom button for font- and background-color; almost finished.

We should create a page for custom buttons! Thanks for the translation, I will put it on the translations page. Сасусlе 02:52, 18 April 2008 (UTC)

If you do so, i will add mine custom buttons. I'm very familiar with Userscripts, so I'm still making new ones.
You've found a solution for my bug? || Jeronevw (talk) 13:50, 18 April 2008 (UTC)

Sorry, I had no time yet to check for the problem, I will do it next week :-) Сасусlе 23:23, 18 April 2008 (UTC)

Fixed in the upcoming version. Сасусlе 03:10, 19 April 2008 (UTC)

Fixed in 0.9.62g Сасусlе 04:26, 26 April 2008 (UTC)

Translation suggestion

Hi, I love this script and I use it a lot on Chinese version of wikipedia.

For most of times I ported articles from English to Chinese, the problem I always hit is there are numbers of article titles which have been translated previously (e.g. en:Isaac Newton = zh:艾萨克·牛顿; en:Cathode ray tube = zh:陰極射線管) by someones, and I have to copy the terminology in English, search an English version wikipedia, click the Chinese version wikipedia link on the left hand side, and copy down the title. Just wonder if there is any way I could make wikEd suggest it (e.g. like google suggest by press down-arrow key) or where I should start to look up in your script.

Thanks a lot. --Zanhsieh (talk) 18:07, 18 April 2008 (UTC)

Sorry, I do not yet understand what the requested function would suggest - the interlanguage links are already on the page. Сасусlе 01:01, 19 April 2008 (UTC)

Sorry for confusion. Let me provide a live example: zh:電子遊戲歷史; click HERE to edit. You would see university, mainframe computer, and MIT cannot be indexed in zh.wikipedia.org, but they will be indexed properly in en.wikipedia.org. In order to finish the word university translation, I have to go to en.wikipedia.org/wiki/university, check the link zh.wikipedia.org/wiki/%E5%A4%A7%E5%AD%B8, and copy down %E5%A4%A7%E5%AD%B8 (which is 大學) and paste back to the article I just edited. The function I suggest is, if wikEd could make each terminology-has-not-been-translated having a "cross-language wiki translation recommandation" (in this case: university -> 大學), that would be wonderful. Thanks a lot --Zanhsieh (talk) 16:51, 19 April 2008 (UTC)

I think I understand. While this would be beyond the scope of wikEd, it would be something that could be added to Wikipedia:Tools/Navigation_popups (if it is not already been implemented there). Сасусlе 02:00, 22 April 2008 (UTC)

Case Toggle stucks when &

As soon as the (marked) text (not only one word) has and ampersand the toggle function stucks on UPPER CASE. Example:
abc & def [toggle] ABC & DEF [toggle] ABC & DEF while it should be
abc & def [toggle] ABC & DEF [toggle] Abc & Def

And the &Amp; bug descibed here is still active. Maybe also try copy-pasting text with & from somewhere into the edit field and then toggle. --Subfader (talk) 21:37, 11 May 2008 (UTC)

It works fine for me, what version are you using (hover over the logo on top of the page) and which browser. Cacycle 22:31, 11 May 2008 (UTC)

wikEd 0.9.62g | Firefox 2.0.0.14 --Subfader

It works for me using wikEd 0.9.62g as a gadget (G) under Firefox 2.0.0.14. Cacycle 03:51, 12 May 2008 (UTC)

Hmh, I use it as gadget, copied the Gadget-wikEd.js into my wiki. --Subfader (talk) 08:20, 14 May 2008 (UTC)

Question

I'm doing disambiguation page cleanup, and I've probably removed about 25,000 brackets so far because editors want to blue link half the words on the page. Instead of my having to delete all those brackets one by one, I'd like something which would let me pull a bunch of brackets out all at once. Usually the first word or phrase in a sentence should stay blue linked, the rest of the links should go. Would your editor (or any other scripts you know of) be useful for this? I can't just pull all the brackets from the page, or even all from a sentence, ideally I'd like to be able to highlight a bunch of text and have all those brackets be removed. --Xyzzyplugh (talk) 18:15, 12 May 2008 (UTC)

That's easy: click for regular expression search and replace, put \[\[|\]\] in the find field, and leave the replace field empty. Select the text and push the button to delete all double brackets from your selection. In addition, you could enable the AutoWikiBrowser RegExTypoFix button (see User:Cacycle/wikEd_customization) and create your own set of words that should never be linked to. Cacycle 20:43, 12 May 2008 (UTC)

Thanks! This should making removing the next 25,000 brackets much easier. --Xyzzyplugh (talk) 10:09, 13 May 2008 (UTC)

Hi, I have a request for assistance. If I set the text size to be larger than normal, then the find and replace box, which you mentioned above, does not display properly. See [2]. Is there any way to fix this? --Xyzzyplugh (talk) 18:04, 13 May 2008 (UTC)

Unfortunately, there is no easy fix for this (although somebody with a lot of time at his hand could probably develop a hack. If you use the button you can increase the editing text size while keeping the user interface intact. Cacycle 01:01, 14 May 2008 (UTC)

Maybe try Extension:Replace Text? --Subfader (talk) 08:18, 14 May 2008 (UTC)

Bug-Edit tools don't work with wikEd

Hi,I'm a Wikia user from Wikia.com.I use your editor,which is very cool and works great,but I've found out that you can't use the edit tools (the box of codes below the "save changes",etc.,buttons) with your edit.When you try to click on one of the characters,it simply scrolls to the top of the page,not inserting anything.There are import codes that I need to use on Wikia that are in there,so how can I fix it so it works?Please help!

Oracle Techie (A.K.A. The Oracle23 on Wikia) 03:20, 17 May 2008 (UTC)

This happens only if you use wikEd under GreaseMonkey (it is actually a GreaseMonkey security feature). Try is as a gadget (if available) or install it as a user script on your monobook.js (or whatever you use on Wikia) page. Cacycle (talk) 04:37, 17 May 2008 (UTC)

Firefox 3.0b5 + MW 1.12 Does not work

• I have wasted an entire day trying to get this to work on my Mediawiki install.
• I have tried every possible method listed (Gadget, Complete, Greasemonkey) - NONE Are Working
• Yet the Greasemonkey method does work here (meaning I can see it while writing this bug report)

• Mozilla/5.0 (MAC OS X; U; MAC OS X 10.5.1; it; rv:1.9b5) Gecko/2008030714 Firefox/3.0b5
• WikEd (Latest version available)
• Does not work means, I do not see the WikEd logo, I do not see the Toolbar in Edit, I do not see any sort of error in the Error Console

• Have I discovered the ultimate stealthy bug? —Preceding unsigned comment added by Oldr4ver (talk • contribs) 23:21, 16 May 2008 (UTC)

Did you check your MediaWiki settings to allow user scripts as described on User:Cacycle/wikEd_installation? Which skin are you using? Please could you give me or email me a link to your installation. Cacycle (talk) 04:35, 17 May 2008 (UTC)

Another question

wikiEd is working great for me so far, it's extremely useful in the disambiguation page cleanup I'm doing. However, I find myself using the Replace All Matches button about 500 times per day (not an exaggeration), and i'm wondering if there is some way to map this button to a key. --Xyzzyplugh (talk) 19:06, 18 May 2008 (UTC)

Add the following to your monobook.js page:

// define wikEd accesskeys for edit buttons (wikEd button number: key string, JS key code)
var wikEdButtonKey = {
  46: ['a', 65] // shift-alt-a: replace all button shortcut
}

Cacycle (talk) 01:18, 19 May 2008 (UTC)

Thanks again. shift-alt-a is fairly awkward, but I figured out how to make a simple autohotkey script to turn F12 into shift-alt-a, so that simplifies things greatly. I'm not sure if this is the easiest way to get it down to one keypress, but it works! --Xyzzyplugh (talk) 08:58, 19 May 2008 (UTC)

Improvements for Find / Replace

Useless and bugging me:

• When you enter " Text" into the find field the blank is removed to "Text". Automation is good but this just annoying cos I always have to enter it again.

Will check this, it is not intentionally. Cacycle (talk) 19:07, 25 May 2008 (UTC)

• It always marks the first find but I use this function to replace all, that always requeires a click in the field to unmark it. It might be good for the find function though but ugly when you want to replace all cos the WikEd_replace_all button is not working then (maybe overrun?).

Since I always experience both per one action it takes me double work to simply replace text. --Subfader 16:01, 25 May 2008 (UTC)

The reason is that Replace all works only on the selected text. The text gets selected because you have the Find ahead as you type button pushed (). Add "window.wikEdFindAheadSelected = false;" to your monobook.js page to disable the find-ahead preset. Cacycle (talk) 19:07, 25 May 2008 (UTC)

Fix search link

{{editprotected}} The line "The following search link gives you an idea which users of the English Wikipedia are using wikEd: Search Wikipedia" link does not work, and should be removed. ffm 19:58, 2 June 2008 (UTC)

The link works fine for me... Cacycle (talk) 01:07, 3 June 2008 (UTC)

invalid range in character class

This seems similar the bug discussed in User_talk:Cacycle/wikEd#Swiftfox_broken but not identical, nor do those fixes solve the problem.

• Your wikEd version: 0.9.62g (local installation since this is on a corporate intranet)
• Your browser id: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
• Error console errors': Error: invalid range in character class
  • There are no additional details, like which class or which line. There is simply the one line with the error.
• Which browser add-ons have you installed: none at this point
• Which user scripts have you installed on your monobook.js page: none at this point
• Which operating system do you use: Windows XP SP2 32-bit
• Description of Problem:
  • I don't see any logos or links for editing, and the JS error appears.
  • I tried the swiftfox workaround for editing the regexp range but that didn't fix anything.
  • Help! :)

---

--Gneveu (talk) 14:04, 5 June 2008 (UTC)

How do you exactly load wikEd? Did you lose the UTF-8 formatting while pasting the code (i.e. do you see the heart in the code header)? Cacycle (talk) 20:59, 5 June 2008 (UTC)

I can reproduce your error report when I save the code as ANSI/ASCII and not as UTF-8. Use a UTF-8-capable text editor when you paste the code to your wiki and specify UTF-8 as your file format when you save your text file. Check the pasted code on your wiki for the the following line in the header text:

The code has to be saved as UTF-8 in your editor to preserve Unicode characters like ♥ (heart)

Cacycle (talk) 23:08, 5 June 2008 (UTC)

Ugg, I think I copy-pasted it into notepad which would explain the loss... I'm a fool. I will check right away and post back if that fixes things. Thanks for the very quick reply!

--Gneveu (talk) 11:35, 6 June 2008 (UTC)

That worked, it was the UTF-8 issue as you observed. Thanks again! Love wikEd already!!!

--Gneveu (talk) 11:41, 6 June 2008 (UTC)

blank pages follwing text editing / bug in an extension! Hook wfWikiwygToggle failed

Hi, couple days ago I installed wikEd (updated with latest version 0.9.61f) in the following way: 1. monobook (webbased via Userprofile of English Wikipedia on 6th Feb 2008, no other changes yet I did in the monobook, wikeEd is the only change I did) 2. Installation of Greasemonkey (in the latest Firefox version 2.0.0.12) plus code in the localsettings and installation of the extension of my own MediaWiki (Version 1.11 of Jan2008).

It seems to work during a couple of days, the tool appeared on every wiki site at wikipedia (wikinews, german Wikipedia, English Wikipedia, other wikipedias based on MediaWiki). It was comfortable to set the codes that way. Now unexpected some problems appeared. I loose text and a bug error message appears (on my own MediaWiki where I installed the extension.) On other MediaWikis I loose text within the editing process same. Please have a look on my posting at the MediaWiki Forum. There I describe all details (But yet didn't get any response from MW). Would thank you for your quick advice how to proceed --ElJay Arem (talk) 23:02, 14 February 2008 (UTC) (Meanwhile I have set the extension code in the localsettings on passive (#). The problem of lost text and white blank site still exists.)

Please see my reply on mw:Extension_talk:Wikiwyg. Сасусlе 02:29, 15 February 2008 (UTC)

Highlighting bug?

I've just been editing Gliding#Badges, & found that some of the text is highlighted & greyed-out as if it were a continuation of a <ref>. Is this a bug? --NigelG (or Ndsg) | Talk 11:09, 15 February 2008 (UTC)

The line in question is highlighted as a line starting with a space. It is a weakness of the regular expression-based highlighting approach that is used because real MediaWiki code parsing would be too complicated. I guess we have to live with that... Сасусlе 05:57, 16 February 2008 (UTC)

OK, thanks for the reply. I thought it might be something like that. --NigelG (or Ndsg) | Talk 20:24, 16 February 2008 (UTC)