diff --git a/doc/guide.html b/doc/guide.html index 6d4d81a02..30869296d 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -1804,6 +1804,7 @@ all entries end with a comma: mod_private_odbcPrivate XML Storage (XEP-0049)supported DB (*) mod_proxy65SOCKS5 Bytestreams (XEP-0065)  mod_pubsubPub-Sub (XEP-0060), PEP (XEP-0163)mod_caps +mod_pubsub_odbcPub-Sub (XEP-0060), PEP (XEP-0163)supported DB (*) and mod_caps mod_registerIn-Band Registration (XEP-0077)  mod_rosterRoster management (XMPP IM)  mod_roster_odbcRoster management (XMPP IM)supported DB (*) @@ -2774,14 +2775,25 @@ usage, as every item is stored in memory. This allow to define a Key-Value list to choose defined node plugins on given PEP namespace. The following example will use node_tune instead of node_pep for every PEP node with tune namespace: 
  {mod_pubsub, [{pep_mapping, [{"http://jabber.org/protocol/tune", "tune"}]}]}
-

Example: +

Example of configuration that uses flat nodes as default, and allows use of flat, nodetree and pep nodes: 

{modules,
  [
   ...
   {mod_pubsub, [
                 {access_createnode, pubsub_createnode},
-                {plugins, ["default", "pep"]}
-               ]}
+                {plugins, ["flat", "hometree", "pep"]}
+               ]},
+  ...
+ ]}.
+

Using ODBC database requires use of dedicated plugins. The following example shows previous configuration +with ODBC usage: +

{modules,
+ [
+  ...
+  {mod_pubsub_odbc, [
+                {access_createnode, pubsub_createnode},
+                {plugins, ["flat_odbc", "hometree_odbc", "pep_odbc"]}
+               ]},
   ...
  ]}.