You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this PR all twitter mentions were replaced by "X". Since this is only merged into master and will be made available with stable release of 17.1, is there a possibility to merge this PR also into older releases since twitter is not available any longer and the current behaviour of all stable release branches leads to errors when trying to use content elements using twitter.
Additionally is there a planned roadmap for the stable release of 17.1?
Thanks in advance and best regards
Ronald
The text was updated successfully, but these errors were encountered:
Sure, we can backport commits to stable branches and release patch level versions. Which version would you be interested in?
We are currently wrapping up work on the first iteration of a new Hotspots element for Pageflow Next and would probably do the 17.1 release once that's launched.
I have not found a list of supported versions. In my humble opinion a backport to 16.0 and higher (16.1 & 16.2) would be appropriate. But i do not know how your support policy is defined for things like this. We have a projekt running on 16.0 and will soon iteratively update to 16.1 followed by 16.2
Thanks for your quick answers as always and best regards
Ronald
Sorry for not getting back earlier. We will soon release a new version. As an alternative, I have added a wiki page that describes the steps required to run Pageflow from a branch. That way you can cherry pick the desired commits onto arbitrary stable branches without us having to cut a larger set of patch level releases.
Hello Pageflow Team,
In this PR all twitter mentions were replaced by "X". Since this is only merged into master and will be made available with stable release of 17.1, is there a possibility to merge this PR also into older releases since twitter is not available any longer and the current behaviour of all stable release branches leads to errors when trying to use content elements using twitter.
Additionally is there a planned roadmap for the stable release of 17.1?
Thanks in advance and best regards
Ronald
The text was updated successfully, but these errors were encountered: