Update documentation to 25.10 with: make clean extract

Author: badlop

content/CHANGELOG.md

@@ -5,6 +5,81 @@ search:
 
 # ChangeLog
 
+## Version 25.10
+
+#### Ad-hoc Commands
+
+- `mod_configure`: New ad-hoc commands that were missing from XEP-0133
+- `mod_adhoc_api`: Add support for asynchronous command calling
+- `mod_adhoc_api`: If argument is a list of jids, type is `jid-multi`
+- `mod_adhoc_api`: If field has several values, type is `text-multi`
+
+#### API Commands
+
+- Add commands argument type `binary_or_list`
+- `mod_http_api`: Format sub elements for tuples from maps
+- `mod_admin_extra`: Improve roster API commands documentation
+- `mod_announce`: New API commands, reusing existing ad-hoc functions
+- `ejabberd_admin`: New API command `restart_kindly`, improve `stop_kindly`
+- `mod_admin_extra`: New API commands `list_banned` and `count_banned`
+- `mod_admin_extra`: Improve API command `status_list`: support for status to be a list
+- `mod_muc_admin`: New API commands `muc_get_registered_nick` and nicks ([#4468](https://github.com/processone/ejabberd/issues/4468))
+- Use `mod_private:del_data` in `unban_account` API command
+
+#### Configuration
+
+- Rename `New` SQL schema to `Multihost`, and `Default` to `Singlehost` ([#4456](https://github.com/processone/ejabberd/issues/4456))
+- Add config transformer from `use_new_schema` -> `sql_multihost_schema`
+- `mod_sip`: Fix problem parsing `via` in `yconf` library ([#4444](https://github.com/processone/ejabberd/issues/4444))
+
+#### Erlang/OTP support
+
+- Enable feature `maybe_expr` in the compiler for Erlang/OTP 26 ([#4459](https://github.com/processone/ejabberd/issues/4459))
+- Enable feature `maybe_expr` also in the runtime for Erlang/OTP 25
+- Runtime: Remove Erlang 24 which won't work anymore with `maybe_expr`
+- Remove `EX_RULE` and `EX_STACK` macros only used with ancient erlang
+
+#### GitHub Workflows
+
+- CI: Bump XMPP-Interop-Testing/xmpp-interop-tests-action ([#4469](https://github.com/processone/ejabberd/issues/4469))
+- CI: Don't care to include commit details in the CT logs HTML page
+- CI and Runtime: Reorganize steps to run in parallel, and ARM runner ([#4460](https://github.com/processone/ejabberd/issues/4460))
+- Add local composite actions to manage ejabberd and databases
+- Container: Build ARM in native runner instead of QEMU, merge and clean
+- Installers: Generate ARM installers in native runner
+- Tests: Run agnostic-database tests only once, not for every backend
+- Tests: The odbc backend is not actually used in Commont Tests
+- Weekly: New workflow that condenses CI, test all erlang without caching
+
+#### Installers and Container
+
+- Bump Erlang/OTP version to 27.3.4.3 in installers and container
+- Bump Expat 2.7.3, OpenSSL 3.5.4, unixODBC 2.3.14 in installers
+
+#### MUC
+
+- `mod_mam`: New option `archive_muc_as_mucsub`
+- `mod_muc`: Check if room is hibernated before calling mod_muc process
+- `mod_muc`: Update implementation of XEP-0317 Hats to version 0.3.1 ([#4380](https://github.com/processone/ejabberd/issues/4380))
+- `mod_muc`: Make mod_muc_sql properly handle new hats data ([#4380](https://github.com/processone/ejabberd/issues/4380))
+- `mod_muc_room`: Don't require password if user is owner of room
+- `mod_muc_admin`: Use in WebAdmin the new API commands that get nick registers
+
+#### Core and Modules
+
+- `ejabberd_http_ws`: Pass HTTP headers from WS to C2S connection ([#4471](https://github.com/processone/ejabberd/issues/4471))
+- `ejabberd_listener`: Properly pass `send_timeout` option to listener sockets
+- `ejabberdctl`: When ping returns pang, return also status code 1 ([#4327](https://github.com/processone/ejabberd/issues/4327))
+- `ext_mod`: Print module status message after installation
+- `misc`: json_encode should always call json with our filter
+- `mod_admin_update_sql`: Use same index name than when creating database
+- `mod_block_strangers`: Clarify `access` and `captcha` documentation ([#4221](https://github.com/processone/ejabberd/issues/4221))
+- `mod_http_upload`: Encode URL before parsing, as done before `bba1a1e3c` ([#4450](https://github.com/processone/ejabberd/issues/4450))
+- `mod_private`: Add `del_data/3`, `get_users_with_data/2`, `count_users_with_data/2`
+- `mod_pubsub`: Don't catch `exit:{aborted, _}` inside mnesia transactions
+- `mod_push`: Run new hook `push_send_notification` ([#4383](https://github.com/processone/ejabberd/issues/4383))
+- WebAdmin: Respect newline and whitespace characters in results
+
 ## Version 25.08
 
 #### API Commands

content/CONTAINER.md

@@ -1072,7 +1072,7 @@ Let's summarize the differences between both container images. Legend:
 | Generated by          | [container.yml](https://github.com/processone/ejabberd/blob/master/.github/workflows/container.yml) | [tests.yml](https://github.com/processone/docker-ejabberd/blob/master/.github/workflows/tests.yml) |
 | Built for             | stable releases <br /> `master` branch | stable releases <br /> [`master` branch zip](https://github.com/processone/docker-ejabberd/actions/workflows/tests.yml) |
 | Architectures         | `linux/amd64` <br /> `linux/arm64` | `linux/amd64` |
-| Software              | Erlang/OTP 27.3.4.2-alpine <br /> Elixir 1.18.4 | Alpine 3.19 <br /> Erlang/OTP 26.2 <br /> Elixir 1.15.7 |
+| Software              | Erlang/OTP 27.3.4.3-alpine <br /> Elixir 1.18.4 | Alpine 3.22 <br /> Erlang/OTP 26.2 <br /> Elixir 1.18.3 |
 | Published in          | [ghcr.io/processone/ejabberd](https://github.com/processone/ejabberd/pkgs/container/ejabberd) | [docker.io/ejabberd/ecs](https://hub.docker.com/r/ejabberd/ecs/) <br /> [ghcr.io/processone/ecs](https://github.com/processone/docker-ejabberd/pkgs/container/ecs) |
 | :black_square_button: **Additional content** |
 | [ejabberd-contrib](#ejabberd-contrib) | included | not included |

content/admin/configuration/modules.md

@@ -7,7 +7,7 @@ search:
 
 !!! info "Please note"
 
-    This section describes modules options of ejabberd [25.08](../../archive/25.08/index.md).  If you are using an old ejabberd release, please refer to the corresponding archived version of this page in the [Archive](../../archive/index.md).
+    This section describes modules options of ejabberd [25.10](../../archive/25.10/index.md).  If you are using an old ejabberd release, please refer to the corresponding archived version of this page in the [Archive](../../archive/index.md).
 
     The modules that changed in this version are marked with 🟤.
 
@@ -160,13 +160,15 @@ supported. When the module is loaded use [update_sql](../../developer/ejabberd-a
 
 The module has no options.
 
+**API Tags:** [sql](../../developer/ejabberd-api/admin-tags.md#sql)
+
 mod\_announce
 -------------
 
 This module enables configured users to broadcast announcements and to
 set the message of the day (MOTD). Configured users can perform these
 actions with an XMPP client either using Ad-Hoc Commands or sending
-messages to specific JIDs.
+messages to specific JIDs. Equivalent API commands are also available.
 
 !!! note
 
@@ -244,6 +246,9 @@ only.
 - **use\_cache**: `true | false`  
 Same as top-level [use_cache](toplevel.md#use_cache) option, but applied to this module only.
 
+**API Tags:**
+[announce](../../developer/ejabberd-api/admin-tags.md#announce)
+
 mod\_antispam
 -------------
 
@@ -435,11 +440,11 @@ __Available options:__
 
 - **access**: `AccessName`  
 The option is supposed to be used when `allow_local_users` and
-`allow_transports` are not enough. It’s an ACL where `deny` means the
-message will be rejected (or a CAPTCHA would be generated for a
-presence, if configured), and `allow` means the sender is whitelisted
-and the stanza will pass through. The default value is `none`, which
-means nothing is whitelisted.
+`allow_transports* are not enough. It’s an Access Rule where *deny`
+means the stanza will be rejected; there’s an exception if option
+`captcha` is configured. And `allow` means the sender is whitelisted and
+the stanza will pass through. The default value is `none`, which means
+nothing is whitelisted.
 
 - **allow\_local\_users**: `true | false`  
 This option specifies if strangers from the same local host should be
@@ -451,9 +456,10 @@ messages from any user of this server are accepted even if no
 subscription present. The default value is `true`.
 
 - **captcha**: `true | false`  
-Whether to generate CAPTCHA or not in response to messages from
-strangers. See also section [CAPTCHA](basic.md#captcha) of the
-Configuration Guide. The default value is `false`.
+Whether to generate CAPTCHA challenges in response to incoming presence
+subscription requests from strangers. See also section
+[CAPTCHA](basic.md#captcha) of the Configuration Guide. The default
+value is `false`.
 
 - **drop**: `true | false`  
 This option specifies if strangers messages should be dropped or not.
@@ -617,8 +623,11 @@ delivered. The default value is `true`.
 While a client is inactive, queue presence stanzas that indicate
 (un)availability. The default value is `true`.
 
-mod\_configure
---------------
+mod\_configure 🟤
+-----------------
+
+<!-- md:version improved in [25.10](../../archive/25.10/index.md) -->
+
 
 The module provides server configuration functionalities using
 [XEP-0030: Service Discovery](https://xmpp.org/extensions/xep-0030.html)
@@ -633,6 +642,30 @@ Commands](https://xmpp.org/extensions/xep-0050.html):
 
 -   Additional custom ad-hoc commands specific to ejabberd
 
+Ad-hoc commands from XEP-0133 that behave differently to the XEP:
+
+-   `get-user-roster`: returns standard fields instead of roster items
+    that client cannot display
+
+Those ad-hoc commands from XEP-0133 do not include in the response the
+client that executed the command:
+
+-   `get-active-users-num`
+
+-   `get-idle-users-num`
+
+-   `get-active-users`
+
+-   `get-idle-users`
+
+Those ad-hoc commands from XEP-0133 are not implemented:
+
+-   `edit-blacklist`
+
+-   `edit-whitelist`
+
+-   `edit-admin`
+
 This module requires [mod_adhoc](#mod_adhoc) (to execute the commands), and
 recommends [mod_disco](#mod_disco) (to discover the commands).
 
@@ -1421,6 +1454,14 @@ __Available options:__
 This access rule defines who is allowed to modify the MAM preferences.
 The default value is `all`.
 
+- **archive\_muc\_as\_mucsub 🟤`*: `true | false*  
+<!-- md:version added in [25.10](../../archive/25.10/index.md) -->
+ When this option is enabled
+incoming groupchat messages for users that have mucsub subscription to a
+room from which message originated will have those messages archived
+after being converted to mucsub event messages.The default value is
+`false`.
+
 - **assume\_mam\_usage**: `true | false`  
 This option determines how ejabberd’s stream management code (see
 [mod_stream_mgmt](#mod_stream_mgmt)) handles unacknowledged messages when the connection
@@ -1480,8 +1521,8 @@ default value is `false`.
 **API Tags:** [mam](../../developer/ejabberd-api/admin-tags.md#mam),
 [purge](../../developer/ejabberd-api/admin-tags.md#purge)
 
-mod\_matrix\_gw 🟤
-------------------
+mod\_matrix\_gw
+---------------
 
 <!-- md:version improved in [25.08](../../archive/25.08/index.md) -->
 
@@ -1909,11 +1950,11 @@ capability. The `Options` are:
    Short description of the room.
     The default value is an empty string.
 
-    - **enable\_hats**: `true | false`  
-   `Note` about this option: improved
-    in [25.03](../../archive/25.03/index.md). Allow extended roles as defined in XEP-0317 Hats. Check
-    the [MUC Hats](../../tutorials/muc-hats.md) tutorial. The default
-    value is `false`.
+    - **enable\_hats 🟤`*: `true | false*  
+   `Note` about this option:
+    improved in [25.10](../../archive/25.10/index.md). Allow extended roles as defined in XEP-0317 Hats.
+    Check the [MUC Hats](../../tutorials/muc-hats.md) tutorial. The
+    default value is `false`.
 
     - **lang**: `Language`  
    Preferred language for the discussions in the
@@ -2783,8 +2824,8 @@ modules:
       outgoing: all
 ~~~
 
-mod\_providers 🟤
------------------
+mod\_providers
+--------------
 
 <!-- md:version added in [25.08](../../archive/25.08/index.md) -->
 

content/admin/configuration/toplevel.md

@@ -7,7 +7,7 @@ search:
 
 !!! info "Please note"
 
-    This section describes top level options of ejabberd [25.08](../../archive/25.08/index.md).  If you are using an old ejabberd release, please refer to the corresponding archived version of this page in the [Archive](../../archive/index.md).
+    This section describes top level options of ejabberd [25.10](../../archive/25.10/index.md).  If you are using an old ejabberd release, please refer to the corresponding archived version of this page in the [Archive](../../archive/index.md).
 
     The options that changed in this version are marked with 🟤.
 
@@ -1123,21 +1123,15 @@ or it will lead to subtle bugs. Usually leaving default value of this is
 option is best, tweak it only if you know what you are doing. The
 default value is `1 minute`.
 
-## new\_sql\_schema
+## new\_sql\_schema 🟤
 
 `true | false`  
 
-Whether to use the
-[new SQL schema](database.md#default-and-new-schemas). All schemas are
-located at <https://github.com/processone/ejabberd/tree/25.08/sql>.
-There are two schemas available. The default legacy schema stores one
-XMPP domain into one ejabberd database. The `new` schema can handle
-several XMPP domains in a single ejabberd database. Using this `new`
-schema is best when serving several XMPP domains and/or changing domains
-from time to time. This avoid need to manage several databases and
-handle complex configuration changes. The default depends on
-configuration flag `--enable-new-sql-schema` which is set at compile
-time.
+<!-- md:version obsoleted in [25.10](../../archive/25.10/index.md) -->
+
+This option was renamed to
+[sql_schema_multihost](#sql_schema_multihost) in ejabberd [25.10](../../archive/25.10/index.md). Please update your
+configuration to use the new option name
 
 ## oauth\_access
 
@@ -1783,6 +1777,25 @@ The type of a request queue for the SQL server. See description of
 [queue_type](#queue_type) option for the explanation. The default value is the
 value defined in [queue_type](#queue_type) or `ram` if the latter is not set.
 
+## sql\_schema\_multihost 🟤
+
+`true | false`  
+
+<!-- md:version renamed in [25.10](../../archive/25.10/index.md) -->
+
+Whether to use the
+[multihost SQL schema](database.md#default-and-new-schemas). All
+schemas are located at
+<https://github.com/processone/ejabberd/tree/25.10/sql>. There are two
+schemas available. The legacy `singlehost` schema stores one XMPP domain
+into one ejabberd database. The `multihost` schema can handle several
+XMPP domains in a single ejabberd database. The `multihost` schema is
+preferable when serving several XMPP domains and/or changing domains
+from time to time. This avoid need to manage several databases and
+handle complex configuration changes. The default depends on
+configuration flag `--enable-sql-schema-multihost` which is set at
+compile time.
+
 ## sql\_server
 
 `Host | IP Address | ODBC Connection String | Unix Socket Path`