Closed donni106 closed 2 years ago
Reverting to 0.4.3 works again. I have downloaded https://github.com/humhub/rest/releases/tag/v0.4.3 and put it in my installed instance. Additionally i needed to uninstall the 0.5.0 module to make the 0.4.3 visible in order to activate it. So please take care of the bug and inform we once a new version is out. Thanks!
@donni106 Yes, you are right we added in response new content columns here https://github.com/humhub/rest/pull/86/commits/0efdaece6d998c62a9033dc18cf4cae204b2a043#diff-c3b324e68fe919cca901505ab531fd1bdf9a46c645850a4c895af68dcbdd8e86R47
What HumHub version do you use?
The Content field locked_comments
was added here https://github.com/humhub/humhub/commit/01270ff#diff-b035dbac3239b41d6820053cd38eb34872b4881a9d7ecc0eca6a7ff3b73e5945R15 for HumHub version 1.10
.
@luke- Should we increase min HumHub version for the REST module to 1.10
, or modify the code to something like? :
'locked_comments' => (bool) $content->locked_comments ?? false
thanks, good info!
using HumHub Community Edition Version: 1.8.3
i would need to invest further if i can safely update to at least 1.10, but will keep you up to date if i did and everything worked out well.
@yurabakhtin Let's increase the min version of the REST API
nice, now the module is listed with "last compatible version 0.4.3" for my 1.8.3 HumHub instance
That is correct or not? The new version 0.5.1 with "locked_comments" requires at least HumHub 1.10.
yes, it's perfect now! just wanted to confirm it for my case.
Ok, thanks! :-)
I updated to 0.5.0 and now i get error results when getting posts for space container where posts exist:
i am not sure, if this is related to 0.5.0, but i do not know about any other changes or udpated configs.
using HumHub Community Edition Version: 1.8.3