Joomla! Documentation - User contributions [en]

Security Checklist/Hosting and Server Setup/nl

2018-12-06T09:55:40Z

Webcatsolutions: Created page with " ===Maak geen gebruik van PHP allow_url_include==="

<noinclude><languages /></noinclude>
{{:Security Checklist/TOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this [https://resources.joomla.org/en/category/hosting-providers list of hosts] who meet the security requirements of a typical Joomla site. ([[S:MyLanguage/Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])
===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.
==Configuring Apache==
===Use Apache .htaccess===
''See also [[S:MyLanguage/htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching to PHP7.

: Joomla ships with a [[S:MyLanguage/Preconfigured htaccess|preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

: Consider using a serverside filtering solution like Apache mod_security - a great starting point is the OWASP ModSecurity [https://coreruleset.org/ CoreRuleSet]

===PHP Being Run as an Apache Module===

This causes ownership issues and thus permission problems which will lead to security issues. It is better to select a server setup/host that runs php as a cgi process (such as cgi-fcgi) along with using phpSuExec or a similar configuration.

The two best tutorials and explanations on permissions, ownerships and their relations are from this official Joomla doc page:
*[[S:MyLanguage/Where can you learn more about file permissions?|File Permissions]]
*[[S:MyLanguage/Why_can't_you_install_any_extensions%3F#File_ownership_advice_from_ianmac|File ownership advice]]

Specific topics to read would be the following two:
*[[S:MyLanguage/How do UNIX file permissions work?|Unix Permissions Primer]]
And for information on phpSuExec and similar implementations:
*[[S:MyLanguage/Using phpSuExec|Using phpSuExec]]
===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [https://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [https://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)
==Configuring MySQL==
===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)
== Configuring PHP==
===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install.
===Use PHP7===
PHP versions become deprecated and has become obsolete. Some hosting providers still have several available on servers to support outdated scripts. Joomla should be using PHP7.x. (See [https://downloads.joomla.org/technical-requirements Joomla Requirements])
===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only affect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the backend administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.
===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open
===Consider Using PHP open_basedir===
: You ''might'' consider enabling ''open_basedir''. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: ''' ''This PHP feature has been depreciated as of PHP 5.3.0 (30-06-2009) and has been removed from php as of PHP 5.4.0.'''''

: Adjust the ''magic_quotes_gpc'' directive as needed for your site.
*Joomla! 3.0 and above '''requires''' ''magic_quotes_gpc'' to be set to off and will not install if ''magic_quotes_gpc'' is on.
*Joomla! advises ''magic_quotes_gpc'' to be set to off when using Joomla 2.5.xx.
*Joomla! 1.5 ignores the magic_quotes setting and works fine either way. The safest method is to turn magic_quotes_gpc off and avoid all poorly-written extensions.
*The recommended settings for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions.

: For more information, see either [[S:MyLanguage/Magic quotes and security|Magic quotes and security]] or [http://php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

to turn off magic_quotes_gpc = 0
to turn on magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Relying on this feature is highly discouraged. Avoid the use of PHP safe_mode. This was an attempt to solve shared security problems and provides a false sense of security. Safe mode can also cause ownership problems with applications and any files created by the applications. See the official PHP site for more information. [http://php.net/manual/en/features.safe-mode.php PHP Manual: Safe Mode]

safe_mode = 0
===Don't use PHP register_globals===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server.

: For more information, see [http://php.net/manual/en/security.globals.php PHP Manual: Using Register Globals].

register_globals = 0

===Maak geen gebruik van PHP allow_url_include===

: Do not use PHP ''allow_url_include''. This PHP option allows a programmer to include a remote file using an URL rather than a local file path. This is insecure. If an application (or extension) can be tricked into including content from a URL outside itself, an attacker could force the application (or extension) to start running code from their own web site. If an application or extension claims to require this feature to function, you should look into alternatives, as a requirement to use of this feature indicates serious design flaws within the application or extension.

=== Use allow_url_fopen ===
: This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons. '''Enable and use allow_url_fopen to allow Joomla's One-Click-Update to work properly.'''

: For more information see: [http://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen PHP Manual: allow_url_fopen and allow_url_include]

Proper setup will have this:
allow_url_fopen = 1
allow_url_include = 0

PHP default: allow_url_fopen is enabled
PHP default: allow_url_include is disabled

== Bestandsrechten ==
: If a Joomla installation is hosted on Apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP:
*DocumentRoot directory: 750 (e.g. public_html)
*Bestanden: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)

: With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.

: Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

: If a Joomla installation is hosted on Apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 750 (e.g. public_html)
* PHP bestanden: 600 (400 als je paranoïde bent)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)

: '''If''' the server your are on requires 777 permissions for Joomla to work correctly, then '''request to be put on another server''' with php as cgi and suphp and up-to-date serverside software (apache, php etc) on your existing host or find another server host if necessary.

: Do check with your hosting provider to see if they have purposely secured the server your site is on; and that they or you perform regular (weekly) security updates to keep the server up to date. Check you have jail shell. A rule of thumb is the less you pay, the less they care.

: More information on file permissions can be found here: [[S:MyLanguage/Security Checklist/Where can you learn more about file permissions?|File permissions]]

==Setup a backup and recovery process==
===The most important rule===
: You should at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

#Kapotte site door een foutieve upgrade.
#Hardware failure, such as dead hard drives, power failures, server theft, etc.
#Authoritarian government intervention. (More common than some think.)
#Needing to quickly relocate to a new server or hosting provider.

: Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van de backups om een gehackte site te herstellen, zal juist de hack weer terugzetten.

<noinclude>
[[Category:Security Checklist{{#translation:}}]]
[[Category:Server configurations{{#translation:}}]]
</noinclude>

Translations:Security Checklist/Hosting and Server Setup/61/nl

2018-12-06T09:55:40Z

Webcatsolutions: Created page with " ===Maak geen gebruik van PHP allow_url_include==="

===Maak geen gebruik van PHP allow_url_include===

Security Checklist/Hosting and Server Setup/nl

2018-12-06T09:54:56Z

Webcatsolutions: Created page with "== Bestandsrechten =="

<noinclude><languages /></noinclude>
{{:Security Checklist/TOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this [https://resources.joomla.org/en/category/hosting-providers list of hosts] who meet the security requirements of a typical Joomla site. ([[S:MyLanguage/Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])
===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.
==Configuring Apache==
===Use Apache .htaccess===
''See also [[S:MyLanguage/htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching to PHP7.

: Joomla ships with a [[S:MyLanguage/Preconfigured htaccess|preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

: Consider using a serverside filtering solution like Apache mod_security - a great starting point is the OWASP ModSecurity [https://coreruleset.org/ CoreRuleSet]

===PHP Being Run as an Apache Module===

This causes ownership issues and thus permission problems which will lead to security issues. It is better to select a server setup/host that runs php as a cgi process (such as cgi-fcgi) along with using phpSuExec or a similar configuration.

The two best tutorials and explanations on permissions, ownerships and their relations are from this official Joomla doc page:
*[[S:MyLanguage/Where can you learn more about file permissions?|File Permissions]]
*[[S:MyLanguage/Why_can't_you_install_any_extensions%3F#File_ownership_advice_from_ianmac|File ownership advice]]

Specific topics to read would be the following two:
*[[S:MyLanguage/How do UNIX file permissions work?|Unix Permissions Primer]]
And for information on phpSuExec and similar implementations:
*[[S:MyLanguage/Using phpSuExec|Using phpSuExec]]
===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [https://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [https://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)
==Configuring MySQL==
===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)
== Configuring PHP==
===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install.
===Use PHP7===
PHP versions become deprecated and has become obsolete. Some hosting providers still have several available on servers to support outdated scripts. Joomla should be using PHP7.x. (See [https://downloads.joomla.org/technical-requirements Joomla Requirements])
===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only affect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the backend administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.
===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open
===Consider Using PHP open_basedir===
: You ''might'' consider enabling ''open_basedir''. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: ''' ''This PHP feature has been depreciated as of PHP 5.3.0 (30-06-2009) and has been removed from php as of PHP 5.4.0.'''''

: Adjust the ''magic_quotes_gpc'' directive as needed for your site.
*Joomla! 3.0 and above '''requires''' ''magic_quotes_gpc'' to be set to off and will not install if ''magic_quotes_gpc'' is on.
*Joomla! advises ''magic_quotes_gpc'' to be set to off when using Joomla 2.5.xx.
*Joomla! 1.5 ignores the magic_quotes setting and works fine either way. The safest method is to turn magic_quotes_gpc off and avoid all poorly-written extensions.
*The recommended settings for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions.

: For more information, see either [[S:MyLanguage/Magic quotes and security|Magic quotes and security]] or [http://php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

to turn off magic_quotes_gpc = 0
to turn on magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Relying on this feature is highly discouraged. Avoid the use of PHP safe_mode. This was an attempt to solve shared security problems and provides a false sense of security. Safe mode can also cause ownership problems with applications and any files created by the applications. See the official PHP site for more information. [http://php.net/manual/en/features.safe-mode.php PHP Manual: Safe Mode]

safe_mode = 0
===Don't use PHP register_globals===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server.

: For more information, see [http://php.net/manual/en/security.globals.php PHP Manual: Using Register Globals].

register_globals = 0

===Don't use PHP allow_url_include===

: Do not use PHP ''allow_url_include''. This PHP option allows a programmer to include a remote file using an URL rather than a local file path. This is insecure. If an application (or extension) can be tricked into including content from a URL outside itself, an attacker could force the application (or extension) to start running code from their own web site. If an application or extension claims to require this feature to function, you should look into alternatives, as a requirement to use of this feature indicates serious design flaws within the application or extension.

=== Use allow_url_fopen ===
: This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons. '''Enable and use allow_url_fopen to allow Joomla's One-Click-Update to work properly.'''

: For more information see: [http://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen PHP Manual: allow_url_fopen and allow_url_include]

Proper setup will have this:
allow_url_fopen = 1
allow_url_include = 0

PHP default: allow_url_fopen is enabled
PHP default: allow_url_include is disabled

== Bestandsrechten ==
: If a Joomla installation is hosted on Apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP:
*DocumentRoot directory: 750 (e.g. public_html)
*Bestanden: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)

: With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.

: Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

: If a Joomla installation is hosted on Apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 750 (e.g. public_html)
* PHP bestanden: 600 (400 als je paranoïde bent)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)

: '''If''' the server your are on requires 777 permissions for Joomla to work correctly, then '''request to be put on another server''' with php as cgi and suphp and up-to-date serverside software (apache, php etc) on your existing host or find another server host if necessary.

: Do check with your hosting provider to see if they have purposely secured the server your site is on; and that they or you perform regular (weekly) security updates to keep the server up to date. Check you have jail shell. A rule of thumb is the less you pay, the less they care.

: More information on file permissions can be found here: [[S:MyLanguage/Security Checklist/Where can you learn more about file permissions?|File permissions]]

==Setup a backup and recovery process==
===The most important rule===
: You should at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

#Kapotte site door een foutieve upgrade.
#Hardware failure, such as dead hard drives, power failures, server theft, etc.
#Authoritarian government intervention. (More common than some think.)
#Needing to quickly relocate to a new server or hosting provider.

: Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van de backups om een gehackte site te herstellen, zal juist de hack weer terugzetten.

<noinclude>
[[Category:Security Checklist{{#translation:}}]]
[[Category:Server configurations{{#translation:}}]]
</noinclude>

Translations:Security Checklist/Hosting and Server Setup/66/nl

2018-12-06T09:54:56Z

Webcatsolutions: Created page with "== Bestandsrechten =="

== Bestandsrechten ==

Security Checklist/Hosting and Server Setup/nl

2018-12-06T09:54:07Z

Webcatsolutions: Created page with "PHP bestanden: 600 (400 als je paranoïde bent)"

<noinclude><languages /></noinclude>
{{:Security Checklist/TOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this [https://resources.joomla.org/en/category/hosting-providers list of hosts] who meet the security requirements of a typical Joomla site. ([[S:MyLanguage/Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])
===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.
==Configuring Apache==
===Use Apache .htaccess===
''See also [[S:MyLanguage/htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching to PHP7.

: Joomla ships with a [[S:MyLanguage/Preconfigured htaccess|preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

: Consider using a serverside filtering solution like Apache mod_security - a great starting point is the OWASP ModSecurity [https://coreruleset.org/ CoreRuleSet]

===PHP Being Run as an Apache Module===

This causes ownership issues and thus permission problems which will lead to security issues. It is better to select a server setup/host that runs php as a cgi process (such as cgi-fcgi) along with using phpSuExec or a similar configuration.

The two best tutorials and explanations on permissions, ownerships and their relations are from this official Joomla doc page:
*[[S:MyLanguage/Where can you learn more about file permissions?|File Permissions]]
*[[S:MyLanguage/Why_can't_you_install_any_extensions%3F#File_ownership_advice_from_ianmac|File ownership advice]]

Specific topics to read would be the following two:
*[[S:MyLanguage/How do UNIX file permissions work?|Unix Permissions Primer]]
And for information on phpSuExec and similar implementations:
*[[S:MyLanguage/Using phpSuExec|Using phpSuExec]]
===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [https://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [https://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)
==Configuring MySQL==
===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)
== Configuring PHP==
===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install.
===Use PHP7===
PHP versions become deprecated and has become obsolete. Some hosting providers still have several available on servers to support outdated scripts. Joomla should be using PHP7.x. (See [https://downloads.joomla.org/technical-requirements Joomla Requirements])
===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only affect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the backend administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.
===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open
===Consider Using PHP open_basedir===
: You ''might'' consider enabling ''open_basedir''. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: ''' ''This PHP feature has been depreciated as of PHP 5.3.0 (30-06-2009) and has been removed from php as of PHP 5.4.0.'''''

: Adjust the ''magic_quotes_gpc'' directive as needed for your site.
*Joomla! 3.0 and above '''requires''' ''magic_quotes_gpc'' to be set to off and will not install if ''magic_quotes_gpc'' is on.
*Joomla! advises ''magic_quotes_gpc'' to be set to off when using Joomla 2.5.xx.
*Joomla! 1.5 ignores the magic_quotes setting and works fine either way. The safest method is to turn magic_quotes_gpc off and avoid all poorly-written extensions.
*The recommended settings for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions.

: For more information, see either [[S:MyLanguage/Magic quotes and security|Magic quotes and security]] or [http://php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

to turn off magic_quotes_gpc = 0
to turn on magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Relying on this feature is highly discouraged. Avoid the use of PHP safe_mode. This was an attempt to solve shared security problems and provides a false sense of security. Safe mode can also cause ownership problems with applications and any files created by the applications. See the official PHP site for more information. [http://php.net/manual/en/features.safe-mode.php PHP Manual: Safe Mode]

safe_mode = 0
===Don't use PHP register_globals===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server.

: For more information, see [http://php.net/manual/en/security.globals.php PHP Manual: Using Register Globals].

register_globals = 0

===Don't use PHP allow_url_include===

: Do not use PHP ''allow_url_include''. This PHP option allows a programmer to include a remote file using an URL rather than a local file path. This is insecure. If an application (or extension) can be tricked into including content from a URL outside itself, an attacker could force the application (or extension) to start running code from their own web site. If an application or extension claims to require this feature to function, you should look into alternatives, as a requirement to use of this feature indicates serious design flaws within the application or extension.

=== Use allow_url_fopen ===
: This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons. '''Enable and use allow_url_fopen to allow Joomla's One-Click-Update to work properly.'''

: For more information see: [http://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen PHP Manual: allow_url_fopen and allow_url_include]

Proper setup will have this:
allow_url_fopen = 1
allow_url_include = 0

PHP default: allow_url_fopen is enabled
PHP default: allow_url_include is disabled

== File permissions ==
: If a Joomla installation is hosted on Apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP:
*DocumentRoot directory: 750 (e.g. public_html)
*Bestanden: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)

: With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.

: Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

: If a Joomla installation is hosted on Apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 750 (e.g. public_html)
* PHP bestanden: 600 (400 als je paranoïde bent)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)

: '''If''' the server your are on requires 777 permissions for Joomla to work correctly, then '''request to be put on another server''' with php as cgi and suphp and up-to-date serverside software (apache, php etc) on your existing host or find another server host if necessary.

: Do check with your hosting provider to see if they have purposely secured the server your site is on; and that they or you perform regular (weekly) security updates to keep the server up to date. Check you have jail shell. A rule of thumb is the less you pay, the less they care.

: More information on file permissions can be found here: [[S:MyLanguage/Security Checklist/Where can you learn more about file permissions?|File permissions]]

==Setup a backup and recovery process==
===The most important rule===
: You should at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

#Kapotte site door een foutieve upgrade.
#Hardware failure, such as dead hard drives, power failures, server theft, etc.
#Authoritarian government intervention. (More common than some think.)
#Needing to quickly relocate to a new server or hosting provider.

: Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van de backups om een gehackte site te herstellen, zal juist de hack weer terugzetten.

<noinclude>
[[Category:Security Checklist{{#translation:}}]]
[[Category:Server configurations{{#translation:}}]]
</noinclude>

Translations:Security Checklist/Hosting and Server Setup/75/nl

2018-12-06T09:54:06Z

Webcatsolutions: Created page with "PHP bestanden: 600 (400 als je paranoïde bent)"

PHP bestanden: 600 (400 als je paranoïde bent)

Security Checklist/Hosting and Server Setup/nl

2018-12-06T09:53:10Z

Webcatsolutions: Created page with "Bestanden: 644"

<noinclude><languages /></noinclude>
{{:Security Checklist/TOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this [https://resources.joomla.org/en/category/hosting-providers list of hosts] who meet the security requirements of a typical Joomla site. ([[S:MyLanguage/Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])
===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.
==Configuring Apache==
===Use Apache .htaccess===
''See also [[S:MyLanguage/htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching to PHP7.

: Joomla ships with a [[S:MyLanguage/Preconfigured htaccess|preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

: Consider using a serverside filtering solution like Apache mod_security - a great starting point is the OWASP ModSecurity [https://coreruleset.org/ CoreRuleSet]

===PHP Being Run as an Apache Module===

This causes ownership issues and thus permission problems which will lead to security issues. It is better to select a server setup/host that runs php as a cgi process (such as cgi-fcgi) along with using phpSuExec or a similar configuration.

The two best tutorials and explanations on permissions, ownerships and their relations are from this official Joomla doc page:
*[[S:MyLanguage/Where can you learn more about file permissions?|File Permissions]]
*[[S:MyLanguage/Why_can't_you_install_any_extensions%3F#File_ownership_advice_from_ianmac|File ownership advice]]

Specific topics to read would be the following two:
*[[S:MyLanguage/How do UNIX file permissions work?|Unix Permissions Primer]]
And for information on phpSuExec and similar implementations:
*[[S:MyLanguage/Using phpSuExec|Using phpSuExec]]
===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [https://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [https://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)
==Configuring MySQL==
===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)
== Configuring PHP==
===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install.
===Use PHP7===
PHP versions become deprecated and has become obsolete. Some hosting providers still have several available on servers to support outdated scripts. Joomla should be using PHP7.x. (See [https://downloads.joomla.org/technical-requirements Joomla Requirements])
===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only affect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the backend administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.
===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open
===Consider Using PHP open_basedir===
: You ''might'' consider enabling ''open_basedir''. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: ''' ''This PHP feature has been depreciated as of PHP 5.3.0 (30-06-2009) and has been removed from php as of PHP 5.4.0.'''''

: Adjust the ''magic_quotes_gpc'' directive as needed for your site.
*Joomla! 3.0 and above '''requires''' ''magic_quotes_gpc'' to be set to off and will not install if ''magic_quotes_gpc'' is on.
*Joomla! advises ''magic_quotes_gpc'' to be set to off when using Joomla 2.5.xx.
*Joomla! 1.5 ignores the magic_quotes setting and works fine either way. The safest method is to turn magic_quotes_gpc off and avoid all poorly-written extensions.
*The recommended settings for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions.

: For more information, see either [[S:MyLanguage/Magic quotes and security|Magic quotes and security]] or [http://php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

to turn off magic_quotes_gpc = 0
to turn on magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Relying on this feature is highly discouraged. Avoid the use of PHP safe_mode. This was an attempt to solve shared security problems and provides a false sense of security. Safe mode can also cause ownership problems with applications and any files created by the applications. See the official PHP site for more information. [http://php.net/manual/en/features.safe-mode.php PHP Manual: Safe Mode]

safe_mode = 0
===Don't use PHP register_globals===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server.

: For more information, see [http://php.net/manual/en/security.globals.php PHP Manual: Using Register Globals].

register_globals = 0

===Don't use PHP allow_url_include===

: Do not use PHP ''allow_url_include''. This PHP option allows a programmer to include a remote file using an URL rather than a local file path. This is insecure. If an application (or extension) can be tricked into including content from a URL outside itself, an attacker could force the application (or extension) to start running code from their own web site. If an application or extension claims to require this feature to function, you should look into alternatives, as a requirement to use of this feature indicates serious design flaws within the application or extension.

=== Use allow_url_fopen ===
: This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons. '''Enable and use allow_url_fopen to allow Joomla's One-Click-Update to work properly.'''

: For more information see: [http://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen PHP Manual: allow_url_fopen and allow_url_include]

Proper setup will have this:
allow_url_fopen = 1
allow_url_include = 0

PHP default: allow_url_fopen is enabled
PHP default: allow_url_include is disabled

== File permissions ==
: If a Joomla installation is hosted on Apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP:
*DocumentRoot directory: 750 (e.g. public_html)
*Bestanden: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)

: With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.

: Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

: If a Joomla installation is hosted on Apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 750 (e.g. public_html)
* PHP files: 600 (400 if you are truly paranoid)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)

: '''If''' the server your are on requires 777 permissions for Joomla to work correctly, then '''request to be put on another server''' with php as cgi and suphp and up-to-date serverside software (apache, php etc) on your existing host or find another server host if necessary.

: Do check with your hosting provider to see if they have purposely secured the server your site is on; and that they or you perform regular (weekly) security updates to keep the server up to date. Check you have jail shell. A rule of thumb is the less you pay, the less they care.

: More information on file permissions can be found here: [[S:MyLanguage/Security Checklist/Where can you learn more about file permissions?|File permissions]]

==Setup a backup and recovery process==
===The most important rule===
: You should at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

#Kapotte site door een foutieve upgrade.
#Hardware failure, such as dead hard drives, power failures, server theft, etc.
#Authoritarian government intervention. (More common than some think.)
#Needing to quickly relocate to a new server or hosting provider.

: Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van de backups om een gehackte site te herstellen, zal juist de hack weer terugzetten.

<noinclude>
[[Category:Security Checklist{{#translation:}}]]
[[Category:Server configurations{{#translation:}}]]
</noinclude>

Translations:Security Checklist/Hosting and Server Setup/69/nl

2018-12-06T09:53:10Z

Webcatsolutions: Created page with "Bestanden: 644"

Bestanden: 644

Security Checklist/Hosting and Server Setup/nl

2018-12-06T09:52:50Z

Webcatsolutions: Created page with "Kapotte site door een foutieve upgrade."

<noinclude><languages /></noinclude>
{{:Security Checklist/TOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this [https://resources.joomla.org/en/category/hosting-providers list of hosts] who meet the security requirements of a typical Joomla site. ([[S:MyLanguage/Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])
===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.
==Configuring Apache==
===Use Apache .htaccess===
''See also [[S:MyLanguage/htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching to PHP7.

: Joomla ships with a [[S:MyLanguage/Preconfigured htaccess|preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

: Consider using a serverside filtering solution like Apache mod_security - a great starting point is the OWASP ModSecurity [https://coreruleset.org/ CoreRuleSet]

===PHP Being Run as an Apache Module===

This causes ownership issues and thus permission problems which will lead to security issues. It is better to select a server setup/host that runs php as a cgi process (such as cgi-fcgi) along with using phpSuExec or a similar configuration.

The two best tutorials and explanations on permissions, ownerships and their relations are from this official Joomla doc page:
*[[S:MyLanguage/Where can you learn more about file permissions?|File Permissions]]
*[[S:MyLanguage/Why_can't_you_install_any_extensions%3F#File_ownership_advice_from_ianmac|File ownership advice]]

Specific topics to read would be the following two:
*[[S:MyLanguage/How do UNIX file permissions work?|Unix Permissions Primer]]
And for information on phpSuExec and similar implementations:
*[[S:MyLanguage/Using phpSuExec|Using phpSuExec]]
===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [https://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [https://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)
==Configuring MySQL==
===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)
== Configuring PHP==
===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install.
===Use PHP7===
PHP versions become deprecated and has become obsolete. Some hosting providers still have several available on servers to support outdated scripts. Joomla should be using PHP7.x. (See [https://downloads.joomla.org/technical-requirements Joomla Requirements])
===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only affect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the backend administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.
===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open
===Consider Using PHP open_basedir===
: You ''might'' consider enabling ''open_basedir''. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: ''' ''This PHP feature has been depreciated as of PHP 5.3.0 (30-06-2009) and has been removed from php as of PHP 5.4.0.'''''

: Adjust the ''magic_quotes_gpc'' directive as needed for your site.
*Joomla! 3.0 and above '''requires''' ''magic_quotes_gpc'' to be set to off and will not install if ''magic_quotes_gpc'' is on.
*Joomla! advises ''magic_quotes_gpc'' to be set to off when using Joomla 2.5.xx.
*Joomla! 1.5 ignores the magic_quotes setting and works fine either way. The safest method is to turn magic_quotes_gpc off and avoid all poorly-written extensions.
*The recommended settings for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions.

: For more information, see either [[S:MyLanguage/Magic quotes and security|Magic quotes and security]] or [http://php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

to turn off magic_quotes_gpc = 0
to turn on magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Relying on this feature is highly discouraged. Avoid the use of PHP safe_mode. This was an attempt to solve shared security problems and provides a false sense of security. Safe mode can also cause ownership problems with applications and any files created by the applications. See the official PHP site for more information. [http://php.net/manual/en/features.safe-mode.php PHP Manual: Safe Mode]

safe_mode = 0
===Don't use PHP register_globals===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server.

: For more information, see [http://php.net/manual/en/security.globals.php PHP Manual: Using Register Globals].

register_globals = 0

===Don't use PHP allow_url_include===

: Do not use PHP ''allow_url_include''. This PHP option allows a programmer to include a remote file using an URL rather than a local file path. This is insecure. If an application (or extension) can be tricked into including content from a URL outside itself, an attacker could force the application (or extension) to start running code from their own web site. If an application or extension claims to require this feature to function, you should look into alternatives, as a requirement to use of this feature indicates serious design flaws within the application or extension.

=== Use allow_url_fopen ===
: This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons. '''Enable and use allow_url_fopen to allow Joomla's One-Click-Update to work properly.'''

: For more information see: [http://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen PHP Manual: allow_url_fopen and allow_url_include]

Proper setup will have this:
allow_url_fopen = 1
allow_url_include = 0

PHP default: allow_url_fopen is enabled
PHP default: allow_url_include is disabled

== File permissions ==
: If a Joomla installation is hosted on Apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP:
*DocumentRoot directory: 750 (e.g. public_html)
*Files: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)

: With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.

: Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

: If a Joomla installation is hosted on Apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 750 (e.g. public_html)
* PHP files: 600 (400 if you are truly paranoid)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)

: '''If''' the server your are on requires 777 permissions for Joomla to work correctly, then '''request to be put on another server''' with php as cgi and suphp and up-to-date serverside software (apache, php etc) on your existing host or find another server host if necessary.

: Do check with your hosting provider to see if they have purposely secured the server your site is on; and that they or you perform regular (weekly) security updates to keep the server up to date. Check you have jail shell. A rule of thumb is the less you pay, the less they care.

: More information on file permissions can be found here: [[S:MyLanguage/Security Checklist/Where can you learn more about file permissions?|File permissions]]

==Setup a backup and recovery process==
===The most important rule===
: You should at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

#Kapotte site door een foutieve upgrade.
#Hardware failure, such as dead hard drives, power failures, server theft, etc.
#Authoritarian government intervention. (More common than some think.)
#Needing to quickly relocate to a new server or hosting provider.

: Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van de backups om een gehackte site te herstellen, zal juist de hack weer terugzetten.

<noinclude>
[[Category:Security Checklist{{#translation:}}]]
[[Category:Server configurations{{#translation:}}]]
</noinclude>

Translations:Security Checklist/Hosting and Server Setup/84/nl

2018-12-06T09:52:50Z

Webcatsolutions: Created page with "Kapotte site door een foutieve upgrade."

Kapotte site door een foutieve upgrade.

Security Checklist/Hosting and Server Setup/nl

2018-12-06T09:51:42Z

Webcatsolutions: Created page with "Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van..."

<noinclude><languages /></noinclude>
{{:Security Checklist/TOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this [https://resources.joomla.org/en/category/hosting-providers list of hosts] who meet the security requirements of a typical Joomla site. ([[S:MyLanguage/Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])
===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.
==Configuring Apache==
===Use Apache .htaccess===
''See also [[S:MyLanguage/htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching to PHP7.

: Joomla ships with a [[S:MyLanguage/Preconfigured htaccess|preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

: Consider using a serverside filtering solution like Apache mod_security - a great starting point is the OWASP ModSecurity [https://coreruleset.org/ CoreRuleSet]

===PHP Being Run as an Apache Module===

This causes ownership issues and thus permission problems which will lead to security issues. It is better to select a server setup/host that runs php as a cgi process (such as cgi-fcgi) along with using phpSuExec or a similar configuration.

The two best tutorials and explanations on permissions, ownerships and their relations are from this official Joomla doc page:
*[[S:MyLanguage/Where can you learn more about file permissions?|File Permissions]]
*[[S:MyLanguage/Why_can't_you_install_any_extensions%3F#File_ownership_advice_from_ianmac|File ownership advice]]

Specific topics to read would be the following two:
*[[S:MyLanguage/How do UNIX file permissions work?|Unix Permissions Primer]]
And for information on phpSuExec and similar implementations:
*[[S:MyLanguage/Using phpSuExec|Using phpSuExec]]
===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [https://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [https://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)
==Configuring MySQL==
===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)
== Configuring PHP==
===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install.
===Use PHP7===
PHP versions become deprecated and has become obsolete. Some hosting providers still have several available on servers to support outdated scripts. Joomla should be using PHP7.x. (See [https://downloads.joomla.org/technical-requirements Joomla Requirements])
===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only affect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the backend administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.
===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open
===Consider Using PHP open_basedir===
: You ''might'' consider enabling ''open_basedir''. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: ''' ''This PHP feature has been depreciated as of PHP 5.3.0 (30-06-2009) and has been removed from php as of PHP 5.4.0.'''''

: Adjust the ''magic_quotes_gpc'' directive as needed for your site.
*Joomla! 3.0 and above '''requires''' ''magic_quotes_gpc'' to be set to off and will not install if ''magic_quotes_gpc'' is on.
*Joomla! advises ''magic_quotes_gpc'' to be set to off when using Joomla 2.5.xx.
*Joomla! 1.5 ignores the magic_quotes setting and works fine either way. The safest method is to turn magic_quotes_gpc off and avoid all poorly-written extensions.
*The recommended settings for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions.

: For more information, see either [[S:MyLanguage/Magic quotes and security|Magic quotes and security]] or [http://php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

to turn off magic_quotes_gpc = 0
to turn on magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Relying on this feature is highly discouraged. Avoid the use of PHP safe_mode. This was an attempt to solve shared security problems and provides a false sense of security. Safe mode can also cause ownership problems with applications and any files created by the applications. See the official PHP site for more information. [http://php.net/manual/en/features.safe-mode.php PHP Manual: Safe Mode]

safe_mode = 0
===Don't use PHP register_globals===
: ''' ''This PHP feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 5.4.0'''''

: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server.

: For more information, see [http://php.net/manual/en/security.globals.php PHP Manual: Using Register Globals].

register_globals = 0

===Don't use PHP allow_url_include===

: Do not use PHP ''allow_url_include''. This PHP option allows a programmer to include a remote file using an URL rather than a local file path. This is insecure. If an application (or extension) can be tricked into including content from a URL outside itself, an attacker could force the application (or extension) to start running code from their own web site. If an application or extension claims to require this feature to function, you should look into alternatives, as a requirement to use of this feature indicates serious design flaws within the application or extension.

=== Use allow_url_fopen ===
: This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons. '''Enable and use allow_url_fopen to allow Joomla's One-Click-Update to work properly.'''

: For more information see: [http://www.php.net/manual/en/filesystem.configuration.php#ini.allow-url-fopen PHP Manual: allow_url_fopen and allow_url_include]

Proper setup will have this:
allow_url_fopen = 1
allow_url_include = 0

PHP default: allow_url_fopen is enabled
PHP default: allow_url_include is disabled

== File permissions ==
: If a Joomla installation is hosted on Apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP:
*DocumentRoot directory: 750 (e.g. public_html)
*Files: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)

: With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.

: Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

: If a Joomla installation is hosted on Apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 750 (e.g. public_html)
* PHP files: 600 (400 if you are truly paranoid)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)

: '''If''' the server your are on requires 777 permissions for Joomla to work correctly, then '''request to be put on another server''' with php as cgi and suphp and up-to-date serverside software (apache, php etc) on your existing host or find another server host if necessary.

: Do check with your hosting provider to see if they have purposely secured the server your site is on; and that they or you perform regular (weekly) security updates to keep the server up to date. Check you have jail shell. A rule of thumb is the less you pay, the less they care.

: More information on file permissions can be found here: [[S:MyLanguage/Security Checklist/Where can you learn more about file permissions?|File permissions]]

==Setup a backup and recovery process==
===The most important rule===
: You should at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

#Broken site due to a faulty upgrade.
#Hardware failure, such as dead hard drives, power failures, server theft, etc.
#Authoritarian government intervention. (More common than some think.)
#Needing to quickly relocate to a new server or hosting provider.

: Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van de backups om een gehackte site te herstellen, zal juist de hack weer terugzetten.

<noinclude>
[[Category:Security Checklist{{#translation:}}]]
[[Category:Server configurations{{#translation:}}]]
</noinclude>

Translations:Security Checklist/Hosting and Server Setup/88/nl

2018-12-06T09:51:42Z

Het wordt afgeraden om een gehackte website te herstellen via backup bestanden, omdat het mogelijk is dat de backups de aangepaste en gehackte bestanden bevat. Het gebruik van de backups om een gehackte site te herstellen, zal juist de hack weer terugzetten.

Help310:Components Cache Manager Settings/nl

2017-03-31T12:41:50Z

Webcatsolutions: Created page with "==Hoe toegang te krijgen=="

<noinclude><languages /></noinclude>

{{tip|title=This page needs your help
|text = If you want to help the Joomla! Documentation Team with the Administrator Help Screens, please consider joining the [https://volunteers.joomla.org/teams/documentation-helpscreen-team Documentation Helpscreen Team].
}}
==Beschrijving==
==Hoe toegang te krijgen==
==Schermafbeelding==
==Kolomkoppen==
==Opties==
==Werkbalk==
==Lijst filters==
==Verwante Informatie==

<noinclude>
[[Category:Documentation Working Group]]
</noinclude>

Translations:Help36:Components Cache Manager Settings/4/nl

2017-03-31T12:41:49Z

Webcatsolutions: Created page with "==Hoe toegang te krijgen=="

==Hoe toegang te krijgen==

Help310:Menus Menu Item Menu Item Alias/nl

2017-03-31T12:40:32Z

Webcatsolutions: Created page with "====Algemene opties===="

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe toegang te krijgen==
To create a new Alias Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] and then click the Menu Item Alias link under System Links.

To edit an existing Menu Item Alias, click its Title in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

==Description==
Used to create a link from one Menu Item to another Menu Item. This link can be to another Menu's, Menu Item or within the same Menu. See [[S:MyLanguage/Help31:Menus Menu Item Menu Item Alias#Quick_Tips|Quick Tips]] for use.

==Schermafbeelding==
[[File:Help-Menus-Menu-Item-Alias-screenshot-nl.png|800px]]

==Gegevens==
===Tabblad Gegevens===
====Verplicht====
These are the required settings:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu Item/en}}
{{chunk30:colheader|Menu/en}}

====Notable Settings====
Leave the Alias blank if the Menu Item Alias has the same Parent (in the same Menu Name).
*{{Chunk30:colheader|Alias/nl}}

====Algemene opties====
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: Edit/New Menu Item]] for help on fields common to all Menu Item types, under the '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Advanced Details Tab]]''' which includes:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]'''

===Module Assignments Tab===
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

==Snelle Tips==
*Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.

*A Main Menu Item Alias could link to an Article Menu's 'Some Menu Type' Menu Item. By using Module Assignments, a possible use would be to replace the Main Menu with the Article Menu when the Alias Menu Item is clicked. A return to Main Menu when another Alias Menu Item is clicked pointed back to a Menu Item in the Main Menu.

==Werkbalk==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

<noinclude>
[[Category:Help screen 3.0]]
[[Category:Help screen 3.1]]
[[Category:Help screen 3.2]]
[[Category:Help screen 3.3]]
[[Category:Help screen 3.4]]
[[Category:Help screen 3.5]]
[[Category:Help screen 3.6]]
[[Category:Documentation Working Group]]
[[Category:Help screens]]
[[Category:Menu Item Manager Help Screens]]
[[Category:Menus Help Screens]]
</noinclude>

Translations:Help36:Menus Menu Item Menu Item Alias/24/nl

2017-03-31T12:40:31Z

Webcatsolutions: Created page with "====Algemene opties===="

====Algemene opties====

Help310:Menus Menu Item Menu Item Alias/nl

2017-03-31T12:40:17Z

Webcatsolutions: Created page with "====Verplicht===="

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe toegang te krijgen==
To create a new Alias Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] and then click the Menu Item Alias link under System Links.

To edit an existing Menu Item Alias, click its Title in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

==Description==
Used to create a link from one Menu Item to another Menu Item. This link can be to another Menu's, Menu Item or within the same Menu. See [[S:MyLanguage/Help31:Menus Menu Item Menu Item Alias#Quick_Tips|Quick Tips]] for use.

==Schermafbeelding==
[[File:Help-Menus-Menu-Item-Alias-screenshot-nl.png|800px]]

==Gegevens==
===Tabblad Gegevens===
====Verplicht====
These are the required settings:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu Item/en}}
{{chunk30:colheader|Menu/en}}

====Notable Settings====
Leave the Alias blank if the Menu Item Alias has the same Parent (in the same Menu Name).
*{{Chunk30:colheader|Alias/nl}}

====Common Options====
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: Edit/New Menu Item]] for help on fields common to all Menu Item types, under the '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Advanced Details Tab]]''' which includes:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]'''

===Module Assignments Tab===
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

==Snelle Tips==
*Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.

*A Main Menu Item Alias could link to an Article Menu's 'Some Menu Type' Menu Item. By using Module Assignments, a possible use would be to replace the Main Menu with the Article Menu when the Alias Menu Item is clicked. A return to Main Menu when another Alias Menu Item is clicked pointed back to a Menu Item in the Main Menu.

==Werkbalk==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

<noinclude>
[[Category:Help screen 3.0]]
[[Category:Help screen 3.1]]
[[Category:Help screen 3.2]]
[[Category:Help screen 3.3]]
[[Category:Help screen 3.4]]
[[Category:Help screen 3.5]]
[[Category:Help screen 3.6]]
[[Category:Documentation Working Group]]
[[Category:Help screens]]
[[Category:Menu Item Manager Help Screens]]
[[Category:Menus Help Screens]]
</noinclude>

Translations:Help36:Menus Menu Item Menu Item Alias/13/nl

2017-03-31T12:40:17Z

Webcatsolutions: Created page with "====Verplicht===="

====Verplicht====

Help310:Menus Menu Item Menu Item Alias/nl

2017-03-31T12:40:05Z

Webcatsolutions: Created page with "===Tabblad Gegevens==="

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe toegang te krijgen==
To create a new Alias Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] and then click the Menu Item Alias link under System Links.

To edit an existing Menu Item Alias, click its Title in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

==Description==
Used to create a link from one Menu Item to another Menu Item. This link can be to another Menu's, Menu Item or within the same Menu. See [[S:MyLanguage/Help31:Menus Menu Item Menu Item Alias#Quick_Tips|Quick Tips]] for use.

==Schermafbeelding==
[[File:Help-Menus-Menu-Item-Alias-screenshot-nl.png|800px]]

==Gegevens==
===Tabblad Gegevens===
====Required====
These are the required settings:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu Item/en}}
{{chunk30:colheader|Menu/en}}

====Notable Settings====
Leave the Alias blank if the Menu Item Alias has the same Parent (in the same Menu Name).
*{{Chunk30:colheader|Alias/nl}}

====Common Options====
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: Edit/New Menu Item]] for help on fields common to all Menu Item types, under the '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Advanced Details Tab]]''' which includes:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]'''

===Module Assignments Tab===
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

==Snelle Tips==
*Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.

*A Main Menu Item Alias could link to an Article Menu's 'Some Menu Type' Menu Item. By using Module Assignments, a possible use would be to replace the Main Menu with the Article Menu when the Alias Menu Item is clicked. A return to Main Menu when another Alias Menu Item is clicked pointed back to a Menu Item in the Main Menu.

==Werkbalk==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

<noinclude>
[[Category:Help screen 3.0]]
[[Category:Help screen 3.1]]
[[Category:Help screen 3.2]]
[[Category:Help screen 3.3]]
[[Category:Help screen 3.4]]
[[Category:Help screen 3.5]]
[[Category:Help screen 3.6]]
[[Category:Documentation Working Group]]
[[Category:Help screens]]
[[Category:Menu Item Manager Help Screens]]
[[Category:Menus Help Screens]]
</noinclude>

Translations:Help36:Menus Menu Item Menu Item Alias/12/nl

2017-03-31T12:40:04Z

Webcatsolutions: Created page with "===Tabblad Gegevens==="

===Tabblad Gegevens===

Help310:Menus Menu Item Menu Item Alias/nl

2017-03-31T12:39:31Z

Webcatsolutions: Created page with "==Gegevens=="

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe toegang te krijgen==
To create a new Alias Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] and then click the Menu Item Alias link under System Links.

To edit an existing Menu Item Alias, click its Title in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

==Description==
Used to create a link from one Menu Item to another Menu Item. This link can be to another Menu's, Menu Item or within the same Menu. See [[S:MyLanguage/Help31:Menus Menu Item Menu Item Alias#Quick_Tips|Quick Tips]] for use.

==Schermafbeelding==
[[File:Help-Menus-Menu-Item-Alias-screenshot-nl.png|800px]]

==Gegevens==
===Details Tab===
====Required====
These are the required settings:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu Item/en}}
{{chunk30:colheader|Menu/en}}

====Notable Settings====
Leave the Alias blank if the Menu Item Alias has the same Parent (in the same Menu Name).
*{{Chunk30:colheader|Alias/nl}}

====Common Options====
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: Edit/New Menu Item]] for help on fields common to all Menu Item types, under the '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Advanced Details Tab]]''' which includes:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]'''

===Module Assignments Tab===
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

==Snelle Tips==
*Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.

*A Main Menu Item Alias could link to an Article Menu's 'Some Menu Type' Menu Item. By using Module Assignments, a possible use would be to replace the Main Menu with the Article Menu when the Alias Menu Item is clicked. A return to Main Menu when another Alias Menu Item is clicked pointed back to a Menu Item in the Main Menu.

==Werkbalk==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

<noinclude>
[[Category:Help screen 3.0]]
[[Category:Help screen 3.1]]
[[Category:Help screen 3.2]]
[[Category:Help screen 3.3]]
[[Category:Help screen 3.4]]
[[Category:Help screen 3.5]]
[[Category:Help screen 3.6]]
[[Category:Documentation Working Group]]
[[Category:Help screens]]
[[Category:Menu Item Manager Help Screens]]
[[Category:Menus Help Screens]]
</noinclude>

Translations:Help36:Menus Menu Item Menu Item Alias/11/nl

2017-03-31T12:39:31Z

Webcatsolutions: Created page with "==Gegevens=="

==Gegevens==

Help310:Menus Menu Item Menu Item Alias/nl

2017-03-31T12:39:06Z

Webcatsolutions:

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe toegang te krijgen==
To create a new Alias Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] and then click the Menu Item Alias link under System Links.

To edit an existing Menu Item Alias, click its Title in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

==Description==
Used to create a link from one Menu Item to another Menu Item. This link can be to another Menu's, Menu Item or within the same Menu. See [[S:MyLanguage/Help31:Menus Menu Item Menu Item Alias#Quick_Tips|Quick Tips]] for use.

==Schermafbeelding==
[[File:Help-Menus-Menu-Item-Alias-screenshot-nl.png|800px]]

==Details==
===Details Tab===
====Required====
These are the required settings:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu Item/en}}
{{chunk30:colheader|Menu/en}}

====Notable Settings====
Leave the Alias blank if the Menu Item Alias has the same Parent (in the same Menu Name).
*{{Chunk30:colheader|Alias/nl}}

====Common Options====
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: Edit/New Menu Item]] for help on fields common to all Menu Item types, under the '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Advanced Details Tab]]''' which includes:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]'''

===Module Assignments Tab===
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

==Snelle Tips==
*Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.

*A Main Menu Item Alias could link to an Article Menu's 'Some Menu Type' Menu Item. By using Module Assignments, a possible use would be to replace the Main Menu with the Article Menu when the Alias Menu Item is clicked. A return to Main Menu when another Alias Menu Item is clicked pointed back to a Menu Item in the Main Menu.

==Werkbalk==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

<noinclude>
[[Category:Help screen 3.0]]
[[Category:Help screen 3.1]]
[[Category:Help screen 3.2]]
[[Category:Help screen 3.3]]
[[Category:Help screen 3.4]]
[[Category:Help screen 3.5]]
[[Category:Help screen 3.6]]
[[Category:Documentation Working Group]]
[[Category:Help screens]]
[[Category:Menu Item Manager Help Screens]]
[[Category:Menus Help Screens]]
</noinclude>

Translations:Help36:Menus Menu Item Menu Item Alias/45/nl

2017-03-31T12:39:05Z

Webcatsolutions:

Help310:Menus Menu Item Menu Item Alias/nl

2017-03-31T12:38:44Z

Webcatsolutions:

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe toegang te krijgen==
To create a new Alias Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-en.png]] and then click the Menu Item Alias link under System Links.

To edit an existing Menu Item Alias, click its Title in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

==Description==
Used to create a link from one Menu Item to another Menu Item. This link can be to another Menu's, Menu Item or within the same Menu. See [[S:MyLanguage/Help31:Menus Menu Item Menu Item Alias#Quick_Tips|Quick Tips]] for use.

==Schermafbeelding==
[[File:Help-Menus-Menu-Item-Alias-screenshot-nl.png|800px]]

==Details==
===Details Tab===
====Required====
These are the required settings:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu Item/en}}
{{chunk30:colheader|Menu/en}}

====Notable Settings====
Leave the Alias blank if the Menu Item Alias has the same Parent (in the same Menu Name).
*{{Chunk30:colheader|Alias/nl}}

====Common Options====
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: Edit/New Menu Item]] for help on fields common to all Menu Item types, under the '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Advanced Details Tab]]''' which includes:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]'''

===Module Assignments Tab===
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

==Snelle Tips==
*Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.

*A Main Menu Item Alias could link to an Article Menu's 'Some Menu Type' Menu Item. By using Module Assignments, a possible use would be to replace the Main Menu with the Article Menu when the Alias Menu Item is clicked. A return to Main Menu when another Alias Menu Item is clicked pointed back to a Menu Item in the Main Menu.

==Werkbalk==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

<noinclude>
[[Category:Help screen 3.0]]
[[Category:Help screen 3.1]]
[[Category:Help screen 3.2]]
[[Category:Help screen 3.3]]
[[Category:Help screen 3.4]]
[[Category:Help screen 3.5]]
[[Category:Help screen 3.6]]
[[Category:Documentation Working Group]]
[[Category:Help screens]]
[[Category:Menu Item Manager Help Screens]]
[[Category:Menus Help Screens]]
</noinclude>

Translations:Help36:Menus Menu Item Menu Item Alias/45/nl

2017-03-31T12:38:44Z

Webcatsolutions:

Help310:Menus Menu Item Menu Item Alias/nl

2017-03-31T12:38:11Z

Webcatsolutions: Created page with "nl"

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe toegang te krijgen==
To create a new Alias Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] and then click the Menu Item Alias link under System Links.

To edit an existing Menu Item Alias, click its Title in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

==Description==
Used to create a link from one Menu Item to another Menu Item. This link can be to another Menu's, Menu Item or within the same Menu. See [[S:MyLanguage/Help31:Menus Menu Item Menu Item Alias#Quick_Tips|Quick Tips]] for use.

==Schermafbeelding==
[[File:Help-Menus-Menu-Item-Alias-screenshot-nl.png|800px]]

==Details==
===Details Tab===
====Required====
These are the required settings:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu Item/en}}
{{chunk30:colheader|Menu/en}}

====Notable Settings====
Leave the Alias blank if the Menu Item Alias has the same Parent (in the same Menu Name).
*{{Chunk30:colheader|Alias/nl}}

====Common Options====
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: Edit/New Menu Item]] for help on fields common to all Menu Item types, under the '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Advanced Details Tab]]''' which includes:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]'''

===Module Assignments Tab===
See [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

==Snelle Tips==
*Leave the alias field empty if the menu item alias and the menu item linked to by the alias have the same parent.

*A Main Menu Item Alias could link to an Article Menu's 'Some Menu Type' Menu Item. By using Module Assignments, a possible use would be to replace the Main Menu with the Article Menu when the Alias Menu Item is clicked. A return to Main Menu when another Alias Menu Item is clicked pointed back to a Menu Item in the Main Menu.

==Werkbalk==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

<noinclude>
[[Category:Help screen 3.0]]
[[Category:Help screen 3.1]]
[[Category:Help screen 3.2]]
[[Category:Help screen 3.3]]
[[Category:Help screen 3.4]]
[[Category:Help screen 3.5]]
[[Category:Help screen 3.6]]
[[Category:Documentation Working Group]]
[[Category:Help screens]]
[[Category:Menu Item Manager Help Screens]]
[[Category:Menus Help Screens]]
</noinclude>

Translations:Help36:Menus Menu Item Menu Item Alias/45/nl

2017-03-31T12:38:11Z

Webcatsolutions: Created page with "nl"

Help310:Menus Menu Item Article Archived/nl

2017-03-31T12:32:19Z

Webcatsolutions:

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe te beginnen==
Om een nieuw 'Gearchiveerd artikel' menu-item te maken:
* Selecteer {{rarr|Menu's,[naam van het menu]}} uit het drop-down menu in de back-end van uw Joomla! installatie (bijvoorbeeld {{rarr|Menu's,Hoofdmenu}}).
* Klik op de knop Nieuw in de werkbalk om een nieuw menu-item te maken.
* Klik op de Menu-itemtype Selecteren knop [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] en klik dan op de Gearchiveerde artikelen link onder de Artikelen link.

Om een bestaand Gearchiveerd artikel menu-item te bewerken, klikt u op de titel in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menubeheer: Menu-items]].

==Beschrijving==
Wordt gebruikt om een lijst met gearchiveerde artikelen te tonen. De lijst met gearchiveerde artikelen kan worden getoond op datum, gefilterd en met de introductietekst zoals hieronder.

==Schermafbeelding==
[[Image:Help30-Menus-Menu-Item-Article-Archived-screen-nl.png|800px]]

Gearchiveerde artikelen worden niet meer gepubliceerd maar worden nog steeds op de site opgeslagen. Artikelen worden gearchiveerd met behulp met het [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]] scherm. Let op dat artikelen gekoppeld aan de "Niet gecategoriseerd" categorie niet getoond wordt in de lijst met gearchiveerde artikelen.

==Gegevens==
===Gegevens Tab===
====Verplichte instellingen====
Het gearchiveerde artikelen menu-item heeft de volgende verplichte instellingen:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu/nl}}

===Geavanceerde details tabblad===
====Archief opties====
De gearchiveerde artikelen weergave heeft de volgende archief opties, zoals hieronder getoond.
:[[Image:Help30-Menus-Menu-Article-Archived-archive-options-subscreen-nl.png]]
*'''Artikel volgorde.''' De volgorde van artikelen in deze weergave. De volgende opties zijn beschikbaar.
** ''Oudste eerst:'' Artikelen worden getoond met de oudste als eerste en eindigen met de nieuwste.
** ''Meest recente eerst:'' Artikelen worden getoond te beginnen met de nieuwste en eindigend met de oudste.
** ''Titel alfabetisch:'' Artikelen worden op titel alfabetisch gesorteerd getoond (A to Z)
** ''Titel alfabetisch omgekeerd:'' Artikelen worden getoond op de titel in omgekeerd alfabetische volgorde (Z tot A)
** ''Author Alphabetical:'' Articles are displayed by Author in alphabetical order (A to Z)
** ''Author Reverse Alphabetical:'' Articles are displayed by Author in reverse alphabetical order (Z to A)
** ''Meeste hits:'' Artikelen worden getoond op het aantal weergaven door het aantal hits, te beginnen met de meeste hits en eindigen met de minste hits.
** ''Minste hits:'' Artikelen worden getoond door het aantal hits, te beginnen met de minste hits en eindigend met de meeste hits.
** ''Volgorde:'' Artikelen worden gesorteerd volgens de Volgorde kolom opgegeven in Artikelbeheer.
{{Chunk30:colheader|Date for Ordering/nl}}
{{Chunk30:colheader|No Articles to List/nl}}
*'''Filterveld.''' (Gebruik algemeen/Verberg/Toon) Of een filterveld getoond moet worden voor een lijst met artikelen. Indien verborgen, wordt er geen filterveld getoond. Anders wordt het filterveld getoond volgens de algemeen instellingen.
*'''Limiet introtekst.''' Het maximum aantal tekens dat in de introtekst getoond moet worden. Indien de introtekst langer is als deze waarde dan wordt het afgekapt op deze lengte.

====Artikel opties====
De Gearchiveerde artikelen optie heeft de volgende opties, zoals hieronder getoond. Deze opties bepalen hoe artikelen getoond worden op de website.
:[[Image:Help30-Menus-Menu-Item-Article-Single-Article-options-modal-article-options-tab-nl.png]]

Let op dat de opties "'''Gebruik algemeen'''" bevatten. Indien dit geselecteerd is, dan worden de instellingen van de [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer opties]] gebruikt.
{{Chunk30:colheader|Show Intro Text/nl}}
{{Chunk30:colheader|Position of Article Info/nl}}
*'''Article Info Title.''' Displays the 'Article Info' title on top of the article information block.
{{Chunk30:colheader|Show Category/nl}}
{{Chunk30:colheader|Link Category/nl}}
{{Chunk30:colheader|Show Parent/nl}}
{{Chunk30:colheader|Link Parent/nl}}
{{Chunk30:colheader|Linked Titles/nl}}
{{Chunk30:colheader|Show Author/nl}}
{{Chunk30:colheader|Link Author/nl}}
{{Chunk30:colheader|Show Create Date/nl}}
{{Chunk30:colheader|Show Modify Date/nl}}
{{Chunk30:colheader|Show Publish Date/nl}}
{{Chunk30:colheader|Show Navigation/nl}}
{{Chunk30:colheader|Show Hits/nl}}

===Algemene opties===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu-item bewerken]] onder de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Gegevens]]''' voor hulp bij velden die voor alle menu items gelijk zijn, hieronder vallen:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Linktype opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Page Display Options|Paginaweergave opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Metadata Options|Metadata opties]]'''

===Moduletoewijzing tab===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu item bewerken]] voor hulp met betrekking tot de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Moduletoewijzing]]''' velden.

==Werkbalk==
Aan de bovenkant links ziet u de werkbalk:

[[Image:Help30-Save-SaveClose-SaveNew-SaveCopy-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

==Snelle Tips==
* De gearchiveerde artikelen weergave geeft u de mogelijkheid oude of verlopen artikelen te benaderen die u niet geheel van de website wilt verwijderen.
* Indien u oude artikelen wilt zien een categorie blog of lijst, maak dan een categorie aan voor ouder artikelen en verplaats de artikelen naar deze categorie (in plaats van de status te wijzigen naar gearchiveerd).

==Verwante informatie==
* Artikelen worden gearchiveerd met behulp van [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]].

{| class="wikitable"
|-
! Verwante helpschermen !! Beschrijving
|-
| [[S:MyLanguage/Help36:Components_Article_Manager_Options|Component artikelbeheer opties]] || Wordt gebruikt om de algemene standaards voor menu-items die artikelen tonen in te stellen. Deze standaard waarden worden gebruikt als "Gebruik algemeen" wordt geselecteerd als optie in een artikel menu-item. Om bijvoorbeeld de 'Aanmaak datum' te tonen bij een artikel in uw artikel menu-items, zet die optie dan hier op "Toon" en het wordt de standaard waarde. U hoeft geen van deze opties in te stellen. Uw Joomla site zal met de standaard instellingen werken.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager|Inhoud artikelbeheer]] || Artikelbeheer wordt gebruikt voor het vinden, markeren, toevoegen en bewerken van artikelen. Zie [[Special:MyLanguage/Help30:Content_Article_Manager#Toolbar|Werkbalk]] hieronder voor een gedetailleerde lijst van alle functies.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager_Edit|Inhoud artikelbeheer bewerken]] || Dit is het beheergedeelte scherm waar u artikelen kunt toevoegen en bewerken. Hetzelfde scherm wordt gebruikt voor het toevoegen van nieuwe artikelen en het bewerken van een bestaand artikel. U kunt ook de sectie en categorie van een artikel selecteren en aangeven of een artikel al dan niet gepubliceerd wordt en of het op de voorpagina moet worden getoond.
De artikelinhoud wordt bewerkt met de standaard tekstverwerker die gekozen wordt in [[Special:MyLanguage/Help30:Users_User_Manager_Edit|Gebruikersbeheer - Nieuw/Bewerk]]. De standaard Joomla! tekstverwerker heet TinyMCE.
Een aantal parameters kunnen ingesteld worden voor het artikel. Metadata kunnen ook opgegeven worden.
|-
| [[S:MyLanguage/Help36:Content_Featured_Articles|Inhoud speciale artikelen]] || Wordt gebruikt om te bepalen welk 'speciale artikel' getoond worden op de voorpagina en in welke volgorde ze worden getoond. De voorpagina is vaak de startpagina van een website, maar het kan iedere pagina op de site zijn. De voorpagina wordt aangemaakt met een menu-item met het 'Speciale artikelen' menu-itemtype.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Categories|Menu's - Menu-item - Artikel categorieën]] || Wordt gebruikt om een lijst met categorieën te tonen. Categorieën worden getoond in een hiërarchische lijst, zoals hieronder getoond. Afhankelijk van de geselecteerde opties voor de lay-out, kunt u op een categorietitel drukken om de artikelen in die categorie te tonen.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_Blog|Menu's - Menu-item - Artikel categorie blog]] || Wordt gebruikt om artikelen in een bepaalde categorie in blog lay-out te tonen. Regelt de introductie ofwel het leidende artikel, aanvullende artikelen met intro tekst en extra links naar meer artikelen in dezelfde categorie. Enkele voorbeelden van de instellingen voor het blog lay-out formaat zijn: aantal artikelen, artikel kolommen, horizontale of verticale lay-out en het aantal extra links. Zie [[S:MyLanguage/Help30:Menus Menu Item Article Category Blog#Advanced Details Tab|het geavanceerde detail tabblad]] voor alles over dit menu-item.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_List|Menu's - Menu-item - Artikel categorie lijst]] || Wordt gebruikt om artikelen die tot een bepaalde categorie horen in een lijst weergave.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Create|Menu's - Menu-item - Artikel aanmaken]] || Geeft de mogelijkheid aan gebruikers om een artikel in te dienen. Normaliter is dit alleen beschikbaar voor gebruikers die ingelogd zijn op de website. Gebruikers moeten rechten hebben om artikelen aan te maken. Indien de maak-artikel pagina wordt getoond op de website, dan worden de voorbeeld-schermen getoond uit de volgende [[Special:MyLanguage/Help30:Menus_Menu_Item_Article_Create#Front_End_Screenshots|website schermafbeeldingen]] sectie.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Featured|Menu's - Menu-item - Speciale artikelen]] || Wordt gebruikt om alle artikelen te tonen die aangemerkt zijn als 'Speciaal'. Artikelen worden getoond in blog lay-out.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Single_Article|Menu's - Menu-item - Artikel - Een enkel artikel]] || Wordt gebruikt om één artikel op de website te tonen.
|}

<noinclude>
[[Category:Help screen 3.0/nl|Helpscherm 3.0]]
[[Category:Help screen 3.1/nl|Helpscherm 3.1]]
[[Category:Help screen 3.2/nl|Helpscherm 3.2]]
[[Category:Help screen 3.3/nl|Helpscherm 3.3]]
[[Category:Help screen 3.4/nl|Helpscherm 3.4]]
[[Category:Help screen 3.5/nl|Helpscherm 3.5]]
[[Category:Help screen 3.6/nl|Helpscherm 3.6]]
[[Category:Documentation Working Group/nl|Documentatie werkgroep]]
[[Category:Help screens/nl|Helpschermen]]
[[Category:Menu Item Manager Help Screens/nl|Menu-item helpschermen]]
[[Category:Menus Help Screens/nl|Menu helpschermen]]
</noinclude>

Translations:Help36:Menus Menu Item Article Archived/5/nl

2017-03-31T12:32:19Z

Webcatsolutions:

* Klik op de Menu-itemtype Selecteren knop

Help310:Menus Menu Item Article Archived/nl

2017-03-31T12:26:31Z

Webcatsolutions:

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe te beginnen==
Om een nieuw 'Gearchiveerd artikel' menu-item te maken:
* Selecteer {{rarr|Menu's,[naam van het menu]}} uit het drop-down menu in de back-end van uw Joomla! installatie (bijvoorbeeld {{rarr|Menu's,Hoofdmenu}}).
* Klik op de knop Nieuw in de werkbalk om een nieuw menu-item te maken.
* Klik op de Menu-itemtype Selecteren knop [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] en klik dan op de Gearchiveerde artikelen link onder de Artikelen link.

Om een bestaand Gearchiveerd artikel menu-item te bewerken, klikt u op de titel in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menubeheer: Menu-items]].

==Beschrijving==
Wordt gebruikt om een lijst met gearchiveerde artikelen te tonen. De lijst met gearchiveerde artikelen kan worden getoond op datum, gefilterd en met de introductietekst zoals hieronder.

==Schermafbeelding==
[[Image:Help30-Menus-Menu-Item-Article-Archived-screen-nl.png|800px]]

Gearchiveerde artikelen worden niet meer gepubliceerd maar worden nog steeds op de site opgeslagen. Artikelen worden gearchiveerd met behulp met het [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]] scherm. Let op dat artikelen gekoppeld aan de "Niet gecategoriseerd" categorie niet getoond wordt in de lijst met gearchiveerde artikelen.

==Gegevens==
===Gegevens Tab===
====Verplichte instellingen====
Het gearchiveerde artikelen menu-item heeft de volgende verplichte instellingen:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu/nl}}

===Geavanceerde details tabblad===
====Archief opties====
De gearchiveerde artikelen weergave heeft de volgende archief opties, zoals hieronder getoond.
:[[Image:Help30-Menus-Menu-Article-Archived-archive-options-subscreen-nl.png]]
*'''Artikel volgorde.''' De volgorde van artikelen in deze weergave. De volgende opties zijn beschikbaar.
** ''Oudste eerst:'' Artikelen worden getoond met de oudste als eerste en eindigen met de nieuwste.
** ''Meest recente eerst:'' Artikelen worden getoond te beginnen met de nieuwste en eindigend met de oudste.
** ''Titel alfabetisch:'' Artikelen worden op titel alfabetisch gesorteerd getoond (A to Z)
** ''Titel alfabetisch omgekeerd:'' Artikelen worden getoond op de titel in omgekeerd alfabetische volgorde (Z tot A)
** ''Author Alphabetical:'' Articles are displayed by Author in alphabetical order (A to Z)
** ''Author Reverse Alphabetical:'' Articles are displayed by Author in reverse alphabetical order (Z to A)
** ''Meeste hits:'' Artikelen worden getoond op het aantal weergaven door het aantal hits, te beginnen met de meeste hits en eindigen met de minste hits.
** ''Minste hits:'' Artikelen worden getoond door het aantal hits, te beginnen met de minste hits en eindigend met de meeste hits.
** ''Volgorde:'' Artikelen worden gesorteerd volgens de Volgorde kolom opgegeven in Artikelbeheer.
{{Chunk30:colheader|Date for Ordering/nl}}
{{Chunk30:colheader|No Articles to List/nl}}
*'''Filterveld.''' (Gebruik algemeen/Verberg/Toon) Of een filterveld getoond moet worden voor een lijst met artikelen. Indien verborgen, wordt er geen filterveld getoond. Anders wordt het filterveld getoond volgens de algemeen instellingen.
*'''Limiet introtekst.''' Het maximum aantal tekens dat in de introtekst getoond moet worden. Indien de introtekst langer is als deze waarde dan wordt het afgekapt op deze lengte.

====Artikel opties====
De Gearchiveerde artikelen optie heeft de volgende opties, zoals hieronder getoond. Deze opties bepalen hoe artikelen getoond worden op de website.
:[[Image:Help30-Menus-Menu-Item-Article-Single-Article-options-modal-article-options-tab-nl.png]]

Let op dat de opties "'''Gebruik algemeen'''" bevatten. Indien dit geselecteerd is, dan worden de instellingen van de [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer opties]] gebruikt.
{{Chunk30:colheader|Show Intro Text/nl}}
{{Chunk30:colheader|Position of Article Info/nl}}
*'''Article Info Title.''' Displays the 'Article Info' title on top of the article information block.
{{Chunk30:colheader|Show Category/nl}}
{{Chunk30:colheader|Link Category/nl}}
{{Chunk30:colheader|Show Parent/nl}}
{{Chunk30:colheader|Link Parent/nl}}
{{Chunk30:colheader|Linked Titles/nl}}
{{Chunk30:colheader|Show Author/nl}}
{{Chunk30:colheader|Link Author/nl}}
{{Chunk30:colheader|Show Create Date/nl}}
{{Chunk30:colheader|Show Modify Date/nl}}
{{Chunk30:colheader|Show Publish Date/nl}}
{{Chunk30:colheader|Show Navigation/nl}}
{{Chunk30:colheader|Show Hits/nl}}

===Algemene opties===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu-item bewerken]] onder de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Gegevens]]''' voor hulp bij velden die voor alle menu items gelijk zijn, hieronder vallen:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Linktype opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Page Display Options|Paginaweergave opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Metadata Options|Metadata opties]]'''

===Moduletoewijzing tab===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu item bewerken]] voor hulp met betrekking tot de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Moduletoewijzing]]''' velden.

==Werkbalk==
Aan de bovenkant links ziet u de werkbalk:

[[Image:Help30-Save-SaveClose-SaveNew-SaveCopy-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

==Snelle Tips==
* De gearchiveerde artikelen weergave geeft u de mogelijkheid oude of verlopen artikelen te benaderen die u niet geheel van de website wilt verwijderen.
* Indien u oude artikelen wilt zien een categorie blog of lijst, maak dan een categorie aan voor ouder artikelen en verplaats de artikelen naar deze categorie (in plaats van de status te wijzigen naar gearchiveerd).

==Verwante informatie==
* Artikelen worden gearchiveerd met behulp van [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]].

{| class="wikitable"
|-
! Verwante helpschermen !! Beschrijving
|-
| [[S:MyLanguage/Help36:Components_Article_Manager_Options|Component artikelbeheer opties]] || Wordt gebruikt om de algemene standaards voor menu-items die artikelen tonen in te stellen. Deze standaard waarden worden gebruikt als "Gebruik algemeen" wordt geselecteerd als optie in een artikel menu-item. Om bijvoorbeeld de 'Aanmaak datum' te tonen bij een artikel in uw artikel menu-items, zet die optie dan hier op "Toon" en het wordt de standaard waarde. U hoeft geen van deze opties in te stellen. Uw Joomla site zal met de standaard instellingen werken.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager|Inhoud artikelbeheer]] || Artikelbeheer wordt gebruikt voor het vinden, markeren, toevoegen en bewerken van artikelen. Zie [[Special:MyLanguage/Help30:Content_Article_Manager#Toolbar|Werkbalk]] hieronder voor een gedetailleerde lijst van alle functies.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager_Edit|Inhoud artikelbeheer bewerken]] || Dit is het beheergedeelte scherm waar u artikelen kunt toevoegen en bewerken. Hetzelfde scherm wordt gebruikt voor het toevoegen van nieuwe artikelen en het bewerken van een bestaand artikel. U kunt ook de sectie en categorie van een artikel selecteren en aangeven of een artikel al dan niet gepubliceerd wordt en of het op de voorpagina moet worden getoond.
De artikelinhoud wordt bewerkt met de standaard tekstverwerker die gekozen wordt in [[Special:MyLanguage/Help30:Users_User_Manager_Edit|Gebruikersbeheer - Nieuw/Bewerk]]. De standaard Joomla! tekstverwerker heet TinyMCE.
Een aantal parameters kunnen ingesteld worden voor het artikel. Metadata kunnen ook opgegeven worden.
|-
| [[S:MyLanguage/Help36:Content_Featured_Articles|Inhoud speciale artikelen]] || Wordt gebruikt om te bepalen welk 'speciale artikel' getoond worden op de voorpagina en in welke volgorde ze worden getoond. De voorpagina is vaak de startpagina van een website, maar het kan iedere pagina op de site zijn. De voorpagina wordt aangemaakt met een menu-item met het 'Speciale artikelen' menu-itemtype.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Categories|Menu's - Menu-item - Artikel categorieën]] || Wordt gebruikt om een lijst met categorieën te tonen. Categorieën worden getoond in een hiërarchische lijst, zoals hieronder getoond. Afhankelijk van de geselecteerde opties voor de lay-out, kunt u op een categorietitel drukken om de artikelen in die categorie te tonen.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_Blog|Menu's - Menu-item - Artikel categorie blog]] || Wordt gebruikt om artikelen in een bepaalde categorie in blog lay-out te tonen. Regelt de introductie ofwel het leidende artikel, aanvullende artikelen met intro tekst en extra links naar meer artikelen in dezelfde categorie. Enkele voorbeelden van de instellingen voor het blog lay-out formaat zijn: aantal artikelen, artikel kolommen, horizontale of verticale lay-out en het aantal extra links. Zie [[S:MyLanguage/Help30:Menus Menu Item Article Category Blog#Advanced Details Tab|het geavanceerde detail tabblad]] voor alles over dit menu-item.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_List|Menu's - Menu-item - Artikel categorie lijst]] || Wordt gebruikt om artikelen die tot een bepaalde categorie horen in een lijst weergave.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Create|Menu's - Menu-item - Artikel aanmaken]] || Geeft de mogelijkheid aan gebruikers om een artikel in te dienen. Normaliter is dit alleen beschikbaar voor gebruikers die ingelogd zijn op de website. Gebruikers moeten rechten hebben om artikelen aan te maken. Indien de maak-artikel pagina wordt getoond op de website, dan worden de voorbeeld-schermen getoond uit de volgende [[Special:MyLanguage/Help30:Menus_Menu_Item_Article_Create#Front_End_Screenshots|website schermafbeeldingen]] sectie.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Featured|Menu's - Menu-item - Speciale artikelen]] || Wordt gebruikt om alle artikelen te tonen die aangemerkt zijn als 'Speciaal'. Artikelen worden getoond in blog lay-out.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Single_Article|Menu's - Menu-item - Artikel - Een enkel artikel]] || Wordt gebruikt om één artikel op de website te tonen.
|}

<noinclude>
[[Category:Help screen 3.0/nl|Helpscherm 3.0]]
[[Category:Help screen 3.1/nl|Helpscherm 3.1]]
[[Category:Help screen 3.2/nl|Helpscherm 3.2]]
[[Category:Help screen 3.3/nl|Helpscherm 3.3]]
[[Category:Help screen 3.4/nl|Helpscherm 3.4]]
[[Category:Help screen 3.5/nl|Helpscherm 3.5]]
[[Category:Help screen 3.6/nl|Helpscherm 3.6]]
[[Category:Documentation Working Group/nl|Documentatie werkgroep]]
[[Category:Help screens/nl|Helpschermen]]
[[Category:Menu Item Manager Help Screens/nl|Menu-item helpschermen]]
[[Category:Menus Help Screens/nl|Menu helpschermen]]
</noinclude>

Translations:Help36:Menus Menu Item Article Archived/5/nl

2017-03-31T12:26:30Z

Webcatsolutions:

* Klik op de Menu-itemtype Selecteren knop [[File:Help30-Menu-Item-Type-Select-Button-nl.png]]

Help310:Menus Menu Item Article Archived/nl

2017-03-31T12:25:19Z

Webcatsolutions: Created page with "nl"

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe te beginnen==
Om een nieuw 'Gearchiveerd artikel' menu-item te maken:
* Selecteer {{rarr|Menu's,[naam van het menu]}} uit het drop-down menu in de back-end van uw Joomla! installatie (bijvoorbeeld {{rarr|Menu's,Hoofdmenu}}).
* Klik op de knop Nieuw in de werkbalk om een nieuw menu-item te maken.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] en klik dan op de Gearchiveerde artikelen link onder de Artikelen link.

Om een bestaand Gearchiveerd artikel menu-item te bewerken, klikt u op de titel in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menubeheer: Menu-items]].

==Beschrijving==
Wordt gebruikt om een lijst met gearchiveerde artikelen te tonen. De lijst met gearchiveerde artikelen kan worden getoond op datum, gefilterd en met de introductietekst zoals hieronder.

==Schermafbeelding==
[[Image:Help30-Menus-Menu-Item-Article-Archived-screen-nl.png|800px]]

Gearchiveerde artikelen worden niet meer gepubliceerd maar worden nog steeds op de site opgeslagen. Artikelen worden gearchiveerd met behulp met het [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]] scherm. Let op dat artikelen gekoppeld aan de "Niet gecategoriseerd" categorie niet getoond wordt in de lijst met gearchiveerde artikelen.

==Gegevens==
===Gegevens Tab===
====Verplichte instellingen====
Het gearchiveerde artikelen menu-item heeft de volgende verplichte instellingen:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu/nl}}

===Geavanceerde details tabblad===
====Archief opties====
De gearchiveerde artikelen weergave heeft de volgende archief opties, zoals hieronder getoond.
:[[Image:Help30-Menus-Menu-Article-Archived-archive-options-subscreen-nl.png]]
*'''Artikel volgorde.''' De volgorde van artikelen in deze weergave. De volgende opties zijn beschikbaar.
** ''Oudste eerst:'' Artikelen worden getoond met de oudste als eerste en eindigen met de nieuwste.
** ''Meest recente eerst:'' Artikelen worden getoond te beginnen met de nieuwste en eindigend met de oudste.
** ''Titel alfabetisch:'' Artikelen worden op titel alfabetisch gesorteerd getoond (A to Z)
** ''Titel alfabetisch omgekeerd:'' Artikelen worden getoond op de titel in omgekeerd alfabetische volgorde (Z tot A)
** ''Author Alphabetical:'' Articles are displayed by Author in alphabetical order (A to Z)
** ''Author Reverse Alphabetical:'' Articles are displayed by Author in reverse alphabetical order (Z to A)
** ''Meeste hits:'' Artikelen worden getoond op het aantal weergaven door het aantal hits, te beginnen met de meeste hits en eindigen met de minste hits.
** ''Minste hits:'' Artikelen worden getoond door het aantal hits, te beginnen met de minste hits en eindigend met de meeste hits.
** ''Volgorde:'' Artikelen worden gesorteerd volgens de Volgorde kolom opgegeven in Artikelbeheer.
{{Chunk30:colheader|Date for Ordering/nl}}
{{Chunk30:colheader|No Articles to List/nl}}
*'''Filterveld.''' (Gebruik algemeen/Verberg/Toon) Of een filterveld getoond moet worden voor een lijst met artikelen. Indien verborgen, wordt er geen filterveld getoond. Anders wordt het filterveld getoond volgens de algemeen instellingen.
*'''Limiet introtekst.''' Het maximum aantal tekens dat in de introtekst getoond moet worden. Indien de introtekst langer is als deze waarde dan wordt het afgekapt op deze lengte.

====Artikel opties====
De Gearchiveerde artikelen optie heeft de volgende opties, zoals hieronder getoond. Deze opties bepalen hoe artikelen getoond worden op de website.
:[[Image:Help30-Menus-Menu-Item-Article-Single-Article-options-modal-article-options-tab-nl.png]]

Let op dat de opties "'''Gebruik algemeen'''" bevatten. Indien dit geselecteerd is, dan worden de instellingen van de [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer opties]] gebruikt.
{{Chunk30:colheader|Show Intro Text/nl}}
{{Chunk30:colheader|Position of Article Info/nl}}
*'''Article Info Title.''' Displays the 'Article Info' title on top of the article information block.
{{Chunk30:colheader|Show Category/nl}}
{{Chunk30:colheader|Link Category/nl}}
{{Chunk30:colheader|Show Parent/nl}}
{{Chunk30:colheader|Link Parent/nl}}
{{Chunk30:colheader|Linked Titles/nl}}
{{Chunk30:colheader|Show Author/nl}}
{{Chunk30:colheader|Link Author/nl}}
{{Chunk30:colheader|Show Create Date/nl}}
{{Chunk30:colheader|Show Modify Date/nl}}
{{Chunk30:colheader|Show Publish Date/nl}}
{{Chunk30:colheader|Show Navigation/nl}}
{{Chunk30:colheader|Show Hits/nl}}

===Algemene opties===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu-item bewerken]] onder de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Gegevens]]''' voor hulp bij velden die voor alle menu items gelijk zijn, hieronder vallen:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Linktype opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Page Display Options|Paginaweergave opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Metadata Options|Metadata opties]]'''

===Moduletoewijzing tab===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu item bewerken]] voor hulp met betrekking tot de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Moduletoewijzing]]''' velden.

==Werkbalk==
Aan de bovenkant links ziet u de werkbalk:

[[Image:Help30-Save-SaveClose-SaveNew-SaveCopy-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

==Snelle Tips==
* De gearchiveerde artikelen weergave geeft u de mogelijkheid oude of verlopen artikelen te benaderen die u niet geheel van de website wilt verwijderen.
* Indien u oude artikelen wilt zien een categorie blog of lijst, maak dan een categorie aan voor ouder artikelen en verplaats de artikelen naar deze categorie (in plaats van de status te wijzigen naar gearchiveerd).

==Verwante informatie==
* Artikelen worden gearchiveerd met behulp van [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]].

{| class="wikitable"
|-
! Verwante helpschermen !! Beschrijving
|-
| [[S:MyLanguage/Help36:Components_Article_Manager_Options|Component artikelbeheer opties]] || Wordt gebruikt om de algemene standaards voor menu-items die artikelen tonen in te stellen. Deze standaard waarden worden gebruikt als "Gebruik algemeen" wordt geselecteerd als optie in een artikel menu-item. Om bijvoorbeeld de 'Aanmaak datum' te tonen bij een artikel in uw artikel menu-items, zet die optie dan hier op "Toon" en het wordt de standaard waarde. U hoeft geen van deze opties in te stellen. Uw Joomla site zal met de standaard instellingen werken.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager|Inhoud artikelbeheer]] || Artikelbeheer wordt gebruikt voor het vinden, markeren, toevoegen en bewerken van artikelen. Zie [[Special:MyLanguage/Help30:Content_Article_Manager#Toolbar|Werkbalk]] hieronder voor een gedetailleerde lijst van alle functies.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager_Edit|Inhoud artikelbeheer bewerken]] || Dit is het beheergedeelte scherm waar u artikelen kunt toevoegen en bewerken. Hetzelfde scherm wordt gebruikt voor het toevoegen van nieuwe artikelen en het bewerken van een bestaand artikel. U kunt ook de sectie en categorie van een artikel selecteren en aangeven of een artikel al dan niet gepubliceerd wordt en of het op de voorpagina moet worden getoond.
De artikelinhoud wordt bewerkt met de standaard tekstverwerker die gekozen wordt in [[Special:MyLanguage/Help30:Users_User_Manager_Edit|Gebruikersbeheer - Nieuw/Bewerk]]. De standaard Joomla! tekstverwerker heet TinyMCE.
Een aantal parameters kunnen ingesteld worden voor het artikel. Metadata kunnen ook opgegeven worden.
|-
| [[S:MyLanguage/Help36:Content_Featured_Articles|Inhoud speciale artikelen]] || Wordt gebruikt om te bepalen welk 'speciale artikel' getoond worden op de voorpagina en in welke volgorde ze worden getoond. De voorpagina is vaak de startpagina van een website, maar het kan iedere pagina op de site zijn. De voorpagina wordt aangemaakt met een menu-item met het 'Speciale artikelen' menu-itemtype.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Categories|Menu's - Menu-item - Artikel categorieën]] || Wordt gebruikt om een lijst met categorieën te tonen. Categorieën worden getoond in een hiërarchische lijst, zoals hieronder getoond. Afhankelijk van de geselecteerde opties voor de lay-out, kunt u op een categorietitel drukken om de artikelen in die categorie te tonen.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_Blog|Menu's - Menu-item - Artikel categorie blog]] || Wordt gebruikt om artikelen in een bepaalde categorie in blog lay-out te tonen. Regelt de introductie ofwel het leidende artikel, aanvullende artikelen met intro tekst en extra links naar meer artikelen in dezelfde categorie. Enkele voorbeelden van de instellingen voor het blog lay-out formaat zijn: aantal artikelen, artikel kolommen, horizontale of verticale lay-out en het aantal extra links. Zie [[S:MyLanguage/Help30:Menus Menu Item Article Category Blog#Advanced Details Tab|het geavanceerde detail tabblad]] voor alles over dit menu-item.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_List|Menu's - Menu-item - Artikel categorie lijst]] || Wordt gebruikt om artikelen die tot een bepaalde categorie horen in een lijst weergave.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Create|Menu's - Menu-item - Artikel aanmaken]] || Geeft de mogelijkheid aan gebruikers om een artikel in te dienen. Normaliter is dit alleen beschikbaar voor gebruikers die ingelogd zijn op de website. Gebruikers moeten rechten hebben om artikelen aan te maken. Indien de maak-artikel pagina wordt getoond op de website, dan worden de voorbeeld-schermen getoond uit de volgende [[Special:MyLanguage/Help30:Menus_Menu_Item_Article_Create#Front_End_Screenshots|website schermafbeeldingen]] sectie.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Featured|Menu's - Menu-item - Speciale artikelen]] || Wordt gebruikt om alle artikelen te tonen die aangemerkt zijn als 'Speciaal'. Artikelen worden getoond in blog lay-out.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Single_Article|Menu's - Menu-item - Artikel - Een enkel artikel]] || Wordt gebruikt om één artikel op de website te tonen.
|}

<noinclude>
[[Category:Help screen 3.0/nl|Helpscherm 3.0]]
[[Category:Help screen 3.1/nl|Helpscherm 3.1]]
[[Category:Help screen 3.2/nl|Helpscherm 3.2]]
[[Category:Help screen 3.3/nl|Helpscherm 3.3]]
[[Category:Help screen 3.4/nl|Helpscherm 3.4]]
[[Category:Help screen 3.5/nl|Helpscherm 3.5]]
[[Category:Help screen 3.6/nl|Helpscherm 3.6]]
[[Category:Documentation Working Group/nl|Documentatie werkgroep]]
[[Category:Help screens/nl|Helpschermen]]
[[Category:Menu Item Manager Help Screens/nl|Menu-item helpschermen]]
[[Category:Menus Help Screens/nl|Menu helpschermen]]
</noinclude>

Translations:Help36:Menus Menu Item Article Archived/104/nl

2017-03-31T12:25:19Z

Webcatsolutions: Created page with "nl"

Help310:Menus Menu Item Article Archived/nl

2017-03-31T12:25:15Z

Webcatsolutions: Created page with "en klik dan op de Gearchiveerde artikelen link onder de Artikelen link."

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe te beginnen==
Om een nieuw 'Gearchiveerd artikel' menu-item te maken:
* Selecteer {{rarr|Menu's,[naam van het menu]}} uit het drop-down menu in de back-end van uw Joomla! installatie (bijvoorbeeld {{rarr|Menu's,Hoofdmenu}}).
* Klik op de knop Nieuw in de werkbalk om een nieuw menu-item te maken.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] en klik dan op de Gearchiveerde artikelen link onder de Artikelen link.

Om een bestaand Gearchiveerd artikel menu-item te bewerken, klikt u op de titel in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menubeheer: Menu-items]].

==Beschrijving==
Wordt gebruikt om een lijst met gearchiveerde artikelen te tonen. De lijst met gearchiveerde artikelen kan worden getoond op datum, gefilterd en met de introductietekst zoals hieronder.

==Schermafbeelding==
[[Image:Help30-Menus-Menu-Item-Article-Archived-screen-nl.png|800px]]

Gearchiveerde artikelen worden niet meer gepubliceerd maar worden nog steeds op de site opgeslagen. Artikelen worden gearchiveerd met behulp met het [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]] scherm. Let op dat artikelen gekoppeld aan de "Niet gecategoriseerd" categorie niet getoond wordt in de lijst met gearchiveerde artikelen.

==Gegevens==
===Gegevens Tab===
====Verplichte instellingen====
Het gearchiveerde artikelen menu-item heeft de volgende verplichte instellingen:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu/en}}

===Geavanceerde details tabblad===
====Archief opties====
De gearchiveerde artikelen weergave heeft de volgende archief opties, zoals hieronder getoond.
:[[Image:Help30-Menus-Menu-Article-Archived-archive-options-subscreen-nl.png]]
*'''Artikel volgorde.''' De volgorde van artikelen in deze weergave. De volgende opties zijn beschikbaar.
** ''Oudste eerst:'' Artikelen worden getoond met de oudste als eerste en eindigen met de nieuwste.
** ''Meest recente eerst:'' Artikelen worden getoond te beginnen met de nieuwste en eindigend met de oudste.
** ''Titel alfabetisch:'' Artikelen worden op titel alfabetisch gesorteerd getoond (A to Z)
** ''Titel alfabetisch omgekeerd:'' Artikelen worden getoond op de titel in omgekeerd alfabetische volgorde (Z tot A)
** ''Author Alphabetical:'' Articles are displayed by Author in alphabetical order (A to Z)
** ''Author Reverse Alphabetical:'' Articles are displayed by Author in reverse alphabetical order (Z to A)
** ''Meeste hits:'' Artikelen worden getoond op het aantal weergaven door het aantal hits, te beginnen met de meeste hits en eindigen met de minste hits.
** ''Minste hits:'' Artikelen worden getoond door het aantal hits, te beginnen met de minste hits en eindigend met de meeste hits.
** ''Volgorde:'' Artikelen worden gesorteerd volgens de Volgorde kolom opgegeven in Artikelbeheer.
{{Chunk30:colheader|Date for Ordering/nl}}
{{Chunk30:colheader|No Articles to List/nl}}
*'''Filterveld.''' (Gebruik algemeen/Verberg/Toon) Of een filterveld getoond moet worden voor een lijst met artikelen. Indien verborgen, wordt er geen filterveld getoond. Anders wordt het filterveld getoond volgens de algemeen instellingen.
*'''Limiet introtekst.''' Het maximum aantal tekens dat in de introtekst getoond moet worden. Indien de introtekst langer is als deze waarde dan wordt het afgekapt op deze lengte.

====Artikel opties====
De Gearchiveerde artikelen optie heeft de volgende opties, zoals hieronder getoond. Deze opties bepalen hoe artikelen getoond worden op de website.
:[[Image:Help30-Menus-Menu-Item-Article-Single-Article-options-modal-article-options-tab-nl.png]]

Let op dat de opties "'''Gebruik algemeen'''" bevatten. Indien dit geselecteerd is, dan worden de instellingen van de [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer opties]] gebruikt.
{{Chunk30:colheader|Show Intro Text/nl}}
{{Chunk30:colheader|Position of Article Info/nl}}
*'''Article Info Title.''' Displays the 'Article Info' title on top of the article information block.
{{Chunk30:colheader|Show Category/nl}}
{{Chunk30:colheader|Link Category/nl}}
{{Chunk30:colheader|Show Parent/nl}}
{{Chunk30:colheader|Link Parent/nl}}
{{Chunk30:colheader|Linked Titles/nl}}
{{Chunk30:colheader|Show Author/nl}}
{{Chunk30:colheader|Link Author/nl}}
{{Chunk30:colheader|Show Create Date/nl}}
{{Chunk30:colheader|Show Modify Date/nl}}
{{Chunk30:colheader|Show Publish Date/nl}}
{{Chunk30:colheader|Show Navigation/nl}}
{{Chunk30:colheader|Show Hits/nl}}

===Algemene opties===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu-item bewerken]] onder de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Gegevens]]''' voor hulp bij velden die voor alle menu items gelijk zijn, hieronder vallen:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Linktype opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Page Display Options|Paginaweergave opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Metadata Options|Metadata opties]]'''

===Moduletoewijzing tab===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu item bewerken]] voor hulp met betrekking tot de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Moduletoewijzing]]''' velden.

==Werkbalk==
Aan de bovenkant links ziet u de werkbalk:

[[Image:Help30-Save-SaveClose-SaveNew-SaveCopy-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

==Snelle Tips==
* De gearchiveerde artikelen weergave geeft u de mogelijkheid oude of verlopen artikelen te benaderen die u niet geheel van de website wilt verwijderen.
* Indien u oude artikelen wilt zien een categorie blog of lijst, maak dan een categorie aan voor ouder artikelen en verplaats de artikelen naar deze categorie (in plaats van de status te wijzigen naar gearchiveerd).

==Verwante informatie==
* Artikelen worden gearchiveerd met behulp van [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]].

{| class="wikitable"
|-
! Verwante helpschermen !! Beschrijving
|-
| [[S:MyLanguage/Help36:Components_Article_Manager_Options|Component artikelbeheer opties]] || Wordt gebruikt om de algemene standaards voor menu-items die artikelen tonen in te stellen. Deze standaard waarden worden gebruikt als "Gebruik algemeen" wordt geselecteerd als optie in een artikel menu-item. Om bijvoorbeeld de 'Aanmaak datum' te tonen bij een artikel in uw artikel menu-items, zet die optie dan hier op "Toon" en het wordt de standaard waarde. U hoeft geen van deze opties in te stellen. Uw Joomla site zal met de standaard instellingen werken.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager|Inhoud artikelbeheer]] || Artikelbeheer wordt gebruikt voor het vinden, markeren, toevoegen en bewerken van artikelen. Zie [[Special:MyLanguage/Help30:Content_Article_Manager#Toolbar|Werkbalk]] hieronder voor een gedetailleerde lijst van alle functies.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager_Edit|Inhoud artikelbeheer bewerken]] || Dit is het beheergedeelte scherm waar u artikelen kunt toevoegen en bewerken. Hetzelfde scherm wordt gebruikt voor het toevoegen van nieuwe artikelen en het bewerken van een bestaand artikel. U kunt ook de sectie en categorie van een artikel selecteren en aangeven of een artikel al dan niet gepubliceerd wordt en of het op de voorpagina moet worden getoond.
De artikelinhoud wordt bewerkt met de standaard tekstverwerker die gekozen wordt in [[Special:MyLanguage/Help30:Users_User_Manager_Edit|Gebruikersbeheer - Nieuw/Bewerk]]. De standaard Joomla! tekstverwerker heet TinyMCE.
Een aantal parameters kunnen ingesteld worden voor het artikel. Metadata kunnen ook opgegeven worden.
|-
| [[S:MyLanguage/Help36:Content_Featured_Articles|Inhoud speciale artikelen]] || Wordt gebruikt om te bepalen welk 'speciale artikel' getoond worden op de voorpagina en in welke volgorde ze worden getoond. De voorpagina is vaak de startpagina van een website, maar het kan iedere pagina op de site zijn. De voorpagina wordt aangemaakt met een menu-item met het 'Speciale artikelen' menu-itemtype.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Categories|Menu's - Menu-item - Artikel categorieën]] || Wordt gebruikt om een lijst met categorieën te tonen. Categorieën worden getoond in een hiërarchische lijst, zoals hieronder getoond. Afhankelijk van de geselecteerde opties voor de lay-out, kunt u op een categorietitel drukken om de artikelen in die categorie te tonen.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_Blog|Menu's - Menu-item - Artikel categorie blog]] || Wordt gebruikt om artikelen in een bepaalde categorie in blog lay-out te tonen. Regelt de introductie ofwel het leidende artikel, aanvullende artikelen met intro tekst en extra links naar meer artikelen in dezelfde categorie. Enkele voorbeelden van de instellingen voor het blog lay-out formaat zijn: aantal artikelen, artikel kolommen, horizontale of verticale lay-out en het aantal extra links. Zie [[S:MyLanguage/Help30:Menus Menu Item Article Category Blog#Advanced Details Tab|het geavanceerde detail tabblad]] voor alles over dit menu-item.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_List|Menu's - Menu-item - Artikel categorie lijst]] || Wordt gebruikt om artikelen die tot een bepaalde categorie horen in een lijst weergave.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Create|Menu's - Menu-item - Artikel aanmaken]] || Geeft de mogelijkheid aan gebruikers om een artikel in te dienen. Normaliter is dit alleen beschikbaar voor gebruikers die ingelogd zijn op de website. Gebruikers moeten rechten hebben om artikelen aan te maken. Indien de maak-artikel pagina wordt getoond op de website, dan worden de voorbeeld-schermen getoond uit de volgende [[Special:MyLanguage/Help30:Menus_Menu_Item_Article_Create#Front_End_Screenshots|website schermafbeeldingen]] sectie.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Featured|Menu's - Menu-item - Speciale artikelen]] || Wordt gebruikt om alle artikelen te tonen die aangemerkt zijn als 'Speciaal'. Artikelen worden getoond in blog lay-out.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Single_Article|Menu's - Menu-item - Artikel - Een enkel artikel]] || Wordt gebruikt om één artikel op de website te tonen.
|}

<noinclude>
[[Category:Help screen 3.0/nl|Helpscherm 3.0]]
[[Category:Help screen 3.1/nl|Helpscherm 3.1]]
[[Category:Help screen 3.2/nl|Helpscherm 3.2]]
[[Category:Help screen 3.3/nl|Helpscherm 3.3]]
[[Category:Help screen 3.4/nl|Helpscherm 3.4]]
[[Category:Help screen 3.5/nl|Helpscherm 3.5]]
[[Category:Help screen 3.6/nl|Helpscherm 3.6]]
[[Category:Documentation Working Group/nl|Documentatie werkgroep]]
[[Category:Help screens/nl|Helpschermen]]
[[Category:Menu Item Manager Help Screens/nl|Menu-item helpschermen]]
[[Category:Menus Help Screens/nl|Menu helpschermen]]
</noinclude>

Translations:Help36:Menus Menu Item Article Archived/103/nl

2017-03-31T12:25:15Z

Webcatsolutions: Created page with "en klik dan op de Gearchiveerde artikelen link onder de Artikelen link."

en klik dan op de Gearchiveerde artikelen link onder de Artikelen link.

Help310:Menus Menu Item Article Archived/nl

2017-03-31T12:22:00Z

Webcatsolutions: Created page with "nl"

<noinclude><languages /></noinclude>
{{RightTOC}}
==Hoe te beginnen==
Om een nieuw 'Gearchiveerd artikel' menu-item te maken:
* Selecteer {{rarr|Menu's,[naam van het menu]}} uit het drop-down menu in de back-end van uw Joomla! installatie (bijvoorbeeld {{rarr|Menu's,Hoofdmenu}}).
* Klik op de knop Nieuw in de werkbalk om een nieuw menu-item te maken.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button-nl.png]] and then click the Archived Articles link under Articles link.

Om een bestaand Gearchiveerd artikel menu-item te bewerken, klikt u op de titel in [[S:MyLanguage/Help30:Menus_Menu_Item_Manager|Menubeheer: Menu-items]].

==Beschrijving==
Wordt gebruikt om een lijst met gearchiveerde artikelen te tonen. De lijst met gearchiveerde artikelen kan worden getoond op datum, gefilterd en met de introductietekst zoals hieronder.

==Schermafbeelding==
[[Image:Help30-Menus-Menu-Item-Article-Archived-screen-nl.png|800px]]

Gearchiveerde artikelen worden niet meer gepubliceerd maar worden nog steeds op de site opgeslagen. Artikelen worden gearchiveerd met behulp met het [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]] scherm. Let op dat artikelen gekoppeld aan de "Niet gecategoriseerd" categorie niet getoond wordt in de lijst met gearchiveerde artikelen.

==Gegevens==
===Gegevens Tab===
====Verplichte instellingen====
Het gearchiveerde artikelen menu-item heeft de volgende verplichte instellingen:
{{chunk30:colheader|Menu Title/nl}}
{{chunk30:colheader|Menu Item Type/nl}}
{{chunk30:colheader|Menu/en}}

===Geavanceerde details tabblad===
====Archief opties====
De gearchiveerde artikelen weergave heeft de volgende archief opties, zoals hieronder getoond.
:[[Image:Help30-Menus-Menu-Article-Archived-archive-options-subscreen-nl.png]]
*'''Artikel volgorde.''' De volgorde van artikelen in deze weergave. De volgende opties zijn beschikbaar.
** ''Oudste eerst:'' Artikelen worden getoond met de oudste als eerste en eindigen met de nieuwste.
** ''Meest recente eerst:'' Artikelen worden getoond te beginnen met de nieuwste en eindigend met de oudste.
** ''Titel alfabetisch:'' Artikelen worden op titel alfabetisch gesorteerd getoond (A to Z)
** ''Titel alfabetisch omgekeerd:'' Artikelen worden getoond op de titel in omgekeerd alfabetische volgorde (Z tot A)
** ''Author Alphabetical:'' Articles are displayed by Author in alphabetical order (A to Z)
** ''Author Reverse Alphabetical:'' Articles are displayed by Author in reverse alphabetical order (Z to A)
** ''Meeste hits:'' Artikelen worden getoond op het aantal weergaven door het aantal hits, te beginnen met de meeste hits en eindigen met de minste hits.
** ''Minste hits:'' Artikelen worden getoond door het aantal hits, te beginnen met de minste hits en eindigend met de meeste hits.
** ''Volgorde:'' Artikelen worden gesorteerd volgens de Volgorde kolom opgegeven in Artikelbeheer.
{{Chunk30:colheader|Date for Ordering/nl}}
{{Chunk30:colheader|No Articles to List/nl}}
*'''Filterveld.''' (Gebruik algemeen/Verberg/Toon) Of een filterveld getoond moet worden voor een lijst met artikelen. Indien verborgen, wordt er geen filterveld getoond. Anders wordt het filterveld getoond volgens de algemeen instellingen.
*'''Limiet introtekst.''' Het maximum aantal tekens dat in de introtekst getoond moet worden. Indien de introtekst langer is als deze waarde dan wordt het afgekapt op deze lengte.

====Artikel opties====
De Gearchiveerde artikelen optie heeft de volgende opties, zoals hieronder getoond. Deze opties bepalen hoe artikelen getoond worden op de website.
:[[Image:Help30-Menus-Menu-Item-Article-Single-Article-options-modal-article-options-tab-nl.png]]

Let op dat de opties "'''Gebruik algemeen'''" bevatten. Indien dit geselecteerd is, dan worden de instellingen van de [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer opties]] gebruikt.
{{Chunk30:colheader|Show Intro Text/nl}}
{{Chunk30:colheader|Position of Article Info/nl}}
*'''Article Info Title.''' Displays the 'Article Info' title on top of the article information block.
{{Chunk30:colheader|Show Category/nl}}
{{Chunk30:colheader|Link Category/nl}}
{{Chunk30:colheader|Show Parent/nl}}
{{Chunk30:colheader|Link Parent/nl}}
{{Chunk30:colheader|Linked Titles/nl}}
{{Chunk30:colheader|Show Author/nl}}
{{Chunk30:colheader|Link Author/nl}}
{{Chunk30:colheader|Show Create Date/nl}}
{{Chunk30:colheader|Show Modify Date/nl}}
{{Chunk30:colheader|Show Publish Date/nl}}
{{Chunk30:colheader|Show Navigation/nl}}
{{Chunk30:colheader|Show Hits/nl}}

===Algemene opties===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu-item bewerken]] onder de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Advanced Details Tab|Gegevens]]''' voor hulp bij velden die voor alle menu items gelijk zijn, hieronder vallen:
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Linktype opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Page Display Options|Paginaweergave opties]]'''
*'''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Metadata Options|Metadata opties]]'''

===Moduletoewijzing tab===
Zie [[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit|Menu-item beheer: Menu item bewerken]] voor hulp met betrekking tot de '''[[S:MyLanguage/Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Moduletoewijzing]]''' velden.

==Werkbalk==
Aan de bovenkant links ziet u de werkbalk:

[[Image:Help30-Save-SaveClose-SaveNew-SaveCopy-Cancel-Help-toolbar-nl.png]]

De functies zijn:
{{Chunk30:Help_screen_toolbar_icon_Save/nl|menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy/nl|Menu-item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel/nl}}
{{Chunk30:Help_screen_toolbar_icon_Help/nl}}

==Snelle Tips==
* De gearchiveerde artikelen weergave geeft u de mogelijkheid oude of verlopen artikelen te benaderen die u niet geheel van de website wilt verwijderen.
* Indien u oude artikelen wilt zien een categorie blog of lijst, maak dan een categorie aan voor ouder artikelen en verplaats de artikelen naar deze categorie (in plaats van de status te wijzigen naar gearchiveerd).

==Verwante informatie==
* Artikelen worden gearchiveerd met behulp van [[S:MyLanguage/Help30:Content_Article_Manager|Artikelbeheer]].

{| class="wikitable"
|-
! Verwante helpschermen !! Beschrijving
|-
| [[S:MyLanguage/Help36:Components_Article_Manager_Options|Component artikelbeheer opties]] || Wordt gebruikt om de algemene standaards voor menu-items die artikelen tonen in te stellen. Deze standaard waarden worden gebruikt als "Gebruik algemeen" wordt geselecteerd als optie in een artikel menu-item. Om bijvoorbeeld de 'Aanmaak datum' te tonen bij een artikel in uw artikel menu-items, zet die optie dan hier op "Toon" en het wordt de standaard waarde. U hoeft geen van deze opties in te stellen. Uw Joomla site zal met de standaard instellingen werken.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager|Inhoud artikelbeheer]] || Artikelbeheer wordt gebruikt voor het vinden, markeren, toevoegen en bewerken van artikelen. Zie [[Special:MyLanguage/Help30:Content_Article_Manager#Toolbar|Werkbalk]] hieronder voor een gedetailleerde lijst van alle functies.
|-
| [[S:MyLanguage/Help36:Content_Article_Manager_Edit|Inhoud artikelbeheer bewerken]] || Dit is het beheergedeelte scherm waar u artikelen kunt toevoegen en bewerken. Hetzelfde scherm wordt gebruikt voor het toevoegen van nieuwe artikelen en het bewerken van een bestaand artikel. U kunt ook de sectie en categorie van een artikel selecteren en aangeven of een artikel al dan niet gepubliceerd wordt en of het op de voorpagina moet worden getoond.
De artikelinhoud wordt bewerkt met de standaard tekstverwerker die gekozen wordt in [[Special:MyLanguage/Help30:Users_User_Manager_Edit|Gebruikersbeheer - Nieuw/Bewerk]]. De standaard Joomla! tekstverwerker heet TinyMCE.
Een aantal parameters kunnen ingesteld worden voor het artikel. Metadata kunnen ook opgegeven worden.
|-
| [[S:MyLanguage/Help36:Content_Featured_Articles|Inhoud speciale artikelen]] || Wordt gebruikt om te bepalen welk 'speciale artikel' getoond worden op de voorpagina en in welke volgorde ze worden getoond. De voorpagina is vaak de startpagina van een website, maar het kan iedere pagina op de site zijn. De voorpagina wordt aangemaakt met een menu-item met het 'Speciale artikelen' menu-itemtype.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Categories|Menu's - Menu-item - Artikel categorieën]] || Wordt gebruikt om een lijst met categorieën te tonen. Categorieën worden getoond in een hiërarchische lijst, zoals hieronder getoond. Afhankelijk van de geselecteerde opties voor de lay-out, kunt u op een categorietitel drukken om de artikelen in die categorie te tonen.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_Blog|Menu's - Menu-item - Artikel categorie blog]] || Wordt gebruikt om artikelen in een bepaalde categorie in blog lay-out te tonen. Regelt de introductie ofwel het leidende artikel, aanvullende artikelen met intro tekst en extra links naar meer artikelen in dezelfde categorie. Enkele voorbeelden van de instellingen voor het blog lay-out formaat zijn: aantal artikelen, artikel kolommen, horizontale of verticale lay-out en het aantal extra links. Zie [[S:MyLanguage/Help30:Menus Menu Item Article Category Blog#Advanced Details Tab|het geavanceerde detail tabblad]] voor alles over dit menu-item.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Category_List|Menu's - Menu-item - Artikel categorie lijst]] || Wordt gebruikt om artikelen die tot een bepaalde categorie horen in een lijst weergave.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Create|Menu's - Menu-item - Artikel aanmaken]] || Geeft de mogelijkheid aan gebruikers om een artikel in te dienen. Normaliter is dit alleen beschikbaar voor gebruikers die ingelogd zijn op de website. Gebruikers moeten rechten hebben om artikelen aan te maken. Indien de maak-artikel pagina wordt getoond op de website, dan worden de voorbeeld-schermen getoond uit de volgende [[Special:MyLanguage/Help30:Menus_Menu_Item_Article_Create#Front_End_Screenshots|website schermafbeeldingen]] sectie.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Featured|Menu's - Menu-item - Speciale artikelen]] || Wordt gebruikt om alle artikelen te tonen die aangemerkt zijn als 'Speciaal'. Artikelen worden getoond in blog lay-out.
|-
| [[S:MyLanguage/Help36:Menus_Menu_Item_Article_Single_Article|Menu's - Menu-item - Artikel - Een enkel artikel]] || Wordt gebruikt om één artikel op de website te tonen.
|}

<noinclude>
[[Category:Help screen 3.0/nl|Helpscherm 3.0]]
[[Category:Help screen 3.1/nl|Helpscherm 3.1]]
[[Category:Help screen 3.2/nl|Helpscherm 3.2]]
[[Category:Help screen 3.3/nl|Helpscherm 3.3]]
[[Category:Help screen 3.4/nl|Helpscherm 3.4]]
[[Category:Help screen 3.5/nl|Helpscherm 3.5]]
[[Category:Help screen 3.6/nl|Helpscherm 3.6]]
[[Category:Documentation Working Group/nl|Documentatie werkgroep]]
[[Category:Help screens/nl|Helpschermen]]
[[Category:Menu Item Manager Help Screens/nl|Menu-item helpschermen]]
[[Category:Menus Help Screens/nl|Menu helpschermen]]
</noinclude>

Translations:Help36:Menus Menu Item Article Archived/102/nl

2017-03-31T12:22:00Z

Webcatsolutions: Created page with "nl"

Translations:Chunk30:Help-3x-add-user-note/Page display title/nl

2017-03-31T12:19:45Z

Webcatsolutions: Created page with "Help-Gebruikersnotitie toevoegen"

Help-Gebruikersnotitie toevoegen

Translations:Chunk30:Help-3x-add-user-note/1/nl

2017-03-31T12:19:00Z

Webcatsolutions: Created page with "en"

Chunk30:Help-3x-add-user-note/nl

2017-03-31T12:18:55Z

Webcatsolutions: Created page with "*'''Notitie:''' Voer de notitie in."

<noinclude><languages /></noinclude>
<noinclude>
==Screenshot==
</noinclude>
[[Image:help-3x-users-notes-en.png|800px|none]]

==Gegevens==
*'''Onderwerp:''' Het onderwerp van de notitie.
*'''Gebruiker:''' De gebruiker voor wie de notitie is. U kunt een bestaande gebruiker selecteren.
*'''Categorie:''' (''Ongecategoriseerd''). De categorie waar deze notitie aan toegewezen is.
*'''Status:''' (''Gepubliceerd''/''Gedepubliceerd''/''Verplaatst naar prullenbak''). Stel publicatiestatus in.
*'''Herzieningsdatum:''' De herzieningsdatum is een handmatig ingevoerde datum die u kunt gebruiken al naar gelang de manier waarop deze in uw workflow past. Voorbeelden hiervan zijn het veld vullen met een datum waarop u wilt dat een gebruiker wordt beoordeeld, of de meest recente datum waarop een gebruiker voor het laatst door u is beoordeeld.
*'''Notitie versie:''' Vul optioneel een notitie in voor deze versie van het item.
*'''Notitie:''' Voer de notitie in.

Translations:Chunk30:Help-3x-add-user-note/8/nl

2017-03-31T12:18:55Z

Webcatsolutions: Created page with "*'''Notitie:''' Voer de notitie in."

*'''Notitie:''' Voer de notitie in.

Chunk30:Help-3x-add-user-note/nl

2017-03-31T12:18:30Z

Webcatsolutions: Created page with "*'''Notitie versie:''' Vul optioneel een notitie in voor deze versie van het item."

Translations:Chunk30:Help-3x-add-user-note/7/nl

2017-03-31T12:18:29Z

Webcatsolutions: Created page with "*'''Notitie versie:''' Vul optioneel een notitie in voor deze versie van het item."

*'''Notitie versie:''' Vul optioneel een notitie in voor deze versie van het item.

Chunk30:Help-3x-add-user-note/nl

2017-03-31T12:17:41Z

Webcatsolutions: Created page with "*'''Herzieningsdatum:''' De herzieningsdatum is een handmatig ingevoerde datum die u kunt gebruiken al naar gelang de manier waarop deze in uw workflow past. Voorbeelden hierv..."

<noinclude><languages /></noinclude>
<noinclude>
==Screenshot==
</noinclude>
[[Image:help-3x-users-notes-en.png|800px|none]]

==Gegevens==
*'''Onderwerp:''' Het onderwerp van de notitie.
*'''Gebruiker:''' De gebruiker voor wie de notitie is. U kunt een bestaande gebruiker selecteren.
*'''Categorie:''' (''Ongecategoriseerd''). De categorie waar deze notitie aan toegewezen is.
*'''Status:''' (''Gepubliceerd''/''Gedepubliceerd''/''Verplaatst naar prullenbak''). Stel publicatiestatus in.
*'''Herzieningsdatum:''' De herzieningsdatum is een handmatig ingevoerde datum die u kunt gebruiken al naar gelang de manier waarop deze in uw workflow past. Voorbeelden hiervan zijn het veld vullen met een datum waarop u wilt dat een gebruiker wordt beoordeeld, of de meest recente datum waarop een gebruiker voor het laatst door u is beoordeeld.
*'''Version Note:''' Enter an optional note for this version of the item.
*'''Note:''' Enter the note.

Translations:Chunk30:Help-3x-add-user-note/6/nl

2017-03-31T12:17:41Z

*'''Herzieningsdatum:''' De herzieningsdatum is een handmatig ingevoerde datum die u kunt gebruiken al naar gelang de manier waarop deze in uw workflow past. Voorbeelden hiervan zijn het veld vullen met een datum waarop u wilt dat een gebruiker wordt beoordeeld, of de meest recente datum waarop een gebruiker voor het laatst door u is beoordeeld.

Chunk30:Help-3x-add-user-note/nl

2017-03-31T12:14:44Z

Webcatsolutions: Created page with "*'''Status:''' (''Gepubliceerd''/''Gedepubliceerd''/''Verplaatst naar prullenbak''). Stel publicatiestatus in."

<noinclude><languages /></noinclude>
<noinclude>
==Screenshot==
</noinclude>
[[Image:help-3x-users-notes-en.png|800px|none]]

==Gegevens==
*'''Onderwerp:''' Het onderwerp van de notitie.
*'''Gebruiker:''' De gebruiker voor wie de notitie is. U kunt een bestaande gebruiker selecteren.
*'''Categorie:''' (''Ongecategoriseerd''). De categorie waar deze notitie aan toegewezen is.
*'''Status:''' (''Gepubliceerd''/''Gedepubliceerd''/''Verplaatst naar prullenbak''). Stel publicatiestatus in.
*'''Review Date:''' Review date is a manually entered date you can use as fits in your workflow. Examples would be to put in a date that you want to review a user or the last date you reviewed the user.
*'''Version Note:''' Enter an optional note for this version of the item.
*'''Note:''' Enter the note.

Translations:Chunk30:Help-3x-add-user-note/5/nl

2017-03-31T12:14:44Z

Webcatsolutions: Created page with "*'''Status:''' (''Gepubliceerd''/''Gedepubliceerd''/''Verplaatst naar prullenbak''). Stel publicatiestatus in."

*'''Status:''' (''Gepubliceerd''/''Gedepubliceerd''/''Verplaatst naar prullenbak''). Stel publicatiestatus in.

Chunk30:Help-3x-add-user-note/nl

2017-03-31T12:14:38Z

Webcatsolutions: Created page with "*'''Categorie:''' (''Ongecategoriseerd''). De categorie waar deze notitie aan toegewezen is."

<noinclude><languages /></noinclude>
<noinclude>
==Screenshot==
</noinclude>
[[Image:help-3x-users-notes-en.png|800px|none]]

==Gegevens==
*'''Onderwerp:''' Het onderwerp van de notitie.
*'''Gebruiker:''' De gebruiker voor wie de notitie is. U kunt een bestaande gebruiker selecteren.
*'''Categorie:''' (''Ongecategoriseerd''). De categorie waar deze notitie aan toegewezen is.
*'''Status:''' (''Published''/''Unpublished''/''Archived''/''Trashed''). Set publication status.
*'''Review Date:''' Review date is a manually entered date you can use as fits in your workflow. Examples would be to put in a date that you want to review a user or the last date you reviewed the user.
*'''Version Note:''' Enter an optional note for this version of the item.
*'''Note:''' Enter the note.

Translations:Chunk30:Help-3x-add-user-note/4/nl

2017-03-31T12:14:37Z

Webcatsolutions: Created page with "*'''Categorie:''' (''Ongecategoriseerd''). De categorie waar deze notitie aan toegewezen is."

*'''Categorie:''' (''Ongecategoriseerd''). De categorie waar deze notitie aan toegewezen is.