This feature was not used in 8 years and from frontend did not even
properly work anymore and was implemented using deprecated API.
So get rid of it.
The last version that was using a changelog from the changelog server
was Nextcloud 20.
We use the firstrunwizard nowadays for informing about Nextcloud
changes in new releases.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
The XHR error handling was duplicated, as we already handle this in
`core/src/init.js` where we intercept Fetch API and XHR API.
So we can drop this jQuery specific duplicate.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Make the class jQuery free to be able to drop it as a dependency.
Also added some unit tests for it.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
The API was not yet deprecated but is not used anymore,
so 1. added a deprecation so we can get rid of it in the future.
But until then we need to drop jQuery so refactored the code to use
vanilla JS.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
1. Remove unused legacy parts (no code match in the whole github
organization).
2. Consolidate `OC.Settings` in `core/src/OC` for consistency.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Show results from providers that don't support active content filters
(date/person) in a separate "Additional results" section with a note
explaining that some filters may have been ignored.
Changes:
- Add computed properties to separate filtered/unfiltered results
- Track filter compatibility using baseProvider for searchFrom providers
- Deduplicate results by resourceUrl across sections
- Skip in-folder results when at root to avoid duplicating Files results
- Fix providerIsCompatibleWithFilters to check correct filter properties
- Add styling for the unfiltered results section
Signed-off-by: nfebe <fenn25.fn@gmail.com>
When date range or person filters were applied, providers that didn't
support these filters were automatically disabled in the UI. This made
the in-folder filter appear auto-applied and prevented users from
searching non-compatible providers.
Remove automatic provider disabling logic from updateDateFilter(),
applyPersonFilter(), and removeFilter(). Content filters now apply only
to compatible providers via existing compatibility checks while keeping
all providers available for selection.
Signed-off-by: nfebe <fenn25.fn@gmail.com>
After ec9e283e there was still such a problem with the legacy app navigation
snapper that its width was only 266 px on the RTL layout instead of the
normal 300 px. The 266 px is the default width of Snap.js module. While the
left side snapper width is configured with the property maxPosition, the right
side snapper is configured by passing a negative value for the property
minPosition.
Signed-off-by: Pauli Järvinen <pauli.jarvinen@gmail.com>
With SSO setups users may otherwise be redirected to the IdP directly
instead of the regular login form that they reset the password for
Signed-off-by: Julius Knorr <jus@bitgrid.net>
- deprecated since Nextcloud 17
- To replace `OC.getHost` use `window.location.host`.
- To replace `OC.getHostName` use `window.location.hostname`.
- To replace `OC.getPort` use `window.location.port`.
- To replace `OC.getProtocol` use `window.location.protocol`.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Its deprecated since Nextcloud 18 and nowadays we have much more complex
logic for this.
So the proper replacement is to use `validateFilename` from
`@nextcloud/files` package.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
- Deprecated since Nextcloud 17
To replace `OC.redirect` directly use `window.location`.
To replace `OC.reload` directly use `window.location.reload`.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
In Nextcloud Vue v8 the `type` prop for dialog buttons
was deprecated and replaces with the `variant` prop.
In v9 the deprecated props are removed.
Use the `variant` prop in the deprecated `OC.dialogs`.
This is a follow up for #55726.
Signed-off-by: Max <max@nextcloud.com>
Cypress has some limitations:
- its vue 2 supported was removed
- it fails with our vue 3 migration due to 2 different vue versions
being present
- its slow compared to vitest
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
