RE: 7.2 B1 - Auto-Propagation of fragments

2019-04-15T19:20:49Z

Personally I'm not even considering the remote possibility of taking fragments seriously ... until the feature becomes stable. I'll play around with it but without being stable I can't advise anyone make that switch and advise production use of web content templates. Is there a Liferay version on the roadmap where fragments are considered done / feature complete?

Currious though, are fragments global? If I say need to make a design change make a change to the "blue" in the fragment, will it go to all sites like web content should?

7.2 B1 - Auto-Propagation of fragments

2019-04-11T13:02:47Z

I played a bit around with fragments and I find it really annoying that I have to propagate each change. That propagate feature is probably really nice in production, but not so much in dev/test environments.

While it is quite nice to have a quick preview of the content in the down-right box, it simply isn't the same as seeing the content on the page. We often need to refresh pages to see the change "in a real environment" or e.g. use browserstack to check if the fix indeed works with Internet Explorer.

It would be really helpful, at least for development, to have a "publish, don't close the editor AND propagate" button instead of only a "Publish" button.

(I hope, when they are deployed, the new versions are automatically used everywhere)