Thanks. I will do that.

I figured out what happens in poll: it does not load chart.js

At first glance it looks like a javascript loading issue. You already mentioned the chart.js from Poll not loading.

Check the browser console (F12) to see if there are any more javascript issues.

Try to isolate the issue to a single plugin (by disabling plugins one by one) and hopefully you can find the origin of the issue.

We have several website where all these plugins are active at the same time and don't have an issue. If you find it, please contact us.

Thank you, Jerome.

I will follow your advice and see what I can find.

I fixed the poll plugin functionality with a small edit to Bootstrap and putting the chart.js files inside the plugin, but if there is a better way, I will try that. 

I posted the event manager issue to github.

CKEditor

For Apache:

Add the correct MIME type for `.mjs`:

<IfModule mod_mime.c>
    AddType application/javascript .mjs
</IfModule>

Then restart Apache (for example, `systemctl restart apache2` or `httpd`).

For nginx:

Make sure `.mjs` is mapped to JavaScript in the `http` block:

http {
    include mime.types;

    types {
        application/javascript  js mjs;
    }

    # ...
}

If you already have a `types` block with `application/javascript js;`, just add `mjs`:

types {
    application/javascript  js mjs;
}

Then reload nginx:

nginx -t
systemctl reload nginx

TinyMCE

These TinyMCE errors mean that the JavaScript files for icons and plugins are not being correctly loaded from the URLs TinyMCE expects (missing files, wrong paths, or HTML error pages instead of JS).

- Check that the files really exist

Open these URLs directly in the browser:

- http://192.168.50.162/cache/1772092595/default/tinymce/icons/default/icons.min.js
- http://192.168.50.162/cache/1772092595/default/tinymce/plugins/autosave/plugin.min.js
- http://192.168.50.162/cache/1772092595/default/tinymce/plugins/emoticons/plugin.min.js

etc

- Run 'Upgrade' via administration to clean the caches

- Clear the browser's caches

The direct links to the cache work perfectly. Otherwise, it wouldn't work with other browsers.

But I solved the problem !!!

Apparently, Firefox was experiencing an intermittent cache management issue for the editor. (in my case)

I proved it by disabling "simplecache" in the administration panel, and it worked (slowly).

So I re-enabled "simplecache" in the administration panel, and removed the "php_opcache.dll" extension from my PHP 8.4.18 server.

Now it works perfectly with Firefox !!!

Thanks, Nikolai, for your help.

Welcome to Elgg!

I'm afraid you'll need a third-party developer's help to integrate an Emoji plugin into CKEditor - it's not a built-in feature in Elgg's setup. Alternatively, consider opening an issue on GitHub to get the core team's attention.

In our projects, we stick with our custom TinyMCE plugin, which packs in massive functionality including full emoji support out of the box.

Hello Nikolai,

Thank you for your reply.

I'm interested in the Tinymce plugin.

I already use Tinymce, which I've implemented on one of my forums.

For faster deployment, I'll purchase your plugin.

However, it's listed for Elgg 6.1.

Is it compatible with Elgg 6.3.3 ?

Regards

Yes, TinyMCE plugin is fully compatible with the latest Elgg version, including 6.3.3. The badge on the product card indicates the minimum compatible Elgg version.

Please reach out to me or our managers directly via the marketplace to avoid cluttering this community ;)

You can schedule this update.

Just comment out \Elgg\Upgrades\ContentOwnerSubscriptions::class, string in this file https://github.com/Elgg/Elgg/blob/5.1/engine/upgrades.php

Like Nikolai said. You can do this upgrade later.

Once you've migrated your site to 5.x you can re-enable the upgrade and run that specific upgrade in the CLI (check the params for elgg-cli upgrade). I don't know if you could run it in batches (by canceling the upgrade mid run) but most of the time these long running upgrades don't have a heavy impact on the database (you could test this). So you can have it running on the background of your live site.

Excellent -- thank you both.  This will really help simplify our migration plan.