.jpg){kind=avatar}
So, in a new demo instance of Creatio, you can go to a message template and click the edit template button. When you do this, you will notice that a new tab is opened and a full page content panel is opened. This is actually a classic module, but you will notice in the url for the page, that it's using the classic shell (/Nui instead of /shell). Really, it opens without any shell at all.
I have a custom version of the same content editor, but when we open this module page the same way, you can see that it initially pops to the right url (similar to the demo instance), but it is immediately routed to a /shell url and stops there.
I don't know if there's some internal router exception for the default editor module in Creatio that allows for it to open under the classic shell or if there's something else I'm missing. In debugging the code, I open the page the same way, simply calling window.open and passing in the url with the same structure.
For those familiar with this module, it's not entity bound, so you can add an exception in UI management. Wouldn't matter anyway, since the default creatio editor isn't doing this either (url would reflect the /shell path, instead of the /Nui classic path).
Anyone have any experience with this?
Jeremy
Like
In Creatio 8.3.2, classic UI Shell is officially deprecated. Probably causing some issues ? So although page is classic UI, if there's no more Classic UI shell, I guess that's the reason why it's not showing a shell ? (not ideal I know). I hope message templates will seen be migrated to a Freedom UI designer like bulk emails.
Couple things on this: although they are deprecating it, the classic shell is still available. Starting with 8.3.2, it will simply be turned on by default. We will actually be turning it off after the update for most of our clients, as we are not fully ready to migrate.
Second, the out of the box editor works exactly like we needed to and like it has in the past, so I know the technology does in fact still support it. I'm guessing it's some sort of static route defined somewhere, that prevents it from being redirected to the freedom Shell.
Just in case something like this comes up for anyone else, to prevent a page from redirecting to the Freedom UI Shell base url, you need to a the base url for your classic module to the Lookup "Blacklist of redirects from Classic UI". There are various modules that Creatio opens in a new tab, that must use the classic base (e.g content editor and BP designer) and this is how they allow for this.