Avainsanana Nextcloud

I think can produce backports too

10. tammikuuta 2019 klo 18.22
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Github, Nextcloud

@juliushaertl Is backporting for docs also done as per the manual? It seems pretty straightforward, so I think I can produce those pull requests too, if needed.

Vastaa viestiin sen kontekstissa (Github)

Fix indefinite article before Nextcloud (an->a)

10. tammikuuta 2019 klo 17.50
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: kieli, Nextcloud

Fix indefinite article before Nextcloud (an->a)

Vastaa viestiin sen kontekstissa (Github)

check_data_directory_permissions allows the admin to turn off the automatic permissions reset

10. tammikuuta 2019 klo 13.48
Sijainti: Keskustelupalstat: Nextcloud
Avainsanat: Google, Nextcloud, turvallisuus

Sorry for necromancing, but because Google seems to like this thread, I just thought I’d add a mention that a check_data_directory_permissions option for config.php has since been implemented (and backported down to NC12), and it allows the admin to turn off the automatic permissions reset (by assigning it false).

This is discouraged however, and ACLs or other means of managing access are still the better option where available.

Vastaa viestiin sen kontekstissa (Nextcloud)

Fix typo: ”parameters and are” -> ”parameters are”

1. tammikuuta 2019 klo 13.51
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Nextcloud

Fix typo: ”parameters and are” -> ”parameters are” in Using the occ command.

Vastaa viestiin sen kontekstissa (Github)

I believe those issues are already being worked on

31. joulukuuta 2018 klo 18.37
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Google, Nextcloud

@skjnldsv The points you raise are about SEO, and (from what I linked to above) I believe those issues are already being worked on. In case I was unclear, I’m not arguing for my idea to supplant the SEO work currently in progress, but to augment it.

Obviously, if #915 gets implemented as requested, my issue becomes moot, but from reading the comments there I understand it’s not so cut and dried that it will be.

Vastaa viestiin sen kontekstissa (Github)

Point ”latest version” links to specific page

31. joulukuuta 2018 klo 13.40
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Google, Nextcloud

As discussed in #915 and #517, Google seems to prefer old versions’ documentation at the expense of newer ones for some reason. The issue was partly mitigated by the fix for #958, which added prominent links to the latest version on top of old pages.

But these links currently point to the manual root. Ideally, I’d like these links to point directly to the latest version of the specific manual page I’m viewing, if available.

For instance, a search for nextcloud occ (for me at least) currently yields the manual page for version 9 as the top result. The ”latest version” link at the top then takes me to the server manual introduction. This means it’s still easier for me to navigate to the latest version of the ”Using the occ command” page by manually replacing the version number in the current URL with ’stable’ (or the latest release number) than to follow the ”latest version” link and try to find the page there.

Producing specific links is probably more laborious than the generic top-level-pointing link. For instance, there may no longer be a corresponding page in the stable version. Detecting such cases should be automatable I think, but there may be other issues that aren’t.

This will be much less of an issue once the SEO issue is resolved, but I think direct links would still remain useful, as people can still come up with search terms that search engines think correspond to old documentation better than the latest.

Vastaa viestiin sen kontekstissa (Github)

Per-user invocation example of occ versions:cleanup is missing users list

2. joulukuuta 2018 klo 11.43
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Nextcloud

”Using the occ command” documents using versions:cleanup either globally or for specific users, with example invocations for both cases. However, said examples are identical in the current revision:

This example deletes all versions for all users:

sudo -u www-data php occ versions:cleanup
Delete all versions
Delete versions for users on backend Database


You can delete versions for specific users in a space-delimited list:

sudo -u www-data php occ versions:cleanup
Delete versions of   freda
Delete versions of   molly

Unless I’m misinterpreting this, the latter example should have the space-delimited list of users following the invocation, like so:

sudo -u www-data php occ versions:cleanup freda molly


Vastaa viestiin sen kontekstissa (Github)

Process: com.nextcloud.client: java.lang.ArrayIndexOutOfBoundsException

5. lokakuuta 2018 klo 15.23
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Motorola, Nextcloud, Nexus, Samsung

All of my devices are affected by this, or something very similar. My server is running Ubuntu 16.06 with Nextcloud 14.0.1 (in a subdirectory). Here’s logs from my

I trimmed them down to (what appears to me as) the essential, filtered out some noise and replaced my username and the server hostname.

Steps to reproduce:

  1. (On desktop) Create a new subdirectory under the sync directory, add two JPEG files into it. Wait for changes to sync.
  2. (On mobile) Open Nextcloud, select the newly created directory, switch to grid view.

Vastaa viestiin sen kontekstissa (Github)

Use a2ensite instead of ln -s to enable site

2. lokakuuta 2018 klo 16.01
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Apache, Debian, Nextcloud

Replace instruction using ln -s to enable Apache site to use a2ensite instead in Debian and derivatives. Closes #884.

Vastaa viestiin sen kontekstissa (Github)

Debian derivatives installation example uses `ln -s` instead of `a2ensite`

30. syyskuuta 2018 klo 13.43
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Apache, Debian, Nextcloud, Ubuntu

Under Apache Web server configuration, there’s a prompt to create a symlink to enable the newly created site:

ln -s /etc/apache2/sites-available/nextcloud.conf /etc/apache2/sites-enabled/nextcloud.conf

As the instructions in this section are written for Debian, Ubuntu, and their derivatives, a2ensite should be used instead:

a2ensite nextcloud.conf

The commands are currently functionally equivalent (AFAIK), but should this change sometime, the latter would be more future proof, besides being much shorter and easier to type.

Additionally, immediately following the ln -s there is a section about Additional Apache configurations, which correctly instructs the use of a2enmod to create the symlinks. Replacing ln -s with a2ensitewould thus harmonize the two sections.

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »