mirror of
https://github.com/nextcloud/documentation.git
synced 2026-03-27 13:38:39 +07:00
fix(branchoff): Make internal doc links stay in Nextcloud 32 docs
Signed-off-by: Joas Schilling <coding@schilljs.com>
This commit is contained in:
@@ -191,9 +191,11 @@ Added APIs
|
||||
- ``OCP\Console\ReservedOptions`` was added and contains constants for options reserved for occ core features. ``--debug-log`` and ``--debug-log-level`` are now reserved by occ as they allow to show debug information to the output on any occ command.
|
||||
- ``OCP\Security\IHasher::validate()`` should return true if the passed string is a valid hash generated by ``OCP\Security\IHasher::hash()``
|
||||
- ``OCP\AppFramework\Http\JSONResponse()`` constructor now supports passing additional ``json_encode`` flags, see https://www.php.net/manual/en/function.json-encode.php for details
|
||||
- ``OCP\EventDispatcher\IWebhookCompatibleEvent`` is a new interface for events compatible with webhooks (`see webhook_listeners documentation <https://docs.nextcloud.com/server/latest/admin_manual/webhook_listeners/index.html>`_).
|
||||
- ``OCP\EventDispatcher\IWebhookCompatibleEvent`` is a new interface for events compatible with webhooks (`see webhook_listeners documentation <https://docs.nextcloud.com/server/32/admin_manual/webhook_listeners/index.html>`_).
|
||||
- ``OCP\EventDispatcher\JsonSerializer`` is a new public helper for serializing users and fileinfos to json (ie for webhook events)
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
Changed APIs
|
||||
^^^^^^^^^^^^
|
||||
|
||||
@@ -222,7 +224,9 @@ Changed APIs
|
||||
- ``OCP\IUserManager::getDisabledUsers`` now has a third parameter for a search string.
|
||||
- ``OCP\User\Backend\IProvideEnabledStateBackend::getDisabledUserList`` now has a third parameter for a search string.
|
||||
- Legacy class ``OC_EventSource`` was moved to ``OC`` namespace with the ``OC_`` prefix. It should not change anything if you already correctly use the ``OCP\IEventSourceFactory`` to create these objects.
|
||||
- ``OCP\Files\Events\Node\AbstractNodeEvent`` and ``OCP\Files\Events\Node\AbstractNodesEvent`` now implements ``OCP\EventDispatcher\IWebhookCompatibleEvent`` so that all file/folder related events are available for webhooks (`see webhook_listeners documentation <https://docs.nextcloud.com/server/latest/admin_manual/webhook_listeners/index.html>`_).
|
||||
- ``OCP\Files\Events\Node\AbstractNodeEvent`` and ``OCP\Files\Events\Node\AbstractNodesEvent`` now implements ``OCP\EventDispatcher\IWebhookCompatibleEvent`` so that all file/folder related events are available for webhooks (`see webhook_listeners documentation <https://docs.nextcloud.com/server/32/admin_manual/webhook_listeners/index.html>`_).
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
Deprecated APIs
|
||||
^^^^^^^^^^^^^^^
|
||||
|
||||
@@ -47,7 +47,7 @@ Admin audit logging
|
||||
|
||||
If you want to log things less for system administration but for compliance reasons, e.g. who accessed which file,
|
||||
who changed the password of an item or made it public, the
|
||||
`admin audit log <https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/logging_configuration.html#admin-audit-log>`_
|
||||
`admin audit log <https://docs.nextcloud.com/server/32/admin_manual/configuration_server/logging_configuration.html#admin-audit-log>`_
|
||||
is the correct place.
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
@@ -110,7 +110,7 @@ The last missing part is to register both classes inside **<myapp>/appinfo/info.
|
||||
`<personal>` instead.
|
||||
|
||||
Additionally since Nextcloud 23, groups can be granted authorization to access individual
|
||||
admin settings (`see admin docs <https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/admin_delegation_configuration.html>`_).
|
||||
admin settings (`see admin docs <https://docs.nextcloud.com/server/32/admin_manual/configuration_server/admin_delegation_configuration.html>`_).
|
||||
This is a feature that needs to be enabled for each admin setting class.
|
||||
To do so, the setting class needs to implement `IDelegatedSettings` instead of `ISettings`
|
||||
and implement two additional methods.
|
||||
|
||||
@@ -225,7 +225,7 @@ Federated Cloud Shares
|
||||
----------------------
|
||||
|
||||
Both the sending and the receiving instance need to have federated cloud sharing
|
||||
enabled and configured. See `Configuring Federated Cloud Sharing <https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/federated_cloud_sharing_configuration.html>`_.
|
||||
enabled and configured. See `Configuring Federated Cloud Sharing <https://docs.nextcloud.com/server/32/admin_manual/configuration_files/federated_cloud_sharing_configuration.html>`_.
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
|
||||
@@ -8,6 +8,6 @@ OCS TaskProcessing API
|
||||
|
||||
The OCS Task processing API allows you to run task processing tasks, like prompting large language models implemented by apps using :ref:`the backend Task Processing API<task_processing>`.
|
||||
|
||||
See the relevant `OpenAPI docs <https://docs.nextcloud.com/server/latest/developer_manual/_static/openapi.html#/operations/core-task_processing_api-schedule>`_.
|
||||
See the relevant `OpenAPI docs <https://docs.nextcloud.com/server/32/developer_manual/_static/openapi.html#/operations/core-task_processing_api-schedule>`_.
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
@@ -21,5 +21,7 @@ You can find additional information here:
|
||||
* `User manual`_
|
||||
* `Admin manual`_
|
||||
|
||||
.. _`User manual`: https://docs.nextcloud.com/server/latest/user_manual/en/desktop/index.html
|
||||
.. _`Admin manual`: https://docs.nextcloud.com/server/latest/admin_manual/desktop/index.html
|
||||
.. _`User manual`: https://docs.nextcloud.com/server/32/user_manual/en/desktop/index.html
|
||||
.. _`Admin manual`: https://docs.nextcloud.com/server/32/admin_manual/desktop/index.html
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
@@ -7,10 +7,12 @@ Context Chat
|
||||
.. versionadded:: 32.0.0
|
||||
|
||||
Nextcloud offers a **Context Chat** API which allows apps like files to submit data
|
||||
to the `Nextcloud Assistant Context Chat <https://docs.nextcloud.com/server/latest/admin_manual/ai/app_context_chat.html>`_,
|
||||
thereby enabling `Nextcloud Assistant <https://docs.nextcloud.com/server/latest/admin_manual/ai/app_assistant.html>`_
|
||||
to the `Nextcloud Assistant Context Chat <https://docs.nextcloud.com/server/32/admin_manual/ai/app_context_chat.html>`_,
|
||||
thereby enabling `Nextcloud Assistant <https://docs.nextcloud.com/server/32/admin_manual/ai/app_assistant.html>`_
|
||||
to answer questions, provide insights and search results based on the submitted data and natural language queries.
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
Implementing a content provider for Context Chat
|
||||
------------------------------------------------
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ Nextcloud AIO implements its own `Docker Socket Proxy container <https://github.
|
||||
you just need to tick the checkbox in the AIO configuration interface to enable it.
|
||||
AppAPI automatically creates the default Deploy daemon configuration for Nextcloud AIO.
|
||||
|
||||
See `Nextcloud in Docker AIO (all-in-one) <https://docs.nextcloud.com/server/latest/admin_manual/exapps_management/DeployConfigurations.html#nextcloud-in-docker-aio-all-in-one>`_ for more details.
|
||||
See `Nextcloud in Docker AIO (all-in-one) <https://docs.nextcloud.com/server/32/admin_manual/exapps_management/DeployConfigurations.html#nextcloud-in-docker-aio-all-in-one>`_ for more details.
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ Here are some common steps to verify the network configuration:
|
||||
ExApp deployment issues
|
||||
-----------------------
|
||||
|
||||
The deployment issues questions are covered in the `Test Deploy <https://docs.nextcloud.com/server/latest/admin_manual/exapps_management/TestDeploy.html>`_ section of the administration guide.
|
||||
The deployment issues questions are covered in the `Test Deploy <https://docs.nextcloud.com/server/32/admin_manual/exapps_management/TestDeploy.html>`_ section of the administration guide.
|
||||
Generally speaking, there are three steps to find the proper error message to understand the problem:
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
@@ -43,7 +43,7 @@ You can then compile them to ``.mo`` files using `ui_example's <https://github.c
|
||||
Manual install
|
||||
**************
|
||||
|
||||
For the ``manual-install`` type, an administrator will have to manually extract to the server's `writable apps directory <https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/config_sample_php_parameters.html#apps-paths>`_ ``l10n`` folder of the ExApp
|
||||
For the ``manual-install`` type, an administrator will have to manually extract to the server's `writable apps directory <https://docs.nextcloud.com/server/32/admin_manual/configuration_server/config_sample_php_parameters.html#apps-paths>`_ ``l10n`` folder of the ExApp
|
||||
(e.g. ``/path/to/apps-writable/<appid>/l10n/*.(js|json)``).
|
||||
This will allow the server to access the ExApp's strings with translations.
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ Request data
|
||||
}
|
||||
|
||||
|
||||
The possible values of ``log_lvl`` are described here: `Nextcloud Log level <https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/logging_configuration.html#log-level>`_
|
||||
The possible values of ``log_lvl`` are described here: `Nextcloud Log level <https://docs.nextcloud.com/server/32/admin_manual/configuration_server/logging_configuration.html#log-level>`_
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ Please follow the steps on this page to set up your development environment manu
|
||||
Set up Web server and database
|
||||
------------------------------
|
||||
|
||||
First `set up your Web server and database <https://docs.nextcloud.com/server/latest/admin_manual/installation/index.html>`_ (**Section**: Manual Installation - Prerequisites).
|
||||
First `set up your Web server and database <https://docs.nextcloud.com/server/32/admin_manual/installation/index.html>`_ (**Section**: Manual Installation - Prerequisites).
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
@@ -25,7 +25,7 @@ Get the source
|
||||
|
||||
There are two ways to obtain Nextcloud sources:
|
||||
|
||||
* Using the `stable version <https://docs.nextcloud.com/server/latest/admin_manual/installation/index.html>`_
|
||||
* Using the `stable version <https://docs.nextcloud.com/server/32/admin_manual/installation/index.html>`_
|
||||
* Using the development version from `GitHub`_ which will be explained below.
|
||||
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
Reference in New Issue
Block a user