Projects tigase _server tigase-pubsub Issues #34
Configuration change has no effect (#34)
Closed
Artur Hefczyc opened 10 years ago
Due Date
2014-10-09

I tried to change PubSub node configuration to turn-off storing publications in DB.

The field for storing items to DB was set to 1 in DB:

<field type="boolean" label="Persist items to storage" var="pubsub#persist_items">
  <value>1</value>
</field>

After running following packet and getting following response from the Tigase server:

<iq to="pubsub.x.tigase.org" type="set" id="config2">
  <pubsub xmlns="http://jabber.org/protocol/pubsub#owner">
    <configure node="generated-2000-0">
      <x xmlns="jabber:x:data" type="form">
        <field type="hidden" var="FORM_TYPE">
          <value>
          http://jabber.org/protocol/pubsub#node_config</value>
        </field>
        <field type="list-single" var="pubsub#node_type">
          <value>leaf</value>
          <option>
            <value>leaf</value>
          </option>
          <option>
            <value>collection</value>
          </option>
        </field>
        <field type="text-single"
        label="A friendly name for the node" var="pubsub#title" />
        <field type="boolean"
        label="Whether to deliver payloads with event notifications"
        var="pubsub#deliver_payloads">
          <value>1</value>
        </field>
        <field type="boolean"
        label="Notify subscribers when the node configuration changes"
        var="pubsub#notify_config">
          <value>0</value>
        </field>
        <field type="boolean" label="Persist items to storage"
        var="pubsub#persist_items">
          <value>0</value>
        </field>
        <field type="text-single" label="Max # of items to persist"
        var="pubsub#max_items">
          <value>10</value>
        </field>
        <field type="text-single"
        label="The collection with which a node is affiliated"
        var="pubsub#collection" />
        <field type="list-single"
        label="Specify the subscriber model"
        var="pubsub#access_model">
          <value>open</value>
          <option>
            <value>authorize</value>
          </option>
          <option>
            <value>open</value>
          </option>
          <option>
            <value>presence</value>
          </option>
          <option>
            <value>roster</value>
          </option>
          <option>
            <value>whitelist</value>
          </option>
        </field>
        <field type="list-single"
        label="Specify the publisher model"
        var="pubsub#publish_model">
          <value>publishers</value>
          <option>
            <value>open</value>
          </option>
          <option>
            <value>publishers</value>
          </option>
          <option>
            <value>subscribers</value>
          </option>
        </field>
        <field type="list-single"
        label="When to send the last published item"
        var="pubsub#send_last_published_item">
          <value>on_sub</value>
          <option>
            <value>never</value>
          </option>
          <option>
            <value>on_sub</value>
          </option>
          <option>
            <value>on_sub_and_presence</value>
          </option>
        </field>
        <field type="text-multi"
        label="The domains allowed to access this node (blank for any)"
        var="pubsub#domains" />
        <field type="boolean"
        label="Whether to deliver notifications to available users only"
        var="pubsub#presence_based_delivery">
          <value>0</value>
        </field>
        <field type="boolean"
        label="Whether to subscription expired when subscriber going offline."
        var="tigase#presence_expired">
          <value>0</value>
        </field>
        <field type="text-multi"
        label="The XSL transformation which can be applied to payloads in order to generate an appropriate message body element."
        var="pubsub#embedded_body_xslt" />
        <field type="text-single"
        label="The URL of an XSL transformation which can be applied to payloads in order to generate an appropriate message body element."
        var="pubsub#body_xslt" />
        <field type="text-multi"
        label="Roster groups allowed to subscribe"
        var="pubsub#roster_groups_allowed" />
        <field type="boolean"
        label="Notify subscribers when owner change their subscription or affiliation state"
        var="pubsub#notify_sub_aff_state">
          <value>1</value>
        </field>
        <field type="boolean"
        label="Allows get list of subscribers for each sybscriber"
        var="tigase#allow_view_subscribers">
          <value>0</value>
        </field>
      </x>
    </configure>
  </pubsub>
</iq>

<iq from="pubsub.x.tigase.org" type="result" id="config2" to="admin@x.tigase.org/ArturBHcMacBook" />

The field in DB was still set to 1 as in above example.

Bartosz MaƂkowski commented 10 years ago

Wrong type of @jabber:x:data@. Type of form must be @submit@.

<iq to="pubsub.x.tigase.org" type="set" id="config2">
  <pubsub xmlns="http://jabber.org/protocol/pubsub#owner">
    <configure node="generated-2000-0">
      <x xmlns="jabber:x:data" type="submit">
        <field type="hidden" var="FORM_TYPE">
          <value>http://jabber.org/protocol/pubsub#node_config</value></field>
        <field type="boolean" label="Persist items to storage" var="pubsub#persist_items">
          <value>0</value>
        </field>
      </x>
    </configure>
  </pubsub>
</iq>
issue 1 of 1
Type
Bug
Priority
Major
Assignee
RedmineID
2322
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/tigase-pubsub#34
Please wait...
Page is in error, reload to recover