Closed edhelas closed 1 year ago
Looks like there is a mismatch when disabling limits of items, one side want to use 'infinity' for that where other expect 'max'. Will try to fix this.
Added change 3c97775573d672f185a3d5839ec82e5fb3debbc5 that i think should fix this.
@edhelas If you don't compile ejabberd yourself, you can find binary packages of ejabberd with that fix on the bottom of page https://github.com/processone/ejabberd/actions/runs/4480250617
Probably you can simply extract one of them and copy mod_pubsub.beam to replace the one in your deployment. (Keep a backup of the old beam file, in case ejabberd cannot start)
<iq to='miho@movim.eu' type='get' id='nWfZxZL'>
<pubsub xmlns='http://jabber.org/protocol/pubsub#owner'>
<configure node='urn:xmpp:microblog:0'/>
</pubsub>
</iq>
<iq lang='en' to='miho@movim.eu/6916870486585674733994' from='miho@movim.eu' type='result' id='nWfZxZL'>
<pubsub xmlns='http://jabber.org/protocol/pubsub#owner'>
<configure node='urn:xmpp:microblog:0'>
<x xmlns='jabber:x:data' type='form'>
...
</x>
</configure>
</pubsub>
</iq>
I replaced mod_pubsub.beam
looks good now :+1:
Environment
XMPP logs
ejabberd error.log