Extension talk:WYSIWYG/2018

• archive of pre lqt talk

Enable image upload

Hi I am using MW 1.30 and WYSIWYG bundle 6, I want to enable ability to upload images, wikieditor has the option through upload file but WYSIWYG does not seem to have that option, is there anything I can do to enable it.

thanks 61.2.42.21 (talk) 17:59, 19 February 2018 (UTC)

One way to upload single image is to use Image- button of Wysiwyg. If image does not yet exist in your wiki, then you should first create image ling using that button and then save the page.

After that in normal viewing mode of mediawiki you just click that new image- link and if you have enabled image updload in your wiki, it should start import of image. Riparap (talk) 09:11, 23 February 2018 (UTC)

Adding unwanted div class "mw-parser-output" in MediaWiki v1.30

Hi, since I installed WYISWYG extension on my mediawiki, each time I try to edit an article it creates a new div class: <div class="mw-parser-output">. If I want to edit again, it just keep adding new <div class="mw-parser-output"> in a row.

How to prevent WYSIWYG from doing this? Acezz67 (talk) 14:03, 5 March 2018 (UTC)

This is due to the Parser::parse() function being called. In MediaWiki v. 1.30 the default is to append a <div class="mw-parser-output"> ... </div> whenever it's done.

A workaround (that appears to work, but I have no idea if there are side effects, so there's no guarantees) is to edit the file at includes/parser/ParserOptions.php to always set 'wrapclass' to false. There are two places to do so. At approximately line 790 and line 1060. I would suggest copying the line and commenting it out (by preceding the line with //) just in case it needs to be reverted. 192.107.155.4 (talk) 21:30, 12 March 2018 (UTC)

Specifically the issue appears to be with the second new feature noted here: MediaWiki 1.30/zh 192.107.155.4 (talk) 21:32, 12 March 2018 (UTC)

This has been fixed in Version 1.5.6_0 [B551+19.05.2018]. Riparap (talk) 14:36, 20 May 2018 (UTC)

Keeping wysiwyg up to date

Hi, Any advise on keeping up to date with any updates to this extension?

Respects

Ian Harper 2A02:C7F:81E:3D00:31A3:A06:FA9F:614A (talk) 04:43, 7 April 2018 (UTC)

opps sorry, well done and thanks 2A02:C7F:81E:3D00:31A3:A06:FA9F:614A (talk) 04:43, 7 April 2018 (UTC)

I have maintained this plugin just "for fun" because I am no expert with html-javascript-php-mediawiki languages. Help is always appreciated and wellcomed. If and when I have time I will try to make it compatible with MW 1.30, at this moment it seems that some kind of manual hacking is needed to make wysiwyg work with MW 1.30. Other than that, I do not have any plans or time to think of other updates. Riparap (talk) 19:53, 10 April 2018 (UTC)

How do I change the skin to "Moono" ?

I tried many options that I found on the Web, but could not change the skin.

I am confused as it is not a pure ckeditor implementation, right?

Also, the toolbar configurator does not work - the toolbar is not displayed. Melvincv (talk) 07:32, 9 April 2018 (UTC)

Actually, wysiwyg is pure implementation of ckeditor but it includes customized wikitext -> html -> wikitext plugin (=mediawiki). This plugin is very sensitive to contents of page that you create in wysiwyg mode. It can not handle all kinds of html content properly. F.ex external plugins of CKeditor that are unknown to wysiwyg may cause problems and corrupt the page when saved when html 'wysiwyg' mode is converted back into wikitext. There are also some commands of wikitext which will not be handled properly when wikitext is converted into html (f.ex some special formats that can be used with images, and I suspect there are others too).

If I remember right, wysiwyg works properly only with skin "kama". However you may try to manually edit ckeditor/ckeditor.js and change text CKEDITOR.skinName = 'kama'; to CKEDITOR.skinName = 'moono';. You have to empty cache of browser after that modification. Maybe it works for you.

If "toolbar configurator"is plugin of ckeditor, you have to manually download and install that plugin and then edit file ckeditor/config.js. You have to at least add new CKEDITOR.plugins.addExternal = ... and modify contents of variable extraPlugins= ... in order to get new plugin active. I do not know if new plugin will work and what kind of effect that plugin has for contents of wiki page...but maybe you can test if it works. Riparap (talk) 19:43, 10 April 2018 (UTC)

Hi there @Riparap,

It's funny because I came here to ask these very two questions.

The skin changing advice worked like a charm, thank you! As for the toolbar configurator - allow me to give you some details about this:

Here in the user's manual they say about customising toolbar:

Extension:WYSIWYG#Customize the toolbar

It is said to be perfectly explained here:

https://docs.ckeditor.com/ckeditor4/latest/guide/dev_toolbar.html

But the instructions provided there are not valid. Being able to configure toolbar by simple drag&drop looks amazing as an idea, though this tool doesn't seem to work. All it shows is the editor window (doubled for some reason) without a possibility to drag or drop anything.

Though somehow I think the modified config this tool provides would not work anyway.

See, I struggle for months now looking for any way to remove some buttons from my WYSIWYG instance and make one or two of my own (ex.,

"Spoiler" button is a must) and still can not find anything. So if you took a look on this Toolbar configurator thing, or gave me a hint on how I can customise the toolbar manually, that would be much appreciated. Toomanynights (talk) 13:36, 31 July 2018 (UTC)

If you create your own config.js for CKeditor by using some external drag and drop tool, it will not work with wysiwyg, because it is missing everything that mediawiki plugin of CKeditor needs (mediawiki plugin for CKeditor + CKeditor itself = WYSIWYG).

You can remove buttons from main menu of CKeditor by removing name of button in ckeditor/config.js of wysiwyg in variable 'config.toolbar_Wiki'. F.ex if you remove name of button 'TransformTextSwitcher' that button will disappear in menu of CKeditor. Note that you may have to empty cache of your browser after you changed config.js in order to make the modification active.

Spoiler is plugin (=add on) of CKeditor but it has not been included in bundle fo CKeditor which comes with wysiwyg. So you have to sepratedly download, install and configure it. In config.js you have to add new CKEDITOR.plugins.addExternal... command for that plugin, declare that plugin as external plugin in variable extraPlugins and add name of that plugin into variable 'config.toolbar_Wiki' at some convenient place of your choise. After these actions button for that plugin should be available in menu of CKeditor. And remember always empty cache of your browser after modifications of config.js.

External plugins of CKeditor may not work properly with wysiwyg, because they will most likely insert html code in page which can not be converted into wikitext. It may also happen that block of that html works in one browser f.ex chrome but fails in some other. Wysiwyg may not always handle these html blocks properly, but you can always test how it goes... Riparap (talk) 14:51, 1 August 2018 (UTC)

@Riparap Thanks a bunch, will try to follow your instructions :) Toomanynights (talk) 07:35, 2 August 2018 (UTC)

What about 1.30 support?

What to do with that version?

Has anybody ported it for 1.30?

Thanks at advance 193.105.201.12 (talk) 09:04, 5 May 2018 (UTC)

Version 1.5.6_0 [B551+19.05.2018] should work with MW1.30. Riparap (talk) 17:36, 8 May 2018 (UTC)

Caching problems?

Hey there, I have a problem regarding WYSIWYG on MW 1.30.

Version: Wysiwyg 1.5.6_0 [B551+10.12.2017], CKEditor 4.6.2 (revision 20af917).

I think it has something to do with caching, but not sure. Very similar to other caching problems I hva had working with mw.

If I do an edit in LocalSetting.php (Doesnt matter what it is, could be a random new line), and saves it.

First article I come to, it shows the fully wysiwyg editor, but after that, I only get the fancy wikitext/html editor. Which destroys article if I save.. Links get fuked up.

Anyway, afaik, this described above is what Ive found out.

'''

$wgMainCacheType = CACHE_NONE;

$wgParserCacheType = CACHE_NONE;

'''

Thats my caching settings in localhost. Tried a few different settings, but still the same.

Any help/tips?

Thanks

// Alf 195.0.160.170 (talk) 11:25, 16 May 2018 (UTC)

Can you test if version 1.5.6_0 [B551+19.05.2018] works any better with MW1.30. You also have to use WikiEditor which comes with wysiwyg bundle. Riparap (talk) 14:37, 20 May 2018 (UTC)

Edit: wrong post was replying to. HellToupee1 (talk) 13:09, 16 September 2018 (UTC)

[WYSIWYG version 1.5.6] Cannot load Category List in WYSIWYG Editor

Hi, I have a problem regarding WYSIWYG version 1.5.6 on MV 1.30.

My WYSIWYG cannot load Category List in Editor Mode. How i fix its. I don't know which i miss something.

image 203.131.216.73 (talk) 05:17, 18 May 2018 (UTC)

I tested categories with version 1.5.6_0 [B551+19.05.2018] and there I can edit them on page (add new, select existing or remove). Maybe you can test this version ... and also check error_log and access_log of your web server, maybe they provide some hints about possible errors. Riparap (talk) 14:46, 20 May 2018 (UTC)

i had this same problem, it was caused by a category is also a subcategory of one of its own subcategorys which caused the category picker to loop, i made this modification posted 2 years ago: Extension talk:WYSIWYG/2016#h-Category_picker_loop-2016-07-28T00:50:00.000Z

The category picker wont break but the offending categories tree will be expandable 50times HellToupee1 (talk) 13:13, 16 September 2018 (UTC)

Your modification has been included in Version 1.5.6_0 [B551-16.09.2018].

Empty list of categories may also be caused by issue of topic "Add/Edit Categories button isn't populating the suggestion list of existing Categories" Extension talk:WYSIWYG/2018#h-Add/Edit_Categories_button_isn't_populating_the_suggestion_list_of_existing_Cate-2018-08-21T18:57:00.000Z Riparap (talk) 15:48, 16 September 2018 (UTC)

Hi, fix isnt quite working. the function calls itself so $i=0 will keep resetting the limit.

I got around that by feeding the limit into the function.

Line 280: should be                 $sub = explode( "\n", wfSajaxSearchCategoryChildrenCKeditor( $row->title, 0 ) );

Line 291: function wfSajaxSearchCategoryChildrenCKeditor( $m_root, $i ){

and 308:                 $sub = explode( "\n", wfSajaxSearchCategoryChildrenCKeditor( $row->title, $i ) );

And commend out or delete $i=0, i suppose a proper fix you could use an array to check against past values instead.

To test if fix works you can make two categories and make them sub categories of each other and they will repeat in picker like this over and over until limit.

......[Unix]

.........[Unix_24x7]

............[Unix]

...............[Unix_24x7] HellToupee1 (talk) 09:20, 17 September 2018 (UTC)

Version 1.5.6_0 [B551+18.09.2018] should work better, it is still using your approach (limit=50). Riparap (talk) 21:32, 18 September 2018 (UTC)

How to install WYSIWYG on Ubuntu 16 ?

I'm newbies for Linux Server. 203.131.216.73 (talk) 06:15, 30 May 2018 (UTC)

You have to install mediawiki and then wysiwyg as plugin there. You also have to to have some database supported By mediawiki on your server, and web server. One way to do it is to use lampp/xampp which contains all you need for mediawiki (database, PHP, web server etc.) Riparap (talk) 11:01, 31 May 2018 (UTC)

1. I use command "git clone https://github.com/Mediawiki-wysiwyg/WYSIWYG-CKeditor.git" for download WYSIWYG folder .
2. Then i use command "cp -R sourcefolder /extensions" for copy all of folder in WYSIWYG to folder extensions. (WYSIWYG, SemanticForms, WikiEditor, .gitignore, LICENSE, README.md)
3. And then i config my LocalSettings.php with $wgGroupPermissions['*']['wysiwyg'] = true; $wgDefaultUserOptions['cke_show'] = 'richeditor'; //Enable CKEditor $wgDefaultUserOptions['riched_use_toggle'] = false; //Editor can toggle CKEditor/WikiText $wgDefaultUserOptions['riched_start_disabled'] = false; //Important!!! else bug... $wgDefaultUserOptions['riched_toggle_remember_state'] = true; //working/bug? $wgDefaultUserOptions['riched_use_popup'] = false; //Deprecated $wgTrackingCategories = Array(); wfLoadExtension( 'WYSIWYG' );
4. Is that right ? But i have a problem with CategoryList they don't show any of Category. (I already create Category.) PHP 7.1.15-0ubuntu0.17.10.1 (cli) mysql  Ver 14.14 203.131.216.73 (talk) 06:41, 1 June 2018 (UTC)

Are you able to edit wiki page in wysiwyg mode = does toolbar of ckeditor show up when you edit your wiki page? ...or do you get toolbar of mediawiki only?

If you do not get toolbar of wysiwyg, then your setup is somehow wrong. In preferences => editing of mediawiki, you should have settings in this way for "Rich Editor"...

DO NOT select these: "Show WikiTextEditor", "Start with rich editor disabled"

DO select these: "Use toggle to switch between wikitext and rich editor...", "Remember last toggle state" and "Paste selected text as link text into link -dialog".

If you can start wysiwyg editor when you edit page of you wiki and the only problem is missing categories of existing page, then I suggest you to look log files of your setup (somewhere under your web server), perhaps there is some hints what goes wrong.

In the end of readme.md of wysiwyg, there is sample setup for your LocalSettings.php. Riparap (talk) 10:02, 2 June 2018 (UTC)

Open reference dialog by doubleclick on the footnote

Hi, I was able to add this feature to my wiki (after I asked for help). You can check here how it works : https://wikirouge.net/Journ%C3%A9es_de_juillet_1917

The changes have been made in these two files :

• WYSIWYG/ckeditor/plugins/mediawiki/dialogs/ref.js
• WYSIWYG/ckeditor/plugins/mediawiki/plugin.js

Here are the changes, in github format (It should be possible to "import" these instructions onto github, right ?) :

diff --git a/extensions/WYSIWYG/ckeditor/plugins/mediawiki/dialogs/ref.js b/extensions/WYSIWYG/ckeditor/plugins/mediawiki/dialogs/ref.js index c116dd8..ec614d6 100644 --- a/extensions/WYSIWYG/ckeditor/plugins/mediawiki/dialogs/ref.js +++ b/extensions/WYSIWYG/ckeditor/plugins/mediawiki/dialogs/ref.js @@ -148,6 +148,12 @@ CKEDITOR.dialog.add( 'MWRefmarker', function( editor ) { if ( span1.getName() == 'span' && span1.hasClass('fck_mw_ref') && span1.getAttribute('data-widget') == 'mwrefmarker' && sup1.getName() == 'sup' && ref1.getName() == 'ref' ) { element = ref1; + } else if (span1 != null && sup1 != null && sup1.getName() == "references") { + var ref = CKEDITOR.plugins.mwreferencesmarkerref; + if (ref != null) { + element = editor.document.find('#cite_ref-' + ref).getItem(0); + CKEDITOR.plugins.mwreferencesmarkerref = null; + } } } } diff --git a/extensions/WYSIWYG/ckeditor/plugins/mediawiki/plugin.js b/extensions/WYSIWYG/ckeditor/plugins/mediawiki/plugin.js index 4042546..cc9c312 100644 --- a/extensions/WYSIWYG/ckeditor/plugins/mediawiki/plugin.js +++ b/extensions/WYSIWYG/ckeditor/plugins/mediawiki/plugin.js @@ -1,4 +1,4 @@ -/** +/** * @license Copyright (c) 2003-2016, CKSource - Frederico Knabben. All rights reserved. * For licensing, see LICENSE.md or http://ckeditor.com/license */ @@ -1159,10 +1159,17 @@ if (!editor.document) return; editor.on( 'doubleclick', function( evt ) { + CKEDITOR.plugins.mwreferencesmarkerref = null; var element = CKEDITOR.plugins.link.getSelectedLink( editor ) || evt.data.element; if ( element == null ) { element = selection.getStartElement(); //For <ref> as text based element, img element is not used } + if (element.hasClass("ref-string-o-row")) { + var className = element.getAttribute('class'), match; + if (match = className.match(/ref-string-o-(\d+)/)) { + CKEDITOR.plugins.mwreferencesmarkerref = match[1]; + } + } /**** if ( element.hasAscendant( 'ref', true ) == true ) { //For <ref> as text based element, img element is not used @@ -1193,6 +1200,9 @@ if (!editor.document) return; element.getAttribute( 'class' ) == 'FCK__MWTemplate' ) { evt.data.dialog = 'MWTemplate'; } //03.02.14 RL<- + else if (element.is("span") && element.hasClass("ref-string-o-row")) { + evt.data.dialog = 'MWRefmarker'; + } else { Varlin (talk) 22:19, 17 June 2018 (UTC)

Great, this is cool function. It has been included in Version 1.5.6_0 [B551-01.07.2018] (#6 bundle) together with button to format selected text with "italic + angle quotes". Riparap (talk) 09:06, 2 July 2018 (UTC)

Image captions editable in WYSIWYG

Hi. I was able to add this feature to my wiki (after I asked for help). You can check here how it works : https://wikirouge.net/Journ%C3%A9es_de_juillet_1917

NOTE that it is not possible to add links in the caption (the parser breaks it) but this is not specific to this feature.

HOW TO DO IT ? Well, I can give you the two files (this one and this one) that have been modified, but I have not kept precise information about which lines precisely have been changed... I should compare with last version on github (because my files are differents due to some tweaks I made) and make the commits, but I think I'll never have the time. Anyway, I hope it will be useful to someone.

NOTE that the mediawiki/plugin.js file in the link above is also affected by changes related to this tweak. Varlin (talk) 22:25, 17 June 2018 (UTC)

Great work.

It looks like this will convert all images to have option "frame" always. This will make it impossible to adjust size of image in document (Help:Images).

I was trying to tweak it but could not quite understand everything it is doing. F.ex. what is purpose of editor.document.getBody().on( 'keyup' ..'click'..'mouseup'..'drop' ..'afterCommandExec' triggers, are they all really needed or are some of them result of your tests?

It also leaves html code (div- block) in wikitext, I am tying to fix this by jumping over div- tags with class 'capturedImage' and rejecting div tags with class 'imageLegend'. Riparap (talk) 09:59, 2 July 2018 (UTC)

I have been trying to convert <div> + <img>image + <div>caption as widget. It looks like this <div> which is used to wrap everything together makes it impossible to have image as inline element (f.ex image in the middle of line).

I am just wondering if there is a way to make <div> to behave like <span>?

...I have tried display:inline + clear:both with styles but for some reason it does work. It looks like <span> tag has to be used when image needs to be inline element....but this will then require various modifications with image.js dialog when alignment related settings are changed. Riparap (talk) 19:41, 12 July 2018 (UTC)

Yes I wanted a really simple behavior : either a frame with a caption, either nothing. I don't have the use of other options like thumbnails etc.

I'm sorry I don't have the answer to your questions, since I did not implement that part of the code myself (too complicated for me)... Varlin (talk) 15:20, 24 October 2018 (UTC)

What about 1.31 LTS support?

Hi community.

Is there anyone out there who tried the new LTS version ? Wingsofcourage (talk) 09:01, 18 June 2018 (UTC)

Current version of Wysiwyg does not yet work with >=MW1.31. There are three issues discribed here. Help is highly appreciated... Riparap (talk) 14:23, 22 June 2018 (UTC)

Version 1.5.6_0 [B551+16.09.2018] can be tested with MW1.31.0. Riparap (talk) 12:04, 23 June 2018 (UTC)

mw 1.31 LTS; Wikifarm, images shared, only few images available at the editor

Hi riparap,

just installed Version 1.5.6_0 [B551++23.06.2018], but I've got problems on inserting images. When klicking the <image>-button only a few of all uploaded images are available. My images directories in the language directories are softlinked to the shared directory and in LocalSettings.php I declared "$wgSharedDB = 'wikiDB'; $wgSharedTables = array(); $wgSharedTables[] = 'extensions'; $wgSharedTables[] = 'images';". Mediawiki always creates new directories for uploaded pictures, e.g. /images/b/b7. Topsnet-holgerd (talk) 08:56, 17 July 2018 (UTC)

I understand only that you are trying to use images from other shared database. Is the problem with your MW setup?.... does images work properly when you do not use wysiwyg? ..if not, then problem is somewhere outside wysiwyg.

Do you get anything on selection list of images in wysiwyg. That list does not display all of your images. There is max limit of 40 items on that list. If you have more images, you have to narrow your search by entering some limiting string for image name in search box.

I suspect that it may be so that wysiwyg fetches image list only from one active database (CKeditorSajax.body.php=>wfSajaxSearchImageCKeditor). I do not know exactly how I could test your setup to verify that.

This has nothing to do with your case but it warns that "Be careful with sharing tables. The images, revisions, pages, and many of the other tables may have bad side effects if you share them.". Riparap (talk) 18:19, 18 July 2018 (UTC)

Chrome issue

Hi,

Just noticed that the latest version of WYSIWYG editor works poorly on Chrome (Mac). It still adds this "<div class="mw-parser-output">" thing, special tags do not show up, and the worst thing - it converts regular wiki text, like "== Heading ==", into "<h1>Heading</h1>".

None of things appear to happen on the very same page opened with different browser (Safari). Toomanynights (talk) 08:43, 1 August 2018 (UTC)

I have not noticed this problem with Windows version of Chrome. Issue with <div class="mw-parser-output"> has been fixed in Version 1.5.6_0 [B551+19.05.2018].

If you are using the latest version of WYSIWYG = Version 1.5.6_0 [B551-01.07.2018] and if this Mac related issue, then I am affraid I can not help, because I do not have possibility to test it.

Well... try switching back to original skin that wysiwyg is using, does it work any better then. Also disabling some external plugins may help to isolate the source of problem(mwtemplate,textselection,tableresize,texttransform), I remember that ealier at least one issue was caused by one of those. Riparap (talk) 14:37, 1 August 2018 (UTC)

@Riparap I've switched back to the original skin, and none of the plugins you mentioned are installed. And I use the latest version. Well... Guess I'll just have to use different browser :)

Thanks Toomanynights (talk) 07:34, 2 August 2018 (UTC)

Thumbnails get mangled after showing preview and/or saving page.

Hi,

When editing existing pages that have images that are bracketed for thumbnails, the editor will add brackets on each save that makes them unusable. An example is: [File:NameOfFile|Picture.png|800px] ... then it adds more brackets and [1]. How can we prevent this from happening? I looked around to see if there's any fixes for it but I didn't see anything.

Thanks! 69.55.70.36 (talk) 15:18, 16 August 2018 (UTC)

Your example [File:NameOfFile|Picture.png|800px] is little confusing to me because in my fresh installation of MW 1.31, that format is not recognized at all by MW. Could you point what situation of this page are you referring to with that syntax?

If I use this syntax [[File:NameOfFile|Picture.png|800px]], I can not reproduce your issue in my MW 1.31 with Wysiwyg 1.5.6_0 [B551-01.07.2018]. It hadles the syntax corretly.

Does it work similarly with different browsers (IE, FF, Chrome) ? Riparap (talk) 11:29, 9 September 2018 (UTC)

Interesting, it might have been an older format from pre 1.29 or something. Thanks for looking into this. It does happen on a variety of browsers. I will see if an older page with two brackets will work fine. 69.55.70.36 (talk) 17:46, 24 September 2018 (UTC)

Just tried it again, it looks correct in the WYSIWIG editor but once I save it it breaks all the images. 69.55.70.36 (talk) 17:49, 24 September 2018 (UTC)

It converts Image: to File: 69.55.70.36 (talk) 17:49, 24 September 2018 (UTC)

For posterity sake, we figured out the issue that was specific to our wiki. It turns out that we had a URI setting to convert File: syntax to file:// which of course broke things. Removing this fixed everything and we're now happy with the extension! 69.55.70.36 (talk) 13:43, 25 April 2019 (UTC)

Add/Edit Categories button isn't populating the suggestion list of existing Categories

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hello all,

When I click on the "Add/Edit Categories" button the "Select Category For The Page" box is empty. Is it supposed to populate with the existing Categories on the wiki?

The element (and it's associated children) is identifiable as:

class="cke_dialog_ui_select" title="Category List"

Here's my version info:

MediaWiki	1.31.0
PHP	7.2.8 (cgi-fcgi)
MySQL	5.6.40-84.0-log
ICU	4.8.1.1

WikiEditor

0.5.1

WYSIWYG editor

Wysiwyg 1.5.6_0 [B551-01.07.2018], CKEditor 4.6.2 (revision 20af917)

Thanks in advance for your help.

-Z -zachMade (talk) 18:57, 21 August 2018 (UTC)

Hi !

I have the same problem. My category list is empty and search box does nothing (no ajax request send). Have you found a fix for your problem ?

Thanks in advance. Wambaloo (talk) 14:29, 30 August 2018 (UTC)

Alas, I have not :( -zachMade (talk) 21:40, 31 August 2018 (UTC)

If in category dialog you type something in search filter box, it should populate the list of categories with category names matching your value of filter.

It looks like COLLATE setting of query for categories is conflicting with settings of database which will make the query fail. Workaround and more information can be found here.

Workaround has been included in Version 1.5.6_0 [B551+18.09.2018].

Any ideas how sorting definition should be implemented? Riparap (talk) 11:50, 9 September 2018 (UTC)

Thanks Riparap: that fix worked for me!

I wish I enough enough MySQL to help you out... Hopefully someone more MySQL-savvy will stumble upon this or the GitHub thread. -zachMade (talk) 14:55, 20 September 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

What's the difference or relationship of this extension to the Visual Editor?

This seems to be possibly an earlier attempt at creating functionality that is now covered by VisualEditor ? There is some functionality covered by this extension not covered by the VE but VE seems to be getting more mainstream support and is more current? A part of this page clarifying this information would be helpful to new devs or sysadmins looking to get more involved in working with the MW ecosystem. AslanFrench (talk) 22:26, 28 October 2018 (UTC)

I am not familar with setup or properties of VisualEditor so I can not compare it to Wysiwyg. As far as I can see, Wysiwyg is easier to setup. It has its limitations but works quite well with "standard" wiki pages.

There have been only couble of contributors working with this extensi lately.n. Riparap (talk) 09:16, 29 October 2018 (UTC)

Can't load WYSIWYG -> 500 Error

I'll be the first to admit I am not the best when it comes to web stuff so I've been trying to get the WYSIWYG editor to work to keep some of my homelab documentation on. From the github page I downloaded and extracted the folder to my Extensions. After that I copied over the config that was on that page as well but for some reason I have narrowed down that if I have "wfLoadExtension( 'WYSIWYG' ); " uncommented I get a 500 error. If I comment it out I can load my site just fine. Anyone will to help an absolute noob here? 2620:0:1A10:7723:5D0F:F6A5:8733:47AE (talk) 21:18, 15 November 2018 (UTC)

I should clarify now that I have created an account that I can't even load the index page it is just the 500 error. Milhouz (talk) 21:24, 15 November 2018 (UTC)

Have you checked permissions of WYSWIYG directory so that they are in same way as with other extensions you have there. Riparap (talk) 09:43, 27 November 2018 (UTC)