If for whatever reason appdata got into a strange state this will at
least propegate up and not make it do boom the next run.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
LDAP plugins must change the createUser method to return the DN, as we
need this to update the cache.
Signed-off-by: Vinicius Cubas Brand <viniciuscb@gmail.com>
This commit fix an error happening when the subadmin tries to create an
user, adding him/her to the group s/he is subadmin of, using a LDAP
User/Group plugin.
This just forces the cache to be reset after an user is added to a
group.
Signed-off-by: Vinicius Cubas Brand <viniciuscb@gmail.com>
This fixes collisions that were causing uploads to break in a very
terrible way.
Kudos to @kesselb for finding the problematic place and to
@hottwister for the proposed solution.
Fixes#10527.
If a file is on external storage there is no owner. WHich means we can't
check. So just return an empty array then.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Don't try to connect to the lookup server if the lookup server was disabled
by the admin or an empty lookup server URL was given
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
we can only store etags up to 40 characters long in the database, so when we get an etag that's longer we simply hash it to bring down the length
Signed-off-by: Robin Appelman <robin@icewind.nl>
* tests/acceptance/features/login.feature:15
<details><summary>Show full log</summary>
```
Scenario: log in with valid user and invalid password once fixed by admin # /drone/src/github.com/nextcloud/server/tests/acceptance/features/login.feature:15
Given I act as John # ActorContext::iActAs()
And I can not log in with user user0 and password 654231 # LoginPageContext::iCanNotLogInWithUserAndPassword()
When I act as Jane # ActorContext::iActAs()
And I am logged in as the admin # LoginPageContext::iAmLoggedInAsTheAdmin()
And I open the User settings # SettingsMenuContext::iOpenTheUserSettings()
And I set the password for user0 to 654321 # UsersSettingsContext::iSetTheFieldForUserTo()
And I act as John # ActorContext::iActAs()
And I log in with user user0 and password 654321 # LoginPageContext::iLogInWithUserAndPassword()
Then I see that the current page is the Files app # FilesAppContext::iSeeThatTheCurrentPageIsTheFilesApp()
Failed asserting that 'http://acceptance-login/index.php/login?user=user0' starts with "http://acceptance-login/index.php/apps/files/".
```
</details>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Fails with:
* tests/acceptance/features/app-files.feature:90
<details><summary>Show full log</summary>
```
Scenario: show favorites # /drone/src/github.com/nextcloud/server/tests/acceptance/features/app-files.feature:90
Given I am logged in # LoginPageContext::iAmLoggedIn()
And I mark "welcome.txt" as favorite # FileListContext::iMarkAsFavorite()
When I open the "Favorites" section # AppNavigationContext::iOpenTheSection()
Then I see that the current section is "Favorites" # AppNavigationContext::iSeeThatTheCurrentSectionIs()
Then I see that the file list contains a file named "welcome.txt" # FileListContext::iSeeThatTheFileListContainsAFileNamed()
Row for file welcome.txt in file list could not be found after 100 seconds (NoSuchElementException)
```
</details>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Fails with:
* tests/acceptance/features/apps.feature:66
<details><summary>Show full log</summary>
```
Scenario: Show section from app store # /drone/src/github.com/nextcloud/server/tests/acceptance/features/apps.feature:66
Given I act as Jane # ActorContext::iActAs()
And I am logged in as the admin # LoginPageContext::iAmLoggedInAsTheAdmin()
And I open the Apps management # SettingsMenuContext::iOpenTheAppsManagement()
And I see that the current section is "Your apps" # AppNavigationContext::iSeeThatTheCurrentSectionIs()
When I open the "Files" section # AppNavigationContext::iOpenTheSection()
Files section item in App Navigation could not be found after 100 seconds (NoSuchElementException)
Then I see that there some apps listed from the app store # AppsManagementContext::iSeeThatThereSomeAppsListedFromTheAppStore()
And I see that the current section is "Files" # AppNavigationContext::iSeeThatTheCurrentSectionIs()
```
</details>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Fails with:
* tests/acceptance/features/app-files-tags.feature:42
<details><summary>Show full log</summary>
```
Scenario: add tags using the dropdown in the details view # /drone/src/github.com/nextcloud/server/tests/acceptance/features/app-files-tags.feature:42
Given I am logged in as the admin # LoginPageContext::iAmLoggedInAsTheAdmin()
And I visit the settings page # SettingsMenuContext::iVisitTheSettingsPage()
And I open the "Tag management" section # AppNavigationContext::iOpenTheSection()
And I see that the button to select tags is shown # SettingsContext::iSeeThatTheButtonToSelectTagsIsShown()
And I create the tag "tag1" in the settings # SettingsContext::iCreateTheTagInTheSettings()
And I create the tag "tag2" in the settings # SettingsContext::iCreateTheTagInTheSettings()
And I create the tag "tag3" in the settings # SettingsContext::iCreateTheTagInTheSettings()
And I create the tag "tag4" in the settings # SettingsContext::iCreateTheTagInTheSettings()
And I see that the dropdown for tags in the settings eventually contains the tag "tag1" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag()
And I see that the dropdown for tags in the settings eventually contains the tag "tag2" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag()
And I see that the dropdown for tags in the settings eventually contains the tag "tag3" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag()
And I see that the dropdown for tags in the settings eventually contains the tag "tag4" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag()
And I log out # SettingsMenuContext::iLogOut()
And I am logged in # LoginPageContext::iAmLoggedIn()
And I open the details view for "welcome.txt" # FileListContext::iOpenTheDetailsViewFor()
And I open the input field for tags in the details view # FilesAppContext::iOpenTheInputFieldForTagsInTheDetailsView()
When I check the tag "tag2" in the dropdown for tags in the details view # FilesAppContext::iCheckTheTagInTheDropdownForTagsInTheDetailsView()
And I check the tag "tag4" in the dropdown for tags in the details view # FilesAppContext::iCheckTheTagInTheDropdownForTagsInTheDetailsView()
Then I see that the tag "tag2" in the dropdown for tags in the details view is checked # FilesAppContext::iSeeThatTheTagInTheDropdownForTagsInTheDetailsViewIsChecked()
And I see that the tag "tag4" in the dropdown for tags in the details view is checked # FilesAppContext::iSeeThatTheTagInTheDropdownForTagsInTheDetailsViewIsChecked()
And I see that the input field for tags in the details view contains the tag "tag2" # FilesAppContext::iSeeThatTheInputFieldForTagsInTheDetailsViewContainsTheTag()
Failed asserting that false is true.
And I see that the input field for tags in the details view contains the tag "tag4" # FilesAppContext::iSeeThatTheInputFieldForTagsInTheDetailsViewContainsTheTag()
```
</details>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Fails with:
* build/integration/federation_features/federated.feature:183
* build/integration/federation_features/federated.feature:232
* build/integration/federation_features/federated.feature:247
* build/integration/federation_features/federated.feature:263
<details><summary>Show full log</summary>
```
Scenario: Reshare a federated shared file # /drone/src/github.com/nextcloud/server/build/integration/federation_features/federated.feature:183
Given Using server "REMOTE" # FederationContext::usingServer()
And user "user1" exists # FederationContext::assureUserExists()
And user "user2" exists # FederationContext::assureUserExists()
And Using server "LOCAL" # FederationContext::usingServer()
And user "user0" exists # FederationContext::assureUserExists()
And User "user0" from server "LOCAL" shares "/textfile0.txt" with user "user1" from server "REMOTE" # FederationContext::federateSharing()
And User "user1" from server "REMOTE" accepts last pending share # FederationContext::acceptLastPendingShare()
And Using server "REMOTE" # FederationContext::usingServer()
And As an "user1" # FederationContext::asAn()
When creating a share with # FederationContext::creatingShare()
| path | /textfile0 (2).txt |
| shareType | 0 |
| shareWith | user2 |
| permissions | 19 |
Then the OCS status code should be "100" # FederationContext::theOCSStatusCodeShouldBe()
Failed asserting that SimpleXMLElement Object &000000007d8e0d3c00000000403fd08a (
0 => '404'
) matches expected '100'.
...
{"message":"Can not find share with ID: 8"}
Scenario: Overwrite a federated shared folder as recipient # /drone/src/github.com/nextcloud/server/build/integration/federation_features/federated.feature:232
Given Using server "REMOTE" # FederationContext::usingServer()
And user "user1" exists # FederationContext::assureUserExists()
And user "user2" exists # FederationContext::assureUserExists()
And Using server "LOCAL" # FederationContext::usingServer()
And user "user0" exists # FederationContext::assureUserExists()
And User "user0" from server "LOCAL" shares "/PARENT" with user "user1" from server "REMOTE" # FederationContext::federateSharing()
And User "user1" from server "REMOTE" accepts last pending share # FederationContext::acceptLastPendingShare()
And Using server "REMOTE" # FederationContext::usingServer()
And As an "user1" # FederationContext::asAn()
And User "user1" modifies text of "/textfile0.txt" with text "BLABLABLA" # FederationContext::modifyTextOfFile()
When User "user1" uploads file "../../data/user1/files/textfile0.txt" to "/PARENT (2)/textfile0.txt" # FederationContext::userUploadsAFileTo()
Client error: `PUT http://localhost:8180/remote.php/webdav/PARENT%20(2)/textfile0.txt` resulted in a `404 Not Found` response:
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DA (truncated...)
(GuzzleHttp\Exception\ClientException)
...
{"message":"Can not find share with ID: 10"}
Scenario: Overwrite a federated shared file as recipient using old chunking # /drone/src/github.com/nextcloud/server/build/integration/federation_features/federated.feature:247
Given Using server "REMOTE" # FederationContext::usingServer()
And user "user1" exists # FederationContext::assureUserExists()
And user "user2" exists # FederationContext::assureUserExists()
And Using server "LOCAL" # FederationContext::usingServer()
And user "user0" exists # FederationContext::assureUserExists()
And User "user0" from server "LOCAL" shares "/textfile0.txt" with user "user1" from server "REMOTE" # FederationContext::federateSharing()
And User "user1" from server "REMOTE" accepts last pending share # FederationContext::acceptLastPendingShare()
And Using server "REMOTE" # FederationContext::usingServer()
And As an "user1" # FederationContext::asAn()
And user "user1" uploads chunk file "1" of "3" with "AAAAA" to "/textfile0 (2).txt" # FederationContext::userUploadsChunkFileOfWithToWithChecksum()
Client error: `PUT http://localhost:8180/remote.php/webdav/textfile0%20(2).txt-chunking-42-3-0` resulted in a `404 Not Found` response:
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DA (truncated...)
(GuzzleHttp\Exception\ClientException)
...
{"message":"Can not find share with ID: 11"}
Scenario: Overwrite a federated shared folder as recipient using old chunking # /drone/src/github.com/nextcloud/server/build/integration/federation_features/federated.feature:263
Given Using server "REMOTE" # FederationContext::usingServer()
And user "user1" exists # FederationContext::assureUserExists()
And user "user2" exists # FederationContext::assureUserExists()
And Using server "LOCAL" # FederationContext::usingServer()
And user "user0" exists # FederationContext::assureUserExists()
And User "user0" from server "LOCAL" shares "/PARENT" with user "user1" from server "REMOTE" # FederationContext::federateSharing()
And User "user1" from server "REMOTE" accepts last pending share # FederationContext::acceptLastPendingShare()
And Using server "REMOTE" # FederationContext::usingServer()
And As an "user1" # FederationContext::asAn()
And user "user1" uploads chunk file "1" of "3" with "AAAAA" to "/PARENT (2)/textfile0.txt" # FederationContext::userUploadsChunkFileOfWithToWithChecksum()
Client error: `PUT http://localhost:8180/remote.php/webdav/PARENT%20(2)/textfile0.txt-chunking-42-3-0` resulted in a `404 Not Found` response:
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DA (truncated...)
(GuzzleHttp\Exception\ClientException)
...
{"message":"Can not find share with ID: 12"}
```
</details>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Fails with:
There was 1 failure:
1) TrashbinTest::testExpireOldFiles
Failed asserting that null is identical to 'file2.txt'.
/drone/src/github.com/nextcloud/server/apps/files_trashbin/tests/TrashbinTest.php:186
OR
1) TrashbinTest::testExpireOldFiles
Failed asserting that null is identical to 'file2.txt'.
/drone/src/github.com/nextcloud/server/apps/files_trashbin/tests/TrashbinTest.php:193
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Nested groups are now cached in a CappedMemoryCache object to reduce
queries to the LDAP backend.
Signed-off-by: Roland Tapken <roland@bitarbeiter.net>
The previous patch fixed the problem only for one level of indirection
because groupsMatchFilter() had been applied on each recursive call (and
thus there would be no second level if the first level fails the check).
This new implementation replaces the recursive call with a stack that
iterates all nested groups before filtering with groupsMatchFilter().
Signed-off-by: Roland Tapken <roland@bitarbeiter.net>
Currently groupsMatchFilter is called before nested groups are resolved.
This basicly breaks this feature since it is not possible to inherit
membership in a group from another group.
Minimal example:
Group filter: (&(objectClass=group),(cn=nextcloud))
Nested groups: enabled
cn=nextcloud,ou=Nextcloud,ou=groups,dn=company,dn=local
objectClass: group
cn=IT,ou=groups,dn=company,dn=local
objectClass: group
memberOf: cn=nextcloud,ou=Nextcloud,ou=groups,dn=company,dn=local
cn=John Doe,ou=users,dn=company,dn=local
objectClass: person
memberOf: cn=IT,ou=groups,dn=company,dn=local
Since 'cn=IT,ou=groups,dn=company,dn=local' doesn't match the group
filter, John wouldn't be a member of group 'nextcloud'.
This patch fixes this by filtering the groups after all nested groups
have been collected. If nested groups is disabled the result will be the
same as without this patch.
Signed-off-by: Roland Tapken <roland@bitarbeiter.net>
If the job is still present we should also not fire it off if there is
not a single active 2FA provider.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#14125
Listen to 2FA disable event. If a provider is disabled for a user. We
check if there are no more providers. If there are no more providers we
Remove the backupcode reminder notification (if still present).
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
When $data is null (which can happen when $request->getBodyAsStream() returns
null), the Exceptions says "copied bytes: 0, expected filesize: 0", which
sounds more like success...
when an addBodyListItem() is not directly followed by addBodyButton(), resulting HTML is broken
Signed-off-by: Tomasz Paluszkiewicz <tomasz.paluszkiewicz@gmail.com>
Without the lookupserver GS is kind of useless.
If the admin places their lookup sever outside of the reachable network
that is not something we can help.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#14298
If a storage doesn'tclose the write stream then $isEOF is not yet set.
So we have to fallback.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
The stream is already closed at this point. Which means feof will always
return false. We have to determine if the stream is EOF in the
preCloseCallback. And pass this info along. Then the logic works as
expected.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#12568
Since the clearing of the execution context causes another reload. We
should not do the redirect_uri handling as this results in redirecting
back to the logout page on login.
This adds a simple middleware that will just check if the
ClearExecutionContext session variable is set. If that is the case it
will just redirect back to the login page.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
otherwise they will be skipped when the results is being formatted and the
lower-cased result keys do not match.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
When a single file was dropped on the trash bin the file information was
gotten from the original element in the file list. When several files
were dropped on the trash bin the file information was gotten from the
helper elements being dragged around. The helper element also contain
the needed file information when a single file is being dragged, so the
handling was unified to always get the file information from the helper
elements.
As the handling of several files is the same as before there is still
the issue of only deleting those files shown in the drag helper instead
of all the selected files.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The "droppedOnTrash" event was being triggered when the file list was
initialized, but it should be triggered only when the user actually
drops a file on the trash bin.
Besides that, the event had no effect; only the file list handles it,
but as it was not triggered on any element it ended being triggered on
the document, and thus not handled. Moreover, even if it had been
triggered on the file list it would have been done before the handler
was set, so it would not have been handled anyway. And even if it had
been handled no data was provided, so the handler would have failed.
In conclusion, triggering the event there was not needed, and thus it
was removed.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Since 6ad7f32938 SVG icons are directly embedded in "icons-vars.css", so
the starred trash icon is now loaded along with the regular trash icon
all at once. Therefore it is not needed to explicitly prefetch it using
a hidden div.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
In order to show the autocompletion it was needed to type at least
another character after "@", so only the mentions that matched that
character were shown. Now the autocompletion is shown as soon as "@" is
typed, which shows all the possible mentions.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
log the error in case a notification mail of a new share couldn't
be send to the recipient and finish the share operation successfully
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
When a password is reste we should make sure that all users are properly
logged in. Pending states should be cleared. For example a session where
the 2FA code is not entered yet should be cleared.
The token is now removed so the session will be killed the next time
this is checked (within 5 minutes).
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
To make sure that the versions in the legacy backend are shared again we
have to check the storage of a file. Since all shared files are still on
the owners storage.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
The password input was shown in the popup menu when passwords were not
enforced, or when they were enforced but no password was set, which
prevented updating/changing the password once set. As the password input
should be shown too when password are enforced and a password is set no
condition is needed, so now the password input is always shown.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When the uploaded files have a relative path (that is, when a folder is
uploaded) it is first ensured that all the parent folders exist, which
is done by trying to create them. When a folder is created in the
currently opened folder the file list is updated and a row for the new
folder is added. However, this was done too when the folder already
existed, which caused the previous row to be removed and a new one added
to replace it.
For security reasons, some special headers need to be set in requests;
this is done automatically for jQuery by handling the "ajaxSend" event
in the document. In the case of DAV requests, if the headers are not set
the server rejects the request with "CSRF check not passed".
When a file or folder is dropped on a folder row the jQuery upload
events are chained from the initial drop event, which has the row as its
target. In order to upload the file jQuery performs a request, which
triggers the "ajaxSend" event in the row; this event then bubbles up to
the document, which is then handled by adding the special headers to the
request.
However, when a folder was dropped on a folder row that folder row was
removed when ensuring that the folder exists. The jQuery upload events
were still triggered on the row, but as it had been removed it had no
parent nodes, and thus the events did not bubble up. Due to this the
"ajaxSend" event never reached the document when triggered on the
removed row, the headers were not set, and the upload failed.
All this is simply fixed by not removing the folder row when trying to
create it if it existed already.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
parallel search is not compatible with paged search, but the letter is
usually always applied.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
If the remember_login_cookie_lifetime is set to 0 this means we do not
want to use remember me at all. In that case we should also not creatae
a remember me cookie and should create a proper temp token.
Further this specifies that is not 0 the remember me time should always
be larger than the session timeout. Because else the behavior is not
really defined.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#13285
The wrapper logger should not be used here. But we need the real logger.
Since this in internal we can just pass that on directly.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
It seems iOS doesn't like us to change the location. So now we submit it
to the server that geneartes the redirect.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Admin should _not_ be able to change password when:
- if an encryption module is loaded and it uses per-user keys
- if encryption is enabled but no encryption modules are loaded
Admin should be able to change the password when:
- no encryption module is loaded and encryption is disabled
- encryption module is loaded but it doesn't require per user keys
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
Before the joining and filtering removed unkown files. Resulting in
manual queries for all the files with no (unread) comments (the 99%).
Long story short. This will return a list of all the files in the parent
folder with their unread comment count (can be 0). But this makes sure
that the result is properly cached. In the dav handling.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
"OC.dirname" removes everything after the last "/", so a path without
slashes is returned without changes. "result.path" does not include
leading nor trailing "/", so when the path is for a file or folder in
the base folder "OC.dirname(result.path)" returns "result.path".
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When id column has no autoincrement flag query for lastInsertId fails
on postgres because no value has been generated. Call lastInsertId only
if id is null.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
Else on scss files we'd get <file>?v=<hash>?v=<hash2>
This is of course not valid. Now it becomes <file>?v=<hash>-<hash2>
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#7084
Now entering wrongly cased email (roeland@ instead of Roeland@) for
password reset etc. Will also work.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Because the redirect from the SAML/SSO endpoint is a POST the lax/strict
cookies are not properly send.
Note that it is not strictly requried on this endpoint as we do not need
the remember me data. Only the real session info is enough. The endpoint
is also already protected by a state token.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
during login they might be cached as non-existing and cause an Exception
in the long run
reduces some duplication, too
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
This prevent the object store and cache from getting out of sync
when an objectstore silently fails or the php process get's killed
during the upload without giving us the chance to cleanup
Signed-off-by: Robin Appelman <robin@icewind.nl>
Disabled buttons use the default cursor, but as the cursor property for
primary buttons is set after the cursor property for disabled buttons
the latter is always overridden, even if the primary button is also
disabled. Due to this it is necessary to explicitly set the default
cursor for disabled primary buttons.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Fixes#12588
Probably needs more fixing for the other cases. But this is the quick
fix I could come up with for now.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
When a touch is done (i.e. when creating a new file in the node API)
The hooks contain 'write' and 'touch' (and the operation is touch as
well). This would cause a double write update. Which doesn't make sense.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
The second execute statement should be inside the if block. Else it gets
executed twice which makes no sense.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#9058
If the option to autocomplete users is disabled. We also should not
enumerate the users on this endpoint.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
c23a66cda4 broke the system address book.
We now move the ACL rules for this special case up and all is good in
the world again.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Having both "FilesAppSharingContext" and "FilesSharingAppContext" was
confusing, so "FilesSharingAppContext" was renamed to a more descriptive
name.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
To reshare a file there must be at least three enabled users in the
system; although it would be possible to run the steps to create a third
user in the scenarios that need it for convenience a third enabled user
besides "admin" and "user0" was added to the default setup.
In a similar way, a new step was added too to login as a given user
name, similar to the steps to log in as "user0" and as "admin".
Finally, another actor, "Jim", was introduced for those scenarios which
should be played by three standard actors (that is, without a special
configuration like "Rubeus").
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
If the server is too slow, changing to a different file immediately
after sending a new comment but without waiting for the comment to be
shown for the original file could cause the new comment to be shown for
the current file instead.
This is, indeed, a bug in the comments. However, it is not possible to
test it reliably in the acceptance tests, as it depends on how fast the
server adds the message and how fast the client changes to a different
file; sometimes the test would fail and sometimes it would not.
Therefore, now it is waited for the comment to be added before changing
to another file, as in this case it can be reliably tested that changing
to a different file does not cause the comments from the previous file
to be shown in the current file (this was a different bug already fixed
and due to which this test was added in the first place).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When the "Comments" tab is open the empty content element is always in
the DOM, although it is only shown once the message collection was
fetched and there were no messages. Due to this it is necessary to
explicitly wait for it to be shown instead of relying on the implicit
wait made to find the element; otherwise it would be found immediately
and if the collection was not fetched yet it would not be visible,
causing the test to fail.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Navigating to the root folder is already handled by
OCA.Files.Navigation.setActiveItem in case the view doesn't change.
Signed-off-by: Julius Härtl <jus@bitgrid.net>
When a view is rendered it should not be concerned with where it is
going to be placed in the document; in general this should be a
responsibility of the object using the view.
Moreover, when the details view is rendered it should simply prepare a
skeleton that includes the root elements provided by the plugins; those
elements will be updated by the plugins as needed when a file or a tab
is selected.
Finally, the details view should not be explicitly rendered. The
rendering removes the previous elements, but that is needed only when
the details view is in a dirty state, that is, when new plugins were
added since the last time that it was rendered. However, that dirty
state is internally handled, and the view is automatically rendered
again if needed when a file info is set.
Due to all that the details view is no longer explicitly rendered when
updating it with a different file. Also, as each file list has its own
details view, and each details view has its own element, but there can
be only one details view/sidebar element in the document, when the file
list updates the details view it also replaces the current one in the
document with its own details view if needed (that is, if it is not the
current one already).
Besides that, when the element of a details view is replaced with the
element of a different details view the old one should be detached from
the document, but never removed. Otherwise the event handlers would not
work when that element is attached again later (when changing to a
different section in the Files app and then going back to the previous
one).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Tab headers that should not be shown are marked with the "hidden" CSS
class. The CSS rules set "display: none" for ".hidden" elements, but as
the rules for ".tabHeaders .tabHeader" are more specific than rules for
".hidden" the "display" property is overriden and ends being "flex".
Therefore, it is necessary to explicitly set a rule for ".tabHeaders
.tabHeader.hidden" elements.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Fixes#12498
This means that we set that it is a proper app token once it is
validated. This will allow the 2FA middleware to just run the same
check.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* integrity warning is shown during update and in the admin setup checks
* there is also the plan to retire this old way of notification
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* fixes#9305 by not being prone to the race condition in insertIfNotExists
* fixes#6899 by not using a query that can result in a deadlock
* replaces the insertIfNotExists call with an insert which is wrapped into a try-catch block
* followup to #12371
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* fixes#6160 by not being prone to the race condition in insertIfNotExists
* fixes#12228 by not using a query that can result in a deadlock
* replaces the insertIfNotExists call with an insert which is wrapped into a try-catch block
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
The "Download" item in the menu of public share pages is no longer shown
in wide (>768px) windows (although the element is in the DOM and shown
if resized to a narrow window).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
For local users / groups the display name is enough to show, we just need details for email/remote shares
Signed-off-by: Julius Härtl <jus@bitgrid.net>
LDAP servers respond with that even if a limit was passed with the
request. Having this statement logged causes a lot of confusion.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Due to legacy reasons the password of link shares was returned in the
"share_with" and "share_with_displayname" parameters of the response
data. Now a proper "password" parameter is returned too; the old
"share_with" and "share_with_displayname" parameters are kept, although
deprecated, and they will be removed in a future version of Nextcloud.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Fixes#1020
When an external storage is shared with you in full the root is ''
(empty). This adds an extra check for an empty jail basically.
Because if the jail is on the empty string. It matches all paths.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
There is no reason to log FileLock errors as exceptions to the log file.
Locks happen for very legit reasons and it is actually a sign of the
code doing its job.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
fixes#10934
Else it triggers the rendering two times. Resulting is weird state in
for example the comments. Because the comments for OLD_FILEID are
retrieved but then the model is changed to NEW_FILEID. But the old
comments still get in and get parsed.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
In the acceptance tests the link share menu is automatically opened if
needed before interacting with an item in the menu; if the menu is not
open it is opened by clicking on its toggle.
However, since a recent change the link share menu is automatically
opened by the regular UI after the link share is created. This causes
that, sometimes, after the creation of a link share the acceptance tests
check whether the menu is shown or not before the menu was automatically
opened; as the menu is not open then the acceptance tests proceed to
click on the toggle, but in the meantime the link share was created and
the menu opened, so clicking on the toggle now closes it. As the menu is
closed it is not possible to interact with its items and the test fails.
To prevent that now the acceptance tests wait for the link share menu to
open after a link share is created before continuing with the other
steps.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
If the sendmail binary can't be found at all we fallback to the default
path.
It most likely is not there but then at least a proper error message
pops up.
Updated the tests to also properly pass.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
`sendmail` can very well be in a path different from
`/usr/sbin/sendmail`.
We already search `$PATH` at `lib/private/Settings/Admin/Mail.php` to
detect whether we want to offer sendmail as a mail transfer method, so
let's be consistent and actually initialize `\Swift_SendmailTransport`
with this path to sendmail, instead of just hardcoding
`/usr/sbin/sendmail`.
Signed-off-by: Florian Klink <flokli@flokli.de>
If the userbackend doesn't allow validating the password for a given uid
then there is no need to perform this check.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
On some backends (saml for example) users can't revalidate their
passwords as Nextcloud has no way to do verify it.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
When Talk is enabled the menu for link shares now shows a checkbox to
protect the password by Talk (that is, to show the "Request password by
Talk" UI in the authentication page for the link share).
Although in e-mail shares protecting the share with a password and
protecting the password by Talk are mutually exclusive actions (as when
the password is set it is sent to the sharee, so it must be set again
when protecting it by Talk to be able to verify the identity of the
sharee), in the case of link shares protecting the password by Talk is
an additional step to protecting the share with a password (as just
setting the password does not disclose it to anyone). As such, the
checkbox is shown only when there is a password set for the link share
(even if the field itself for the password is not shown, like when they
are enforced in the settings).
Note that the icon set for the field, "icon-passwordtalk", does not
currently exist; it is the same used for e-mail shares, and it is needed
simply to get the right padding in the menu.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The update share tests only checked that the share returned by
"update()" had the expected values. However, as "update()" returns the
same share that was given as a parameter the tests were not really
verifying that the values were updated in the database.
In a similar way, the test that checked that a password was removed did
not set a password first, so even if the database returned null it could
be simply returning the default value for the share; a password must be
set first to ensure that it is removed.
Besides that, a typo was fixed too that made the checks on the original
share instead of on the one returned by "update()"; right now it is the
same share, so the change makes no difference, but it is how the check
should be done anyway.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Although now it is possible to create several link shares the acceptance
tests currently handles only the first link share; this first link share
is now created by clicking an "Add new share" button instead of a
checkbox.
Besides that, the "Copy link" button has been moved from the menu to the
row, next to the menu trigger.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
If a user can't authenticate normally (because they have 2FA that is not
available on their devices for example). The redirect that is generated
should be of the proper format.
This means
1. Include the protocol
2. Include the possible subfolder
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Allows apps to register version backends for storage types
The existing versions backend is wrapped in a "legacy" backend.
Signed-off-by: Robin Appelman <robin@icewind.nl>
this removes the need for temporary storages with some external storage backends.
The new method is added to a separate interface to maintain compatibility with
storage backends implementing the storage interface directly (without inheriting common)
Currently the interface is implemented for objectstorage based storages and local storage
and used by webdav uploads
Signed-off-by: Robin Appelman <robin@icewind.nl>
Before we'd round up all preview request to their nearest power of two.
This resulted still in a lot of possible images. Generating a lot of
server load and taking up a lot of space.
This moves it to previews to be powers of 4: 64, 256, 1024 and 4096
Also the first two powers are always skipped (4, 16) as it doesn't make
sense to generate previews for that.
We cache preview pretty agressively and I feel this is a better
tradeoff.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Just some house keeping. IUserTools with used in even older days for
easier creation of Access instances…
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Fixes#12131
If we hit an expired token there is no need to continue checking. Since
we know it is a token.
We also should not register this with the bruteforce throttler as it is
actually a valid token. Just expired. Instead the authentication should
fail. And buisness continues as usual.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Hiding the download does not depend on other settings and it does not
affect other settings either (for example, it would be possible to hide
the downloads yet make the share editable), so a simple checkbox was
added to the menu. However, note that this option is only available for
files, but not for folders.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When the "hide download" property of a share is set the public share
page will not show the download button nor the menu with the download,
direct link and "Add to your Nextcloud" actions; the "downloadURL"
hidden field will not be included either in the generated HTML.
Despite that, note that the "downloadURL" parameter is still set and
passed to the template, as this could be needed anyway to generate
previews (for example, of audio files).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
… when an unmapped user logs in for the first time when background job
mode is ajax and no memcache was configured.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
When using atoken obtained via OAuth the token expires. Resulting in
brute force attempts hitting the requesting IP.
This resets the brute force attempts for that UID on a valid refresh of
the token.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
If doing achunked upload the mimetype of the folder would otherwise be
guessed from the path. Which always returned application/octet-stream.
If an access control rule to block that is in place this means that all
chunked uploads fail hard in directories as the isCreatable on the
directory always fails.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
The PHP built-in server can crash when certain actions are performed in
Nextcloud (but although the crash is triggered by Nextcloud it does not
seem to be a Nextcloud bug), which can lead to failures in the
acceptance tests that would have otherwise passed.
A crash of the PHP built-in server during an acceptance test can be
identified by the message "sh: 1: kill: No such process" in the
acceptance tests output; as the PHP built-in server crashed its process
does no longer exist when it is tried to be killed when the scenario
ends.
Although the crash has been observed in other tests too it is more
prevalent in the tests for tags and the theming app. In order to
reduce the false positives those tests are now run on Apache instead of
on the PHP built-in sever. However, the rest of tests are still run on
the PHP built-in server due to its lower resource consumption.
In order to run a feature or just a scenario using Apache it has to be
tagged with "@apache"; features or scenarios without that tag (the
default) will run on the PHP built-in server instead.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
In order to run the acceptance tests in Apache "/var/www/html" has to be
linked to the root directory of the Nextcloud server. Before this was
automatically done when launching the acceptance tests through
"./run.sh", but an explicit command was needed when run in Drone. Now
the linking was moved from "run.sh" to "run-local.sh", so it is
automatically done when run through "./run.sh" and in Drone, including
when running the tests for an app instead of for the server.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Each time a new actor appears in a scenario the browser window of the
new actor is put in front of the browser windows of the previous actors.
Before, when acting again as a previous actor his browser window stayed
in the background; in most cases everything worked fine even if the
window was in the background, but due to a bug in the Firefox driver of
Selenium and/or maybe in Firefox itself when the window was in the
background it was not possible to set the value of an input field that
had a range selected.
Now, when acting again as a previous actor his browser window is brought
to the foreground. This prevents the bug from manifesting, but also
reflects better how a user would interact with the browser in real life.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This will make it possible to act propely on moves of future files if we
need to know the size (like for max size virus scanning).
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
As discussed in https://github.com/nextcloud/server/issues/11594 when discovering if
x-forwarded-for is working properly its not possible to use getRemoteAddr because
the "client ip" is returned. For this check the ip of the last hop would be required.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
A revert triggers a move in the DAV client, and the DAV client expects a
DAV error message to be provided by the server in case of failure; if
no error message is given the client ends trying to get an attribute
from an undefined object and "crashes".
Besides that, if the revert fails the "done" callback of the promise
(the first parameter of "then") is never called, so a "fail" callback
should be used instead.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
In Jasmine 2.5 the "it" function takes an optional parameter that should
be called when the async work is completed (returning a promise was
introduced in Jasmine 2.7, so it is not supported yet in the tests). If
the parameter is not declared then the next test is executed without
waiting for the asynchronous work in the previous one to finish, which
could cause that asynchronous work to finish while a different test is
being run.
Note that if that happens the test could still work as expected if it
relied only in local variables. However, in the case of the successful
revert tests, the stubs being checked are not the ones created when that
test was initialized, but the ones created when the next test, the
failed revert test, was initialized and the previous variables were
replaced (although the model itself calls the proper stubs, as they are
set through parameters in function calls).
Besides all that, the checks in the failed revert test were never
executed due to a different problem which will be fixed in the next
commit.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
humanFileSize: add test with locale
humanFileSize: use canonical locale
humanFileSize: skip test w/o toLocaleString support
humanFileSize: stub getCanonicalLocale
OC.getCanonicalLocale: cover undefined case
humanFileSize: fix getCanonicalLocale stub
Signed-off-by: Claas Augner <git@caugner.de>
Before it quit right after finding the theme version of the l10n file which results in a not translated part of the UI.
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
The custom handler for "URL changed" events were added to reload the
file list whenever the sections for favorites and shares were opened;
this was used to fix the problem of not reloading the file lists when
opening them for a second time. However, besides that the handlers were
not really necessary, and as the root of the bug was fixed in the
previous commit those handlers are now removed.
The file list for tags uses the handler for a different purpose, though,
so that one was kept.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When a section is open in the Files app a "show" event is triggered.
File list objects handle that event by reloading themselves, but only
if the file list was shown at least once. However, the file list objects
of plugins are created when the "show" event is triggered for the first
time for their section; as the file list objects register their handler
for the "show" event when they are created they never handle the first
triggered "show" event, as the handler is set while that event is being
already handled. Therefore, from the point of view of the handler, the
second time that a "show" event was triggered it was seen as if the file
list was shown for the first time, and thus it was not reloaded. Now the
"shown" property is explicitly set for those file lists that are created
while handling a "show" event, which causes them to be reloaded as
expected when opening their section again.
Note that it is not possible to just reload the file list whenever it is
shown; the file list is reloaded also when the directory changes, and
this can happen when the web page is initially loaded and the URL is
parsed. In that case, if file lists were reloaded when shown for the
first time then it could be reloaded twice, one with the default
parameters due to the "show" event and another one with the proper
parameters once the URL was parsed, and the files that appeard in the
list would depend on which response from the server was received the
last.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This fixes errors from LGTM like the following one:
Variable i is used like a local variable,
but is missing a declaration.
Signed-off-by: Stefan Weil <sw@weilnetz.de>
The old code would emit the hooks twice. Thus having the version written
twice. Which is not very performant as it is first read twice as well.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
This fixes some recommendations from LGTM:
Avoid automated semicolon insertion (90% of all statements
in the enclosing function have an explicit semicolon).
Signed-off-by: Stefan Weil <sw@weilnetz.de>
since the target user is known at the time of creating the trashitem
the original location can already be adjusted on a per user level
Signed-off-by: Robin Appelman <robin@icewind.nl>
fix select statement
Make trashbin api modules
Apps can register trashbin backends for specific storages,
allowing them to modify trashbin behavior for storages
The old trashbin implementation has been wrapped in a "legacy" backend,
for future work this can be replaced with a new backend that better handles
shares while still keeping the legacy backend around to keep existing trash
from being accessible
Signed-off-by: Robin Appelman <robin@icewind.nl>
When obtaining the SourceRootInfo we can call init. If this fails the
cache is set to a failed cache and the storage to a failed storage.
However we did not check for this. Which means that if the storage was
invalid it would fail later on.
Now we will properly error out.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Some related tests had to be changed because they relied on internals, see also from the PHPUnit documentation:
"Exercise caution when using [the at] matcher as it can lead to brittle tests which are too closely tied to specific implementation details."
Signed-off-by: Zulan <git@zulan.net>
No more weird eval to construct a plural function.
We just use the plural function from symfony.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
This was the error message that we have seen:
```
Argument 1 passed to OC\\Share20\\Share::setSendPasswordByTalk() must be of the type boolean, null given, called in apps/sharebymail/lib/ShareByMailProvider.php on line 981
```
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Fixes#11637
If we do not normalize the unjailed path we might end up with a path
like files/user/folder/. which can break on objectstores
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
When "session_lifetime" can not be converted to a number the interval
becomes a NaN due to dividing it by 2. This NaN was "dragged" over all
the other mathematical operations and caused the csrftoken to be got
again and again due to an infinite loop with no pauses in "setInterval".
Now, the interval is set to the default value instead if the
"session_lifetime" can not be converted to a number.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The check is based on the HTTP status returned by the URL, and different
URLs may return different status (for example, DAV returns 207, while
a service like WebFinger would return 200), so the expected status needs
to be set depending on the URL.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This is IMO a bit more readable and it seems to make the code faster.
Tested it on the company instance where there are over 3k calls to this
function. It shaves off around 10ms.
The advantage here is that the pattern gets optimized by php itsel and
cached.
Also looking for all patterns at the same time and especially no longer
looping for /./ patterns should save time.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
fixes#11617
The OCS routes are only absolute for now as they are often exposed to
the outside anyway and are on a different endpoint than index.php in
anyway.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
This adds abstract classes to base background jobs on.
Right now almost all uses of this use the private namespace.
For most usages it will be enough to just extend the the abstract
classes QueuedJob or TimedJob.
It should be a straight forward drop in replacement.
The private jobs can then be killed off after a few releases. So we have
a nice public API.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
To allow us to create previews of files stored in appdata we need to
construct the view differently.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
In general the style of the tabs container should not change depending
on which tab is the currently selected one. However, this could be
needed in some very specific cases, so now the tab views can specify the
extra CSS classes to be used in their container when they are selected.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Fixes#10852
A quick hack. Still ensures some type safety however now also accepts
null. Else we'd need to add a whole new layer of middlewares.
This can only happen when a guest user wants to access a controller that
requries the user_id.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Show icon if no provider is available
* Reduce shown text if no provider available
* Fix login button icons
* Make backup codes button primary if the only options to log in
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
Now that we allow enforcing 2 factor auth it make sense if we also allow
and endpoint where the clients can in the background fetch an
apppassword if they were configured before the login flow was present.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#11097
If your password hash changed (becuse your are on 7.2 and we moved to
ARGON2). Then we shold not 'set a new password' but just update the
hash. As else we invoke the password policy again which might lock out
users.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Now that we can enforce 2FA we also should notify users that have
enabled 2FA but do not yet have backup codes generated.
This adds a repair step that inserts a background job to do this.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* On weblogin check if we have invalid public key tokens
* If so update them all with the new token
This ensures that your marked as invalid tokens work again if you once
login on the web.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
The file logger currently resets the mode of the logfile to 0640.
When the webserver is running as a different user than the cron job
(but both are in the same group) the files mode has to be 0660. The
current implementation breaks logging for the user that is not the
owner of the logfile.
This patch introduces a new config option 'logfilemode' that expects
an octal value (defaults to 0640). Unless the value is lower or equal
than 0 the logfiles mode will be resetted to this value.
Signed-off-by: Roland Tapken <roland@bitarbeiter.net>
OC.generateUrl(OC.linkTo('contacts', 'js/')) will append index.php, we
should not have that!
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
This allows elegant upserts where the entity ID is provided (e.g. by an
external system) and when that data is fed into our database multiple
times.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
Generate a notification to generate backup codes if you enable an other
2FA provider but backup codes are not yet generated.
* Add event listner
* Insert background job
* Background job tests and emits notification every 2 weeks
* If the backup codes are generated the next run will remove the job
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
For now it is small and there is no real standard yet. But it is better
to start with something.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
This protects our cookies a bit more. It makes sure that when a 3rdparty
websites embededs a public alendar for example. That all the users see
this in anonymous mode there.
It adds a small helper function.
In the future we can think about protecting other cookies like this as
well. But for now this is sufficient to not have the user logged in at
all when doing 3rdparty requests.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
The check is run only if its last parameter is true; data() tries to
convert the HTML attribute string to an actual JavaScript value, so
"true" is returned as an actual boolean instead of an string; as a
strict comparison against "true" was used the result was false and thus
the checks were not run.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Since there is no calendar release for 15 yet we should use an app that
we can quickly release for 15 as well.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
for instance if a user of an external user backend is not available
currently, the whole Files UI would be frozen.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
The default implementation of initialize in AbstractDatabase writes
database information to config.php. The method is overwritten in
Sqlite but parent is never called. Database-Name and Database-Table-Prefix
are never written to config.php. But from this point setup use values
from config.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
Before each scenario of the acceptance tests is run the Nextcloud server
is reset to a default state. To do this the full directory of the
Nextcloud server is commited to a local Git repository and then reset to
that commit when needed.
Unfortunately, Git does not support including empty directories in a
commit. Due to this, when the default state was restored, it could
happen that the file cache listed an empty directory that did not exist
because it was not properly restored (for example,
"data/appdata_*/css/icons"), and that in turn could lead to an error
when the directory was used.
Currently the only way to force Git to include an empty directory is to
add a dummy file to the directory (so it will no longer be empty,
but that should not be a problem in the affected directories, even if
the dummy file is not included in the file cache); although Git FAQ
suggests using a ".gitignore" file a ".keep" file was used instead, as
it conveys better its purpose.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
For some reason the docker image does not setup the permissions correctly,
by using a different name the nextcloud installer will create the database instead
with the correct permissions
Signed-off-by: Robin Appelman <robin@icewind.nl>
There are no default CSS rules for the contacts menu, as its position
depends on the element on which it is shown. Note, however, that if no
explicit rules are provided the contacts menu on mentions is affected by
the rules for the contacts menu on shares from the sharing tab.
The contacts menu is now positioned to show the tip of the arrow
horizontally aligned with the center of the avatar, and with the top of
the menu slightly below the bottom border of the mention.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The contacts menu was triggered only when the avatar or the name of the
user were clicked. Due to this, clicking on certain (small) areas of a
mention (like the right end, or the space between the avatar and the
name) did not show the contacts menu. Now the contacts menu is shown
when any area of the mention is clicked.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This is needed for the Global Scale setup to allow the master
node to perform different operations during login, depending
on the user management. Because in case of SAML, the authentication
at the idp happens at the master node.
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
Large files are not uploaded in a single operation, but uploaded in
several chunks; once all the chunks are uploaded then the server needs
to assemble them to get the final file.
Before, once the chunks were uploaded the progress bar was hidden.
However, this was confusing for the users, as the file could still need
some time to appear in the file list due to the assembling. Now once all
the chunks are uploaded the text in the progress bar changes to inform
the user that there are still some pending operations, and only when the
file is finally assembled the progress bar is hidden.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The php documentation states that an empty string should be used for a cookie when it has no real value.
null leads to the following error: expects parameter 2 to be string, null given
Signed-off-by: Martin Böh <mart.b@outlook.de>
The submit button is placed in the text area using absolute positioning,
so it is not taken into account when calculating the text layout. Due to
this it is necessary to add an explicit padding to the right of the text
area to prevent the text from overlapping the submit button.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Now that we actually check thepermissions properly we have to update the
tests.
* We checked an invalid path
* We checked from wrong permissions (files never have CREATE permissions
for example)
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
isCreatable only works on folders
isUpdatable if the file is not there but it is a part file also has to
be checked on the folder
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#10584
We deleted the main token when using the login flow else mutliple tokens
would show up for a single user.
However in the case of OAuth this is perfectly fine as the
authentication happens really in your browser:
1. You are already logged in, no need to log you out
2. You are not logged in yet, but since you log in into the exact same
browser the expected behavior is to stay logged in.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Otherwise a line break could be added between the avatar and the user
name when the wrapper is close to the right border of the message.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Most of the properties of the rule are not needed for mentions, so the
rule is no longer applied to them; the only needed property was moved to
the main rule for mentions.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When the cursor is on an avatar wrapper the cursor is shown as a pointer
to inform the user that it can be clicked (which will either show the
contacts menu or insert a mention, depending on the case); the cursor
must be explicitly defined for the "img" element that shows the avatar
too, or otherwise the default cursor would be shown.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Like done in Talk, mentions to the current user are now shown with the
primary colors to make them more prominent.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Different browsers use different font weights for strong elements
(Chromium uses "bold", but Firefox uses "bolder", which is relative to
the font weight of the parent), so now the user name in mentions is
explicitly shown with a bold weight.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The avatar should be shown immediately after the avatar to be able to
accurately define the space between them using only CSS rules.
Note that in the case of the "atwho" menu it is not really needed, as a
whitespace removal seems to be done automatically by the plugin, but it
was modified for its displayed elements too for consistency.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Visually it makes no difference, but as the ".avatar" element is inside
a "span" element it can not be a block element to be compliant with the
HTML specification.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Some popover menus, like the contacts menu, still show their icon using
an img element. The main CSS rules assume that a "content-box" sizing is
being used, and thus set the size and padding of the image to add up to
the line height.
However, ".app-*" descendants use a "border-box" sizing, so when a menu
with an image was shown in an app the icon was not properly shown. Now
both the width and height of the image is set to the item height in
those cases, which causes the visible size of the icon to be the item
height minus the padding (the same as when "content-box" sizing is
used).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This makes sure that for example app for the context is always set.
We can in the future extend this to include more info.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
Fixes#11035
Since the child-src directive is deprecated (we should kill it at some
point) we need to have the proper worker-src available
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* this fixes a download error and an exception if the data content
for encryption is empty
* #3958: for recovering encrypted files with a damaged signature
this is necessary in addition to turning the signature check off
Signed-off-by: Stefan Weiberg <sweiberg@suse.com>
When two or more user share the same email address its not possible to
reset password by email. Even when only one account is active.
This pr reduce list of users returned by getByEmail by disabled users.
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
2018-08-19 16:32:46 +02:00
2458 changed files with 76624 additions and 70691 deletions
Thanks for your first pull request and welcome to the community!
Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
Most developers hang out on IRC. So join \#nextcloud-dev on Freenode for a chat!
*:file_folder:**Access your Data** You can store your files, contacts, calendars and more on a server of your choosing.
*:package:**Sync your Data** You keep your files, contacts, calendars and more synchronized amongst your devices.
*:arrows_counterclockwise:**Share your Data** …by giving others access to the stuff you want them to see or to collaborate with.
*:rocket:**Expandable with dozens of Apps** ...like [Calendar](https://github.com/nextcloud/calendar), [Contacts](https://github.com/nextcloud/contacts), [Mail](https://github.com/nextcloud/mail) and all those you can discover in our [App Store](https://apps.nextcloud.com)
*:lock:**Security** with our encryption mechanisms, [HackerOne bounty program](https://hackerone.com/nextcloud) and two-factor authentication.
*📁**Access your Data** You can store your files, contacts, calendars and more on a server of your choosing.
*🔄**Sync your Data** You keep your files, contacts, calendars and more synchronized amongst your devices.
*🙌**Share your Data** …by giving others access to the stuff you want them to see or to collaborate with.
*🚀**Expandable with dozens of Apps** ...like [Calendar](https://github.com/nextcloud/calendar), [Contacts](https://github.com/nextcloud/contacts), [Mail](https://github.com/nextcloud/mail) and all those you can discover in our [App Store](https://apps.nextcloud.com)
*🔒**Security** with our encryption mechanisms, [HackerOne bounty program](https://hackerone.com/nextcloud) and two-factor authentication.
*You want to learn more about how you can use Nextcloud to access, share and protect your files, calendars, contacts, communication & more at home and at your Enterprise?* [**Learn about all our Features**](https://nextcloud.com/features).
You want to learn more about how you can use Nextcloud to access, share and protect your files, calendars, contacts, communication & more at home and at your Enterprise? [**Learn about all our Features**](https://nextcloud.com/features).
## Get your Nextcloud
## Get your Nextcloud 🚚
- [**Install** a server by yourself on your own hardware or by using one of our ready to use **Appliances**](https://nextcloud.com/install/#instructions-server)
-[Buy one of the awesome **devices** coming with a preinstalled Nextcloud](https://nextcloud.com/devices/)
-[Find a service**provider** who is hosting Nextcloud for you or your company](https://nextcloud.com/providers/)
- ☑️ [**Simply sign up**](https://nextcloud.com/signup/) either through our website or through the apps directly.
-🖥 [**Install** a server by yourself](https://nextcloud.com/install/#instructions-server) on your own hardware or by using one of our ready to use **appliances**
-📦 Buy one of the [awesome **devices** coming with a preinstalled Nextcloud](https://nextcloud.com/devices/)
- 🏢 Find a [service **provider**](https://nextcloud.com/providers/) who hosts Nextcloud for you or your company
*Enterprise? Public Sector or Education user? You may want to have a look into the [**Enterprise Support Subscription**](https://nextcloud.com/enterprise/) provided by the Nextcloud GmbH*
Enterprise? Public Sector or Education user? You may want to have a look into the [**Enterprise Support Subscription**](https://nextcloud.com/enterprise/) provided by the Nextcloud GmbH.
[…learn more about how to get support for Nextcloud here!](https://nextcloud.com/support)
You can also [get support for Nextcloud](https://nextcloud.com/support)!
## Join the team :family:
### How to contribute
## Join the team 👪
1. [Set up your local development environment](https://docs.nextcloud.com/server/14/developer_manual/general/devenv.html) :rocket:
2. [Pick a good first issue](https://github.com/nextcloud/server/labels/good%20first%20issue) :notebook:
3. Create a branch, a [Pull Request](https://opensource.guide/how-to-contribute/#opening-a-pull-request) and `@mention` the people from the issue :computer:
4. Wait for it to get merged and :tada:
There are many ways to contribute, of which development is only one! Find out [how to get involved](https://nextcloud.com/contribute/), including as translator, designer, tester, helping others and much more! 😍
### Contribution Guidelines
### Development setup 👩💻
1. 🚀 [Set up your local development environment](https://docs.nextcloud.com/server/14/developer_manual/general/devenv.html)
2. 🐛 [Pick a good first issue](https://github.com/nextcloud/server/labels/good%20first%20issue)
3. 👩🔧 Create a branch and make your changes. Remember to sign off your commits using `git commit -sm "Your commit message"`
4. ⬆ Create a [pull request](https://opensource.guide/how-to-contribute/#opening-a-pull-request) and `@mention` the people from the issue to review
5. 👍 Fix things that come up during review
6. 🎉 Wait for it to get merged!
Third-party components are handled as git submodules which have to be initialized first. So aside from the regular git checkout invoking `git submodule update --init` or a similar command is needed, for details see Git documentation.
Several apps that are included by default in regular releases such as [First run wizard](https://github.com/nextcloud/firstrunwizard) or [Activity](https://github.com/nextcloud/activity) are missing in `master` and have to be installed manually by cloning them into the `apps` subfolder.
Otherwise, git checkouts can be handled the same as release archives, by using the `stable*` branches. Note they should never be used on production systems.
### Building front-end code 🏗
We move more and more towards using Vue.js in the frontend, starting with Settings. For building the code on changes, use these terminal commands in the `settings` subfolder:
``` bash
# install dependencies
make dev-setup
# build for development
make build-js
# build for development and watch edits
make watch-js
# build for production with minification
make build-js-production
# clean output files
make clean
```
**When making changes, also commit the compiled files!**
We still use Handlebars templates some places in Files and Settings. We will replace these step-by-step with Vue.js, but in the meantime you need to compile them separately.
If you don’t have Handlebars installed yet, you can do it with this terminal command:
```
sudo npm install -g handlebars
```
Then inside the root folder of your local Nextcloud development installation, run this command in the terminal every time you changed a `.handlebars` file to compile it:
```
./build/compile-handlebars-templates.sh
```
### Tools we use 🛠
- [👀 BrowserStack](https://browserstack.com) for cross-browser testing
- [🌊 WAVE](https://wave.webaim.org/extension/) for accessibility testing
- [🚨 Lighthouse](https://developers.google.com/web/tools/lighthouse/) for testing of performance, accessibility and more
## Contribution guidelines 📜
All contributions to this repository from June, 16 2016 on are considered to be
licensed under the AGPLv3 or any later version.
@@ -61,20 +118,6 @@ changed it substantially:
Please read the [Code of Conduct](https://nextcloud.com/community/code-of-conduct/). This document offers some guidance to ensure Nextcloud participants can cooperate effectively in a positive and inspiring atmosphere, and to explain how together we can strengthen and support each other.
Please review the [guidelines for contributing](https://github.com/nextcloud/server/blob/master/CONTRIBUTING.md) to this repository.
Please review the [guidelines for contributing](.github/CONTRIBUTING.md) to this repository.
More information how to contribute: [https://nextcloud.com/contribute/](https://nextcloud.com/contribute/)
### Running master checkouts
Third-party components are handled as git submodules which have to be initialized first. So aside from the regular git checkout invoking `git submodule update --init` or a similar command is needed, for details see Git documentation.
Several apps that are included by default in regular releases such as [firstrunwizard](https://github.com/nextcloud/firstrunwizard) or [gallery](https://github.com/nextcloud/gallery) are missing in `master` and have to be installed manually.
That aside Git checkouts can be handled the same as release archives.
Note they should never be used on production systems.
"%1$s commented on %2$s":"%1$s كتب تعليق على %2$s",
"{author} commented on {file}":"{author} علّق على {file}",
@@ -21,7 +20,6 @@ OC.L10N.register(
"Allowed characters {count} of {max}":"عدد الأحرف المسموح بها {count} من {max}",
"Error occurred while updating comment with id {id}":"حصل خطأ أثناء تعديل التعليق رقم {id}",
"Error occurred while posting comment":"حصل خطأ أثناء إرسال التعليق",
"_%n unread comment_::_%n unread comments_":["%n تعليق غير مقروء","%n تعليق غير مقروء","تعليقان غير مقروءة","%n تعليقات غير مقروء","%n تعليق غير مقروء","%n تعليق غير مقروء"],
"%1$s commented on %2$s":"%1$s كتب تعليق على %2$s",
"{author} commented on {file}":"{author} علّق على {file}",
@@ -19,7 +18,6 @@
"Allowed characters {count} of {max}":"عدد الأحرف المسموح بها {count} من {max}",
"Error occurred while updating comment with id {id}":"حصل خطأ أثناء تعديل التعليق رقم {id}",
"Error occurred while posting comment":"حصل خطأ أثناء إرسال التعليق",
"_%n unread comment_::_%n unread comments_":["%n تعليق غير مقروء","%n تعليق غير مقروء","تعليقان غير مقروءة","%n تعليقات غير مقروء","%n تعليق غير مقروء","%n تعليق غير مقروء"],
"Error occurred while updating comment with id {id}":"Hi ha hagut un error en actualitzar el comentari amb id {id}",
"Error occurred while posting comment":"Hi ha hagut un error en publicar el comentari",
"_%n unread comment_::_%n unread comments_":["%n comentari no llegit","%n comentaris no llegits"],
"_1 new comment_::_{unread} new comments_":["1 comentari nou","{unread} comentaris nous"],
"Comment":"Comentari",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Hau estat esmentats a \"%s\" en un comentari d'un usuari que ja no existeix",
"%1$s mentioned you in a comment on “%2$s”":"%1$s us ha esmentat en un comentari a “%2$s”"
"Error occurred while updating comment with id {id}":"Hi ha hagut un error en actualitzar el comentari amb id {id}",
"Error occurred while posting comment":"Hi ha hagut un error en publicar el comentari",
"_%n unread comment_::_%n unread comments_":["%n comentari no llegit","%n comentaris no llegits"],
"_1 new comment_::_{unread} new comments_":["1 comentari nou","{unread} comentaris nous"],
"Comment":"Comentari",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Hau estat esmentats a \"%s\" en un comentari d'un usuari que ja no existeix",
"%1$s mentioned you in a comment on “%2$s”":"%1$s us ha esmentat en un comentari a “%2$s”"
"_1 new comment_::_{unread} new comments_":["1 ny kommentar","{unread} nye kommentarer"],
"Comment":"Kommentér",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Du blev nævnt i \"%s”, I en kommentar af en bruger der er blevet slettet efterfølgende",
"%1$s mentioned you in a comment on “%2$s”":"%1$s nævnte dig i en kommentarer på “%2$s”"
"_1 new comment_::_{unread} new comments_":["1 ny kommentar","{unread} nye kommentarer"],
"Comment":"Kommentér",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Du blev nævnt i \"%s”, I en kommentar af en bruger der er blevet slettet efterfølgende",
"%1$s mentioned you in a comment on “%2$s”":"%1$s nævnte dig i en kommentarer på “%2$s”"
"<strong>Comments</strong> for files":"<strong>Σχόλια</strong> για αρχεία",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"Το όνομά σας αναφέρθηκε στο “{file}”, σε σχόλιο ενός χρήστη ο οποίος έχει πλέον διαγραφεί",
"{user} mentioned you in a comment on “{file}”":"Ο {user} σας ανέφερε σε σχόλιο στο “{file}”",
"Files app plugin to add comments to files":"Επέκταση της εφαρμογής αρχείων που επιτρέπει την προσθήκη σχολίων σε αρχεία",
"Files app plugin to add comments to files":"Επέκταση της εφαρμογής αρχείων που επιτρέπει την προσθήκη σχολίων σε αρχεία.",
"Edit comment":"Επεξεργασία σχολίου",
"Delete comment":"Διαγραφή σχολίου",
"New comment …":"Νέο σχόλιο …",
"New comment …":"Νέο σχόλιο ...",
"Post":"Δημοσίευση",
"Cancel":"Ακύρωση",
"[Deleted user]":"[Διαγραμμένος χρήστης]",
"No comments yet, start the conversation!":"Δεν υπάρχουν σχόλια, ξεκινήστε την συζήτηση!",
"More comments …":"Περισσότερα σχόλια …",
"More comments …":"Περισσότερα σχόλια ...",
"Save":"Αποθήκευση",
"Allowed characters {count} of {max}":"Επιτρεπόμενοι χαρακτήρες {count} από {max}",
"Error occurred while retrieving comment with ID {id}":"Παρουσιάστηκε σφάλμα κατά την ανάκτηση σχολίου με ID {id}",
"Error occurred while updating comment with id {id}":"Ένα σφάλμα προέκυψε κατά την ενημέρωση του σχολίου με το id {id}",
"Error occurred while updating comment with id {id}":"Ένα σφάλμα προέκυψε κατά την ενημέρωση του σχολίου με το αναγνωριστικό {id}",
"Error occurred while posting comment":"Ένα σφάλμα προέκυψε κατά την δημοσίευση σχολίου",
"_1 new comment_::_{unread} new comments_":["1 νέο σχόλιο","{unread} νέα σχόλια"],
"Comment":"Σχόλιο",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Το όνομά σας αναφέρθηκε στο \"%s\", σε σχόλιο ενός χρήστη ο οποίος έχει πλέον διαγραφεί",
"%1$s mentioned you in a comment on “%2$s”":"%1$s σας ανέφερε σε σχόλιο στο “%2$s”"
"<strong>Comments</strong> for files":"<strong>Σχόλια</strong> για αρχεία",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"Το όνομά σας αναφέρθηκε στο “{file}”, σε σχόλιο ενός χρήστη ο οποίος έχει πλέον διαγραφεί",
"{user} mentioned you in a comment on “{file}”":"Ο {user} σας ανέφερε σε σχόλιο στο “{file}”",
"Files app plugin to add comments to files":"Επέκταση της εφαρμογής αρχείων που επιτρέπει την προσθήκη σχολίων σε αρχεία",
"Files app plugin to add comments to files":"Επέκταση της εφαρμογής αρχείων που επιτρέπει την προσθήκη σχολίων σε αρχεία.",
"Edit comment":"Επεξεργασία σχολίου",
"Delete comment":"Διαγραφή σχολίου",
"New comment …":"Νέο σχόλιο …",
"New comment …":"Νέο σχόλιο ...",
"Post":"Δημοσίευση",
"Cancel":"Ακύρωση",
"[Deleted user]":"[Διαγραμμένος χρήστης]",
"No comments yet, start the conversation!":"Δεν υπάρχουν σχόλια, ξεκινήστε την συζήτηση!",
"More comments …":"Περισσότερα σχόλια …",
"More comments …":"Περισσότερα σχόλια ...",
"Save":"Αποθήκευση",
"Allowed characters {count} of {max}":"Επιτρεπόμενοι χαρακτήρες {count} από {max}",
"Error occurred while retrieving comment with ID {id}":"Παρουσιάστηκε σφάλμα κατά την ανάκτηση σχολίου με ID {id}",
"Error occurred while updating comment with id {id}":"Ένα σφάλμα προέκυψε κατά την ενημέρωση του σχολίου με το id {id}",
"Error occurred while updating comment with id {id}":"Ένα σφάλμα προέκυψε κατά την ενημέρωση του σχολίου με το αναγνωριστικό {id}",
"Error occurred while posting comment":"Ένα σφάλμα προέκυψε κατά την δημοσίευση σχολίου",
"_1 new comment_::_{unread} new comments_":["1 νέο σχόλιο","{unread} νέα σχόλια"],
"Comment":"Σχόλιο",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Το όνομά σας αναφέρθηκε στο \"%s\", σε σχόλιο ενός χρήστη ο οποίος έχει πλέον διαγραφεί",
"%1$s mentioned you in a comment on “%2$s”":"%1$s σας ανέφερε σε σχόλιο στο “%2$s”"
"_1 new comment_::_{unread} new comments_":["1nova komento","{unread}novaj komentoj"],
"Comment":"Komento",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Vi estis menciita en „%s“, en komento de uzanto, kiu ekde tiam estis forigita",
"%1$s mentioned you in a comment on “%2$s”":"%1$s menciis vin en komento pri „%2$s“"
"_1 new comment_::_{unread} new comments_":["1nova komento","{unread}novaj komentoj"],
"Comment":"Komento",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Vi estis menciita en „%s“, en komento de uzanto, kiu ekde tiam estis forigita",
"%1$s mentioned you in a comment on “%2$s”":"%1$s menciis vin en komento pri „%2$s“"
"%1$s commented on %2$s":"%1$s %2$s-en iruzkin du",
"{author} commented on {file}":"{author}-(e)k {file}-en iruzkin du",
"<strong>Comments</strong> for files":"Fitxategientzako <strong>iruzkinak",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":" “{file}” fitxategian ezabatu izan den erabiltzaile batek aipatu zaitu",
"{user} mentioned you in a comment on “{file}”":"{user}-(e)k aipatu zaitu iruzkinean “{file}”",
"Files app plugin to add comments to files":"Fitxategiei iruzkinak gehitzeko fitxategien aplikazioaren plugina",
"Edit comment":"Iruzkina editatu",
"Delete comment":"Ezabatu iruzkina",
"New comment …":"Iruzkin berria...",
@@ -24,12 +22,10 @@ OC.L10N.register(
"Save":"Gorde",
"Allowed characters {count} of {max}":"Onartutako karaktereak {max}-tik {count}",
"Error occurred while retrieving comment with ID {id}":"Errorea gertatu da {id} ID-a duen iruzkina berreskuratzerakoan",
"Error occurred while updating comment with id {id}":"Errore bat gertatu da {id} id-a duen iruzkina aldatzerakoan",
"Error occurred while posting comment":"Errore bat gertatu da iruzkina bidaltzerakoan",
"Error occurred while updating comment with id {id}":"Akats bat gertatu da {id} id duen iruzkina aldatzerakoan",
"Error occurred while posting comment":"Akats bat gertatu da iruzkina bidaltzerakoan",
"_1 new comment_::_{unread} new comments_":["Iruzkin berri 1","{unread} iruzkin berri"],
"Comment":"Iruzkina",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"“%s” iruzkinean dagoeneko ezabatuta dagoen erabiltzaile batek aipatu zaitu.",
"%1$s mentioned you in a comment on “%2$s”":"%1$s-(e)k aipatu zaitu iruzkinean “%2$s”"
"%1$s commented on %2$s":"%1$s %2$s-en iruzkin du",
"{author} commented on {file}":"{author}-(e)k {file}-en iruzkin du",
"<strong>Comments</strong> for files":"Fitxategientzako <strong>iruzkinak",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":" “{file}” fitxategian ezabatu izan den erabiltzaile batek aipatu zaitu",
"{user} mentioned you in a comment on “{file}”":"{user}-(e)k aipatu zaitu iruzkinean “{file}”",
"Files app plugin to add comments to files":"Fitxategiei iruzkinak gehitzeko fitxategien aplikazioaren plugina",
"Edit comment":"Iruzkina editatu",
"Delete comment":"Ezabatu iruzkina",
"New comment …":"Iruzkin berria...",
@@ -22,12 +20,10 @@
"Save":"Gorde",
"Allowed characters {count} of {max}":"Onartutako karaktereak {max}-tik {count}",
"Error occurred while retrieving comment with ID {id}":"Errorea gertatu da {id} ID-a duen iruzkina berreskuratzerakoan",
"Error occurred while updating comment with id {id}":"Errore bat gertatu da {id} id-a duen iruzkina aldatzerakoan",
"Error occurred while posting comment":"Errore bat gertatu da iruzkina bidaltzerakoan",
"Error occurred while updating comment with id {id}":"Akats bat gertatu da {id} id duen iruzkina aldatzerakoan",
"Error occurred while posting comment":"Akats bat gertatu da iruzkina bidaltzerakoan",
"_1 new comment_::_{unread} new comments_":["Iruzkin berri 1","{unread} iruzkin berri"],
"Comment":"Iruzkina",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"“%s” iruzkinean dagoeneko ezabatuta dagoen erabiltzaile batek aipatu zaitu.",
"%1$s mentioned you in a comment on “%2$s”":"%1$s-(e)k aipatu zaitu iruzkinean “%2$s”"
"You commented on %1$s":"Vi ste komentirali %1$s",
"You commented on {file}":"Komentirali ste {file}",
"%1$s commented on %2$s":"%1$s je komentirao %2$s",
"{author} commented on {file}":"{author} je komentirao {file}",
"<strong>Comments</strong> for files":"<strong>Komentari</strong> za datoteke",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"Spomenuti ste u „{file}”, u komentaru korisnika koji je nakon toga izbrisan",
"{user} mentioned you in a comment on “{file}”":"{user} vas je spomenuo u komentaru na „{file}”",
"Files app plugin to add comments to files":"Dodatak za aplikaciju Datoteke za dodavanje komentara na datoteke",
"Edit comment":"Uredi komentar",
"Delete comment":"Izbriši komentar",
"New comment …":"Novi komentar…",
"Post":"Objavi",
"Cancel":"Odustani",
"[Deleted user]":"[Izbrisan korisnik]",
"No comments yet, start the conversation!":"Još nema komentara, započnite razgovor!",
"More comments …":"Više komentara...",
"Save":"Spremi",
"Allowed characters {count} of {max}":"Dopušteni znakovi {count} od {max}",
"Error occurred while retrieving comment with ID {id}":"Došlo je do pogreške prilikom dohvaćanja komentara s ID-om {id}",
"Error occurred while updating comment with id {id}":"Došlo je do pogreške prilikom ažuriranja komentara s ID-om {id}",
"Error occurred while posting comment":"Došlo je do pogreške prilikom objavljivanja komentara",
"_1 new comment_::_{unread} new comments_":["1 novi komentar","{unread} novih komentara","{unread} novih komentara"],
"Comment":"Komentar",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Spomenuti ste u „%s”, u komentaru korisnika koji je nakon toga izbrisan",
"%1$s mentioned you in a comment on “%2$s”":"%1$s vas je spomenuo u komentaru na „%2$s”"
"You commented on %1$s":"Vi ste komentirali %1$s",
"You commented on {file}":"Komentirali ste {file}",
"%1$s commented on %2$s":"%1$s je komentirao %2$s",
"{author} commented on {file}":"{author} je komentirao {file}",
"<strong>Comments</strong> for files":"<strong>Komentari</strong> za datoteke",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"Spomenuti ste u „{file}”, u komentaru korisnika koji je nakon toga izbrisan",
"{user} mentioned you in a comment on “{file}”":"{user} vas je spomenuo u komentaru na „{file}”",
"Files app plugin to add comments to files":"Dodatak za aplikaciju Datoteke za dodavanje komentara na datoteke",
"Edit comment":"Uredi komentar",
"Delete comment":"Izbriši komentar",
"New comment …":"Novi komentar…",
"Post":"Objavi",
"Cancel":"Odustani",
"[Deleted user]":"[Izbrisan korisnik]",
"No comments yet, start the conversation!":"Još nema komentara, započnite razgovor!",
"More comments …":"Više komentara...",
"Save":"Spremi",
"Allowed characters {count} of {max}":"Dopušteni znakovi {count} od {max}",
"Error occurred while retrieving comment with ID {id}":"Došlo je do pogreške prilikom dohvaćanja komentara s ID-om {id}",
"Error occurred while updating comment with id {id}":"Došlo je do pogreške prilikom ažuriranja komentara s ID-om {id}",
"Error occurred while posting comment":"Došlo je do pogreške prilikom objavljivanja komentara",
"_1 new comment_::_{unread} new comments_":["1 novi komentar","{unread} novih komentara","{unread} novih komentara"],
"Comment":"Komentar",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Spomenuti ste u „%s”, u komentaru korisnika koji je nakon toga izbrisan",
"%1$s mentioned you in a comment on “%2$s”":"%1$s vas je spomenuo u komentaru na „%2$s”"
"_1 new comment_::_{unread} new comments_":["1 új hozzászólás","{unread} új hozzászólás"],
"Comment":"Hozzászólás",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Megemlítették ennél: „%s”, egy már törölt felhasználó hozzászólásában",
"%1$s mentioned you in a comment on “%2$s”":"%1$s megemlítette egy hozzászólásban ennél: „%2$s”"
"_1 new comment_::_{unread} new comments_":["1 új hozzászólás","{unread} új hozzászólás"],
"Comment":"Hozzászólás",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Megemlítették ennél: „%s”, egy már törölt felhasználó hozzászólásában",
"%1$s mentioned you in a comment on “%2$s”":"%1$s megemlítette egy hozzászólásban ennél: „%2$s”"
"_1 new comment_::_{unread} new comments_":["1 ný athugasemd","{unread} nýjar athugasemdir"],
"Comment":"Athugasemd",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Minnst var á þig í “%s”, í athugasemd frá notanda sem síðan þá hefur verið eytt",
"%1$s mentioned you in a comment on “%2$s”":"%1$s minntist á þig í athugasemd við “%2$s”"
"_1 new comment_::_{unread} new comments_":["1 ný athugasemd","{unread} nýjar athugasemdir"],
"Comment":"Athugasemd",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Minnst var á þig í “%s”, í athugasemd frá notanda sem síðan þá hefur verið eytt",
"%1$s mentioned you in a comment on “%2$s”":"%1$s minntist á þig í athugasemd við “%2$s”"
"You commented on {file}":"Коментиравте на {file}",
"%1$s commented on %2$s":"%1$s коментираше на %2$s",
"{author} commented on {file}":"{author} коментираше на {file}",
"<strong>Comments</strong> for files":"<strong>Коментари</strong> за датотеки",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"Бевте спомнати на коментар на “{file}”, од корисник кој сега е избришан",
"{user} mentioned you in a comment on “{file}”":"{user} те спомна во коментар на датотеката “{file}”",
"Files app plugin to add comments to files":"Додади додаток за коментирање на датотеки",
"Edit comment":"Измени го коментарот",
"Delete comment":"Избриши коментар",
"New comment …":"Нов коментар ...",
"Post":"Испрати",
"Cancel":"Откажи",
"[Deleted user]":"[Избришан корисник]",
"No comments yet, start the conversation!":"Сеуште нема коментари, започнете разговор!",
"More comments …":"Повеќе коментари ...",
"Save":"Сними",
"Allowed characters {count} of {max}":"Дозволен број на карактери {count} од {max}",
"Error occurred while retrieving comment with ID {id}":"Настана грешка при обидот за вчитување на коментарот со број {id}",
"Error occurred while updating comment with id {id}":"Настана грешка при обидот за ажурирање на коментарот со број {id}",
"Error occurred while posting comment":"Настана грешка при обидот за испраќање на коментарот",
"You commented on {file}":"Коментиравте на {file}",
"%1$s commented on %2$s":"%1$s коментираше на %2$s",
"{author} commented on {file}":"{author} коментираше на {file}",
"<strong>Comments</strong> for files":"<strong>Коментари</strong> за датотеки",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"Бевте спомнати на коментар на “{file}”, од корисник кој сега е избришан",
"{user} mentioned you in a comment on “{file}”":"{user} те спомна во коментар на датотеката “{file}”",
"Files app plugin to add comments to files":"Додади додаток за коментирање на датотеки",
"Edit comment":"Измени го коментарот",
"Delete comment":"Избриши коментар",
"New comment …":"Нов коментар ...",
"Post":"Испрати",
"Cancel":"Откажи",
"[Deleted user]":"[Избришан корисник]",
"No comments yet, start the conversation!":"Сеуште нема коментари, започнете разговор!",
"More comments …":"Повеќе коментари ...",
"Save":"Сними",
"Allowed characters {count} of {max}":"Дозволен број на карактери {count} од {max}",
"Error occurred while retrieving comment with ID {id}":"Настана грешка при обидот за вчитување на коментарот со број {id}",
"Error occurred while updating comment with id {id}":"Настана грешка при обидот за ажурирање на коментарот со број {id}",
"Error occurred while posting comment":"Настана грешка при обидот за испраќање на коментарот",
"_1 new comment_::_{unread} new comments_":["1 новый комментарий","{unread} новых комментариев","{unread} новых комментариев","{unread} новых комментариев"],
"Comment":"Комментарий",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Вы были упомянуты в комментарии к файлу «%s» пользователем, учётная запись которого была удалена",
"%1$s mentioned you in a comment on “%2$s”":"%1$s упомянул вас в комментарии к \"%2$s\""
"_1 new comment_::_{unread} new comments_":["1 новый комментарий","{unread} новых комментариев","{unread} новых комментариев","{unread} новых комментариев"],
"Comment":"Комментарий",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Вы были упомянуты в комментарии к файлу «%s» пользователем, учётная запись которого была удалена",
"%1$s mentioned you in a comment on “%2$s”":"%1$s упомянул вас в комментарии к \"%2$s\""
"_1 new comment_::_{unread} new comments_":["1 nový komentár","{unread} nové komentáre","{unread} nových komentárov","{unread} nových komentárov"],
"Comment":"Komentár",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Boli ste spomenutý v \"%s\", v komentári používateľom ktorý bol už vymazaný",
"%1$s mentioned you in a comment on “%2$s”":"%1$s vás spomenul v komentári k \"%2$s\""
"_1 new comment_::_{unread} new comments_":["1 nový komentár","{unread} nové komentáre","{unread} nových komentárov","{unread} nových komentárov"],
"Comment":"Komentár",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"Boli ste spomenutý v \"%s\", v komentári používateľom ktorý bol už vymazaný",
"%1$s mentioned you in a comment on “%2$s”":"%1$s vás spomenul v komentári k \"%2$s\""
"{author} commented on {file}":"{author}, {file} hakkında yorum yaptı",
"<strong>Comments</strong> for files":"Dosyalar için <strong>yorumlar</strong>",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"“{file}” hakkında bir yorumda silinmiş bir kullanıcı tarafından anıldınız",
"{user} mentioned you in a comment on “{file}”":"{user}, “{file}” hakkındaki bir yorumda sizi andı",
"{user} mentioned you in a comment on “{file}”":"{user}, “{file}” hakkındaki bir yorumda sizden bahsetti",
"Files app plugin to add comments to files":"Dosyalara notlar eklenmesini sağlayan dosyalar uygulaması eki",
"Edit comment":"Yorumu düzenle",
"Delete comment":"Yorumu sil",
@@ -30,6 +30,6 @@ OC.L10N.register(
"_1 new comment_::_{unread} new comments_":["1 yeni yorum","{unread} yeni yorum"],
"Comment":"Yorum",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"\"%s\" hakkında bir yorumda silinmiş bir kullanıcı tarafından anıldınız",
"%1$s mentioned you in a comment on “%2$s”":"%1$s, “%2$s” hakkındaki bir yorumda sizi andı"
"%1$s mentioned you in a comment on “%2$s”":"%1$s, “%2$s” hakkındaki bir yorumda sizden bahsetti"
"{author} commented on {file}":"{author}, {file} hakkında yorum yaptı",
"<strong>Comments</strong> for files":"Dosyalar için <strong>yorumlar</strong>",
"You were mentioned on “{file}”, in a comment by a user that has since been deleted":"“{file}” hakkında bir yorumda silinmiş bir kullanıcı tarafından anıldınız",
"{user} mentioned you in a comment on “{file}”":"{user}, “{file}” hakkındaki bir yorumda sizi andı",
"{user} mentioned you in a comment on “{file}”":"{user}, “{file}” hakkındaki bir yorumda sizden bahsetti",
"Files app plugin to add comments to files":"Dosyalara notlar eklenmesini sağlayan dosyalar uygulaması eki",
"Edit comment":"Yorumu düzenle",
"Delete comment":"Yorumu sil",
@@ -28,6 +28,6 @@
"_1 new comment_::_{unread} new comments_":["1 yeni yorum","{unread} yeni yorum"],
"Comment":"Yorum",
"You were mentioned on “%s”, in a comment by a user that has since been deleted":"\"%s\" hakkında bir yorumda silinmiş bir kullanıcı tarafından anıldınız",
"%1$s mentioned you in a comment on “%2$s”":"%1$s, “%2$s” hakkındaki bir yorumda sizi andı"
"%1$s mentioned you in a comment on “%2$s”":"%1$s, “%2$s” hakkındaki bir yorumda sizden bahsetti"
"The meeting »%1$s« with %2$s was updated.":"La reunió »%1$s« amb %2$s ha estat actualitzada.",
"%1$s invited you to »%2$s«":"%1$s us ha convidat a »%2$s«",
"When:":"Quan:",
"Where:":"On:",
"Description:":"Descripció:",
"Link:":"Enllaç:",
"Accept":"Accepta",
"Decline":"Rebutja",
@@ -96,8 +81,6 @@ OC.L10N.register(
"Automatically generate a birthday calendar":"Genera automàticament un calendari d’aniversari",
"Birthday calendars will be generated by a background job.":"Els calendaris d'aniversari es generaran per un procés en segon pla..",
"Hence they will not be available immediately after enabling but will show up after some time.":"Per tant, no estaran disponibles immediatament després d'habilitar-los, però apareixeran d'aquí una estona.",
"Send notifications for events":"Envia notificacions per als esdeveniments",
"Notifications will be send through background jobs, so these need to happen often enough.":"Les notificacions s'enviaran a través de tasques en segon terme; per tant, cal que succeeixin prou sovint.",
"%s via %s":"%s via %s",
"The meeting »%s« with %s was canceled.":"La reunió »%s« amb %s ha estat cancel·lada.",
"The meeting »%s« with %s was updated.":"La reunió »%s« amb %s ha estat actualitzada.",
"The meeting »%1$s« with %2$s was updated.":"La reunió »%1$s« amb %2$s ha estat actualitzada.",
"%1$s invited you to »%2$s«":"%1$s us ha convidat a »%2$s«",
"When:":"Quan:",
"Where:":"On:",
"Description:":"Descripció:",
"Link:":"Enllaç:",
"Accept":"Accepta",
"Decline":"Rebutja",
@@ -94,8 +79,6 @@
"Automatically generate a birthday calendar":"Genera automàticament un calendari d’aniversari",
"Birthday calendars will be generated by a background job.":"Els calendaris d'aniversari es generaran per un procés en segon pla..",
"Hence they will not be available immediately after enabling but will show up after some time.":"Per tant, no estaran disponibles immediatament després d'habilitar-los, però apareixeran d'aquí una estona.",
"Send notifications for events":"Envia notificacions per als esdeveniments",
"Notifications will be send through background jobs, so these need to happen often enough.":"Les notificacions s'enviaran a través de tasques en segon terme; per tant, cal que succeeixin prou sovint.",
"%s via %s":"%s via %s",
"The meeting »%s« with %s was canceled.":"La reunió »%s« amb %s ha estat cancel·lada.",
"The meeting »%s« with %s was updated.":"La reunió »%s« amb %s ha estat actualitzada.",
"The meeting »%1$s« with %2$s was updated.":"Der Termin »%1$s« mit %2$s wurde aktualisiert.",
"%1$s invited you to »%2$s«":"%1$s hat Dich zu »%2$s« eingeladen",
"When:":"Wann:",
"Where:":"Wo:",
"Description:":"Beschreibung:",
"Link:":"Link:",
"Accept":"Akzeptieren",
"Decline":"Ablehnen",
@@ -96,9 +81,6 @@ OC.L10N.register(
"Automatically generate a birthday calendar":"Automatisch einen Kalender für Geburtstage erstellen",
"Birthday calendars will be generated by a background job.":"Kalender für Geburtstage werden von einem Hintergrund-Auftrag erstellt",
"Hence they will not be available immediately after enabling but will show up after some time.":"Die Einträge werden nicht sofort angezeigt. Nach der Aktivierung wird es ein wenig dauern bis zur Anzeige.",
"Send notifications for events":"Sende Benachrichtigungen für Ereignisse",
"Notifications will be send through background jobs, so these need to happen often enough.":"Benachrichtigungen werden von Hintergrundjobs erstellt, sodass diese häufig genug ausgeführt werden müssen.",
"Enable notifications for events via push":"Benachrichtigungen für Ereignisse per Push aktivieren",
"%s via %s":"%s über %s",
"The meeting »%s« with %s was canceled.":"Der Termin »%s« mit %s wurde abgesagt.",
"The meeting »%s« with %s was updated.":"Der Termin »%s« mit %s wurde aktualisiert.",
"The meeting »%1$s« with %2$s was updated.":"Der Termin »%1$s« mit %2$s wurde aktualisiert.",
"%1$s invited you to »%2$s«":"%1$s hat Dich zu »%2$s« eingeladen",
"When:":"Wann:",
"Where:":"Wo:",
"Description:":"Beschreibung:",
"Link:":"Link:",
"Accept":"Akzeptieren",
"Decline":"Ablehnen",
@@ -94,9 +79,6 @@
"Automatically generate a birthday calendar":"Automatisch einen Kalender für Geburtstage erstellen",
"Birthday calendars will be generated by a background job.":"Kalender für Geburtstage werden von einem Hintergrund-Auftrag erstellt",
"Hence they will not be available immediately after enabling but will show up after some time.":"Die Einträge werden nicht sofort angezeigt. Nach der Aktivierung wird es ein wenig dauern bis zur Anzeige.",
"Send notifications for events":"Sende Benachrichtigungen für Ereignisse",
"Notifications will be send through background jobs, so these need to happen often enough.":"Benachrichtigungen werden von Hintergrundjobs erstellt, sodass diese häufig genug ausgeführt werden müssen.",
"Enable notifications for events via push":"Benachrichtigungen für Ereignisse per Push aktivieren",
"%s via %s":"%s über %s",
"The meeting »%s« with %s was canceled.":"Der Termin »%s« mit %s wurde abgesagt.",
"The meeting »%s« with %s was updated.":"Der Termin »%s« mit %s wurde aktualisiert.",
"The meeting »%1$s« with %2$s was updated.":"Der Termin »%1$s« mit %2$s wurde aktualisiert.",
"%1$s invited you to »%2$s«":"%1$s hat Sie zu »%2$s« eingeladen",
"When:":"Wann:",
"Where:":"Wo:",
"Description:":"Beschreibung:",
"Link:":"Link:",
"Accept":"Akzeptieren",
"Decline":"Ablehnen",
@@ -96,9 +81,6 @@ OC.L10N.register(
"Automatically generate a birthday calendar":"Automatisch einen Kalender für Geburtstage erstellen",
"Birthday calendars will be generated by a background job.":"Kalender für Geburtstage werden von einem Hintergrund-Auftrag erstellt",
"Hence they will not be available immediately after enabling but will show up after some time.":"Die Einträge werden nicht sofort angezeigt. Nach der Aktivierung wird es ein wenig dauern bis zur Anzeige.",
"Send notifications for events":"Sende Benachrichtigungen für Ereignisse",
"Notifications will be send through background jobs, so these need to happen often enough.":"Benachrichtigungen werden von Hintergrundjobs erstellt, sodass diese häufig genug ausgeführt werden müssen.",
"Enable notifications for events via push":"Benachrichtigungen für Ereignisse per Push aktivieren",
"%s via %s":"%s über %s",
"The meeting »%s« with %s was canceled.":"Der Termin »%s« mit %s wurde abgesagt.",
"The meeting »%s« with %s was updated.":"Der Termin »%s« mit %s wurde aktualisiert.",
"The meeting »%1$s« with %2$s was updated.":"Der Termin »%1$s« mit %2$s wurde aktualisiert.",
"%1$s invited you to »%2$s«":"%1$s hat Sie zu »%2$s« eingeladen",
"When:":"Wann:",
"Where:":"Wo:",
"Description:":"Beschreibung:",
"Link:":"Link:",
"Accept":"Akzeptieren",
"Decline":"Ablehnen",
@@ -94,9 +79,6 @@
"Automatically generate a birthday calendar":"Automatisch einen Kalender für Geburtstage erstellen",
"Birthday calendars will be generated by a background job.":"Kalender für Geburtstage werden von einem Hintergrund-Auftrag erstellt",
"Hence they will not be available immediately after enabling but will show up after some time.":"Die Einträge werden nicht sofort angezeigt. Nach der Aktivierung wird es ein wenig dauern bis zur Anzeige.",
"Send notifications for events":"Sende Benachrichtigungen für Ereignisse",
"Notifications will be send through background jobs, so these need to happen often enough.":"Benachrichtigungen werden von Hintergrundjobs erstellt, sodass diese häufig genug ausgeführt werden müssen.",
"Enable notifications for events via push":"Benachrichtigungen für Ereignisse per Push aktivieren",
"%s via %s":"%s über %s",
"The meeting »%s« with %s was canceled.":"Der Termin »%s« mit %s wurde abgesagt.",
"The meeting »%s« with %s was updated.":"Der Termin »%s« mit %s wurde aktualisiert.",
"Please contact the organizer directly.":"Παρακαλώ επικοινωνήστε απ' ευθείας με τον διοργανωτή.",
"Are you accepting the invitation?":"Αποδέχεστε την πρόσκληση;",
"Save":"Αποθήκευση",
"Your attendance was updated successfully.":"Η παρουσία σας ενημερώθηκε με επιτυχία.",
"Send invitations to attendees":"Αποστολή προσκλήσεων στους συμμετέχοντες.",
"Automatically generate a birthday calendar":"Δημιουργία ημερολογίου γενεθλίων αυτόματα",
"Birthday calendars will be generated by a background job.":"Τα ημερολόγια γενεθλίων θα δημιουργηθούν από μία εργασία παρασκηνίου.",
"Notifications will be send through background jobs, so these need to happen often enough.":"Οι ειδοποιήσεις θα αποστέλλονται μέσω εργασιών στο παρασκήνιο, οπότε αυτές πρέπει να συμβαίνουν αρκετά συχνά.",
"%s via %s":"%s μέσω %s",
"The meeting »%s« with %s was canceled.":"Το meeting »%s« με τον/την %s ακυρώθηκε.",
"The meeting »%s« with %s was updated.":"Το meeting » %s « με τον/την %s ενημερώθηκε.",
"%s invited you to »%s«":"Ο %s σας προσκάλεσε στο »%s«",
"Please make sure to properly set up the email settings above.":"Παρακαλούμε σιγουρευθείτε οτι θα ενημερώσετε τις ρυθμίσεις email, παραπάνω."
"Please contact the organizer directly.":"Παρακαλώ επικοινωνήστε απ' ευθείας με τον διοργανωτή.",
"Are you accepting the invitation?":"Αποδέχεστε την πρόσκληση;",
"Save":"Αποθήκευση",
"Your attendance was updated successfully.":"Η παρουσία σας ενημερώθηκε με επιτυχία.",
"Send invitations to attendees":"Αποστολή προσκλήσεων στους συμμετέχοντες.",
"Automatically generate a birthday calendar":"Δημιουργία ημερολογίου γενεθλίων αυτόματα",
"Birthday calendars will be generated by a background job.":"Τα ημερολόγια γενεθλίων θα δημιουργηθούν από μία εργασία παρασκηνίου.",
"Notifications will be send through background jobs, so these need to happen often enough.":"Οι ειδοποιήσεις θα αποστέλλονται μέσω εργασιών στο παρασκήνιο, οπότε αυτές πρέπει να συμβαίνουν αρκετά συχνά.",
"%s via %s":"%s μέσω %s",
"The meeting »%s« with %s was canceled.":"Το meeting »%s« με τον/την %s ακυρώθηκε.",
"The meeting »%s« with %s was updated.":"Το meeting » %s « με τον/την %s ενημερώθηκε.",
"%s invited you to »%s«":"Ο %s σας προσκάλεσε στο »%s«",
"Please make sure to properly set up the email settings above.":"Παρακαλούμε σιγουρευθείτε οτι θα ενημερώσετε τις ρυθμίσεις email, παραπάνω."
"The meeting »%1$s« with %2$s was updated.":"La reunión »%1$s« con %2$s se ha actualizado.",
"%1$s invited you to »%2$s«":"%1$s te ha invitado a »%2$s«",
"When:":"Cuándo:",
"Where:":"Dónde:",
"Description:":"Descripción:",
"Link:":"Enlace:",
"Accept":"Aceptar",
"Decline":"Rechazar",
@@ -95,8 +81,6 @@ OC.L10N.register(
"Automatically generate a birthday calendar":"Generar automáticamente un calendario de cumpleaños",
"Birthday calendars will be generated by a background job.":"Los calendarios de cumpleaños se generarán mediante un trabajo en segundo plano.",
"Hence they will not be available immediately after enabling but will show up after some time.":"Por ello, no estarán disponibles inmediatamente tras activarlos, sino que aparecerán después de cierto tiempo.",
"Send notifications for events":"Enviar notificaciones de los eventos",
"Notifications will be send through background jobs, so these need to happen often enough.":"Las notificaciones se enviarán a través de trabajos en segundo plano, por lo que estos deben llevarse a cabo con cierta frecuencia.",
"%s via %s":"%s vía %s",
"The meeting »%s« with %s was canceled.":"La reunión »%s« con %s se ha cancelado.",
"The meeting »%s« with %s was updated.":"La reunión »%s« con %s se ha actualizado.",
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.