Closed cuducos closed 3 years ago
We can not support backwards compatibility, there is a 2.8 branch in case you are interested. We have limited resources to maintain this extension, I hope you find a workaround.
there is a 2.8 branch in case you are interested
Sounds good. Shouldn't it be in the docs (README.md
)? I mean… if it was, probably I wouldn't have opened this issue. I can open a PR if this is interesting for the project : )
I added a comment in the README, thanks for pointing it out. Feel free to contribute, for us is enough with the CKAN 2.9 support.
Closed by e7c01d2bd33a7b4a5a7de26cc831f6e0cce87a21
Depending on
ckan.lib.webassets_tools.add_public_path
makesckanext-composite
compatible with CKAN 2.9, but breaks compatibility with CKAN 2.8:https://github.com/EnviDat/ckanext-composite/blob/afce956a8da095e10646cf041375c8cc24bd92d6/ckanext/composite/plugin.py#L3
Is this intended? Should we have a tag with the latest version compatible with 2.8? Should we add something to the docs?