User talk:Cacycle/wikEd/Archive 006

Has anyone worked on this? I'm going to start but don't want to redo someone else's work. Ericmock 16:37, 30 August 2007 (UTC)

:: Sorry, I have missed your post (they are usually added at the bottom). It does not sound as if somebody is working on it, but I have no idea what you mean. wikEd is user-side browser-executed JavaScript, PHP is a server-side scripting language. Cacycle 14:09, 19 September 2007 (UTC)

Hi Cacycle, you've got a really cool tool here. I am trying to paste a numbered list from Microsoft Word 2002 and the "Wikify pasted content" button does not work for numbered lists. Instead, it converts it to a plain text numbered list with an extra line between every item. Is that enough information? It'd be great if you could fix that... thanks! ~MDD4696 18:50, 13 February 2007 (UTC)

:It only seems to occur when I have different settings for the numbered list indents (accessible via the Customize button on the Bullets and Numbering selector). If I set it to the default (Aligned at: .25", Tab space after: 0.5", Indent At: 0.5") then it converts to wiki code just fine. ~MDD4696 13:36, 15 February 2007 (UTC)

:: I will try to fix that if possible as soon as I find the time. Thanks, Cacycle 04:16, 19 February 2007 (UTC)

::: Fixed in 0.9.38 Cacycle 01:20, 19 July 2007 (UTC)

Can wikEdTypoFix replace things like:

• {{desambig}} by {{desambiguação}}
• == Links == and ==Links== by =={{Ligações externas}}==
• [[Category: by [[Categoria:

Can wikEdTypoFix delete things like Imagem:Exemplo.jpg too?

:: That is language specific and has to be added as a custom function using the custo buttons as explained in the wikEd customization section. Cacycle 03:31, 17 April 2007 (UTC)

wikEdTypoFix can't do that?

AutoWikiBrowser Typos (portuguese) have:

for replacing {{desambig}} by {{desambiguação}}

I tried this in wikEdTypoFix:

//{{desambiguação}}

obj.str = obj.str.replace(/\{\{desambig\}\}, "{{desambiguação}}");

and I get an error in JavaScript console. Mosca2 07:34, 17 April 2007 (UTC)

Great tool! One bug: when I edit a page that does not exist, I cannot type into the iframe. I can work around this if I click on 'use full screen editing', and then click back to the regular edit view - then I am able to type into the iframe. I suspect this is a mac and firefox issue, but I consider it a major one - if users can't easily create new pages, that's a problem. Any ideas? I am using the latest wikEd, firefox, and OS X. It may also be an issue with the skin I am using. You can check it out here:

http://www.wikicheatsheets.com/w/index.php?title=Test2&action=edit

Thanks! Nick

--81.159.111.166 20:39, 1 May 2007 (UTC)

:: Yes, users have reported similar problems before. It is a FireFox for Mac bug. Would you like to participate in fixing this? That may take a while, but it would be cool to track this down. Simply change your wikEd.js call to wikEd_dev.js in your monobook.js (or whatever skin you use). It is currently identical to the main version. I would make changes and you would have to report back what it does :-) Cacycle 23:32, 1 May 2007 (UTC)

:: OK, I may take a look at this, but I would copy the js file to a place where I could edit it in order to make changes and see effects myself. I will probably live with the problem for now, but may take a stab at it soon. Thanks! --81.159.111.166 00:01, 2 May 2007 (UTC)

We are a school district that uses MediaWiki (and Wikipedia) extensively, and have many teachers working on collaborative curriculum development. All staff and students are Mac OS X users. Those who also use the latest Firefox and Flock versions are having the WONDERFUL WikEd toolbar fail to allow text entry on NEW pages unless they use the "full screen" workaround. We would be more than happy to help identify and fix this problem. WikEd really is a useful tool, Cacycle, and we really appreciate your efforts in developing it. Our wiki has about 5800 pages of K-12 curriculum and resources, and is growing rapidly.

http://wiki.bssd.org

Johncn

Cool, let's find a workaround! I am a bit busy right now and this is a tricky bug, so it might take a while. Please could you start by describing your problem and all possible workarounds in every possible detail so that I (without a OS X system) can get an idea of what happens (e.g. when does it happen, what exactly happens, what is broken, what does work, exact steps to reproduce everything and what happens at each step, are there JavaScript error messages or warnings.). Thanks, Cacycle 05:22, 28 May 2007 (UTC)

Sorry...summer vacation. We're back at work now, and I'm doing training on Wiked in a couple days.

We are using OS X 10.4.7, and Firefox 'above 1.5.0.1 (which does actually work) on all our machines. When we load the edit page in more recent Firefox versions, the Wiked HTML Editor appears, but you can't type in the entry box.

If you hit the "Full Screen" button, you can enter text in that mode, or just return to regular mode and all is normal again. The problem is that we have to teach students to click that before making changes, and many are just using the old style editor instead since it is easier and quicker than using the workaround. Thanks! Johncn --BSSD UNK 17:31, 4 August 2007 (UTC)

2 suggestions:

• give the option of fewer buttons
• hide the existing toolbar when showing yours

A simple interface is the best, people who are scared away by wiki markup are also scared away by 98 buttons! Keep up the good work. Miken32 23:20, 8 May 2007 (UTC)

:I'd second this. The reason that keeps me from using wikiEd is it looks and feels bloated. JoeSmack ^Talk 12:51, 21 May 2007 (UTC)

:: What screen resolution do you use (i.e. does it feel bloated because you have the buttons in multiple rows). Which functionality, buttons, or button bars would you minimize or remove. The standard toolbar can be hidden with one click, these wikEd settings are now preserved between browser sessions. Cacycle 13:34, 21 May 2007 (UTC)

::: I have now removed several buttons to streamline the interface. Cacycle 03:01, 1 June 2007 (UTC)

I did every thing that the one guide told me to do yet it still doesn't show anything at all (offline/Intranet Wiki). Is there a way to fix this? Frostyfrog 02:57, 18 May 2007 (UTC)

:: Maybe, if you give more details. See the top of the page for how to report errors. Make sure to follow the guide on the wikEd homepage. Cacycle 12:58, 18 May 2007 (UTC)

:: Has $wgAllowUserJs = true; been set in LocalSettings.php of your wiki installation by a server admin? Cacycle 13:01, 18 May 2007 (UTC)

:: yes it has been set ($wgAllowUserJs = true; is at the bottom)) Frostyfrog 22:15, 21 May 2007 (UTC)

::: Could you please check the top of this page for the information that I need to help you. Thanks, Cacycle 23:03, 21 May 2007 (UTC)

Hey there, I'm a new Wikipedian and was hoping that wikEd would be able to help me get my feet underneath me as a new editor. However, it is giving me some problems and I'd like to get a little more experience under my belt before I use it. Is there any way to uninstall/remove it? I have "disabled" it by clicking the box in the upper right corner of the screen, but would like to just get a fresh start and come back to it later. Thanks for your help, and for making such a great product! bwowen ^T/C 00:08, 19 May 2007 (UTC)

:: Just remove the installation code from your monobook.js and click Shift-Reload to clear your browser cache. But clicking the "main switch" on top of the page should work too. Which problems did you have, maybe it can be fixed. Cacycle 00:41, 19 May 2007 (UTC)

:::I couldn't edit some pages - I didn't look at the specific error, sorry. I'd edit a page, hit preview, and nothing would happen. Any advice? bwowen ^T/C 02:05, 19 May 2007 (UTC)

:::: That sounds like the bug from above and has been fixed. It was related to the newest feature of making all links in the edit text clickable. Cacycle 04:39, 19 May 2007 (UTC)

:::::So I just put it back in my monobook.js to reinstall it then?bwowen ^T/C 22:45, 20 May 2007 (UTC)

:::::: Good idea :-) See the wikEd homepage for details. Cacycle 23:19, 20 May 2007 (UTC)

I just install MediaWiki for my local host, and trying to install WikEd for it. But after I have followed everything guided in Installation step by step (If I do properly), it still doesn't work. Follow the troubleshooting to the last step, I open the Error Console in Firefox, I get the following error alert:

Error: syntax error

Source File: http://localhost/Wiki/index.php?title=-&action=raw&smaxage=0&gen=js

Line: 19, Column: 1

Source Code:

I'm using:

• WikEd 0.9.33
• WindowXP SP2
• Firefox 2.0.0.3 for browser : Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 *Firefox/2.0.0.3
• And currently, I use All-in-one sidebar
• Bookmark Duplicate Dectector
• Document Map
• DOM Inspector
• Full Cal
• Mozile
• Reminderfox
• Scrapbook
• Tab Mix plus
• Torrent Search Toolbar
• Nandu
• WAMP5 1.7.1 for WAMP soft
• MediaWiki 1.9.3
• user scripts to common.js:

/* Any JavaScript here will be loaded for all users on every page load. */

/* define image path*/

var wikEdImagePath = 'http://localhost/Wiki/images';

/* disable auto update*/

var wikEdAutoUpdate = false;

/* install the wikEd translation (omit if no translation needed) */

document.write('');

/* install [http://en.wikipedia.org/wiki/User:Cacycle/wikEd] in-browser text editor*/

document.write('');

:: wikEd does not work with that ancient MediaWiki installation. Please install a recent version (also for security reasons) or ask for it. Cacycle 12:50, 24 May 2007 (UTC)

:::Sorry, Mines is 1.9.3, not 1.10 <_- is it the latest version.

:::: The problem might be related to the helper scripts. Does it work if you put this before the installation code:

// disable external diff script
var wikEdLoadDiffScript = false;
// disable external wikEdDiff script
var wikEdLoadDiff = false;
// enable external InstaView script
var wikEdLoadInstaView = false;
// enable external RegExTypoFix script
var wikEdLoadRegExTypoFix = false;
// disable RegExTypoFix (http://en.wikipedia.org/wiki/User:Mboverload/RegExTypoFix), needs User:Cacycle/wikEdTypoFix.js or translation
var wikEdRegExTypoFix = false;

If enabled, these scripts should also be copied to your wiki. I will update the instructions later today. Cacycle 14:15, 24 May 2007 (UTC)

:: Sorry to say nothing change, thanks for prompt support

::: Are there other error messages. Or does it help to replace "" with "". Cacycle 15:31, 24 May 2007 (UTC)

:::: This seems the most probable cause of the problems. I have already updated the wikEd homepage. Cacycle 16:04, 24 May 2007 (UTC)

::: You should also use the current version (0.9.36j) and then update later today or tomorrow to get a find/replace bugfix. Cacycle 15:39, 24 May 2007 (UTC)

::: Are you sure it is an uppercased W in wiki in your path? Cacycle 16:02, 24 May 2007 (UTC)

:::Yep, I copy it from the link, so it should be okie. It still have the same error. I'm not sure what you mean by replace..... I think, for the next time, you should export code in txt file, so it wont be mistaken. For example, when copy code from your WikEd and paste to mines, it does not look exactly the same.....

:::: Simply replace every occurrence of "" with "" on common.js. Cacycle 17:12, 24 May 2007 (UTC)

:::Already change, but no effect. The same error for the < /nowiki > < /pre > (I use space to neutralize the code).

Sorry, it took me while. You have to remove the "" parts. I have it already fixed on the homepage. Cacycle 16:41, 26 May 2007 (UTC)

Nothing happen again :(. But I not that, you forget to say about wikEdDiff.js??

:: After removing the "" parts, please could you post your common.js and all related error medssages. Thanks, Cacycle 17:42, 27 May 2007 (UTC)

As you see [http://en.wikipedia.org/w/index.php?title=Smells_Like_Teen_Spirit&diff=134573857&oldid=134573673 here], using "Fix basic, html, and unicode" causes errors in cite tags. Rather than correcting every cite tag manualy, can you make it so that it dosnt change – to –? ffm ✎talk 14:59, 30 May 2007 (UTC)

: This button is explicitly made to convert &ndash; into –, what is wrong with that. I will try to fix the
substitution. These buttons should not be used on the whole text but rather on selected text because intentional and sometimes very tricky formatting might get lost, even during "normal" operation. The problem with the ref tags is that they miss the quotation marks for the name attribute, it must be , not . Cacycle 02:52, 1 June 2007 (UTC)

:: HTML tag parameters are now accepted without quotation marks in 0.9.38a. I will not fix the
substitution as this is the expected functionality of the "fix html" and the "fix all" buttons, please use them only on selected text. Cacycle 02:54, 19 July 2007 (UTC)

Hey, I just started using wiked and (oh, that's cute, I just got the name) it's pretty sweet, but I'm just wondering about keyboard shortcuts. Before I installed this, I had my own javascript (oh, this is on [http://bmearns.net/wwk/ my own wiki], not the pedia) that caught keydown events from the edit box and did things like markup and submit the form and stuff. Since installing yours, these no longer work. The function isn't even getting called, even though I include the javascript and the onkeydown attribute statically in the edit page. Is your script capturing them out from underneath me or something? I'm on Firefox 2.0.0.4 on WinXP Pro SP2 (doubt that's relevant). MediaWiki is pretty old, v 1.6.5, but the script works fine, it just seems to be trumping mine.

If you need to, you should be able to test it out and view the source here: http://bmearns.net/wwk/edit/WorldWideWiki:Sandbox

Ctrl-b is supposed to bold, Ctrl-i is itallicts, and there's some others. They delegate to the media wiki standard insertTags JS function. More importantly, they return false to prevent the keyevent from going any further.

So any help would be appreciated. I'll let you know if I find anything. Thanks. B.Mearns^*, KSC 18:23, 1 June 2007 (UTC)

:: The page is empty for me. But if you give me a list of shortcuts I can add them to wikEd. Cacycle 19:32, 1 June 2007 (UTC)

Hello,

I have recently installed a MediaWiki Server for use at a colabrative information source at the office. I was hoping to add WikiEd to the server, or perhaps on an initial user basis so that it would assist with the learning curve of wiki markup and in hopes that it encouraged more users to contribute.

I have created this account and installed it and it seems to work here on Wikipedia(at least mostly), however the same on my server results in no wikied icon in the upper right.

I have reviewed the documentation provided and have ensured that I followed the sections. My browser is JS enabled, and I get no errors. I have set the requested LocalSetting varriable to enable JS for my users and bounced apache. I reviewed the section for troubleshooting the install and believe I have done as expected, however I still have no WikiEd icon in the upper right.

1. Does WikiEd work in MW 1.10.0?
2. Do you have a simple sample JS that would be able to test this functionality in my Wiki outside of WikiEd
3. mostly: Do you have any suggestions on how to make this work?

Thanks in advanced for any assistance you can provide.

J

:: It should work well with all newer Mediawiki versions. What happens if you install it into your username/monobook.js. Is $wgUseSiteJs set to true. Did you click Shift-Reload to update. In order to help you I need more infos, including the contents of MediaWiki:Common.js. Is $wgUseSiteJs set to true. Cacycle 02:11, 3 June 2007 (UTC)

:::: Hi. I found the problem with J's MediaWiki. I had the exact same problem. Cacycle, your Common.js code refers to wiked.js. However, in your installation instructions, you specify to create wikEd.js. Since MediaWiki is case sensitive, this breaks the installation!

:::: Another thing in your Common.js code - you refer to wikEdDiff.js. However, nowhere in the installation have you provided the code that goes into this file. Is this a mistake? --Pratsx 05:56, 21 September 2007 (UTC)

The newest versions of wikEd seems to collide with link-changing scripts ([http://hu.wikipedia.org/wiki/User:Tgr/vandal.js this one], to be specific) on diff pages. (The script should insert a "bot=1" parameter into rollback links, but the link gets totally messed up, and mostly turned into plaintext. I'm not sure when exactly this started, but used wikEd for quite a while so I think I would have noiced it earlier if it didn't happen recently. I suspected the new linkification feature, but wikEdFollowLinks = false didn't help. (Turning off wikEd with the cookie doesnt help either.) A tried this both with my script loaded before and after wikEd, doesn't change anything.

I use the newest wikEd (0.9.37b) and Firefox (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4) under Windows XP. I only get the error on diff pages, not on other pages with a rollback link (e.g. history pages). I don't get any javascript errors.

This is the original HTML source of the rollback link (for the article "Farkas" last edited by "Don golgi" in huwiki):

[visszaállítás]

This is how it should look (and how it looks when wikEd is turned off):

[visszaállítás]

This is how it looks with wikEd:

[http://hu.wikipedia.org/w/index.php?title=Farkas&action=rollback&bot=1&from=Don+golgi&token=436a4903602fb8798bbd686325e13e6c%5C" title="Farkas">visszaállítás]

Do you have any idea what might cause this? Thanks, --Tgr 00:42, 9 June 2007 (UTC)

:: Quick fix: var wikEdLoadDiffScript = false; to disable the wikEdDiff feature. I'll check for the exact cause and a real fix later. Cacycle 02:26, 9 June 2007 (UTC)

::: It should work now, please could you test it and report back. It is now linkifying only in non-title cells of the diff table. Thanks, Cacycle 03:49, 9 June 2007 (UTC)

Thanks, it works fine now. --Tgr 18:21, 9 June 2007 (UTC)

For some reason, firefox does not spellcheck text entered into wikEd like it does for text entered into the standard edit box. ffm ✎talk 11:42, 12 June 2007 (UTC)

:: It works fine for me in Firefox 2.0.0.4 and 3.0a6pre and the current SeaMonkey. What happens if you update to 2.0.0.4. Or maybe it is a preference setting. Cacycle 14:03, 12 June 2007 (UTC)

Hi im working on a company intranet homepage and want to make things easier for people to use. I wonder if its possible to only have highlighting and nothing else? --192.100.124.219 09:27, 19 June 2007 (UTC)

:: There is no easy way to do this. I would also not be user friendly because one needs at least the [T] button to use wikEd. But I am open to suggestions to simplifu things. Why don't you use it for a while and give me some feedback. Cacycle 12:40, 19 June 2007 (UTC)

• Using: wikEd 0.9.37b
• User string: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
• Error: ruleStyle.replace is not a function; Source File: http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript

Line: 1201

• No add-ons in use
• Monobook scripts: User:AndyZ/peerreviewer.js, Wikipedia:WikiProject User scripts/Scripts/Fix lowercase first letter problem, Wikipedia:WikiProject_User_scripts/Scripts/AutoAFD.js, User:Voice_of_All/Addtabs/monobook.js, User:Lupin/popups.js, User:AzaToth/twinkle.js, Wikipedia:WikiProject User scripts/Scripts/Add LI menu, User:Lupin/recent2.js, User:Outriggr/metadata.js
• OS: Windows Vista
• Issue: Was attempting to add the simpler importScript string to replace much bulkier code I had which called each JS which is part of Twinkle and for whatever reason ended up breaking wikEd. After a stripdown and rebuild of my monobok.js one script at a time, problem still persisted and only Twinkle broke wikEd. Will work as usual when viewing pages but will run into mentioned loading error when trying to edit.
• Steps to reproduce: Edit any page, all other scripts work fine but wikEd fails to load.
• What happens: Nothing, works as if wikEd was disabled.

Any help on this odd, near isolated issue would be helpful! --treelo _talk 01:46, 24 June 2007 (UTC)

:I also have this issue. --Flex (talk/contribs) 02:05, 24 June 2007 (UTC)

:Looks like it was twinkle, but the error is gone. FYI, the error noted happens with or without twinkle enabled. --Andrew Hampe ^Talk 03:39, 24 June 2007 (UTC)

:: I have temporarily fixed it. The error is actually caused by some strange programming in Twinkle and I have contacted AzaToth. Cacycle 04:56, 24 June 2007 (UTC)

I think I finally found what caused the red-bold of some templates that annoyed me for so long: URLs used as parameters. Can that be fixed? Circeus 04:10, 8 July 2007 (UTC)

:: Please could you give me an example. Thanks, Cacycle 13:19, 8 July 2007 (UTC)

::http://en.wikipedia.org/w/index.php?title=Ailanthus_altissima&action=edit§ion=9 Although the {{tl|cquote}} is also bolded. When working with this article, I noted that replacing a url (which are ALSO bade into red bold) with a DOI would cause the template to become normal again. Note that removing the HTML comment in the Cquote will also return it to normal. Not all templates with URL become bold, but the vast majority will. Circeus 04:53, 9 July 2007 (UTC)

When I edit a page, click the main "Preview" button, then make another change and press the green Δ change button, only the last set of changes (i.e., those that have been made in the current page session or whatever the term is) is displayed. (I'm using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 and wikEd 0.9.37c.) --zenohockey 04:34, 9 July 2007 (UTC)

:This is normal behaivor. It is designed to work this way, it is not possible (or would be difficult) to retrive the original page data. Also, it would cause issues if someone changed the page while you were editing it. ffm ✎talk 18:53, 10 July 2007 (UTC)

:: That's right, thanks Firefoxman. I might add the requested function in the future, similar to the preview that uses first a local view and then retrieves a server preview using AJAX techiques. Cacycle 02:36, 11 July 2007 (UTC)

It seems that, when there's a bullet point preceding by an HTML comment, the bulleted text is not "grayed."

For example, click "Edit" and look at this:

*This text is not grayed.

• This text is grayed.

--zenohockey 05:18, 9 July 2007 (UTC)

:: Thanks for noticing, I am not yet sure if this can be fixed easily, we might have to live with it in order to keep the program fast and short. Cacycle 02:38, 11 July 2007 (UTC)

::: Fixed in 0.9.37e. Cacycle 03:17, 15 July 2007 (UTC)

Do you think you could add a button to the toolbar that wraps selected text in ref tags? ffm ✎talk 18:42, 10 July 2007 (UTC)

:: You mean like the Image:WikEd_ref.png button? Cacycle 02:39, 11 July 2007 (UTC)

:::Doesn't that just hide the refs? (I cannot verify as I am on IE right now) ffm ✎talk 15:00, 11 July 2007 (UTC)

:::: Not the blue one on the left button bar :-) Cacycle 18:24, 11 July 2007 (UTC)

:::::Ah, I see. Thank you.You rock~ ffm ✎talk 14:06, 15 July 2007 (UTC)

Links of the formet singular words do not convert properly, they always end up like singular wordsswhen pasted text is wikified by wiked.

:: Fixed in 0.9.37d. Cacycle 02:13, 15 July 2007 (UTC)

Also, characters like the underscore and tilde are converted into percent-encoded element for the purpose of ctrl+click, which often breaks the link. Not to mention links themselves containing percent encoded characters...Circeus 12:33, 14 July 2007 (UTC)

:: Please give me examples so that I can fix it. Thanks, Cacycle 02:13, 15 July 2007 (UTC)

:::Édifice Price, "History" section: the "lachappelle" (name of ref) ref link breaks because it has an underscore. It also highlights improperly, as does the "benoit" ref. Circeus 02:23, 15 July 2007 (UTC)

:::: Thanks, I have fixed it in 0.9.37f. Cacycle 04:08, 15 July 2007 (UTC)

How about compressing the wikEd code? It can make a huge difference, both in file size and performance.

On [http://www.tiddlywiki.com TiddlyWiki] (or rather, [http://tinytiddly.lewcid.org/ TinyTiddly]), this is done with the following tools:

1. [http://alex.dojotoolkit.org/shrinksafe/ ShrinkSafe]
2. [http://www.crockford.com/javascript/jsmin.html JsMin]
3. [http://dean.edwards.name/packer/ Packer]

[http://www.javascriptlint.com/ Lint] might be helpful too...

-- FND, 09:16, 17 July 2007 (UTC)

: Thanks for the suggestion and the interesting links. I am a bit reluctant - it would certainly speed up the script download, but I do not think it would affect the execution speed. JavaScript is load only once and then kept in the browser cache, so that during normal operation there would not be any difference. However, it would be quite some work to compress every version and to keep a readable as well as a compressed version on separate pages. Cacycle 04:30, 18 July 2007 (UTC)

:: You might be right about the execution speed (it might be a different issue with TiddlyWiki's huge load of JS code). As for the effort it would take, that could probably be automated with a script - if you're interested, I could ask the TinyTiddly guy whether his (Ruby) script could be adapted to your needs. -- FND 06:50, 19 July 2007 (UTC)

I would like a greasemonkey version, (and it would nice nice if the whole script was packed together as a single file) so I can use it on all the wiki sites I use, and possibly on intranet systems.

I tried to modify it myself but it kept loading a blank page for me. I do not understand why. So you do it.

Thank you very much. --ALok 21:27, 18 July 2007 (UTC)

: Thanks, I am working on it Cacycle 18:18, 22 July 2007 (UTC)

:: The next wikEd version will also work as a Greasemonkey script! It already works fine under Firefox, but I still have to adapt an automatic update system and probably have to bundle the scripts together. See wikEd_dev.js for a working preview and [http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd_dev.js&action=raw&ctype=text/javascript click here to install it] (the content of these links will be removed/changed in a few days). Cacycle 13:56, 19 September 2007 (UTC)

::: Thanks for the suggestion! wikEd 0.9.44 is now Greasemonkey compatible and the whole bundle can be installed by clicking here. Cacycle 05:05, 24 September 2007 (UTC)

Firefox 2.0.0.5

Intel Mac OS X 10.4.10

wiked 0.9.38a

More details available if needed - the cut function in firefox edit drawdown menu does not show or work - and the two delete buttons dont work SatuSuro 12:31, 22 July 2007 (UTC)

:: This looks like a FireFox for Mac OsX bug, everything works fine with SeaMonkey and FireFox under Windows and your monobook.js also works for me. I am sorry, but I cannot try to find a workaround because I do not have access to a Mac Os X box. You could check the error console for JavaScript errors and/or file a Mozilla bug report. You could also try to disable other, potentially incompatible, browser addons. Cacycle 18:18, 22 July 2007 (UTC)

::Dont apologise - I appreciate the response - what I might do when i have the time is disable all the firefox addons - they are a nuisance anyways - and see what happens - anyways for some type of editing - for the moment disabling between cut/delete editing and other is no big deal - will get back when i have aclearer idea - cheers SatuSuro 01:42, 23 July 2007 (UTC)

:::I assumed this was intentional. But for me not being able to right-click, menu, cut is something I am already missing since I started using this editor yesterday. I've not got a Mac. qp10qp 22:16, 22 July 2007 (UTC)

:::: Qp10qp: You are not using Mac OS X and don't have the cut entry in right click menus? That is really strange as it is there for me. What about the delete and backspace keys. Cacycle 14:03, 23 July 2007 (UTC)

::::This is not intentional. What version of FF are you running? ffm 14:45, 23 July 2007 (UTC)

:::::I think I am on the last but one update of Firefox. It's possible that there is a clash with a dropdown from my tab extension. But the minute I disable this editor, my right click drop down menu is a standard undo, cut, copy, paste, select all list, and I haven't had the problem before. With it enabled, I get select all, but the rest is a drop down related to my tab extension, I think. It does have "back".qp10qp 17:10, 23 July 2007 (UTC)

I've been trying this editor out. Many thanks for all your work: it's very interesting.

I thought I'd try the dash fix thing on the article I am working on, William Shakespeare (I thought it might save me some time converting hyphens to en dashes in date and page ranges); but unless the preview misled me, it appears that the fix intends to put spaces round em dashes. Spaced em dashes are not really very common in print, however, and our MoS now deprecates them ("Em dashes are normally unspaced on Wikipedia"). Spaced en dashes may be used instead of em dashes, but I suspect that the majority of editors would not wish to do that.qp10qp 22:12, 22 July 2007 (UTC)

:: Should I make it en-dashes only or unspaced em-dashes. Personally, I don't like em-dashes... For consistency it could also convert all ems to ens... Cacycle 14:02, 23 July 2007 (UTC)

::: I think this is a real minefield, because there are many schools of thought and different publishing houses use different styles. At the moment, the MoS, rightly I think, advises either unspaced em dashes or spaced en dashes, but I don't think the fix should force one of these two styles (dash nerds like myself would go bonkers). A conversion of spaced ems to unspaced would be in keeping with the MoS, except there would need to be an exception where people have wrongly used ems for date ranges. But ens are difficult because they might be spaced in prose but unspaced in page or date ranges. The most useful thing to me would be changing hyphens to en dashes on page or date ranges, though I think a bot comes round every so often to sort this out; also a quick way of adding dashes to text with key strokes (at the moment, if I type two hyphens, your editor gives me a spaced em dash, and so I have to delete the spaces; the alternative of dropping down to the menu below the edit box is also dreary).qp10qp 16:56, 23 July 2007 (UTC)

:: It is fixed in wikEd 0.9.41. It now removes spaces around em dashes, adds spaces around en-dashes, and converts html character entities into dash characters, -- to en dashes, dashes before numbers into a minus sign, and dashes to en dashes in dates. Cacycle 02:21, 7 September 2007 (UTC)

"Toggles the automatically addition of "…using wikEd" to summaries on submitting the page. This setting affects all new pages and is kept for future sessions."

Just a minor thing for your info: odd English (I didn't correct it because I wasn't sure what it should be).qp10qp 22:39, 22 July 2007 (UTC)

:: Sounds like valid English to me :-) The button toggles a setting that adds some text to the summary after you have pushed the submit button. Cacycle 13:56, 23 July 2007 (UTC)

::Do you mean "toggles the automatic addition of..."? qp10qp 16:41, 23 July 2007 (UTC)

::: Oops... yeah Cacycle 18:53, 23 July 2007 (UTC)

Image:WikEd using.png dosnt appear in the toolbar anymore. ffm 16:00, 23 July 2007 (UTC)

:: Add var wikEdShowUsingButton = true; to your monobook.js before calling wikEd. Cacycle 04:40, 2 September 2007 (UTC)

Firefox 2.0.0.5 is complaining of:

Error: invalid XML tag syntax
Source File: http://nc1lxbuild01.nc.tekelec.com/tekpedia/index.php?title=User:Jhildebr/monobook.js&action=raw&ctype=text/javascript&dontcountme=s
Line: 6, Column: 40
Source Code:
+ '&action=raw&ctype=text/javascript">');
-----------------------------------------^

Which is a part of my installation line in my monobook.js file.

// install User:Cacycle/wikEd in-browser text editor
document.write('');

Hope that helps, Cacycle 13:45, 24 July 2007 (UTC)

::: I've isolated it out. It turns out that there's an incompatibility issue with the [http://www.mediawiki.org/wiki/Extension:LinkedImage#Installation LinkedImages Extension]. Once I took that out, it loaded. Go figure. Thanks for your help. --Hildebrandj 14:21, 24 July 2007 (UTC)

Think it could be incoperated into wikEd? ffm 13:27, 24 July 2007 (UTC)

: Thanks for the suggestion. I will probably not write this as it would bloat the code and slow down the already slow syntax highlighting, even if it would come handy for the handful people that edit JavaScript in the input field :-) Cacycle 00:01, 26 July 2007 (UTC)

Would it be possible to support the use of language tags for the regextypo fixer? AWB supports them so that English spelling corrections are not applied to text tagged as foreign language e.g. {{lang|fr|some text}}. Thanks Rjwilmsi 19:35, 25 July 2007 (UTC)

:: wikEd 0.9.40 now supports the Template:Lang template to exclude text from typo fixing. Please note that the lang template must not contain other nested templates - the excluded text ends currently with the first occurrence of }}. Please notify me if nested templates really need to be supported (it would make the code much more complicated as far as I can see). Cacycle 03:15, 5 September 2007 (UTC)

Has wikEd been tested for compatibility with Apple's [http://www.apple.com/safari Safari 3 Beta]? This version appears to be based at least partly on Mozilla. I have it running on XP and would be happy to help in any testing. —Travis^talk 14:58, 28 July 2007 (UTC)

:: I am currently on vacation. Your help in testing it under Safary would be appreciated, please check User:Cacycle/wikEd_development for the preferences setting to bypass the wikEd browser test. Unfortunately, I cannot help much until I am back. Cacycle 17:23, 1 August 2007 (UTC)

:::I just today returned from vacation myself, so I'll be starting this next week. —Travis^talk 04:09, 5 August 2007 (UTC)

Hello,

the problem is that the wiked.js file isn't loaded properly. I suppose it is cutted after 256 Kilobytes, when I display any site of my wiki. I used the url "http://localhost/wiki/index.php?title=wiked.js&action=raw&ctype=text/javascript" and I just get a part of this file. If I write a plaintext file on the webserver with the content I can download it and the content in OK. So I suppose there must be a Problem in my PHP, MySQL or MediaWiki Configuration. I can edit this page and there everything is fine.

• Your wikEd version: 0.9.38a
• Your MediaWiki Version: 1.9.3
• Your 'browser: id19 Firefox/2.0.0.5'
• Error console errors: Parsing errors because last Part of file is missing
• Which browser add-ons have you installed: just Prefbar
• Which user scripts have you installed on your monobook.js page: no other script
• Which operating system do you use: Server SLES 10, Client Windows 2000

:: It might also be a webserver setting. Cacycle 22:37, 14 August 2007 (UTC)

::: But what should be the problem? I've checked the configuration of Apache, PHP and MySQL and raised all buffers, caches and execution times I could find. But the problem is still the same. --Michael Mann 05:00, 15 August 2007 (UTC)+

:::: Please provide more details :-) Cacycle 23:22, 20 August 2007 (UTC)

::::: What a funny guy ;o), I will supply my php.ini, Media Wiki Configuration, apache config as soon as possible. Which files/informations do you also need? Thanks --Michael Mann 12:44, 21 August 2007 (UTC)

:::::: I was thinking more about: at which position does it break, always at the same position, or is it really 256 kB. Cacycle 13:28, 21 August 2007 (UTC)

::::::: It breaks everytime at a Point where 256 KB was reached and if I delete some lines it's just an other line. But now it works curiously, I restarted the machine because of maintainance issues and after that it works, when I connect via VPN. I will test the problem when I am at work in september and I hope I can tell you what the problem was. Thanks for your help. --Michael Mann 10:30, 26 August 2007 (UTC)

I don't know what's wrong. The Console doesn't show an error for my code, yet I don't see the icon. What's wrong? Laleena^{Talk to me} _{Contributions to Wikipedia} 21:05, 12 August 2007 (UTC)

:: Dunno, please give more infos, see the top of the page for essential information that I need to help you. Cacycle 20:43, 18 August 2007 (UTC)

Hi. First off, thanks for making this script, it is REALLY a time saver! I am converting a wiki from UseMod to MediaWiki and wikiEd has REALLY come in handy for all those HTML-rich pages.

Now, for my concern. I am using wikiEd 0.9.38a on FF 2.0.0.6 on OS X (have you figured out the editing error for OS X yet? :-P) and I had been using it without too many problems for my HTML conversion using the [< >]. For some reason, as of this week or the one before, converting the following link is giving me double square brackets instead of one:

class="wikitable" ! Raw HTML ! (incorrect) wikiEd output ! Reason it is incorrect
blah	blah	This is not an internal link, it should convert it to [http://blah.com blah]

It was working before (pretty sure it was after July 18, so it doesn't seem like an issue with the newest version, although it WAS working fine a few weeks ago...) but for some reason now it thinks those are internal links.

Also, if it is possible, could you make the change so the HTML does not have to be case sensitive? blah converts simply to "blah". Also, not sure if this matters, but I am using MW 1.6.10 (trust me, if I could be using 1.10.x, I would be...). Thanks again! --Eljaco 16:54, 22 August 2007 (UTC)

: I will make these changes as soon as I find the time. Cacycle 13:07, 30 August 2007 (UTC)

:: Please can you give me a link to your wiki so that I can test it - here a Wikipedia it seems to work fine. Thanks, Cacycle 04:22, 2 September 2007 (UTC)

Hello. wikEd automatically aligns text to the left (LTR). How can I add a button (or maybe add it to the next version) that will change text direction RTL<->LTR..? Thanks, Mintz l 13:49, 26 August 2007 (UTC)

: Check User:Cacycle/wikEd#Custom_buttons and change the "div" example to "rtl" (if that is the html tag for it). Cacycle 13:02, 30 August 2007 (UTC)

• Excuse me, but, it's not clear for me, the beginner, to see how to enable it, right to left? I mean, i installed all, but is there a way to change the all direction to Right? —Preceding unsigned comment added by 213.42.21.154 (talk) 21:28, 5 October 2007 (UTC)

:: I probably do not exactly understand what you want, please explain your problem in much more detail. Cacycle 21:30, 6 October 2007 (UTC)

• Hi, i mean, when writing the Arabic wiki, it moves the direction of the writing, To left to Right, i want it to skip this step, and leave the default direction, From Right to Left.

PS. Try an essay, in the arabic wiki , to understand more, about this Issue.

Regards. --Stayfi 00:37, 11 October 2007 (UTC)

::: I have added RTL-support in wikEd 0.9.46. Сасусlе 02:06, 14 October 2007 (UTC)

• Well done, Man. I planned to change ur code, but u did it. Thanks.

:: Regards --Stayfi 19:57, 21 October 2007 (UTC)

Hi, I'm having problems with your WikEd script when working with Lupins fixing disambigs popup. I think it's to do with wikEd is incompatible with other scripts and extensions that rely on or change the text edit box (see the next section). I've already had help from User:After Midnight, and after finding out it was WikEd that was causing the problem, he suggested I speak to you. All the information on the error is here in greater detail, also the conversation we had. Upon removing WikEd from my monobook.js the disambig popup script work.

I have the latest version of the script, and I am using FireFox, and WikEd works perfectly normally.

Any help would be appreciated, your script is very useful and I would like to keep it, while having disambig fixing popups. Thanks in advance -- Halo2 ^Talk 15:50, 26 August 2007 (UTC)

: After a quick look I think the problem is related to this: User:Cacycle/wikEd#Making scripts compatible with wikEd and had to be fixed in the popups script. Cacycle 12:56, 30 August 2007 (UTC)

Thanks for looking at it. I'm a bit lost, I'm not sure whether I fix it when importing the script, ie including the above text into my monobook, or do I contact the author of the Popup script (User:Lupin). -- Halo2 ^Talk 18:46, 30 August 2007 (UTC)

Hello. I tried to install wikEd on MediaWiki 1.10.1, and i got error report by js-console: "JavaScript - http://mtb.tj/mwiki/index.php/Участник:WikiSysop/monobook.js

Inline script compilation

Syntax error while loading: line 4787 of linked script at http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js&action=raw&ctype=text/javascript :

obj.plain = obj.plain.replace(/([\wÀ-ÖØ-öø-\u0220\u0222-\u0

" —Preceding unsigned comment added by 85.141.89.108 (talk) 07:59, August 28, 2007 (UTC)

: No idea... Could be a problem with character encoding, if you set it to UTF-8 in MediaWiki, web server, and browser it might work. Cacycle 13:06, 30 August 2007 (UTC)

:: I've done the problem - this is some kind of Opera's bug - on Firefox everything is OK. Thank you and sorry for idle diturbing. —Preceding unsigned comment added by 85.141.88.147 (talk) 13:03, 19 September 2007 (UTC)

Hello there,

First of all, thanks for the awesome job ! wikEd is indeed wicked :)

Now, I've been meaning to install it on an offline MediaWiki installation. I followed the offline instructions thoroughly but there's a catch. If, in my monobook.js special page, I use {{wikEd}}, wikEd does not show up at all. However, if I type {{subst:wikEd}}, then all is well.

I have not yet investigated the full details of javascript + template inclusion, so I do not know exactly what is going on there. Any insight would be greatly appreciated :)

Cheers !

143.196.159.101 09:17, 30 August 2007 (UTC) (sorry, can't remember whether I had an account here)

:You cannot use templates like {{wikEd}} in your monobook, you have to paste the actual text for it to work. Cacycle 13:09, 30 August 2007 (UTC)

::Thanks. Then may I suggest that the "offline" instructions be changed to reflect that ? Especially the line "users can then install wikEd simply by adding {{wikEd}} to their User:USERNAME/monobook.js page." In fact, hey, I'm going to correct this myself :) Another question though : is it normal that the instant preview does not make use of the templates, ie. it does not render them at all, but displays {{templatename}} instead ? Cheers, Romain 143.196.159.101 08:13, 31 August 2007 (UTC)

::: Thanks for fixing the instructions. The preview first renders the article offline so that templates are not substituted and then fetches a complete preview from the server. Cacycle 12:56, 31 August 2007 (UTC)

:::: Gotcha. In short, use the default preview when you need templates rendered, and wikEd's preview otherwise. Cheers ! Romain 143.196.159.101 14:44, 31 August 2007 (UTC)

::::: No, it gets the complete preview in the background and displays the response from the server. If it does not work then something is wrong. Is there an error message. Cacycle 17:05, 31 August 2007 (UTC)

:::::: Hm nope, I don't think I noticed an error message. I'm using the latest wikEd (downloaded 3 days ago), MediaWiki 1.10.0, on IIS 5 with PHP5. What else could interfere here ? I'll have to check back at work on Monday. Cheers, LeCoyote 19:11, 31 August 2007 (UTC)

:::::: I do confirm : no error message whatsoever. I get the preview window, but templates are not rendered. Also in the preview, link addresses are incorrect : instead of linking to, for example

http://intranet/pathto/wiki/index.php?title=Context:Page

it will point to

http://intranet/pathto/wiki/index.php?title=Context:PageContext:Page

i.e. the full title of the article appears twice. LeCoyote 07:48, 3 September 2007 (UTC)

: Please send me a link to your wiki or thefull html text of an edit page (you can use use the E-mail this user function on the left). Thanks, Cacycle 03:23, 4 September 2007 (UTC)

:: Done. Did you get it ? Can you make any sense out of it ? Thanks a LOT for your time :-) LeCoyote 11:52, 6 September 2007 (UTC)

::: Thanks, got it. I will check it during the next days. Thanks, Cacycle 00:06, 7 September 2007 (UTC)

:::: I have fixed the bug, it was in the User:Pilaf/include/instaview.js script. Now you have to figure out why the Ajax preview does not work... Cacycle 22:36, 8 September 2007 (UTC)

: Hey there ! Thanks for the fix in Instaview. About AJAX however, I am confused. The AJAX diff works perfectly ; AJAX preview works but does neither parse templates nor wiki tables, and it does not render images. There is no error message whatsoever. I am about to dig into the code, although I am not exactly sure where to start. LeCoyote 10:57, 11 September 2007 (UTC)

:: What you see (without template expansion) is the local InstaView preview which is normally replaced by the AJAX server preview that gives exactly the same view as a regular Mediawiki preview. The preview code starts at line 2706 (wikEd 0.9.42) with "// display local preview box". It just fetches a regular preview from the form POST address with an added "&live" to suppress the non-preview part of the served preview page. The diff view is NOT Ajax or server based, it is local. So there is probably a general Ajax problem. Cacycle 02:47, 12 September 2007 (UTC)

"Cacycle 02:47, 12 September 2007 (UTC)

::: Ok, I'm having a go at debugging the whole thing. First finding : at line 2731, typeof(sajax_init_object) is "undefined", hence the clause is false and the ajax preview is never rendered. Since this is my first dig into Ajax code, I do not know where this sajax_init_object is defined. Does that help you figuring out what is going on ? Thanks again for your time. LeCoyote 10:39, 14 September 2007 (UTC)

:: Interesting. sajax_init_object is from the Wikipedia http://en.wikipedia.org/skins-1.5/common/ajax.js, but right now I do not see why this check is needed as wikEd brings its own Ajax interface (?). You might be able to remove this check, I will dig into this later. Cacycle 13:18, 14 September 2007 (UTC)

::: That definitely was the blocking check. It now works as expected. Many thanks ! PS : Added a subtitle for this second issue, to make it more readable. LeCoyote 14:21, 14 September 2007 (UTC)

With default meta Content-Type - text/html everything works fine, when i set it to application/xhtml+xml (XHTML standard) wikiEd doesnt show up.

• wikiEd complete non-offline version, global installation (common.js)
• MediaWiki 1.10.1
• Firefox 2.0.0.6
• Linux 2.6.22.5 (x86_64)

193.93.72.1 23:20, 1 September 2007 (UTC)

:: What's the point of using content type "application/xhtml+xml"? Cacycle 23:53, 1 September 2007 (UTC)

:::: "XHTML 1.0 became a W3C Recommendation January 26, 2000."

:::: When you are using valid XHTML code with "text/html" content type, browser is parsing it just like normal html page, to use "standards compilance mode" you must use "application/xhtml+xml"

:::: 193.93.72.1 10:44, 2 September 2007 (UTC)

: I have no idea why it does not work (any error messages?) and I do not see a reason to serve as application/xhtml+xml (which cannot be read by at least half of all browsers) when text/html works fine. Cacycle 14:39, 2 September 2007 (UTC)

Is anyone working on making this application compatible with Internet Explorer? – 01011000 20:02, 3 September 2007 (UTC)

:: I am not aware of anybody currently working on it. Would you like to? Check wikEd dev and wikEd dev talk. Cacycle 21:56, 3 September 2007 (UTC)

::: I would if I had the technical expertise but, unfortunately, I do not. – 01011000 23:58, 3 September 2007 (UTC)

I really want a better editor for my company's wiki, but turning on JavaScript for all users has me worried. Why do users need to have this ability. If they can run any java script then I am opening my wiki up to all moderatly talented java scripters to do whatever they want (note that I am not a java scripter, so I have only hearsay to go on for what nefarious things can be done with javascript).

Anyway, I was just wondering if there are any plans to make this a bit more secure and not require User or Site wide gifting of Javascript Access.

--Vaccano 22:48, 4 September 2007 (UTC)

:: If you use a site-wide installation then you have the code under your control and do not have to allow individual monobook.js code via $wgAllowUserJs = true;. I have updated and clarified the respective sections on the wikEd homepage. Cacycle 02:09, 5 September 2007 (UTC)

Hi, I'm interesting to use RegExTypoFix from Wikipedia:AutoWikiBrowser/Typos on :fr but when I put var wikEdRegExTypoFix = true; in my [http://fr.wikipedia.org/wiki/Utilisateur:Leag/monobook.js monobook] the Image:WikEd fix reg-ex-typo.png button disappear. How can I do to activate RegExTypoFix with [http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:AutoWikiBrowser/Typos fr AutoWikiBrowser/Typos]? (Is it possible?) Thanks for this great tool. Leag 18:30, 5 September 2007 (UTC)

:: How can it disappear, do you see the button without var wikEdRegExTypoFix = true;. Does it work with the English list. Cacycle 13:09, 6 September 2007 (UTC)

::: Change "Wikip%C3%A9dia" to "Wikipedia". Cacycle 13:17, 6 September 2007 (UTC)

I don't see the button with or without var wikEdRegExTypoFix = true;. Strange !!! I try to desactivate other script in my monobook, there's no way to see the button Image:WikEd fix reg-ex-typo.png The probleme doesn't come from the french translation, I try without. I try with the old var wikEdLoadRegExTypoFix = true; but nothing. Maybe a probleme with {{lang|}} template?

Using AutoWikiBrowser/Typos is a tool I need for a long time, I'm "frustrate" {{;)}} Leag 18:09, 6 September 2007 (UTC)

:: Please check for any JavaScript error messages. It works for me using your monobook.js after removing the "obtenir();" calls and adding "fr:" to the script names. Cacycle 01:25, 7 September 2007 (UTC)

I'm sorry, with only wikEd script in my [http://fr.wikipedia.org/w/index.php?title=Utilisateur:Leag/monobook.js&oldid=20461151 monobook.js] and nothing in [http://fr.wikipedia.org/w/index.php?title=Utilisateur:Leag/monobook.css&oldid=20461105 monobook.css] it didn't work. I can't see the Image:WikEd fix reg-ex-typo.png button. Maybe a probleme in common.js on :fr? Leag 11:01, 7 September 2007 (UTC)

:: Oh, I see it on the French Wikipedia. I'll try to fix it later. Cacycle 13:05, 7 September 2007 (UTC)

:::Thanks a lot Leag 20:55, 7 September 2007 (UTC)

: The rules page address must have the exact same domain name as the used wiki. On the French Wikipedia you have to use the following:

var wikEdRegExTypoFix = true;

var wikEdRegExTypoFixURL = 'http://fr.wikipedia.org/wiki/en:Wikipédia:AutoWikiBrowser/Typos?action=raw';

: I have updated the example on the wikEd homepage. Cacycle

I'm sorry again, with only wikEd script in my [http://fr.wikipedia.org/w/index.php?title=Utilisateur:Leag/monobook.js&oldid=20521627 monobook.js] and nothing in [http://fr.wikipedia.org/w/index.php?title=Utilisateur:Leag/monobook.css&oldid=20521520 monobook.css] it didn't work. Leag 11:24, 9 September 2007 (UTC)

No, don't change anything, it's working without :en :

var wikEdRegExTypoFix = true;

var wikEdRegExTypoFixURL = 'http://fr.wikipedia.org/wiki/Wikipédia:AutoWikiBrowser/Typos?action=raw';

Thanks a lot {{;)}} Leag 11:35, 9 September 2007 (UTC)

Is that something that can reasonably be done? It's extremely frustrating to have to deal with the extra whitespace (ca. 5 linebreaks) generated by any copy-pasted preformatted template code, or the headers, or text from a webpage... Circeus 19:24, 13 September 2007 (UTC)

: Sorry, that's not possible without disabling wikEd - but you can use the Image:WikEd_fix_basic.png button to remove not necessary empty lines and white space. Cacycle 20:39, 13 September 2007 (UTC)

::No thank you. Always end up adding allsort of whitespace in unexpected places. Circeus 14:26, 23 September 2007 (UTC)

::: When do you see those empty lines after copy-pasting - immediately or after using the Image:WikEd_wikify.png button. Also, please let me know if the button adds spaces in the wrong places. Thanks, Cacycle 02:38, 24 September 2007 (UTC)

Hi, I'm using the WikEd Version 0.9.42. I installed it on my previous installed mediawiki which was 1.9.x. Today I upgradet to mediwiki 1.11.0 and now I receive a message saying "Deine Bearbeitung konnte nicht gespeichert werden, da deine Sitzungsdaten verloren gegangen sind.

Da in diesem Wiki reines HTML aktiviert ist, wurde die Vorschau ausgeblendet um JavaScript Attacken vorzubeugen.

Bitte versuche es erneut. Sollte das Problem bestehen bleiben, melden dich ab und wieder an." when I want to use the preview-button of WikEd. What does this mean?

I'm using Firefox 2.0.0.6. and I don't have any errors on my Error-Console.

The extension is setup as serverwide setup, so I did change the Common.js. The mediawiki is runnin on SUSE 10.

Thanks, Dieter —Preceding unsigned comment added by 212.202.50.73 (talk) 18:42, 14 September 2007 (UTC)

:: It is the German text of the session_fail_preview message, it might be caused by waiting too long before submitting an article text. There might also be a Mediawiki setting that could be adjusted for longer timeouts. Cacycle 01:49, 15 September 2007 (UTC)

Hi Cacycle,

I've been using WikEd to convert doc files to wikicode lately. (Current WikEd (0.9.43), Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6, WinXP, MS Office Word 2003.)

While the wikifying function is a huge help, there are a few glitches:

• when there are line breaks in a bold or italic text, it won't close and reopen the wikitags, and will end up with something like this:

'''boldboldbold
boldbold'''plainplainplain

which will result in

:'''boldboldbold

:boldbold'''plainplainplain

thus often turning large paragraphs to bold/italic instead of the first sentence.

• ordered lists are sometimes misidentified as unordered (I'll create a test case when I have the time)
• it would be more practical to prefix image names (currently Image:Clip image###)with the document title so that images in different documents get different names
• :: It now shows the original image name (but the file type seems to be always .png) in wikEd 0.9.46. Сасусlе 02:06, 14 October 2007 (UTC)
• it doesn't recognize footnotes. This regexp finds the first reference and the matching footnote in the rich text html:

var reFootnote = new RegExp(']* href="#_ftn(\\d+)"[^>]*>\\s*[\\s\\S]*?\\s*([\\s\\S]*?)]* id="ftn\\1"[^>]*>\\s*

\\s*([\\s\\S]*?)

\\s*