User talk:Cacycle/wikEd/Archive 003

I use wikEd on the Dutch Wikipedia and I really enjoy using it, except for two things. The first is that I've come across a problem with spaces there. Sometimes wikEd simply removes spaces when I move (copy and paste) a piece of text. Is this some English specific function? If so, can I turn it off? One of these edits is [http://nl.wikipedia.org/w/index.php?title=Wikipedia:Verzoekpagina_voor_moderatoren/Beveiligen&diff=5813996&oldid=5812808], where wikEd removed the spaces between artikelen and beginnen, aantal and deze and de and beveiliging. Do you have any idea what causes this? The second is that I can't simply press Tab to go to the summary field, just like mentioned at #WikiEd suggestions. Is it possible to specify in monobook.js what you want tab to do? I.e. either add four (?) spaces or go to the next edit field. Thanks in advance and thanks for creating wikEd :) --Erwin85 19:25, 16 November 2006 (UTC)

: Actually I have never experienced this and it's definitely not a crazy English function :-) Please could you try to figure out when exactly it happens so that I can reproduce it - that's the only way to fix it. Do you see it right after pasting, after using wikEd buttons, after switching to the classic textareaor, or after saving.

: The tab problem is a tricky one, but I will try to find a way to make the tab button work again.

: Cacycle 23:32, 16 November 2006 (UTC)

::The Spaces problem sounds like the problem with Francis E. Dorn I reported above in "First look at the latest version - diff diffs - spaces?" I'm not comfortable saving a page where someone looking at a diff will see changes reported in paragraphs I didn't touch. --CliffC 00:39, 17 November 2006 (UTC)

::: Actually it is caused by trimmed spaces at the end of lines. If will try to fix that in one of the next versions. Cacycle 04:11, 19 November 2006 (UTC)

: The Tab-to-summary function has been added to the next version. Cacycle 05:53, 20 November 2006 (UTC)

::Thanks, Erwin85 19:30, 20 November 2006 (UTC)

: I have found and fixed the space-eater bug. Please update (Shift-Reload). Cacycle 05:52, 22 November 2006 (UTC)

:: I'm using wikEd again and it looks good, I know everyone here appreciates the hard work that has gone into it. I tested for the 'spaces' problem with Francis E. Dorn again and it is fixed, good show. I turned up a similar but less severe problem elsewhere, diff [http://en.wikipedia.org/w/index.php?title=Donnington_Castle&diff=89591042&oldid=83241119 HERE] shows a change in a paragraph I didn't touch. Thanks for listening to these small but pesky problems. --CliffC 04:47, 23 November 2006 (UTC)

: Thanks :-) Your problem is cause by removed spaces at the end of a paragraph. I will change that soon. Cacycle 05:11, 23 November 2006 (UTC)

:: Fixed in version 0.9.10 Cacycle 05:21, 24 November 2006 (UTC)

Dosent work for me. Appears but then dissapears. Unable to edit useing script on FF. My JS file

The Fox Man of Fire 21:40, 17 November 2006 (UTC)

: Disable the User:Topaz sectionsplitter by deleting the following line: inc("User:Topaz/sectionsplitter.js");". wikEd and this script are incompatible. Cacycle 22:51, 17 November 2006 (UTC)

leftHow about a wikEd user box? You might find more people using wikEd -Will Pittenger 06:34, 18 November 2006 (UTC)

{{User:Cacycle/wikEd userbox}}

Paste the following text to your page:

{{User:Cacycle/wikEd userbox}}

Cacycle 00:33, 19 November 2006 (UTC)

Please add a button to apply <code> tags to the selection. -Will Pittenger 06:39, 18 November 2006 (UTC)

As wikEd toolbars grow, a problem crops up at Wikia.com. They require viewers to surrender part of their screen's width to Google ads (and a few others too). This prevents your toolbars from fitting as designed. (In fact, the newest version doesn't even fit on Wikipedia for me.)

It would help if I had a monitor that was designed for more than 1024x768. You might have to resort to two lines. Now if you know how to move my sidebar into drop menus along the top as shown here... then I could reclaim some space. -Will Pittenger 06:43, 18 November 2006 (UTC)

: Fixed in 0.9.18. Cacycle 02:50, 8 January 2007 (UTC)

Sometimes, when editing an article with wikEd, the page's history lists changed sections that weren't actually changed. For example, if you look at the [http://en.wikipedia.org/w/index.php?title=List_of_Chinese_martial_arts&diff=88716841&oldid=88639865 List of Chinese Martial Arts history from my last edit], you'll see numerous lines listed in change notation even though no changes were made to those lines (edit was made with wikEd 0.9.8). -Erik Harris 01:04, 19 November 2006 (UTC)

: That is caused by trimmed spaces at the end of lines. If will try to fix that in one of the next versions. Cacycle 04:10, 19 November 2006 (UTC)

:: Fixed in version 0.9.10 Cacycle 05:19, 24 November 2006 (UTC)

If I paste from the clipboard, or delete text with the Delete key, wikEd moves my cursor to either the top or bottom of the window. -Will Pittenger 05:22, 20 November 2006 (UTC)

:The same thing happens if I delete the "" before an internal wikilink. For instance, if you [http://en.wikipedia.org/w/index.php?title=Wikipedia:Verifiability&action=edit edit WP:V], on the first line, move the cursor over, delete the double bracket from "[[Wikipedia:Vandalism", and then hit delete again to delete the "W". It won't delete the letter because the cursor is somewhere else. This is a persistent problem. --Flex (talk|contribs) 14:12, 15 February 2007 (UTC)

:: This is a browser bug, one of the many rich text editing related ones. Some of them, including Flex's problem, have already been fixed in the upcoming Firefox releases. It is always important to have a simple test case to replicate the bug, however, I could not yet find a reliable way to replicate Will's problem.

:Ok, and thanks for your excellent work! You are indefatigable and very helpful. :-) (BTW, I see this problem with Firefox 2.0.0.1.) --Flex (talk|contribs) 15:21, 15 February 2007 (UTC)

How about modifying the Insert section? Some of it is duplicated by wikEd. Other parts just take up room. Many times I am trying to get to Wikipedia's preview window (for something LivePreview handles incorrectly) and I have to scroll past all that. The later would be solved if that section could collapse when not needed.

Perhaps you could do the same with the template list. -Will Pittenger 06:49, 20 November 2006 (UTC)

:: Go to 'my preferences' and check 'Show preview before edit box' under 'editing'. Cacycle 23:24, 23 November 2006 (UTC)

Sorry. I originally had that, but got tired of scrolling past long articles to get to the edit box. This would be mute if LivePreview could more completely replace the standard preview. -Will Pittenger 04:02, 24 November 2006 (UTC)

:: Then update to 0.9.10, it has a jumper at the top of the standard preview section. Cacycle 05:19, 24 November 2006 (UTC)

I have tried out the installation and put the content of the Simple Version of the Installation Code into my

userpage http://mydomain/wiki/index.php/Benutzer:Karsten/monobook.js and make many refreshs in my Firefox 1.5.0.7 but nothing happens :-(

Maybe the reason is that i am using a german installation (you see Benutzer instead of user or it is that i am using a MediaWiki Version 1.3.11 ?

(It will be not a problem to install the current stable version)

The complete installation-process looks for me very suspect.

• Why should an insert of an {{subst:wikEd}} in my page install something ?
• And how the simple version will do it ? (A little more explanation to understand would help)
• Will the Javascripts be copied to my wiki on the Server ?
• And what's about the corresponding images ?
• The function of "Pasting formatted content, e.g. from MS-Word" is fine but after doing it the source is not good to read. It would be fine if there would be also a translation without the HTML functionality. Just using the simple formatting options bold' italic underline and the important feature of processing tables.

Maybe i'm to stupid or i can't see the forest because of too many trees?

Kmalcher 18:00, 20 November 2006 (UTC)

:: The template substitution of the ultra-simple version does only work on the English Wikipedia, try {{subst:en:wikEd}} instead from the other language Wikipedias. It does not work for a non-Wikipedia wiki. Check the template page Template:wikEd and the general Wikipedia help on templates for how it works. The javascripts specified in the simple version will always be loaded to your computer from the English Wikipedia, independent of which wiki you use, including non-Wikipedia wikis. The images are hosted on the Mediawiki Commons. To 'unformat' the pasted content simply press the [T] button and to wikify it press [W]. There cannot be a simpler solution because wikEd relies on the browser's integrated rich text editor. Hope that answers your questions, Cacycle 00:51, 21 November 2006 (UTC)

After i have written the text i have tried out the installation in this wiki here and - of course - it works.

But this didn't answer my questions how to use this editor in other wikis.

It's a pity that this editor only work in a Original-Wiki, because i find it is great. It is at least simple to implement and as i have understand without patching the Original Wiki. But the main thing is that it can do a really conversion into the wiki syntax. The other editor-implementations i looked for are working only in HTML

Up to now i thought that the [http://www.mediawiki.org/wiki/MediaWiki MediaWiki] is basing on the same software of the Original-Wiki ?

So what can i do to get a Wiki with your Editor ?

Kmalcher 09:48, 21 November 2006 (UTC)

: You misunderstood me, wikEd works with any MediaWiki installation (at least if it is a recent one). The clutter after wikifying Word content is a bug, i will check that later. Cacycle 19:03, 21 November 2006 (UTC)g

::Sysanalyst 21:37, 21 November 2006 (UTC) This is not true. I have many MediaWiki installations and WikED won't work on any of them. There is some special add-on that is required but I've not found out what it is as of yet. The folks on the MediaWiki help board refer me back here to no avail. I really wish I could get this to work, but it just doesn't.

::: Sysanalyst: what JavaScript console error do you get when you try the current version. Can you please post the html source of an empty edit page here (inserted between <nowiki>

...

::::Sysanalyst 19:44, 22 November 2006 (UTC) Here is a screen shot of the error message;

Image:Wiked java error.jpg

::::The error is different today than the other day, most likely due to changes in wikED. The buttons function to a degree, but the changes are not saved (we hit the java error prior to save?). I've been able to reproduce this error on several different Wiki's. I'd love for you to have access to my Wiki's, but they are behind a firewall. If you'd like to try using WebEX or NetMeeting let me know and you can Wiki away.

::::: Fixed that one for you, try it again after Shift-Reload. Please copy the error text with Ctrl-C (if there is one). Cacycle 22:49, 22 November 2006 (UTC)

:::::: Thanks and outstanding work Cacyle! The Java errors are all gone and WikED is working very well. Thanks for your hard work and dedication to WikED. Sysanalyst 14:54, 27 November 2006 (UTC)

O.K. It's fine that i am not alone with the problem and that a solution is discussed :-)

But - the question of some short installation-instructions on an other wiki are still open ...

Javascript-programming and the internal functions of mediawiki are not my world, but maybe i can help to debug the problem ?

Kmalcher 15:12, 23 November 2006 (UTC)

: If you really need an "ultra-simple installer" on your wiki then read about templates and template substitution and copy the Template:wikEd page to your wiki. Re: helping: go ahead... Cacycle 17:19, 23 November 2006 (UTC)

What i really mean is how to install the editor independent from http://en.wikipedia.org, for instance on a local Webserver with no internet-connection.

So i can't use your simple-installation. And it is generating unnecessary traffic on the wikipedia.

When i look in the main-script wikEd.js i can see that it is hardwired to wikipedia. To install it locally i must

• Extract the *.js scripts
• Extract all the png-images
• Edit all the hardwired pathes
• Install / transfer all somehow in a local mediawiki

Is this correct and is there no better or easier way ?

Kmalcher 11:09, 24 November 2006 (UTC)

Yes, you have to copy all .js files from the wikEd installation code to your own server, the same is true for the images, just follow the 'Images' link in the wikEd jumper box on this page. All paths are user-customizable from user or general .js pages, check the customization section. You could also change the paths directly in the main program, they are all on top of the code. If it works, please could you write a how-to to be put on the wikEd page. Thanks, Cacycle 22:16, 27 November 2006 (UTC)

OK - this should be done. An I think it would be helpful when you concentrate on developing the editor and shawn and myself look for the installation-procedure on local servers.

As i have written in shawn's section i have not to much time to do that but i will try to give my best ;-).

Some points:

• You should tell me (us) when we have a stable Version of the Editor for the moment. It make no sense to make something like a package when the source is not stable and will be changed often.
• We must define an alternative installation in the way that you have normally console- or ftp-access to a server where we want to install the editor. So it would make sense to put all the *.js and *.png into physical pathes on the webserver ?
• Maybe we can use the unix patch utility to make a new "local version" of the editor instead of editing every new release. So the source must fit to do this easily ?
• When we defined how to do it i will write the correponding HowTo.

Kmalcher 11:02, 28 November 2006 (UTC)

I've also got problems with installing WikEd on a local mediawiki installation, unfortunataly; no errors, nothing at all! It seems monobook.js on my userpage does not "load" anything of the external file (ps. the local webserver has access to the internet). Is there anyway to make wikEd the standard editor for the mediawiki installation? Boris 19 feb. 2007 (update, I've read in a post further down that adding: $wgAllowUserJs = true $wgAllowUserCss = true to the LocalSettings.php would help. Maybe you should at it to the installation description since this did the trick!!)

I noticed that when I edit an image link with links in its description, the syntax highlighting is broken. As a test, take the code below out of the nowiki link and see what happens.

First [[Christmas treewith electric lights, in the home of Edward H. Johnson in New York City, December 22 1882.]]

-Will Pittenger 07:30, 23 November 2006 (UTC)

:: Thanks, I have already noticed that myself. I will try to fix that (and several of your other suggestions) soon. Cacycle 20:13, 23 November 2006 (UTC)

It appears that wikEd lost the trailing angle bracket of an html comment, near the bottom of the diff [http://en.wikipedia.org/w/index.php?title=User%3ACliffC&diff=89654487&oldid=89240248 HERE], causing part of the article to disappear from view after being saved. Everything up to the "-->" closing a later comment was considered part of the first. BTW, Happy Thanksgiving! --CliffC 17:35, 23 November 2006 (UTC)

:: Thanks :-) I have tried hard, but I could not reproduce that. Maybe you have done it accidentally yourself? Can you reproduce that by editing the old version again? Thanks and many barnstars... Cacycle 20:11, 23 November 2006 (UTC)

::: Hmm, I can't make it happen again, so maybe I did do it by accident. I thought it might have something to do with the fact that the article started with a section header – I clicked on its '[edit]' to work on just that section, then removed the header along with making a few other changes. I'll keep an eye out. --CliffC 01:46, 24 November 2006 (UTC)

::: FWIW and for the sake of completeness, the trailing ">" was the last character of the section I edited. --CliffC 03:41, 28 November 2006 (UTC)

I have noticed that some situations odd things happen when I paste into wikEd pages. Some are only cosmetic. Something like that would be what happens when you paste a link. However, others are more serious, at least if you click the Update Syntax Hightlighting button.

First, if I paste an entire header from a page, it adds a newline before the header text (and sometimes afterwords). It also shows a newline after the header text. If you then hit the Update Syntax Highlighting button, it adds equal signs before and after the text.

Next, please paste the entire text between the arrows into wikEd: →text← and press Update Syntax Highlighting. wikEd will reproduce the <small> tags I included.

As you may recall, a while back, I suggested something along the lines that would have wikEd detect rich text and offer to either strip it or convert it to Wiki syntax. I think this option would help both problems. -Will Pittenger 04:59, 24 November 2006 (UTC)

:: Unfortunately, all these suggestions are nearly impossible to implement. wikEd relies on the browser-internal rich-text editor. So any changes to the edit frame that do not go through its interface erase the undo/redo history. And I hope you are not seriously suggesting to implement pop-up windows... Cacycle 05:17, 24 November 2006 (UTC)

Could you trigger a clean up code after a paste? As for the poppt thups, a script that adds tabs to warn users pops up a dialog to ask which page to warn the user about. (I don't know which script that was.) A JS window as a CSS layer would preferred over a Windows dialog. (With that other script, I can't go back to check the page name.) -Will Pittenger 05:39, 24 November 2006 (UTC)

:: No, for the reason mentioned above. Either it destroys the undo history or it adds to it. It is also not easy to detect pastings (e.g. mouse drops). Cacycle 06:11, 24 November 2006 (UTC)

::: On a second thought, one could detect new html content on the page after every mouseup and keypress Ctrl-V and then syntax highlight it with an anchored box offering the two options (wikify or textify). I will think about it and all implications. At least the syntax highlighting part sounds interesting, maybe it should blink or get a red or black background... Cacycle 16:54, 24 November 2006 (UTC)

The new buttons to take users from the standard preview to the edit box ends up on top of the edit box when I add a new section and have not previewed the text. -Will Pittenger 05:47, 24 November 2006 (UTC)

: Fixed, please reload. Cacycle 06:07, 24 November 2006 (UTC)

Please hide the new RegEx button for AWB if I am running something other than AWB. -Will Pittenger 05:48, 24 November 2006 (UTC)

Why? It is completely independent, see the help page. Cacycle 05:57, 24 November 2006 (UTC)

If it works in Firefox, why is it disabled for me? -Will Pittenger 08:00, 24 November 2006 (UTC)

: See the help page :-) Cacycle

Do you have an offical presence on Wikia.com? If not, you might consider creating one. It would also help you by providing a place to test your code. As it turns out, the user name Cacycle is available. -Will Pittenger 05:07, 27 November 2006 (UTC)

Thanks, but I think I don't have time for that. I am already wasting too much time for this :-) Cacycle 22:18, 27 November 2006 (UTC)

:It would not be quite as useful, but I could serve as your representative there. I would probably be telling you about any problems there as well has hosting your Wikia pages. For all I know, you might need a Wikia specific version. I would not be able to edit that (I know no JS). But I could host the code. Not a whole lot of help, but it's better than nothing. -Will Pittenger 01:03, 28 November 2006 (UTC)

First off, I just want to say that I really like your editor - it is very helpful when editing articles.

I like it enough that I am trying to implement it on my company's internal wiki so it will be easier for other employee's to enter information. However, I am having trouble getting it to work properly. My assumption is that I have something set up improperly in either the web server or in Mediawiki but I am out of ideas on what to check. Here are the specifics:

Web Sever: IIS V5.1

PHP: 5.2.0 (isapi)

Database: MYSQL Server 5.1.12

Wiki Software: Mediawiki 1.5.8

Web Browser: Firefox 2.0

I have added the following settings to my localsettings.php file:

$wgAllowUserJs = true

$wgAllowUserCss = true

The web server is not public, but it has access to the internet. I have added all the code to monobook.js (just like I do on the Wikipedia, where it works). I've forced a refresh of monobook.js but here is what is happening:

Any page I go to, I can see that the browser is attempting to (or actually is) accessing the site en.wikipedia.org (shows in the status bar at the bottom of screen as the page loads). However, when I go into the edit screen, none of the wikEd buttons show up - it is just the default Mediawiki editor. I do not get any error messages, it just isn't working.

Any assistance would be appreciated.

Thanks,

Shawn

Mck321 15:26, 27 November 2006 (UTC)

:Sysanalyst 20:51, 27 November 2006 (UTC) Java Browser Console Output? Wiki log output? Hint: $wgDebugLogFile ="/tmp/wiki-st.debug.file";

::Mck321 00:06, 28 November 2006 (UTC) The Wiki log output wasn't very useful. However the Java Error Console told a different story. Here is the error I am getting: "wgServer is not defined" and the error hits at line 631 of wikEd.js where the javascript is attempting to use wgServer. I've tried manually overriding my wgServer settings in localsettings.php but the error persists.

::: I have now changed the script so that javascript doesn't throw the error, but that's not a clean solution. You should make sure that wgServer and the other wgXxx variables are correctly set, check the html source of any page. Did you use the right MediaWiki settings file? One has only the initial settings but is no longer used. Cacycle 00:58, 28 November 2006 (UTC)

:Hello, maybe we can establish a solution together ?

:When you look at the topic [http://en.wikipedia.org/wiki/User_talk:Cacycle/wikEd#Installation_does_not_work >Installation<] you can see that i am struggling at least with the same problems.

:My main problem is that i have no console access to my server under the week so i am very slow to work and implement a solution.

:Kmalcher 10:35, 28 November 2006 (UTC)

::Mck321 17:15, 28 November 2006 (UTC) I was able to track down the source of my problem. The problem was the version of Mediawiki that was running. I upgraded to 1.8.2 and wikEd is now functioning properly. Thanks for the assistance!

I got an 'edit conflict' error adding to a section in Talk:Spyware; I think I had two copies of the section open in separate windows (I lost track of where one window was after entering only a few words so I just opened the section again). When I did a Save Page for the second set of edits I got the Edit Conflict message and the earlier edits were saved instead. Nothing lost and no big deal, just a little confusing. --CliffC 17:31, 28 November 2006 (UTC)

: Probably not wikEd related :-) Cacycle 06:46, 30 November 2006 (UTC)

FYI, I run Wikipedia toolbar 0.8.0 (force-enabling it in Firefox 2 with Nightly Tester Tools), and I find that disabling wE (0.9.11c) also disables the classic edit buttons (the blue row) (which offer more options than the toolbar). Conversely, toggling between the classic text area and the wE, the WP toolbar doesn't recognize the wikEd editor (toolbar buttons are not available at all when text is selected, unless the classic text area is live). I'm guessing that it requires more overhead to preserve text selection in the wikEd and classic layers when toggling, or to "hot-wire" the selection of text simultaneously in both layers, so that a user may click whichever Bold button is closest (or visible!!) to the text they're editing, regardless of the editor state (hope this makes sense).

One other buglet still is in evidence, which I find a distraction: After toggling the syntax highlighting, and the classic text edit area to OFF and/or ON, I really would like whatever status is current to be preserved after hitting the preview button. wikEd always "resets" these toggle positions during a preview execution, and this really isn't good program behavior (all the user wants is preview, nothing else). Since the new "master switch" has a memory, I'm hoping the other ones might too before "final candidate" arrives.

 Schweiwikist   (talk)  17:48, 29 November 2006 (UTC)

: Oh, good idea about the toggle button. I will add that asap. The toolbar thing should be doable similar to the current tweak for the standard toolbar. Cacycle 06:45, 30 November 2006 (UTC)

:: Button memory has been added to the next version. The button states will only be remembered during the current browser session. Cacycle 08:19, 2 December 2006 (UTC)

There appears to be a bug when wikEd initialyzes, it duplicates any <gallery> tags it sees. "<gallery>" becomes "<gallery><gallery>". -Will Pittenger 21:19, 29 November 2006 (UTC)

: Yes, that bug irritate a lot. :/

:: Fixed, please update. Cacycle 01:53, 2 December 2006 (UTC)

Fixed. -Will Pittenger 04:38, 6 December 2006 (UTC)

When I go to an edit page with the editor enabled, I don't see anything in the edit box. I have to go to the edit page with the editor disabled and then enable it before I type anything. --- Year2000Prob ^(email) 22:55, 29 November 2006 (UTC)

:I don't have that problem. Are you using the dev version? -Will Pittenger 23:50, 29 November 2006 (UTC)

:: See User:Cacycle/wikEd#Incompatibilities, wikEd is not compatible with the Topaz sectionsplitter. Cacycle 06:25, 30 November 2006 (UTC)

{loses colons to Davey Jones' locker} Fixed. - Year2000Prob 01:25, 3 December 2006 (UTC)

The translation option for the [Preview] and [Changes] buttons (and symbols) are left (or remove the name changing, I think it's not necessary). --Olliminatore 14:23, 30 November 2006 (UTC)

: Your script is in the german help page included, please could you hury with this fix? :). I saw the relevant lines on 1302 (I think the symbol buttons are a bit redundant/ threefold). Thanks --Olliminatore 00:39, 2 December 2006 (UTC)

:: Fixed in next version. I have added the text to the end of the translation example. Cacycle 02:01, 2 December 2006 (UTC)

The auto summary for redirect seems not working correct. --Olliminatore 18:22, 30 November 2006 (UTC)

: Right now it only works if the summary is empty. I have fixed the next version so that the redirect text will always be appended. Cacycle 03:56, 1 December 2006 (UTC)

An apparent bug in Firefox may affect WikEd behavior (at least under Mac OS X Tiger). If WikEd's buttons are causing unnecessary scrolling (to top), check the following in Firefox Preferences: Preferences/“Advanced” tab/“Always use the cursor keys to navigate within pages” checkbox. Unchecking (disabling) this item eliminated the unwanted scrolling bug, which also appeared for this user when browsing a non-WP website (so it's not a bug in WikEd). I can now use WikEd trouble-free (except for the necessity of typing a fresh character into the edit box before selecting/searching/replacing existing text!).
 Schweiwikist   (talk)  05:12, 6 December 2006 (UTC)

I'm using Firefox 1.5.0.8 and Mediawiki 1.6.x. I've tried to put the Complete Installation code given into User:MyUserName/monobook.js but it seems the editor just replaces any