![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
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. - Ste vertigo 19:25, 11 August 2007 (UTC)
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)
// 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(/ /g, ' ');
objBefore.plain = objBefore.plain.replace(/</g, '<');
objBefore.plain = objBefore.plain.replace(/>/g, '>');
objBefore.plain = objBefore.plain.replace(/&/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;
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)
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)
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)
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. -- Thin boy 00 @921, i.e. 21:06, 15 December 2007 (UTC)
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)
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)
This is a relisting of my previous bug, with much more info:
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. -- Thin boy 00 @149, i.e. 02:34, 20 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. -- Thin boy 00 @200, i.e. 03:47, 10 January 2008 (UTC)
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)
var regExp = new RegExp('\\s*[\\w\\- \\u0401-\\u0481\\u0490-\\u04cc\\u04d0-\\u04f5\\u04f8\\u04f9]+\\s*:\\s*' + wikEdText['wikicode Category'] + '\\s*:', 'i');
Ø-ö
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)
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)
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
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)
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)
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)
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)
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)
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)
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)
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)
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)
Tremendous effort Cacycle. Keep up the good work. Riddell ☎ 16:35, 3 February 2008 (UTC)
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)
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.
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)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)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)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)wikEdSetup()
has been called. --
de:Jowereit, 21:50, 6 February 2008 (UTC)WikEdFrameExecCommand('inserthtml', string);
to insert the character, see
http://developer.mozilla.org/en/docs/Midas.
Сасусlе
21:09, 6 February 2008 (UTC)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)
(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)
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)
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)
I've finsched the sicilian translation for Wiked. -- Meloscn ( talk) 21:16, 7 February 2008 (UTC)
Hi, I would like wikiEd to be supported by Internet Explorer, particularly Internet Explorer 7-- Troop350 ( talk) 20:50, 7 February 2008 (UTC)
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)
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)
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)
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)
var wikEdUseWikEdPreset = false;
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):
-- ParaDox ( talk) 14:37, 20 February 2008 (UTC) ( de:User:ParaDox)
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)
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)
var wikEdScrollToEdit = false;
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)
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)
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)
(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)
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)
There is a new skin that can be selected, "Modern". Does wikEd work with it? ff m 16:30, 10 March 2008 (UTC)
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)
monobook.js:
var wikEdFixPunctSpace = ' ';
Greasemonkey:
window.wikEdFixPunctSpace = ' ';
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)
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. 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)
As far as I know the Greasemonkey script for wikED is downloadable from http://en.wikipedia.org/?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)
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)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)
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)
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)
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)
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)
Just checking, do you already have a clue about my initial question? -- Cameltrader ( talk) 10:26, 30 March 2008 (UTC)
The linkification step in wikEdDiff.js leads to null dereferences under some circumstances.
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&action=raw&ctype=text/javascript&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)
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)
This function has a little bugs
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)
// 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)
I've had this in my monobook.js for a long time now, but only use it rarely because of the slowdown it causes.
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
(
wikEdUseWikEdPreset
(
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)
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)
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)
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)
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)
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)
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
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)
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.
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)
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)
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)
\[\[|\]\]
in the find field, and leave the replace field empty. Select the text and push the
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)
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)
// 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 }
Useless and bugging me:
Since I always experience both per one action it takes me double work to simply replace text. -- Subfader 16:01, 25 May 2008 (UTC)
{{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. ff m 19:58, 2 June 2008 (UTC)
This seems similar the bug discussed in User_talk:Cacycle/wikEd#Swiftfox_broken but not identical, nor do those fixes solve the problem.
-- Gneveu ( talk) 14:04, 5 June 2008 (UTC)
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.)
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)
![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
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. - Ste vertigo 19:25, 11 August 2007 (UTC)
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)
// 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(/ /g, ' ');
objBefore.plain = objBefore.plain.replace(/</g, '<');
objBefore.plain = objBefore.plain.replace(/>/g, '>');
objBefore.plain = objBefore.plain.replace(/&/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;
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)
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)
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)
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. -- Thin boy 00 @921, i.e. 21:06, 15 December 2007 (UTC)
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)
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)
This is a relisting of my previous bug, with much more info:
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. -- Thin boy 00 @149, i.e. 02:34, 20 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. -- Thin boy 00 @200, i.e. 03:47, 10 January 2008 (UTC)
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)
var regExp = new RegExp('\\s*[\\w\\- \\u0401-\\u0481\\u0490-\\u04cc\\u04d0-\\u04f5\\u04f8\\u04f9]+\\s*:\\s*' + wikEdText['wikicode Category'] + '\\s*:', 'i');
Ø-ö
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)
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)
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
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)
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)
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)
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)
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)
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)
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)
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)
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)
Tremendous effort Cacycle. Keep up the good work. Riddell ☎ 16:35, 3 February 2008 (UTC)
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)
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.
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)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)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)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)wikEdSetup()
has been called. --
de:Jowereit, 21:50, 6 February 2008 (UTC)WikEdFrameExecCommand('inserthtml', string);
to insert the character, see
http://developer.mozilla.org/en/docs/Midas.
Сасусlе
21:09, 6 February 2008 (UTC)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)
(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)
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)
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)
I've finsched the sicilian translation for Wiked. -- Meloscn ( talk) 21:16, 7 February 2008 (UTC)
Hi, I would like wikiEd to be supported by Internet Explorer, particularly Internet Explorer 7-- Troop350 ( talk) 20:50, 7 February 2008 (UTC)
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)
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)
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)
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)
var wikEdUseWikEdPreset = false;
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):
-- ParaDox ( talk) 14:37, 20 February 2008 (UTC) ( de:User:ParaDox)
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)
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)
var wikEdScrollToEdit = false;
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)
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)
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)
(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)
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)
There is a new skin that can be selected, "Modern". Does wikEd work with it? ff m 16:30, 10 March 2008 (UTC)
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)
monobook.js:
var wikEdFixPunctSpace = ' ';
Greasemonkey:
window.wikEdFixPunctSpace = ' ';
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)
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. 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)
As far as I know the Greasemonkey script for wikED is downloadable from http://en.wikipedia.org/?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)
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)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)
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)
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)
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)
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)
Just checking, do you already have a clue about my initial question? -- Cameltrader ( talk) 10:26, 30 March 2008 (UTC)
The linkification step in wikEdDiff.js leads to null dereferences under some circumstances.
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&action=raw&ctype=text/javascript&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)
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)
This function has a little bugs
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)
// 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)
I've had this in my monobook.js for a long time now, but only use it rarely because of the slowdown it causes.
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
(
wikEdUseWikEdPreset
(
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)
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)
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)
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)
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)
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)
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
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)
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.
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)
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)
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)
\[\[|\]\]
in the find field, and leave the replace field empty. Select the text and push the
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)
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)
// 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 }
Useless and bugging me:
Since I always experience both per one action it takes me double work to simply replace text. -- Subfader 16:01, 25 May 2008 (UTC)
{{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. ff m 19:58, 2 June 2008 (UTC)
This seems similar the bug discussed in User_talk:Cacycle/wikEd#Swiftfox_broken but not identical, nor do those fixes solve the problem.
-- Gneveu ( talk) 14:04, 5 June 2008 (UTC)
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.)
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)