Hi,
Sadly since retiring with health problems, I haven't been able to keep up maintaining this extension.
W.r.t. updating the Tinymce version from the one distributed with the extension, it was decided to stick with a stable version that was know to provide a reasonable set of features that worked well. There were frequent new releases of Tinymce which required significantt ongoing effort to keep up with. The latest free version can be downloaded from the official Tinyme website if anyone would like features available in it but it is likely this would require changes to the extension code base.
Thanks for your ongoing interest Dstjr and finding a fix.

Hi Gary (@Squeak24)
Sorry it's been a while!
After a fair amount of faffing, I believe I have a fix which has now been added to Gerrit (see previous gerritbot comment).
If you are able to test, let me know if this has resolved your problem?
Kind regards
Duncan

Hi Gary (@Squeak24)
Sorry it's been a while. I finally got some serious time to investigate this week! It's been a tricky one to track down. Without boring you with too many details, it is the interaction between how PageForms processes multiple item fields and how TinyMCE initialises itself on them that caused this problem. The latter had changed since version 0.3 of the extension which is why it worked in that version.
I have a solution now that works when creating pages and I have to do some work on when they are subsequently edited but it looks like there is a way forward with this bug. Will let you know when Gerrit has been updated with the patch.

Hi Gary (@Squeak24)
I've investigated a bit more and I think it was the major upgrade I did to the TinyMCE core software where they made some enhancements to how they load their software. I'll investigate further to see if I can come up with a fix.
Happy new year
Duncan

Hi Gary (@Squeak24)
That's a bit strange - v 1.0 of Tinymce extension was released in November 2020! The maintenance policy for TinyMCE is 'master' which means all releases should occur on the master branch on Gerrit. However, whoever made this release used a branch which is based on a truly ancient release of the TinyMCE extension (dated Feb 2019)!
Never mind though, this release does seem to work OK which gives me something to work with. I'll investigate further.

Hi Gary (@Squeak24)
Yes, I'd thought I'd seen this feature working at some point. I wasn't sure what product V0.3 you were referring too? I do tend to keep old configurations and versions saved so, if you can let me know products and version that did work together, I may be able to work out which changes have given rise to the incompatibility?

Hi Gary (@Squeak24),
I have had a look into this. Since TinyMCE works in an ordinary textarea input field in PageForms I'm not sure why it wouldn't work in textarea input fields in a 'multiple' field, unless PageForms is handling these differently.
Hi Yaron (@Yaron_Koren),
I wonder if you might be able to help. I'm not sure why TinyMCE wouldn't initiate on a textarea field in a multiple instance field, when it does in an ordinary textarea field in PageForms. I wonder if there are any differences in how multiple instance fields are implemented which might affect this?
Many thanks
Duncan

Hi @Squeak24, Please let me know if this is resolved so I can update the task status, thanks.

Hi Gary, just added fix to master branch

Hi Gary, fix has just been added to master branch. Let me know if you are still getting this problem?

Hi Gary
Sorry for the delay getting back to you. and thank you for creating the test wiki to demonstrate the issue.
I should have some time next week to look into this.

Hi Gary,
In the hope that this was the cause of the problem, I've added a patch to the master branch of the TinyMCE extension which should solve it. With this patch, TinyMCE will be initialised on class 'tinymce' without needing '$wgTinyMCESettings' to be defined in LocalSettings.php. This, in turn, should mean PageForms will use TinyMCE when asked.
Please do let me know how this goes? I'm away from mid-day today so won't be able to do more on this until next week if it is still a problem, I'm afraid.
If you have any urgent problems in future, please do use the TinyMCE Extension project page on phabricator as I seem to be more reliably alerted to tasks that are recorded there!
Kind regards,
Duncan

Good morning Gary
Thanks for the printouts. The JQMigrate warning is OK, at least it shouldn't affect the loading of TinyMCE in PageForms. Thanks also for trying with Vector - it was one of the things I was going to suggest, and confirms the problem isn't related to using Chameleon.
There is one issue causing PageForms not to use TinyMCE that I have found. If $wgTinyMCESettings is not set for class 'tinymce' in your LocalSettings.php file (see https://www.mediawiki.org/wiki/Extension:TinyMCE/Configuration for example) then page forms doesn't use TinyMCE even if it's available!
I'm not sure if this was a design 'feature' or omission, but I can look at making the declaration of TinyMCE on the 'tinymce' class part of the default configuration. Perhaps you could check whether you have '$wgTinyMCESettings' set up for class 'tinymce' in your LocalSettings and let me know? If not, then this is likely to be the problem. Meanwhile I'll have a look to see how easy this might be to fix!
Many thanks,
Duncan

Hi Gary
I've been trying to recreate your issue. So far I have installed and tested with the following and everything seems to be working OK:

Ok, will check it out Gary

Hi Ashley, I want to give you a star for fixing this (but I'm not allowed as I'm not an admin) so please consider this as a token of my appreciation .

Fix added to master branch

Fix now added to TinyMCE extension

Thank you for your ongoing use of the TinyMCE extension and also reporting this issue. The problem is, in fact, a bug in Firefox (see here). This was fixed in version 84 of Firefox, I believe, which is why you no longer get the problem in version 86.

Hi @Nilasae , that's no problem at all. It's useful to see where users are having problems anyway and problems are how we learn. I'm really pleased you are using our extension and please do let me know if you have any more question or issues. B.T.W. I released version 1.0.8 on my development GitHub master branch over the weekend with a couple of bug fixes so you may wish to move up to that when you can?

Hi @Nilasae
Thank you for using the TinyMCE extension and taking the time to raise this bug report.
I did notice something strange in your example code. Every line except the first starts with a space. According to the mediawiki documentation here (see sections on Bullet Lists and Preformatted Text) and here (see section Wiki Table Markup Summary, first point after the table) list markup and table markup should start on a new line. Also, space before a new line creates a preformatted block.
This is the standard we have applied in the TinyMCE extension.
Although your code does seem to be interpreted as a table by Mediawiki, I am not sure you can rely on that behaviour as it doesn't confirm to what is described in the documentation. Unfortunately, it is impossible for me to be able to test every alternative to what the documentation describes. I tried the wiki markup without spaces at the start of each line and, in my test system at least, it seems to work correctly.
Later this year I plan to upgrade the TinyMCE extension to support the new parser distributed with mediawiki 1.35 which should make it a lot easier to reproduce exactly how Mediawiki renders wiki markup as html. If you are able to work without the spaces at the start of a line until then, my preference would be to do that. Let me know though if this causes a major problem for you?

This is an ancient task referring to a prior incarnation of the TinyMCE extension which I believe is no longer valid for the current version.

Version 1.0 of extension TinyMCE is available in Mediawiki extensions pages

Solved in version 1.0

This should no longer happen in version 1.0

Hi @Servilamina
The new version is available now on the TinyMCE extension page. It is a bit different from the previous version so it is probably worth re-reading the installation and usage documentation..

Thank you for trying this extension and also bringing this problem to my attention.

Hi Yaron
I just added a patch to Gerrit with a fix for this. It will need to reviewed and accepted before the change is made to the master branch. However, if you'd like, or need, to try it sooner you can download the pactch from the link in the gerritbot comment above.
I hope it works well for you, but do note the comment about css above as things may not look exactly as you'd expect after the drop/paste.
B.T.W. did you notice their is an 'image upload' button of the TinyMCE menu bar if you just wish to upload a file from your local disk or a URL?
Hope you are enjoying the extension and please do let me know if you've any other suggestions/comments.
Kind regards, Duncan

Helo Yaron
Thank you for your request, this is indeed a very important feature for the TinyMCE extension. In fact it used to be that one could drag/drop or copy/paste from an HTML source into the TinyMCE editor and it would automatically upload all the images.
Somewhere along the line I must have made a change which has broken that feature, so I will try to fix it and post here when I'm done.
There is a separate problem with drag/drop copy/paste from HTML into the TinyMCE editor. This is because the copy/drag part of the operation doesn't pick up the CSS definitions for the classes in the html being copied/dragged. As a result what is pasted/dropped in the TinyMCE editor may not 'look' like the source document.
This may not be a problem for you, especially if your source document is a local wiki. I will fix the upload and then we can see if this fixes the issue for you?
Alternatively, if you are looking to transfer the content of a local wiki to a remote one, then there are other options for doing that (see, for example here). Bulk transfers of pages and files between wikis is a little outside the scope of the TinyMCE extension. If you need help on doing that it might be advisable to ask on the MediaWiki-l mailing list, where you will get much better advice than I can give!
Otherwise, check back and I will post here when I've fixed the drag/drop copy/paste upload feature of TinyMCE
Kind regards, Duncan

Hi, thank you for retesting and letting me know.

Thanks for the quick response. Due to a misunderstanding on my part, fixes to the code haven't been backported to previous releases. I'm sorry this wasn't clear from the documentation until recently when I added the compatibility policy is 'master'.
The background to this misunderstanding is explained in the dialogue I had with James Forrester in the comments on this patch.
Would you try the current master branch to see if you still get this problem? This should work with mediawiki 1.31.6. I apologise for any inconvenience, Duncan.

Hi, I just tried this with Mediawiki 1.31 and the most recent TinyMCE master and everything seems to be working OK. It might be that a recent change has solved the problem or maybe you are using a different version of mediawiki. Would you let me know which versions you are using? Thanks

OK now I get it, I think. I guess you added this project so that issues etc with the TinyMCE extension that I mention can be tracked. Thanks for that.

Hi, I'm new here so I hope I've responded appropriately? Have you seen the extension TinyMCE for Mediawiki that might meet your needs? I believe it works on Mediawiki versions from 1.23 to at least 1.31.