Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
Slow down!
I can only think that a rushed job could be worse than doing nothing at all. Please slow down, the fixers won't be able to keep up and trying to maintain 7.1, 7.2, 7.3 and 7.4 is only going drag fixes on even longer. Some of us can't devote as much time to keeping track of what changes are going on. It does prove to me that Liferay engineers ARE superhuman, but training and support won't be able to keep up either.
On content pages there are so many differences in the UI between 7.3 GA3 and GA4. I think the best thing Liferay can do at this point approaching 7.3 release is to slow down and make sure what is there is solid. We all know that 7.4 might be the finish line for WEM upgrades, but rushing it can only put more strain on the fixers trying to fix things that come up.
I can't even do screenshots of 7.3 Content Pages and build up user guidance for our users because who knows by GA5 those could all be outdated?
I just managed to get round to raising a years long concern that the new navigation menus (not miller or find a page) ... but the user generated menus, users can't open a link in a new tab. In context it's a small concern but one that can make a big difference. But take the old way of doing it with adding a public page of type link to URL and the option is there. It's this fever pitch of gotta get it done that is leading to missed things. Missed things like something as fundamental as being able to open a link in a new tab. You can say "just ctrl+click" ... that works for me and you but Betty in accounts Payable won't know to do that and even if we mention it she still wants the option to open in a new tab ... it's there in other parts of the protal so why not here? It's rushed and things are being missed.
Maybe there was a long discussion about switching from Alloy Editor back to CK Editor, but a more considered approach might have been to see that Liferay can't get to CK5 which is where they need to be at this point in the 2020's. I feel like CK Editor is riddled with even more issues than AE that have been overlooked because CK isn't the default and again we're stuck on CK4. And TinyMCE is the technically superior choice anyway, but it is being removed.
I think slow down ... or figure out a way to catch up on the stuff that is being overlooked, the small stuff that can make a big difference.
Slow. Down. Get It Right Once. Take consideration of the existing users on 7.0.
Break it fast yep, but it takes months to even get something like this missing link target field added.
It's not even a 7.x series anymore, users of older versions are being left behind and I think it's in danger of repeating the 6.x to 7.x jump that was just too far of a difference that it may have prevented upgrades. For new users this is awesome. For existing users (the end users, typing stuff into Alloy Editor) ... people freak out over small changes. I have no idea what next year holds for us trying to retrain hundreds of people.
On content pages there are so many differences in the UI between 7.3 GA3 and GA4. I think the best thing Liferay can do at this point approaching 7.3 release is to slow down and make sure what is there is solid. We all know that 7.4 might be the finish line for WEM upgrades, but rushing it can only put more strain on the fixers trying to fix things that come up.
I can't even do screenshots of 7.3 Content Pages and build up user guidance for our users because who knows by GA5 those could all be outdated?
I just managed to get round to raising a years long concern that the new navigation menus (not miller or find a page) ... but the user generated menus, users can't open a link in a new tab. In context it's a small concern but one that can make a big difference. But take the old way of doing it with adding a public page of type link to URL and the option is there. It's this fever pitch of gotta get it done that is leading to missed things. Missed things like something as fundamental as being able to open a link in a new tab. You can say "just ctrl+click" ... that works for me and you but Betty in accounts Payable won't know to do that and even if we mention it she still wants the option to open in a new tab ... it's there in other parts of the protal so why not here? It's rushed and things are being missed.
Maybe there was a long discussion about switching from Alloy Editor back to CK Editor, but a more considered approach might have been to see that Liferay can't get to CK5 which is where they need to be at this point in the 2020's. I feel like CK Editor is riddled with even more issues than AE that have been overlooked because CK isn't the default and again we're stuck on CK4. And TinyMCE is the technically superior choice anyway, but it is being removed.
I think slow down ... or figure out a way to catch up on the stuff that is being overlooked, the small stuff that can make a big difference.
Slow. Down. Get It Right Once. Take consideration of the existing users on 7.0.
Break it fast yep, but it takes months to even get something like this missing link target field added.
It's not even a 7.x series anymore, users of older versions are being left behind and I think it's in danger of repeating the 6.x to 7.x jump that was just too far of a difference that it may have prevented upgrades. For new users this is awesome. For existing users (the end users, typing stuff into Alloy Editor) ... people freak out over small changes. I have no idea what next year holds for us trying to retrain hundreds of people.
Unfortunately I cannot agree with Lee... I understand the pains of keeping up with the changes but Liferay badly needs the ongoing evolution. We need a strong CMS for the users to adopt it and good dev tools to make peace with the dev community and regain productivity.
I understand you but it is important to use new world.
Now the new customers want a light and modern product.
The young developers want Angular 10, React, Vue... And for the first time liferay stop using jquery and loadash.
I hope one day we can have angular portlet with good performance. May be with server side rendering or shared libraries to have an immediate rending like we have with jsp or jsf.
And what about SEO, AMP or Open Graph...
A lot of work to make Liferay better than WordPress.
I love Liferay but it is too complex for many web designers or newbies.
Eric.
Now the new customers want a light and modern product.
The young developers want Angular 10, React, Vue... And for the first time liferay stop using jquery and loadash.
I hope one day we can have angular portlet with good performance. May be with server side rendering or shared libraries to have an immediate rending like we have with jsp or jsf.
And what about SEO, AMP or Open Graph...
A lot of work to make Liferay better than WordPress.
I love Liferay but it is too complex for many web designers or newbies.
Eric.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™