summaryrefslogtreecommitdiff
path: root/src/mod_pubsub.erl (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Fix errors and warnings for "rebar3 edoc"Badlop2022-05-171-5/+0
|
* Update copyright year to 2022Badlop2022-02-111-1/+1
|
* mod_pubsub: Unsubscribe JID on whitelist removalHolger Weiss2022-02-021-1/+13
| | | | | If a JID is removed from the affiliation lists of a node with access model 'whitelist', remove it from the list of subscribers as well.
* Fix typosKian-Meng Ang2022-01-241-1/+1
|
* mod_pubsub: Allow for limiting item_expire valueHolger Weiss2022-01-171-6/+15
| | | | | | If mod_pubsub's 'max_item_expire_node' option is specified, reject node configurations with an 'item_expire' value that exceeds the specified limit.
* Annotate modules, options and command major changes in 21.12Badlop2021-12-091-0/+3
|
* Merge pull request #3652 from weiss/bump-max-itemsbadlop2021-12-031-1/+1
|\ | | | | PubSub: Bump default value for 'max_items' limit
| * PubSub: Bump default value for 'max_items' limitHolger Weiss2021-07-281-1/+1
| | | | | | | | | | | | | | | | | | Bump the default value for mod_pubsub's 'max_items_node' option, which hard-limits the 'max_items' value requested by clients. These days, use cases such as microblogging or XEP-0402 may need a large number of items per node. Bumping the limit makes sure such functionality is properly supported with the default configuration.
* | mod_pubsub: Remove unused check_opt_range/3 clauseHolger Weiss2021-10-311-3/+1
| |
* | mod_pubsub: Fix get_max_items_node/1 specificationHolger Weiss2021-10-301-2/+2
| | | | | | | | | | | | | | | | Make it explicit that the get_max_items_node/1 function returns ?MAXITEMS if the 'max_items_node' option isn't specified. The function didn't actually fall back to 'undefined' (but to the 'max_items_node' default; i.e., ?MAXITEMS) anyway. This change just clarifies the behavior and adjusts the function specification accordingly.
* | PubSub: Add delete_expired_pubsub_items commandHolger Weiss2021-10-301-1/+66
| | | | | | | | | | | | | | Support XEP-0060's pubsub#item_expire feature by adding a command for deleting expired PubSub items. Thanks to Ammonit Measurement GmbH for sponsoring this work.
* | Use specific syntax so modules and top-level will be linksBadlop2021-08-231-2/+2
| | | | | | | | | | | | If we use _`whatever`_ here in ejabberd man pages, it is converted to *`whatever`* in markdown, and docs.ejabberd.im/Makefile converts to the proper links
* | PubSub: Add delete_old_pubsub_items commandHolger Weiss2021-08-221-1/+52
| | | | | | | | | | | | | | | | Add a command for keeping only the specified number of items on each node and removing all older items. This might be especially useful if nodes may be configured to have no 'max_items' limit. Thanks to Ammonit Measurement GmbH for sponsoring this work.
* | PubSub: Support unlimited number of itemsHolger Weiss2021-08-211-6/+8
| | | | | | | | | | | | | | | | Allow for setting the mod_pubsub option 'max_items_node' to 'unlimited'. If clients then request a 'max_items' limit of 'max', old items aren't deleted when publishing new ones. Thanks to Ammonit Measurement GmbH for sponsoring this work.
* | PubSub: Support 'max_items=max' node configurationHolger Weiss2021-08-201-2/+5
| | | | | | | | | | | | | | | | | | Let clients request the maximum limit for the node configuration option 'max_items' by specifying the special value 'max' instead of an integer. This was added to XEP-0060, revision 1.17.0 (and clarified in revision 1.20.0). Thanks to Ammonit Measurement GmbH for sponsoring this work.
* | mod_pubsub: Fix check_opt_range/3 specHolger Weiss2021-08-021-1/+2
| |
* | PubSub: Use configured 'max_items' by defaultHolger Weiss2021-07-281-1/+1
|/ | | | | | | If clients don't ask for a specific 'max_items' limit, use the value of mod_pubsub's 'max_items_node' option as default, rather than the hard-coded ?MAXITEMS value. This makes sure clients cannot circumvent a smaller, configured limit.
* fix gen_pubsub_node:get_state return valuefdie2021-03-251-2/+3
|
* Update newest copyright year to 2021 (#3464)Badlop2021-01-271-1/+1
|
* Rename function argumentsPaweł Chmielowski2021-01-251-6/+6
|
* Skip reading pep nodes that we know won't be requested due to capsPaweł Chmielowski2021-01-251-27/+47
|
* Use include_lib() to include headers from dependencies (#3369)Stu Tomlinson2020-09-031-1/+1
|
* mod_pubsub: Fix typo in 'hosts' documentationHolger Weiss2020-08-251-2/+2
| | | | Thanks to Melvin Keskin for spotting this.
* mod_pubsub: Remove 'dag' node plugin documentationHolger Weiss2020-08-181-5/+1
| | | | | Commit c9d3beb9ebbd7a76a74e3e9c22ea62ec21e64a6a removed the 'dag' node/nodetree plugins.
* Update syntax of some options so they are better displayed in DocsBadlop2020-05-121-4/+4
|
* Fix mod_pubsub indentationBadlop2020-04-021-104/+108
|
* Add mod_pubsub configuration documentationBadlop2020-04-021-1/+202
|
* Update copyright to 2020 (#3149)Badlop2020-01-281-1/+1
|
* Limit result set of disco#items for mod_pubsubEvgeny Khramtsov2019-10-241-5/+11
| | | | | | | The size of a list of nodes returned for disco#items request is now controlled by option 'max_nodes_discoitems'. The default value is 100. The name and the default value of the option is chosen to be consistent with mod_muc's 'max_rooms_discoitems' option.
* Replace lager with built-in new logging APIEvgeny Khramtsov2019-10-181-4/+0
| | | | | | | | | | | | | | | This change requires Erlang/OTP-21.0 or higher. The commit also deprecates the following options: - log_rotate_date - log_rate_limit Furthermore, these options have no effect. The logger now fully relies on log_rotate_size, that cannot be 0 anymore. The loglevel option now accepts levels in literal formats. Those are: none, emergency, alert, critical, error, warning, notice, info, debug. Old integer values (0-5) are still supported and automatically converted into literal format.
* Correctly handle unicode in log messagesEvgeny Khramtsov2019-09-231-7/+7
|
* Don't retain module option on gen_mod supervisorEvgeny Khramtsov2019-08-041-2/+2
| | | | | | When module's options were updated (e.g. by reloading ejabberd.yml) and, later, the module's process crashed, gen_mod supervisor restarts the process with outdated options. This is now fixed.
* Introduce 'vcard' option for the modules supporting vCardsEvgeny Khramtsov2019-08-021-9/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The mapping between vCard's XML elements and YAML elements of 'vcard' option is straightforward. For example, if you want mod_muc to return the following vCard: ``` <vCard xmlns='vcard-temp'> <FN>Conferences</FN> <ADR> <WORK/> <STREET>Elm Street</STREET> </ADR> </vCard> ``` you need to set the configuration as: ``` modules: ... mod_muc: vcard: fn: Conferences adr: - work: true street: Elm Street ... ```
* For pubsub items with max_item = 1 use order by in sql queriesPaweł Chmielowski2019-07-311-1/+22
|
* Expose access_model and publish_model in pubsub#metadataEvgeny Khramtsov2019-07-301-0/+2
| | | | Fixes #2931
* Improve handling of errors in tree_action/3Evgeny Khramtsov2019-07-291-14/+33
|
* Appropriately abort pubsub transactionEvgeny Khramtsov2019-07-291-2/+8
|
* Improve handling of errors in pubsub codeEvgeny Khramtsov2019-07-291-394/+577
|
* Fix wrong virtual host in mod_pubsub:send_stanza (#2930)Christophe Romain2019-07-221-1/+5
|
* Fix typos using codespellEvgeny Khramtsov2019-07-161-3/+3
|
* Bump xmpp version and fix revealed bugsEvgeny Khramtsov2019-07-161-4/+5
|
* Fix 'get-pending' command form generationEvgeny Khramtsov2019-07-161-2/+2
|
* Avoid routing packets through a single processEvgeny Khramtsov2019-07-061-12/+16
|
* Make logging messages more consistentEvgeny Khramtsov2019-06-241-9/+9
|
* Improve extraction of translated stringsEvgeny Khramtsov2019-06-221-28/+28
| | | | | | | | | | | | | Now every such string MUST be encapsulated into ?T() macro. The macro itself is defined in include/translate.hrl. Example: -module(foo). -export([bar/1]). -include("translate.hrl"). bar(Lang) -> translate:translate(Lang, ?T("baz")).
* mod_pubsub: Check access_model when publishing PEPHolger Weiss2019-06-201-21/+33
| | | | | | | Don't just adhere to the node's access_model when delivering the last PEP item but also when a new item is published. Many thanks to Philipp Hörist for spotting this.
* Reflect recent pubsub changes in configuration transformerEvgeny Khramtsov2019-06-171-1/+3
|
* Get rid of "well-known" typeEvgeny Khramtsov2019-06-151-3/+3
|
* Use new configuration validatorEvgeny Khramtsov2019-06-141-91/+100
|
* Revert "Fix pubsub compliance XEP-0060 § 7.1.3.6 (#2864)"Christophe Romain2019-06-111-1/+1
| | | | | | This reverts commit 2fff4d1ea6f32babc3ae06ef877faaacb8ba3c1b. This commit broke the XEP compliance. more details here https://xmpp.org/extensions/xep-0060.html#events
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-13 01:37:53 +0000