mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-04 02:36:49 +07:00
Merge branch 'master' into alrac2
Conflicts: admin_manual/configuration/configuration_mail.rst
This commit is contained in:
@@ -423,3 +423,20 @@ using the ``telnet`` command.
|
||||
221 smtp.domain.dom closing connection
|
||||
Connection closed by foreign host.
|
||||
|
||||
=======
|
||||
Enabling Debug Mode
|
||||
-------------------
|
||||
|
||||
If you are unable to send email, it might be useful to activate further debug
|
||||
messages by enabling the mail_smtpdebug parameter:
|
||||
|
||||
.. code-block:: php
|
||||
|
||||
<?php
|
||||
|
||||
"mail_smtpdebug" => true,
|
||||
|
||||
.. note:: Immediately after pressing the **Send email** button, as described
|
||||
before, several **SMTP -> get_lines(): ...** messages appear on the screen.
|
||||
This is expected behavior and can be ignored.
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
Uploading big files > 512MB (as set by default)
|
||||
===============================================
|
||||
It's useful to know limiting factors, that make it impossible to exceed the values given by the ownCloud-system:
|
||||
It's useful to know limiting factors, that make it impossible to exceed the
|
||||
values given by the ownCloud-system:
|
||||
|
||||
Not outnumberable upload limits:
|
||||
--------------------------------
|
||||
@@ -13,53 +14,67 @@ Other recommendable preconditions:
|
||||
----------------------------------
|
||||
|
||||
* Make sure, that the latest version of PHP (at least 5.4.9) is installed
|
||||
* Disable user quota. This means: set the user quota of the account, you are currently logged in, to "unlimited".
|
||||
* Disable user quota. This means: set the user quota of the account, you are
|
||||
currently logged in, to "unlimited".
|
||||
|
||||
This is important, because you possibly could not watch otherwise, whether the desired changes take effect.
|
||||
This is important, because you possibly could not watch otherwise, whether the
|
||||
desired changes take effect.
|
||||
|
||||
Enabling uploading big files
|
||||
============================
|
||||
Note: The order of the following steps is important! If you swap steps described below, the settings may fail.
|
||||
Note: The order of the following steps is important! If you swap steps described
|
||||
below, the settings may fail.
|
||||
|
||||
**Go to the admin section in the ownCloud Web Interface and do the following:**
|
||||
|
||||
* Under "File handling" set the Maximum upload size to the desired value (e.g. 16GB)
|
||||
* Under "File handling" set the Maximum upload size to the desired value (e.g.
|
||||
16GB)
|
||||
* Click the "save"-Button
|
||||
|
||||
**Configuring your webserver**
|
||||
|
||||
ownCloud comes with a .htaccess - file which propagates all config to your webserver. To adapt those settings go to the ownCloud - Folder on your server and set the following two parameters inside the .htaccess file:
|
||||
ownCloud comes with a .htaccess - file which propagates all config to your
|
||||
webserver. To adapt those settings go to the ownCloud - Folder on your server
|
||||
and set the following two parameters inside the .htaccess file:
|
||||
|
||||
* ``upload_max_filesize = 16G`` (e.g., to stay consistent with the example value above)
|
||||
* ``post_max_size = 16G`` (e.g., to stay consistent with the example value above)
|
||||
* ``upload_max_filesize = 16G`` (e.g., to stay consistent with the example
|
||||
value above)
|
||||
* ``post_max_size = 16G`` (e.g., to stay consistent with the example value
|
||||
above)
|
||||
|
||||
If you don't want to use the shipped .htaccess - file, outcomment those options there and edit them in your global php.ini file:
|
||||
If you don't want to use the shipped .htaccess - file, outcomment those options
|
||||
there and edit them in your global php.ini file:
|
||||
|
||||
You can easily learn the loaded configuration file by saving ``<?php phpinfo(); ?>`` code piece
|
||||
into a php file and calling it with your browser. Then look for the **Loaded Configuration File** value.
|
||||
You can easily learn the loaded configuration file by saving ``<?php phpinfo();
|
||||
?>`` code piece into a php file and calling it with your browser. Then look for
|
||||
the **Loaded Configuration File** value.
|
||||
|
||||
Alternatively:
|
||||
|
||||
* Under Debian or SUSE and their derivatives this file lies at /etc/php5/apache2/php.ini
|
||||
* Under Debian or SUSE and their derivatives this file lies at
|
||||
/etc/php5/apache2/php.ini
|
||||
* On Windows, you can find this file within C:/Program Files (x86)/PHP/PHP.ini
|
||||
|
||||
Set the following two parameters inside the php.ini to the same value as chosen inside the admin-section one step before:
|
||||
Set the following two parameters inside the php.ini to the same value as chosen
|
||||
inside the admin-section one step before:
|
||||
|
||||
* ``upload_max_filesize = 16G`` (e.g., to stay consistent with the example value above)
|
||||
* ``post_max_size = 16G`` (e.g., to stay consistent with the example value above)
|
||||
* ``upload_max_filesize = 16G`` (e.g., to stay consistent with the example
|
||||
value above)
|
||||
* ``post_max_size = 16G`` (e.g., to stay consistent with the example value
|
||||
above)
|
||||
|
||||
**Output Buffering** allows you to get performance benefits in some setups. Please make sure you know what you are doing before using it in production. As previously mentioned, add this option in your .htaccess file or edit your php.ini file:
|
||||
**Output Buffering** must be turned off in ``.htaccess`` or ``php.ini``, or PHP
|
||||
will return memory-related errors.
|
||||
|
||||
* ``output_buffering = 16384`` (e.g., to stay consistent with the example value above)
|
||||
* ``output_buffering = 0``
|
||||
|
||||
As you can see, the "output_buffering" has to be given in MegaBytes but as a plain figure (without size-units as 'M' or 'G')
|
||||
|
||||
**These client configurations have been proven by testing maximum file sizes of 16 GB:**
|
||||
**These client configurations have been proven by testing maximum file sizes of
|
||||
16 GB:**
|
||||
|
||||
* Linux 32 Bit: Ubuntu, Firefox => 16GB
|
||||
* Windows 8 64 Bit: Google Chrome => 8GB
|
||||
|
||||
**Note:**
|
||||
You will need a minimum of 16GB (e.g, to stay consistent with the example value above), in your upload_tmp_dir.
|
||||
Normally this points to /tmp. If your /tmp has not enough space,
|
||||
you can change the value of upload_tmp_dir in your php.ini
|
||||
You will need a minimum of 16GB (e.g, to stay consistent with the example value
|
||||
above), in your upload_tmp_dir. Normally this points to /tmp. If your /tmp has
|
||||
not enough space, you can change the value of upload_tmp_dir in your php.ini
|
||||
@@ -3,16 +3,16 @@ Configuring Server-to-Server Sharing
|
||||
|
||||
ownCloud 7 introduces a powerful new feature, server-to-server sharing. With
|
||||
just a few clicks you can easily and securely create public shares for sharing
|
||||
files and directories with other ownCloud 7 servers. You can automatically send
|
||||
an email notification when you create the share, add password protection, allow
|
||||
users to upload files, and set an expiration date.
|
||||
files and directories with other ownCloud 7 servers. (Currently, this works only
|
||||
with OC7 and not older versions.) You can automatically send an email
|
||||
notification when you create the share, add password protection, allow users to
|
||||
upload files, and set an expiration date.
|
||||
|
||||
Follow these steps to create a new public share:
|
||||
|
||||
1. Go to ``admin > Admin`` in your ownCloud Web control panel, and scroll to
|
||||
the Remote Shares section.
|
||||
1. Go to the Admin page and scroll to the Remote Shares section.
|
||||
|
||||
.. figure:: ../images/remote_shares.png
|
||||
.. figure:: ../images/remote_shares.png
|
||||
|
||||
2. To enable server-to-server sharing, and to allow remote users to mount your
|
||||
shares in their ownCloud 7 accounts, check ``Allow other instances to mount
|
||||
@@ -27,7 +27,7 @@ this unchecked disables user-created public shares.
|
||||
you want to share to expose the administration options. Check the ``Share
|
||||
Link`` checkbox to create the share, and to expose all of your sharing options.
|
||||
|
||||
.. figure:: ../images/create_public_share.png
|
||||
.. figure:: ../images/create_public_share.png
|
||||
|
||||
Your new public share is labeled with a chain link. If you do not protect it
|
||||
with a password, it is visible to anyone who has the URL. Users on other
|
||||
|
||||
93
admin_manual/whats_new_admin.rst
Normal file
93
admin_manual/whats_new_admin.rst
Normal file
@@ -0,0 +1,93 @@
|
||||
What's New for Admins in ownCloud 7
|
||||
=================
|
||||
|
||||
New User Management
|
||||
------------------
|
||||
|
||||
Admins can now view all ownCloud users in a single scrolling window, filter user
|
||||
lists by group, and search by user display name using the new text filter. User
|
||||
attributes have also been added, included the file storage location for each
|
||||
user and the last time they logged in. New groups can be added with a click of
|
||||
a button.
|
||||
|
||||
External Storage
|
||||
---------------
|
||||
|
||||
Major improvements to the external storage app include support for FTP, Dropbox,
|
||||
Google Drive, sFTP, Swift, S3, WebDAV, SMB/CIFS and more storage locations to
|
||||
the ownCloud instance. You can control which storage types your users can set up
|
||||
in their Personal tabs. Further performance improvements have made externally
|
||||
mounted storage faster and more responsive.
|
||||
|
||||
Server to Server Sharing
|
||||
----------------------
|
||||
|
||||
ownCloud 7 servers can now connect shares with each other. With just a
|
||||
few clicks you can easily and securely create public shares that are available
|
||||
to other ownCloud 7 users on remote servers, and optionally allow your users to
|
||||
also create their own public shares.
|
||||
|
||||
|
||||
SharePoint Integration (Enterprise Edition only)
|
||||
----------------------
|
||||
|
||||
Native SharePoint support has been added to ownCloud 7 Enterprise Edition as a
|
||||
secondary storage location for SharePoint 2007, 2010 and 2013. When this is
|
||||
enabled, users can access and sync all of their SharePoint content via ownCloud,
|
||||
whether in the desktop sync, mobile or Web interfaces. Updated files are
|
||||
bi-directionally synced automatically. SharePoint shares are created by the
|
||||
ownCloud admin, and optionally by any users who have SharePoint credentials.
|
||||
ownCloud preserves SharePoint ACLs to ensure content is restricted per
|
||||
SharePoint rules.
|
||||
|
||||
Windows Network Drive Integration (Enterprise Edition only)
|
||||
--------------------------------
|
||||
|
||||
ownCloud has always supported mounting Windows network drives, and in OC7 EE it
|
||||
is easier than ever for the administrator to mount Windows Network Drives
|
||||
for a user, a group or the entire ownCloud instance, and allow each user to
|
||||
access the network drives and preserve their ACLs. The network drives appear as
|
||||
normal folders and files, and changes are bi-directionally synced between user
|
||||
devices and the Windows network drives.
|
||||
|
||||
|
||||
Sharing
|
||||
------
|
||||
|
||||
Sharing has been dramatically enhanced and streamlined, making it more flexible,
|
||||
faster and accessible. Improvements include:
|
||||
|
||||
* Force Password: Admins can now force users to set a password when they create
|
||||
shared links. This ensures that files shared outside of ownCloud via a link
|
||||
are properly secured by users.
|
||||
|
||||
* Share Link Default and Max Expiration: When sharing a file with a link,
|
||||
admins can now require users to set a password, and set a specific
|
||||
expiration duration for the link.
|
||||
|
||||
* Antivirus Action Updates: The Antivirus app has been enhanced to allow –
|
||||
with some minor customization – the use of external virus scanners (rather
|
||||
than the default ClamAV) in scanning files as they arrive on the server.
|
||||
|
||||
|
||||
SMTP Configuration Wizard
|
||||
-----------------------
|
||||
|
||||
The new graphical SMTP configuration connects to your mail server in just a few
|
||||
clicks, so that ownCloud can send automated messages to users. ownCloud
|
||||
connects via PHP, Sendmail, or standard SMTP.
|
||||
|
||||
Editable email Templates
|
||||
-------------------
|
||||
|
||||
ownCloud admins can now edit the email templates that ownCloud uses for
|
||||
automatic notifications on the Admin page.
|
||||
|
||||
|
||||
Active Directory and LDAP Enhancements
|
||||
------------------
|
||||
|
||||
Several improvements have been made to the LDAP and Active Directory plug-in
|
||||
application, improving both the performance of the application as well as the
|
||||
compatibility with OpenLDAP and Active Directory.
|
||||
|
||||
@@ -24,22 +24,67 @@ To use the commonly used layout consisting of sidebar navigation and content the
|
||||
|
||||
Navigation
|
||||
==========
|
||||
ownCloud provides a default CSS navigation layout. If list entries should have 16x16 px icons, the **with-icon** class can be added to the base **ul**:
|
||||
ownCloud provides a default CSS navigation layout. If list entries should have 16x16 px icons, the **with-icon** class can be added to the base **ul**. The maximum supported indention level is two, further indentions are not recommended.
|
||||
|
||||
.. code-block:: html
|
||||
|
||||
<div id="app-navigation">
|
||||
<ul class="with-icon">
|
||||
<li><a href="#">First level</a></li>
|
||||
<li><a href="#">First level entry</a></li>
|
||||
<li>
|
||||
<a href="#">First level container</a>
|
||||
<ul>
|
||||
<li><a href="#">Second level</a></li>
|
||||
<li><a href="#">Second level</a></li>
|
||||
<li><a href="#">Second level entry</a></li>
|
||||
<li><a href="#">Second level entry</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
Folders
|
||||
-------
|
||||
|
||||
Folders are like normal entries and are only supported for the first level. In contrast to normal entries, the links which show the title of the folder need to have the **folder-icon** css class.
|
||||
|
||||
If the folder should be collapsible, the **collapsible** class and a button with the class **collapse** are needed. After adding the collapsible class the folder's child entries can be toggled by adding the **open** class to the list element:
|
||||
|
||||
.. code-block:: html
|
||||
|
||||
<div id="app-navigation">
|
||||
<ul class="with-icon">
|
||||
<li><a href="#">First level entry</a></li>
|
||||
<li class="collapsible open">
|
||||
<button class="collapse"></button>
|
||||
<a href="#" class="folder-icon">Folder name</a>
|
||||
<ul>
|
||||
<li><a href="#">Folder contents</a></li>
|
||||
<li><a href="#">Folder contents</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
|
||||
Drag and drop
|
||||
-------------
|
||||
The class which should be applied to a first level element (**li**) that hosts or can host a second level is **drag-and-drop**. This will cause the hovered entry to slide down giving a visual hint that it can accept the dragged element. In case of jQuery UI's droppable feature, the **hoverClass** option should be set to the **drag-and-drop** class.
|
||||
|
||||
.. code-block:: html
|
||||
|
||||
<div id="app-navigation">
|
||||
<ul class="with-icon">
|
||||
<li><a href="#">First level entry</a></li>
|
||||
<li class="drag-and-drop">
|
||||
<a href="#" class="folder-icon">Folder name</a>
|
||||
<ul>
|
||||
<li><a href="#">Folder contents</a></li>
|
||||
<li><a href="#">Folder contents</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
|
||||
Settings Area
|
||||
=============
|
||||
To create a settings area create a div with the id **app-settings** inside the **app-navgiation** div:
|
||||
|
||||
@@ -7,7 +7,7 @@ ownCloud Test Pilots
|
||||
:hidden:
|
||||
|
||||
|
||||
The ownCloud Test Pilots help to test and improve different server and client setups with ownCloud.
|
||||
The ownCloud Test Pilots help to test and improve different server and client setups with ownCloud.
|
||||
|
||||
Why do you want to join
|
||||
-----------------------
|
||||
@@ -75,7 +75,7 @@ tracker. It might even be fixed, sometimes! It can also be fruitful to contact t
|
||||
`developers on irc <irc://freenode/#owncloud-dev>`_. Tell them you're testing ownCloud
|
||||
and share what problem you bumped into. Or just ask on the test-pilots mailing list.
|
||||
|
||||
Finally, if the issue you bump into is a clear bug and the developers are not aware of it, file it as a new issue. See :doc:`../bugtracker`
|
||||
Finally, if the issue you bump into is a clear bug and the developers are not aware of it, file it as a new issue. See :doc:`../bugtracker/index`
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,11 +1,64 @@
|
||||
New in ownCloud 7
|
||||
What's New for Users in ownCloud 7
|
||||
=================
|
||||
|
||||
Changes to the "Shared" folder
|
||||
No More Shared Folder
|
||||
------------------------------
|
||||
|
||||
For all existing ownCloud users: the “Shared” folder has been removed from the ownCloud server. As a result, newly shared files and folders no longer appear in a folder called “Shared”, they appear in the root user’s folder. For example, if Bob shares a folder called “sales” with Earl in ownCloud 6, Earl will see the “Shared” folder appear, and then the folder “sales” appears within “Shared”. Now, in ownCloud 7, the same sharing activity would create a folder called “sales” in Earl’s root directory. Overlay icons will show Earl that this is a shared folder, and the folder can be moved wherever he wants – including into a folder he creates and calls “Shared”. However, the “Shared” directory is no longer required, and will no longer appear by default when a file or folder is shared.
|
||||
The Shared folder has been removed from ownCloud 7. If you are upgrading
|
||||
from older ownCloud versions you will still have your old Shared folder,
|
||||
but new shares will appear in the top-level of your Files page, and the Shared
|
||||
folder is no longer required. You can now create your own folders for
|
||||
storing shared files, and organize and move them around like any other files.
|
||||
|
||||
Selective Sync
|
||||
---------
|
||||
The desktop client now makes it easier for users to configure which folders
|
||||
on their ownCloud instances should be syncing with the desktop, and can easily
|
||||
make changes for special circumstances such as travel and special projects.
|
||||
|
||||
|
||||
If users currently have an earlier version of ownCloud and have shared files and folders via the “Shared” directory, the files and folders will continue to reside in the “Shared” directory after an ownCloud 7 upgrade. However, any files or folders shared after the upgrade will appear in the user’s root directory. These files and folders can be dragged anywhere in the ownCloud file tree (except into another folder that has been shared with this user). For example, the files and folders could be dragged into a “Shared” folder, where they will continue to sync normally. Or they can be dragged into a folder called “Given to me by Bob”. In addition, to make navigating these files easier, the ownCloud 7 web interface now provides a “Shared with Me” filter that automatically shows on the left hand side of the files view in a web browser. Clicking on this filter will display only those paths where files and folders shared with this user reside. This change in behavior provides ownCloud users with far greater flexibility, enabling them to arrange and organize files and folders however they want, even if those folders or files are shared with them.
|
||||
Server to Server Sharing
|
||||
----------------------
|
||||
|
||||
ownCloud 7 servers can now connect shares directly with each other. With just a
|
||||
few clicks you can easily and securely connect to public shares on other
|
||||
ownCloud servers, and optionally create public shares for sharing your own files
|
||||
if your admin allows it.
|
||||
|
||||
File and Activity Notifications
|
||||
------------------
|
||||
|
||||
In ownCloud 7 you can set up automatic notifications of tracked
|
||||
activities such as new shares, and changed or deleted files.
|
||||
|
||||
ownCloud Documents with Word Conversion
|
||||
-------------------------------
|
||||
|
||||
You can convert Word documents on the fly: open them in ownCloud for
|
||||
editing, and live editing with other users, and when you close it reverts
|
||||
to its original Word format with all of your changes embedded.
|
||||
|
||||
|
||||
Mobile Web Browser Support
|
||||
---------------
|
||||
|
||||
ownCloud 7 is friendly to small screens, and can be used on most tablet and
|
||||
mobile browsers without requiring the use of a native mobile app. This provides
|
||||
support for devices that don't have a native app, like Microsoft and
|
||||
Blackberry.
|
||||
|
||||
Lazy Loading Files
|
||||
------------------
|
||||
|
||||
Viewing your Files page is faster now thanks to "lazy loading", which loads
|
||||
files as you scroll down the page instead of loading all of them when you open
|
||||
the page.
|
||||
|
||||
Object Stores as Primary Storage
|
||||
---------------------------
|
||||
|
||||
ownCloud can now leverage SWIFT object stores as primary storage for ownCloud
|
||||
files. Users can choose the best option for their specific needs: local
|
||||
storage,
|
||||
network filesystem mounts, or SWIFT object stores.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user