Web Content Template VersioningWeb Content Template Versioninghttps://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=1184247492026-04-04T21:13:15Z2026-04-04T21:13:15ZRE: Web Content Template VersioningLee Jordanhttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1185009042020-02-13T19:14:10Z2020-02-13T19:14:10ZLet's get it done, why isn't this already a thing?Lee Jordan2020-02-13T19:14:10ZRE: Web Content Template VersioningBijan Vakilihttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1184422002020-02-06T05:02:57Z2020-02-06T05:02:57ZSo the great thing is already there, that is Web Content template versioning is supported on the backend. <br />DDMTEMPLATEVERSION<br />Now, the ability to do this via UI doesn't appear to be curretnly doable.<br />Some related upcoming features about version controlling the templates are here:<br /><a href="https://issues.liferay.com/browse/LPS-58513">https://issues.liferay.com/browse/LPS-58513</a>Bijan Vakili2020-02-06T05:02:57ZWeb Content Template VersioningLee Jordanhttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1184247482020-02-04T21:04:32Z2020-02-04T21:04:32ZAnother great thing to have would be Web Content template versioning. If you're disciplined you'll have the code in source control, however it's a drag to have to back up templates and structures when making a deployment change. Having the ability to revert back to a working version in the web UI editor would be very helpful.<br /><br />Is this there for fragments too? If not version fragments too.Lee Jordan2020-02-04T21:04:32Z