Extension talk:Wikiwyg

From MediaWiki.org

Jump to: navigation, search

Contents

[edit] How can I run, install or setup Wikiwyg??

Hello, I am using WOS-Wiki and I would like to use this extension.

Unfortunatelly there is no detailed description how to do this. They are talking about 2 files, which should be copied into the extensions folder and the patch file. The installation should be easy - at least the readme file claims this . But it doesn't work.

Here are some Informations about my Wiki.

  • MediaWiki: 1.7.1
  • PHP: 5.1.6 (apache2handler)
  • MySQL: 5.0.24a-community-nt

Can you tell me, how to run this plugin? thx


i installed it but changing vision (From wikiwyg to wikitext works, but from wikitext to wikiwyg ir wikitext to preview, doesn't)... it says that Special:EZParser doesn't exist...)

does someone know how to fix it?

[edit] please add Installation instructions

can someone who knows how, add some installation instructions for mediawikis.Bouncingmolar 00:49, 8 April 2007 (UTC)

[edit] Installation progress so far

I downloaded the stuff from http://svn.wikiwyg.net/code/trunk/ uploaded it to my host. I copied the entire wikiwyg directory to the public_html/wiki/extensions/ folder. Then I edited the /public_html/wiki/extensions/wikiwyg/share/MediaWiki/extensions/MediaWikiWyg.php file so that it looked like this:

 
    if (! isset($wgWikiwygPath)) {
        $wgWikiwygPath = "$wgServer/wiki/extensions/wikiwyg";
    }
    if (! isset($wgWikiwygJsPath)) {
        $wgWikiwygJsPath = "$wgWikiwygPath/share/MediaWiki";
    }
    if (! isset($wgWikiwygCssPath)) {
        $wgWikiwygCssPath = "$wgWikiwygPath/share/MediaWiki/css";
    }
    if (! isset($wgWikiwygImagePath)) {
        $wgWikiwygImagePath = "$wgWikiwygPath/share/MediaWiki/images";
    }
    $wgOut->addScript("<style type=\"text/css\" 

I then edited the Localsettings.php file

#Wikiwyg extension:
require_once("$IP/extensions/wikiwyg/share/MediaWiki/extensions/MediaWikiWyg.php");

I had previously tried adding the EZparser file as well, but it caused errors on line 89... ? do I need it? Without the EZparser installed, an option appears on the toolbox Wikiwyg Disabled I changed it to Wikiwyg Enabled but it didn't make any difference. Bouncingmolar 12:36, 9 April 2007 (UTC)

The code has been designed for $wgWikiwygPath to be set in LocalSettings.php file (as all local changes should be done) rather than explicitly changing MediaWikiWyg.php. While both approaches "work", people should change LocalSettings.php to avoid headaches when upgrading in the future. Cheers,--Biyer 19:33, 14 May 2007 (UTC)


[edit] Problem with installation

I installed the extension but nothing happens.

Some information about my wiki:

  • MediaWiki: 1.6.10
  • PHP: 5.2.0 (cgi)
  • MySQL: 4.1.22-standard

I followed the instructions but I don't see any changes while editing pages.

Has anyone an idea what happend? Is there something wrong with my version?


[edit] Does it work with 1.9.3?

I'm interested in seeing this work with 1.9.3. I've tried:

  • extracting the latest code from subversion into my extensions directory
  • including the MediaWikiWyg.php extension in LocalSettings.php
  • updating MediWikiWyg.php with correct $wgWikiwygPath
  • applying the "1.7alpha" patch by hand. The patched sections still appear relevant in 1.9.3

At this point I do see the "Wikiwyg Enabled"/"Wikiwyg Disable" toggle in my toolbox, and I can browse to the URLs for the Wikiwyg .js and .css files now referenced in my wiki page source. However when I edit a page I still get the default edit screen. Firebug is reporting no .js errors.

I'd appreciate any pointers here.

Thanks, Monopolist 20:42, 23 April 2007 (UTC)

Once "Wikipedia Enabled" is set, you should see the edit links in sections change from "Edit" to "Wikiwyg Edit" or "Quick Edit". NOTE: I've only been able to get Wikiwyg to work with sections, not with basic wiki pages. --Joel Franusic 21:34, 23 April 2007 (UTC)
Thanks! After mucking with it for a while the page started rendering differently - I think was being bitten by MediaWiki caching. I also had double-clicking set to edit the page so I may have been missing Wikiwyg on the main page before it switched to the vanilla edit page. Now I can edit individual sections in the page, but only in "Wikitext" mode. "WYSIWYG" mode isn't a choice and "Preview" mode doesn't work (I get an error about a missing "special" page when I try). Monopolist 21:57, 23 April 2007 (UTC)
Glad you made some progress! Have you checked the paths expected by fixupRelativeUrl(url) in MediaWikiWyg.js? (Also, be sure to update the main page with anything you've learned!) --Joel Franusic 22:26, 23 April 2007 (UTC)

Hello. Another user, who is to retarded to integrate wikiwyg on a mediawiki... I'm as far as Monopolist. I can see the "Wikiwyg Enabled"/"Wikiwyg Disable" toggle in my toolbox. The .css and the .js file can also be reached! The only Problem is, that I don't get the wikiwyg-edit-surface! What can be the problem?--141.6.8.75 12:09, 3 May 2007 (UTC)

[edit] Bugs with revision 161

The following bugs have been found using Mediawiki version 1.7.1 and 1.9.3:

  • Does not work on Internet Explorer (partially works on FireFox)
  • Patch needs to be applied manually.
  • Preview does not work (Can not find Special:EZParser)
  • Line breaks do not transfer to view in Wikitext (need 2 consecutive line breaks)

On 1.7.1 (did not validate with on 1.9.3), these additional errors occur:

  • Clicking on the Wysiwyg edit button takes you to the normal edit screen (works when you double click the section you would like to edit)
  • Can not use wysiwyg editing on the vast majority of sections (many markups such as bold tags disable wysiwyg features)
  • The patch for includes/Parser.php overwrites classes as produced via templates and subheadings on the Main page (in each case wiki markup is not interpreted, but rather displayed on screen)

If anyone has developed a workaround to any of these, please update my comments above and the extension page! Cheers--Biyer 18:47, 21 May 2007 (UTC)

It doesn't appear that the social text team is responsive, so I can't recommend this extension. I was able to get Wikiwyg working on Firefox 2 however using some pretty bad hacks (on my part) and will try and recreate/document my changes and put it up here shortly. I haven't gotten it to work in IE yet, but will try to look into that as well (any help is appreciated). After my changes are added, feel free to comment/fix any bugs or improve upon my code design. --Biyer 14:49, 11 June 2007 (UTC)

IE and FireFox now both work correctly. The additional "problems" I perceived in IE was due to my forcing logins to make changes. I will be testing my changes shortly on Mediawiki 1.7.1 and 1.9.3 and comment on my approach (hopefully) in the next week or two. Some improvements remain on the UI, but functionally everything is set --129.83.31.1 19:35, 29 June 2007 (UTC)

[edit] Discontinued?

Has this plugin been discontinued? A wysiwyg editor is in high demand for MediaWiki! Are there any other options available out there? Anyone know if it works with the latest version (1.10.1)? Thanks! -- 216.99.65.63 19:20, 27 August 2007 (UTC)

The version 0.20 works with MW 1.10.1 (see installation instructions section for version 0.20) - Bartek 09:23, 10 September 2007 (UTC)

Was able to get this to work (without switching capability) in version 1.10.1. However, appears to break completely on 1.11.0. Anyone else tried it yet? -- 216.99.65.63 19:17, 11 September 2007 (UTC)

[edit] Blank (white) Screen when using Wikiwyg

Mediawiki: 1.10.0 with LDAP Authentication Patch
Distribution: SLES Enterprise 10 SP1
PHP: 5.1.2

I have installed Wikiwyg as written here: New installation instructions for version 0.20, but the result is a blank (white) screen in the browser (Firefox and IE). Have anyone an idea what went wrong?

[edit] hook processing bug

first error:

Internal error
Set $wgShowExceptionDetails = true; in LocalSettings.php to show detailed debugging information.

after setting $wgShowExceptionDetails = true; we get:

Detected bug in an extension! Hook beforeTidyHook failed to return a value; should return true to continue hook processing or false to abort.

Backtrace:

#0 F:\www\webapps\mediawiki\includes\Parser.php(332): wfRunHooks('ParserBeforeTid...', Array)
#1 F:\www\webapps\mediawiki\includes\Article.php(3017): Parser->parse('== Setup Experi...', Object(Title), Object(ParserOptions), true, true, 451)
#2 F:\www\webapps\mediawiki\includes\Article.php(831): Article->outputWikiText('== Setup Experi...')
#3 F:\www\webapps\mediawiki\includes\Wiki.php(383): Article->view()
#4 F:\www\webapps\mediawiki\includes\Wiki.php(48): MediaWiki->performAction(Object(OutputPage), Object(Article), Object(Title), Object(User), Object(WebRequest))
#5 F:\www\webapps\mediawiki\index.php(89): MediaWiki->initialize(Object(Title), Object(OutputPage), Object(User), Object(WebRequest))
#6 {main}

solution is to edit MediaWikiWyg.php :

function beforeTidyHook($parser,$text) {
    global $wgServer, $wgScriptPath, $wgUser ;
    if ($wgUser->getOption ('in-page', 1) == 0 ) return ;
    $wgScriptPath != "" ? $fixedPath = $wgServer."/".$wgScriptPath : $fixedPath = $wgServer ;
    /* stuff changed in MW 1.9.3, the order of elements is different now */
    /* one more interesting thing - determine the maximum depth of the headers
     (remember, MW uses level 2 headers as suggested ones...) */
    $starting_level = wfDetermineStartingLevel ($text) ;
    $text = wfRecurrentParse ($text, $starting_level, 0) ;
    
// added by PC@ABS    
  return true;
}

see the "return true;" down the bottom. Add that and save. This is the only thing I had to do apart from the 0.20 instructions to get this to work. I haven't done full testing yet but it loads and exists. Hope this helps.

update: spoke too soon. Currently my install on mediawiki 1.11.0 is scrambling text. My install notes (in addition to the 0.20 install instructions) are:

  1. you need to copy the whole directory tree from where you land in the svn repository - a proverbial without an svn client
  2. you need to patch with the bleed patch and the syntax patch for wikiwyg itself - a proverbial without a patch util
  3. you need to add "return true" to the end of each of the four hook functions in MediaWikiWyg.php:
    1. 'beforeTidyHook',
    2. 'wfWikiwygToggle',
    3. 'wfWikiwygHandleEditingPrefs',
    4. 'wfWikiwygAddEditingPrefs'
  4. you need to add "global $wgLivePreview;" to the top of "function getEditingTab" in includes/SpecialPreferences.php
  5. you need to fill out your preferences in the editor tab

[edit] Not used on Wikimedia projects?

Why is this not used on Wikimedia projects? Knowing this will help us decide whether to implement it on Appropedia. If it's just a matter of being too server intensive, we can probably handle it, but if there's more serious problems, we'd like to know. (Apart from the challenges of maintaining the patches when upgrade, which we're already warned about). Thanks! --Chriswaterguy 01:40, 1 February 2008 (UTC)

This extension, while it is a great idea, is very broken still in its current state. It throws out JS errors and mostly doesn't just work. --Sayuri 16:12, 8 June 2008 (UTC)

[edit] Is this the same problem with wikEd ??

Here is a new new "error message" of today in my new Wiki, absed on MediaWiki 1.11 (Rec.: I am an absolute "newbe" (= "0" knowlege of php, apache, mysql just following strictly the manuals at MediaWiki.org how to maintain (mostly) the localsettings.php). ) _______________________________________

Internal error

Detected bug in an extension! Hook wfWikiwygToggle failed to return a value; should return true to continue hook processing or false to abort.

Backtrace:

  1. 0 .../wiki/includes/User.php(871): wfRunHooks('UserToggles', Array)
  2. 1 .../wiki/includes/SpecialPreferences.php(397): User::getToggles()
  3. 2 .../wiki/includes/SpecialPreferences.php(121): PreferencesForm->resetPrefs()
  4. 3 .../wiki/includes/SpecialPreferences.php(14): PreferencesForm->execute()
  5. 4 .../wiki/includes/SpecialPage.php(670): wfSpecialPreferences(NULL, Object(SpecialPage))
  6. 5 .../wiki/includes/SpecialPage.php(476): SpecialPage->execute(NULL)
  7. 6 .../wiki/includes/Wiki.php(201): SpecialPage::executePath(Object(Title))
  8. 7 .../wiki/includes/Wiki.php(45): MediaWiki->initializeSpecialCases(Object(Title), Object(OutputPage), Object(WebRequest))
  9. 8 .../wiki/index.php(89): MediaWiki->initialize(Object(Title), Object(OutputPage), Object(User), Object(WebRequest))
  10. 9 {main}

_______________________________________

When does happend this error: As soon I click in the user's profile on preference. Midday happened also the strange thing that I wrote longer articles and clicking the "safe button" sometimes a "blank page" appeared (means the whole article became empty) or only fragments of the text were kept. - Maybe the MediaWiki limitis automatically too long and too many links inside a text ?? I don't know

What might be the reason because I read "extension" I installed the WYSIWYG Text editor "wikEd". You can find the manuals and all details about here... http://en.wikipedia.org/wiki/User:Cacycle/wikEd

I installed wikEd as part of my FireFox (latest actual version), running under "GreaseMonkey". Maybe that's the problem behind. Instead during the first day since installing on 8th February it seems working proper.

Another aspekt why I think it might be connected with wikEd is the regular editing buttons (MediaWiki's own) in the text editing field are blocked. I cannot set my signature with time stamp etc. ... The problem even exists if I have swtiched off Greasemonkey totally, alternatively running Greasemonkey but turned off wikEd listed inside. Even I started Firefox new with switched off Greasemonkey. The error message meanwhile is the same.

Hope for your quick help. Thank you. - --ElJay Arem 22:05, 13 February 2008 (UTC)

// P.S.: Forgot to recommend. I did these tests of "neutralized Greasemonkey/wikEd" with different user status (Bureuacrat, regular User). Everywhere in the different user profiles the problem as soon clicking on "preferences".//

As wikEd runs in the browser, it cannot give you server errors. Also, Wikiwyg is not compatible with wikEd. Cacycle 02:27, 15 February 2008 (UTC)
This issue has been resolved in rev:36026. --Sayuri 16:12, 8 June 2008 (UTC)