Christoph Rabel 2 Years Ago - Edited Very nice! It is good, that guest file upload support is finally supported. That one was always a major showstopper for me. I will certainly check out the fragment and the adaptive media options, optimizing images for usage (as a preview image) AND for mobile (these are different usecase) is really tricky. I mean, to do as much as possible automatically, but still provide a convenient and easily understandable way for editors to override it. I also think the changes to the minifier and sass are really important. I talked with Chema Balsas(who created the relevant tickets) at Devcon a couple of years ago about this stuff. Performance, caching, cdn are major topics for some websites I manage and we had some headaches there. It is nice to see progress. And thanks for this overview, without such a blog post I would probably only have realized in a couple of months (or never) that some of these changes were made. Please sign in to reply. Reply as... Cancel
Sascha Hofrichter 2 Years Ago - Edited Hey guys,Nice.Now the time has come to migrate the custom Themes :-PIf we deploy our custom Theme to Liferay 7.4.0 we get AutoDeployExceptions with the message: 'does not support this version of Liferay'. Is some documentation or migration guides out there?Next question: Which versions of elasticsearch we should use with Liferay 7.4.0? Please sign in to reply. Reply as... Cancel Christoph Rabel Sascha Hofrichter 2 Years Ago - Edited I haven't tried to create a theme for 7.4 so far, so take my answer with a grain of salt. The supported version is usually part of the theme. There are two settings, in liferay-look-and-feel.xml and in the liferay-plugin-package.properties file. I am not sure which one is relevant, maybe both, and if it is sufficient to just update them. No idea if there are guidelines, we usually create a new theme for 7.x and then apply our changes to it. (You can create a bare 7.3 theme and compare them). That way, we don't lose anything. It can be more work than just copying in the first place, but it the outcome is better, at least in my opinion. Liferay 7.4 uses Elasticsearch 7.9 for demo purposes, but I have already used Liferay 7.3 with Elasticsearch 7.11. So, anything 7.9+ should work. Please sign in to reply. Reply as... Cancel Sascha Hofrichter Christoph Rabel 2 Years Ago - Edited Hey Christoph, Thank you. You saved my life. The changes in liferay-plugin-package.properties and liferay-look-and-feel.xml have solved the problem. I will try the current version of elasticsearch (7.12.1), if it fails I will return to 7.9. Have a nice weekend. Please sign in to reply. Reply as... Cancel
Christoph Rabel Sascha Hofrichter 2 Years Ago - Edited I haven't tried to create a theme for 7.4 so far, so take my answer with a grain of salt. The supported version is usually part of the theme. There are two settings, in liferay-look-and-feel.xml and in the liferay-plugin-package.properties file. I am not sure which one is relevant, maybe both, and if it is sufficient to just update them. No idea if there are guidelines, we usually create a new theme for 7.x and then apply our changes to it. (You can create a bare 7.3 theme and compare them). That way, we don't lose anything. It can be more work than just copying in the first place, but it the outcome is better, at least in my opinion. Liferay 7.4 uses Elasticsearch 7.9 for demo purposes, but I have already used Liferay 7.3 with Elasticsearch 7.11. So, anything 7.9+ should work. Please sign in to reply. Reply as... Cancel Sascha Hofrichter Christoph Rabel 2 Years Ago - Edited Hey Christoph, Thank you. You saved my life. The changes in liferay-plugin-package.properties and liferay-look-and-feel.xml have solved the problem. I will try the current version of elasticsearch (7.12.1), if it fails I will return to 7.9. Have a nice weekend. Please sign in to reply. Reply as... Cancel
Sascha Hofrichter Christoph Rabel 2 Years Ago - Edited Hey Christoph, Thank you. You saved my life. The changes in liferay-plugin-package.properties and liferay-look-and-feel.xml have solved the problem. I will try the current version of elasticsearch (7.12.1), if it fails I will return to 7.9. Have a nice weekend. Please sign in to reply. Reply as... Cancel
Lee Jordan 2 Years Ago - Edited From an Enterprise Edition POV ... Is IE11 support (while still using BS4) being dropped from EE too? The dropping of the compatibility layer I can see that making a 7.3 to 7.4 upgrade painful also. Considering the struggle is real even trying to get a 7.3 upgrade working with the significant changes dropping IE and the Bootstrap Compats, I think that kills 7.4 for Enterprises. The document title issue, I'm cautiously optimistic and remain on edge. We've got to move beyond 404 errors when users rename document titles and we've really got to end the notion that a document title is a filename. Please sign in to reply. Reply as... Cancel Christoph Rabel Lee Jordan 2 Years Ago - Edited Your company is still using Internet Explorer? Puh. Luckily, every company I know of has moved on, the latest one last year. Even Microsoft has dropped IE support for several of their services already and I think all of the O365 family will drop support by August this year. I really can't blame Liferay for that decision. Supporting IE was hard and a pain. Please sign in to reply. Reply as... Cancel Lee Jordan Christoph Rabel 2 Years Ago - Edited Until they uninstall IE someone will use it yes. Even worse I'd be willing to bet some companies are forcing Edge into some form of compatibility mode so their business critical apps carry on working in the short term. In terms of upgrading old software that we actually need to see happen ... CKEditor 5. Let's go, get it done. Or switch to TinyMCE. In terms of the Bootstrap Compatibility layer, I'll get to that once I see a successful upgrade from 7.0 to 7.3. If that stuff starts getting backported to 7.3 there's no hope. Our upgrade from 6.1 to 7.0 they said that will be the last of your pain. This 7.0 to 7.2/3 has been harder than going from 6 to 7. Please sign in to reply. Reply as... Cancel
Christoph Rabel Lee Jordan 2 Years Ago - Edited Your company is still using Internet Explorer? Puh. Luckily, every company I know of has moved on, the latest one last year. Even Microsoft has dropped IE support for several of their services already and I think all of the O365 family will drop support by August this year. I really can't blame Liferay for that decision. Supporting IE was hard and a pain. Please sign in to reply. Reply as... Cancel Lee Jordan Christoph Rabel 2 Years Ago - Edited Until they uninstall IE someone will use it yes. Even worse I'd be willing to bet some companies are forcing Edge into some form of compatibility mode so their business critical apps carry on working in the short term. In terms of upgrading old software that we actually need to see happen ... CKEditor 5. Let's go, get it done. Or switch to TinyMCE. In terms of the Bootstrap Compatibility layer, I'll get to that once I see a successful upgrade from 7.0 to 7.3. If that stuff starts getting backported to 7.3 there's no hope. Our upgrade from 6.1 to 7.0 they said that will be the last of your pain. This 7.0 to 7.2/3 has been harder than going from 6 to 7. Please sign in to reply. Reply as... Cancel
Lee Jordan Christoph Rabel 2 Years Ago - Edited Until they uninstall IE someone will use it yes. Even worse I'd be willing to bet some companies are forcing Edge into some form of compatibility mode so their business critical apps carry on working in the short term. In terms of upgrading old software that we actually need to see happen ... CKEditor 5. Let's go, get it done. Or switch to TinyMCE. In terms of the Bootstrap Compatibility layer, I'll get to that once I see a successful upgrade from 7.0 to 7.3. If that stuff starts getting backported to 7.3 there's no hope. Our upgrade from 6.1 to 7.0 they said that will be the last of your pain. This 7.0 to 7.2/3 has been harder than going from 6 to 7. Please sign in to reply. Reply as... Cancel