summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--.travis.yml2
-rw-r--r--CONTRIBUTING.md5
-rw-r--r--README.md8
-rw-r--r--issue_template.md2
-rw-r--r--js/app/Config.js2
5 files changed, 9 insertions, 10 deletions
diff --git a/.travis.yml b/.travis.yml
index 1c301870d..afbd579a3 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -54,7 +54,7 @@ script:
- make test
after_failure:
- - cat ../../data/owncloud.log
+ - cat ../../data/nextcloud.log
addons:
firefox: "latest"
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f0cd60db9..b20ba9440 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -44,12 +44,12 @@ check if:
```
* Reproduce the Problem
-* Check **data/owncloud.log**
+* Check **data/nextcloud.log**
* Check your [browser's JavaScript console for errors](http://ggnome.com/wiki/Using_The_Browser_Error_Console) if it's a client-side issue
Please provide the following details so that your problem can be fixed:
-* **data/owncloud.log** (important!)
+* **data/nextcloud.log** (important!)
* Nextcloud version
* News version
* Browser and version
@@ -127,4 +127,3 @@ We usually hang out on **irc.freenode.net** in the **#nextcloud-news** and **#ne
* Place a space before and after the parameter block for if, else, for, foreach, function
* Everything should be in pascalCase except classes which should be in CamelCase
* For linting JavaScript, a [jshint file](https://github.com/nextcloud/news/blob/master/js/.jshintrc) is used that is run before compiling the JavaScript
-
diff --git a/README.md b/README.md
index 432706aa4..7014328f6 100644
--- a/README.md
+++ b/README.md
@@ -226,7 +226,7 @@ Some hints:
* type clob is usually an Sql TEXT
* length for integer fields means bytes, so an integer with length 8 means its 64bit
-### I am getting: Exception: Some\\Class does not exist erros in my owncloud.log
+### I am getting: Exception: Some\\Class does not exist erros in my nextcloud.log
This is very often caused by missing or old files, e.g. by failing to upload all of the News app' files or errors during installation. Before you report a bug, please recheck if all files from the archive are in place and accessible.
### How do I reset the News app
@@ -241,7 +241,7 @@ DROP TABLE oc_news_folders;
### App is stuck in maintenance mode after failed update
-Check the **nextcloud/data/owncloud.log** for hints why it failed. After the issues are fixed, turn off the maintenance mode by editing your **nextcloud/config/config.php** by setting the **maintenance** key to false:
+Check the **nextcloud/data/nextcloud.log** for hints why it failed. After the issues are fixed, turn off the maintenance mode by editing your **nextcloud/config/config.php** by setting the **maintenance** key to false:
"maintenance" => false,
@@ -254,7 +254,7 @@ System Cron:
* Check if the cronjob exists with **crontab -u www-data -e** (replace www-data with your httpd user)
* Check the file permissions of the **cron.php** file and if **www-data** (or whatever your httpd user is called like) can read and execute that script
* Check if you can execute the cron with **sudo -u www-data php -f nextcloud/cron.php** (replace www-data with your httpd user)
-* Check your **data/owncloud.log** for errors
+* Check your **data/nextcloud.log** for errors
* Check if the cronjob is ever executed by placing an **error_log('updating');** in the [background job file](https://github.com/nextcloud/news/blob/master/cron/updater.php#L28). If the cronjob runs, there should be an updating log statement in your httpd log.
* If there is no **updating** statement in your logs check if your cronjob is executed by executing a different script
* If your cron works fine but Nextcloud's cronjobs are never executed, file a bug in [core](https://github.com/nextcloud/core/)
@@ -265,7 +265,7 @@ System Cron:
nextcloud_news_updater --loglevel info -c /path/to/config.ini
-* Check your **data/owncloud.log** for errors
+* Check your **data/nextcloud.log** for errors
### Adding feeds that use self-signed certificates
If you want to add a feed that uses a self-signed certificate that is not signed by a trusted CA the request will fail with "SSL certficate is invalid". A common solution is to turn off the certificate verification **which is wrong** and **makes your installation vulnerable to MITM attacks**. Therefore **turning off certificate verification is not supported**.
diff --git a/issue_template.md b/issue_template.md
index 572e506c9..039e446e8 100644
--- a/issue_template.md
+++ b/issue_template.md
@@ -22,7 +22,7 @@ Explain what you did to encounter the issue
* Browser and version:
* Distribution and version:
-## Contents of nextcloud/data/owncloud.log
+## Contents of nextcloud/data/nextcloud.log
```json
diff --git a/js/app/Config.js b/js/app/Config.js
index 4ccbf8cba..830093351 100644
--- a/js/app/Config.js
+++ b/js/app/Config.js
@@ -51,7 +51,7 @@ app.config(function ($routeProvider, $provide, $httpProvider) {
403: t('news', 'Request forbidden. Are you an admin?'),
412: t('news', 'Token expired or app not enabled! Reload the page!'),
500: t('news', 'Internal server error! Please check your ' +
- 'data/owncloud.log file for additional ' +
+ 'data/nextcloud.log file for additional ' +
'information!'),
503: t('news', 'Request failed, Nextcloud is in currently ' +
'in maintenance mode!')