We have an install of Mura that is about 3 years old and which as been running in Docker that whole time. It was on Mura 7.3.1 and Lucee 5.3.6. I'd been putting off and putting off doing anything with it because it 'just worked' but it really needed to be running current versions both of Lucee and Mura or Masa. We rebuilt the docker images with our updated Lucee base images and then by cloning the Masa repo instead of the Mura repo and dropped it in our Docker swarm. It 'just worked' - all sites running, admin logins, everything. Smoothest update we've had for anything in a while! Thanks guys!

Hi Samuel, I was offline the last couple of days. Did you upgrade to the latest version of Masa?

Is there anybody who can help fix this broomdasher.com/news/ works broomdasher.com/news breaks. It's using mod_rewrite apache - muraCMS7.1 RewriteEngine on RewriteRule ^/lucee/(.*) - [F] RewriteRule ^/CFXXXXXXXXXXXbT/(.*) /lucee/$1 [PT] RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d RewriteRule ^([a-zA-Z0-9/-]+)$ /index.cfm%{REQUEST_URI} [PT] Will share more privately

Update from 6/3 when clicking 'save' wouldn't publish: We rebuilt our Docker images (now with 7.3.5) and we are now able to save updates. However, on one page (and one page only, so far) we get an error when clicking 'publish' on a 'full edit': any idea what might be causing this?

Out of curiosity - why is the version of CKEditor in Masa quite so old? We're juggling incompatibilities with plugins and while it's not hard to find older versions of plugins, we didn't have this problem with Mura

I agree that a dependancy like CFEditor should be updated/upgraded regularly. But jumping a major version is a big undertaking. And to be honest, not something that it on our planning in the near future. I don’t understand your remark regarding Mura, the latest public version of Mura is using the same version of CKEditor. If you updated the version in Mura X, that I am not aware of.

I'm not referring to a major version. I think Masa is on 4.11? 4.19 or even 4.17 would be great.

CKEditor 5 is another can of worms, you're right that's not worth the lift

Masa CMS is indeed on 4.11.2, I’ll look into what the effort would be to upgrade to the latest 4.x release.

We’ve been looking forward to this moment, to tell you more about the next version of Masa CMS: 7.4! Version 7.4 features Our focus with version 7.4 is on bringing more functionality to the front end. This includes: • Reviewing the existing frontend modules • Creating new frontend modules • Introducing Masa.js Why Alpha testing? Since this version contains refactoring of part of the javascript code that powers the layout manager and the frontend modules, we want to start testing this as early as possible. Therefor we’re created a first alpha version that contains these changes, together with some new and reviewed frontend modules. What’s already available in v7.4-alpha.2 Right now you can experience the following changes in the alpha release: • Updated Mura.js to the latest version • New Button module • New Info module • New Media module • New Gatted Asset module • Reviewed Form module • Reviewed Image module • Reviewed CTA module • Reviewed navigation module Get started with the Alpha release! We would like to welcome you into testing this alpha version and letting us know how it behaves. If you want to share your feedback: create an Issue on Github, post some feedback in the Discussions or simply send us an email on hello@masacms.com. You can find this alpha version as a pre-release on Github and as an unstable release on Forgebox.

@sknowlton we’ve just released v7.3.8 with some small bug fixes and an update of CKEditor to version 4.19.1!

If you’re at CFSummit, make sure to come and say hi to me! I would love to get your feedback on Masa CMS!

We’ve got a new pre-release version out: 7.4 beta! Version 7.4 features available in this beta release • updated Mura.js to the latest version • new Button module • new Info module • new Media module • new Gated Asset module • reviewed Form module • reviewed Image module • reviewed CTA module • reviewed navigation module • new search module (new) • new primarynav module (new) • new gotofirstchild module (new) • new nextprevnav module (new) • update for the default theme (new) • new setting showextensionsindefault to show the basic tab extended attributes below the editor (new) Get started with the beta release! We would like to invite you to testing this beta version and letting us know how it behaves. If you want to share your feedback: create an Issue on Github, post some feedback in the Discussions or simply send us an email on hello@masacms.com. You can find this beta version as a pre-release on Github and as an unstable release on Forgebox.

Current ‘main’ branch (e10e8d…) has an empty mura.min.js file in

admin/assets/js

.This file is loaded in

core/vendor/ckeditor/plugins/murafilebrowser/filebrowser.cfm

when adding an image to a content page and clicking on ‘Browse Server’ in the Image Properties pop up. Switching this to use the non minified version then errors on

$("#spinner")

in filebrowser.js as jQuery not loading.

@mgallon we’re released a patch release that fixes the issue: https://github.com/MasaCMS/MasaCMS/releases/tag/7.3.9

Join us for Hacktoberfest! https://github.com/MasaCMS/MasaCMS/discussions/137

We’ve successfully migrated from Mura 7.1 to Masa 7.3.9 but we have a problem with our custom modules (inline editing). The modules/display objects are visible in the sidebar, but when we click a module and change some params, nothings get rendered. Is there something we need to do to enable our custom modules for inline editing?

MASA CMS - Important - Security fix We’ve been informed of an authentication bypass vulnerability in Masa CMS. We’ve fixed this issue right away and released patch versions 7.3.10, 7.2.5 and 7.4.0-beta.3. What is fixed ? The mentioned vulnerability has been fixed. What versions are affected? • Masa CMS versions 7.2, 7.3 and 7.4-beta are affected. • Mura CMS versions 5.x, 6.x, 7.0 and 7.1 are affected. What should you upgrade ? If you’re on Masa CMS 7.3, you should update to version 7.3.10 immediately. This can be done by using the “Update Masa CMS Core” option in the menu of the Masa CMS Administrator or by applying a manual update. If you’re on Masa CMS 7.2, you should update to version 7.2.5 immediately. This can be done by applying a manual update. If you’re on Masa CMS 7.4 beta, you should update to version 7.4.0-beta.3 immediately. This can be done by applying a manual update. If you’re on Mura CMS 5.x, 6.x, 7.0 or 7.1, you should consider upgrading to Masa CMS since Mura Software is no longer supporting these versions.

Howdy, I am going to upgrade MuraCMS to MasaCMS for now to deal with the security vulnerabilities. If I could find theme/front end designers for Masa CMS I would be there long term!! Anyway, we are in a load balanced situation with installs on three servers. My question is if I run core update on one server, that will update the DB as well. I would then need to manually add all files to the other instances for this to succeed. Is there a smaller package of changed files to accelerate updating other installs?

Hi @ehoffman that depends on what version of Mura you are upgrading from. Could you elaborate on that? We can help with theme development. ☺️

Hello everyone, I'm new for Masa CMS but having good knowledge and experience in Mura 6 & 7. Here I have tried to do a demo set up for Masa CMS. But while do the basic set up I have facing the below issue. I have tried to fix myself but no luck. Could any one let me know that how I can escape from this issue ? I'm using IIS & CF2018.

Hello - I'd like to switch a local association Mura site that I maintain to Masa but I'm not having any luck with the "autoupdate" route. They're running Mura 7.0.7108 and the autoupdateurl key doesn't exist in the settings.ini.cfm file. I tried to add it and reload the site to update the Core but it doesn't work. Can I update to Masa from any Mura version?