Forum Activity for @brian

Important TinyMCE upgrade in Jamroom Core 6.4.0

Announcements

The newest Jamroom Core 6.4.0 includes an upgrade to TinyMCE 5.0.14 (the "WYSIWYG" editor that Jamroom uses). This NEW release of TinyMCE changes how the editor plugins work, and could show an error in your browser until you full reset your browser caches - especially if you are using Chrome!

Chrome aggressively caches Javascript, which means you are likely to see an error in the editor after upgrading to Jamroom Core 6.4.0. To fix any errors you need to do the following:

1) Make sure any 3rd party Editor plugins (such as the Editor Code Mirror plugin from Ultrajam) are disabled for now until they are updated to support TinyMCE 5+

2) You need to FORCE a full refresh in your browser - unfortunately simply pressing "refresh" in your Chrome browser does NOT do this - you need to do the following:

- If you are using macOS Chrome press Command-Shift-R - this forces a new load that bypasses cache
- If you are on Windows Ctrl-F5 should force a refresh. If you still see an error in the editor, you may need to reset your browser cache completely since this may/may not actually work on some Windows installs.

The upgrade to TinyMCE 5 is an important update since it focuses on improving the mobile editing experience and is needed to address several issues in TinyMCE 4.9 that were not fixed until 5.

If you have any questions please feel free to respond here and we can follow up.

Thanks!
updated by @brian: 06/24/23 10:17:11AM

Jamroom 6.4.0 has been released!

Announcements

After several months of development and testing, we just pushed up Jamroom Core 6.4.0 to the marketplace. This new release includes a significant number of updates and fixes, as well as new events, features and performance improvements. You can view the full change log here:

https://www.jamroom.net/the-jamroom-network/networkmarket/32/system-core?expanded_changelog=1

We've been beta testing the 6.4.0 release for a couple months now and are excited to use it as the new base moving forward.

There were also several dozen skin and module updates that rolled out today to accompany the new Core release- lots of new features and updates

Please update and let us know how it works for you - we hope you enjoy the new releases!
updated by @brian: 04/21/20 02:24:10PM

tifig software error in the System Check.

Installation and Configuration


I will get the documentation updated - we recently moved all the binaries to the System Tools module, so the correct way is jrSystemTools_tifig_binary.

Thanks!

NVME Bump

Yeah they have some awesome prices for yearly - very good deals. Too bad they don't have an API or other services (mainly block storage).

ALLOW_ALL_DOMAINS missing

Installation and Configuration

I was just testing this as the Log in to Stream is not going to fix it. I've just pushed a NEW Core beta - 6.4.0b6 - update to that then:

- Go in to the ACP -> Core -> Core -> Tools
- Click on "Advanced Config"
- in the "add a new advanced config key" section enter:

(for the "Config Key"): jrCore_disable_play_cookies
(for the "Config Value"): on

and save. That will bypass the play cookie checking, which does not work when the stream URL is access directly.

Let me know how that works.

Thanks!

Lots Of Issues With Updates

Design and Skin Customization

Update to Core 6.4.0b6, reset caches and this should be fixed. Let me know if that looks better.

Thanks!

Lots Of Issues With Updates

Design and Skin Customization

I know why the extra spacing issue is happening and am fixing it for the next core release.

ALLOW_ALL_DOMAINS missing

Installation and Configuration

It should still work - make sure the Core -> Global Config -> Content -> "Log in to Stream" is NOT checked.

ALLOW_ALL_DOMAINS missing

Installation and Configuration

Unfortunately this is a change that has been pushed on us over the last couple years by browsers no longer sending a referrer header, so it had to change.

Alt Image Tag Issue

Design and Skin Customization


Let's leave politics out of the forum could we? Thanks!