PubSub Errors After Upgrading to 2.1 from Subversion Release

Hi,

I am in the process upgrading ejabberd to 2.1 from a subversion release from several months ago. After upgrading I ran

$ ejabberdctl rename_default_nodeplugin

as specified by the release notes. I started the server, checked the logs and saw nothing unusual -- everything seems to have migrated properly.

Now, however, whenever a user attempts to create a new node in their /home/host/username/ node, they get a forbidden error.

Can anyone help me debug this problem? Thanks, in advance.

Matt

Quote: whenever a user

Quote:

whenever a user attempts to create a new node in their /home/host/username/ node, they get a forbidden error.

Notice that you should have:

{modules, [
  {mod_pubsub,   [
                  {access_createnode, pubsub_createnode},
                  {ignore_pep_from_offline, true},
                  {last_item_cache, false},
                  {plugins, ["flat", "hometree", "pep"]}  % pep requires mod_caps
                 ]},
 ...
]}.

And users first have to create their /home/host/username/, for later creating other nodes.
See: http://www.ejabberd.im/mod_pubsub-usage

If you think the Pubsub tables had wrong format, and they have no important content, you can simply delete them (using WebAdmin, for example), and then restart ejabberd. They will be created with proper format, but empty, of course.

Problem Fixed!

Thank you very much, badlop. The problem was that I did not have the "hometree" node type listed (it was still called default). I replaced default with hometree and everything appears to be working fine.

Syndicate content