Upgrade to Nextcloud 30

General

Front-end changes

Font sizes

Nextcloud now provides meaningful default styles for heading elements. This can cause visual regressions if your code does not explicitly set font size and weight. If you need to use heading elements outside of text content, you might need to adjust their styles.

Added APIs

Changed APIs

Removed APIs

Removed globals

Deprecated APIs

  • OC.dialogs.fileexists was already deprecated in Nextcloud 29, but is now also marked as such. Use openConflictPicker from @nextcloud/upload instead.

  • Most OC.dialogs API is now deprecated and will be removed in the future. For generic dialogs use the DialogBuilder from the @nextcloud/dialogs. A list of the now deprecated methods:

    • OC.dialogs.alert

    • OC.dialogs.info

    • OC.dialogs.confirm

    • OC.dialogs.confirmDestructive

    • OC.dialogs.confirmHtml

    • OC.dialogs.prompt

    • OC.dialogs.message

Back-end changes

Support for PHP 8.0 removed

In this release support for PHP 8.0 was removed. Follow the steps below to make your app compatible.

  1. If appinfo/info.xml has a dependency specification for PHP, increase the min-version to 8.1.

<dependencies>
  <php min-version="8.1" max-version="8.3" />
  <nextcloud min-version="27" max-version="30" />
</dependencies>

  1. If your app has a composer.json and the file contains the PHP restrictions from info.xml, adjust it as well.

{
  "require": {
    "php": ">=8.1 <=8.3"
  }
}

  1. If you have continuous integration set up, remove PHP 8.0 from the matrices of tests and linters.

Added APIs

  • OCP\Notification\IncompleteNotificationException is thrown by OCP\Notification\IManager::notify() when not all required fields have been set on the OCP\Notification\INotification object

  • OCP\Notification\IncompleteParsedNotificationException is thrown by OCP\Notification\IManager::prepare() when no OCP\Notification\INotifier handled the OCP\Notification\INotification object

  • OCP\Notification\InvalidValueException is thrown by OCP\Notification\IAction::set*() and OCP\Notification\INotification::set*() when the value did not match the required criteria

  • OCP\Notification\UnknownNotificationException should be thrown by OCP\Notification\INotifier::prepare() when they didn’t handle the notification

Changed APIs

  • OCP\Notification\IAction::set*() (all setters) throw OCP\Notification\InvalidValueException instead of \InvalidArgumentException when the value does not match the required criteria.

  • Calling OCP\Notification\IAction::setLink() with a relative URL is deprecated and will throw OCP\Notification\InvalidValueException in a future version.

  • OCP\Notification\IApp::notify() throws OCP\Notification\IncompleteNotificationException instead of \InvalidArgumentException when a required field is not set before notifying.

  • OCP\Notification\IManager::prepare() throws OCP\Notification\IncompleteParsedNotificationException instead of \InvalidArgumentException when a required field is not set after preparing a notification.

  • OCP\Notification\INotification::set*() (all setters) throw OCP\Notification\InvalidValueException instead of \InvalidArgumentException when the value does not match the required criteria.

  • Calling OCP\Notification\INotification::setLink() with a relative URL is deprecated and will throw OCP\Notification\InvalidValueException in a future version.

  • Calling OCP\Notification\INotification::setIcon() with a relative URL is deprecated and will throw OCP\Notification\InvalidValueException in a future version.

  • OCP\Notification\INotifier::prepare() should no longer throw \InvalidArgumentException. OCP\Notification\UnknownNotificationException should be thrown when the notifier does not want to handle the notification. \InvalidArgumentException are logged as debug for now and will be logged as error in the future to help developers find issues from code that unintentionally threw \InvalidArgumentException

Removed APIs

Removed events