diff --git a/source/hu/thoughts-support.txt b/source/hu/thoughts-support.txt index 300760a..547b89b 100644 --- a/source/hu/thoughts-support.txt +++ b/source/hu/thoughts-support.txt @@ -17,33 +17,18 @@ How to find support for issues faced while developing a site. ==== Where can you find support? -The Drupal project is open-source, so if you have questions about or problems -with the software, your options for finding answers and fixes are somewhat -different from what they would be for commercial software. - -There are several options for free support provided by community -volunteers. First, some IRC channels, local groups, and language communities -encourage support questions, through on-line chat, in-person meetings, or -websites (find out more about these on <>). - -Second, some (but not all) contributed module, distribution, and theme projects -encourage you to post support requests in issues. Generally, projects that have -a very large number of users do not allow support requests in their issues -(Drupal Core is in that category), while projects with a smaller number of users -welcome the occasional support question. Be respectful of developer time and -read the documentation for the project before posting a question in an issue. On -the other hand, all projects encourage you to use issues to report problems and -bugs; see <> to learn more about that. - -In addition to those resources, the following sites provide free forums where -volunteers answer support questions about Drupal: +The Drupal project is open-source, so if you have questions about or problems with the software, your options for finding answers and fixes are somewhat different from what they would be for commercial software. + +There are several options for free support provided by community volunteers. First, some IRC channels, local groups, and language communities encourage support questions, through on-line chat, in-person meetings, or websites (find out more about these on <>). + +Second, some (but not all) contributed module, distribution, and theme projects encourage you to post support requests in issues. Generally, projects that have a very large number of users do not allow support requests in their issues (Drupal Core is in that category), while projects with a smaller number of users welcome the occasional support question. Be respectful of developer time and read the documentation for the project before posting a question in an issue. On the other hand, all projects encourage you to use issues to report problems and bugs; see <> to learn more about that. + +In addition to those resources, the following sites provide free forums where volunteers answer support questions about Drupal: * The https://www.drupal.org/forum[_Drupal.org_ Forums] * http://drupal.stackexchange.com/["Drupal Answers" on StackExchange] -If you prefer to pay for support (presumably in exchange for more extensive -service or better availability), you can find service providers in the -https://www.drupal.org/drupal-services["Drupal Marketplace" on _Drupal.org_]. +If you prefer to pay for support (presumably in exchange for more extensive service or better availability), you can find service providers in the https://www.drupal.org/drupal-services["Drupal Marketplace" on _Drupal.org_]. ==== Related topics diff --git a/source/hu/understanding-data.txt b/source/hu/understanding-data.txt index 568eb88..28bb750 100644 --- a/source/hu/understanding-data.txt +++ b/source/hu/understanding-data.txt @@ -19,26 +19,16 @@ Overview of common types of data used in a site. ==== What are the types of data? -The data and information on your site is divided up into four types, which are -edited, translated, and stored differently. These four types are: +The data and information on your site is divided up into four types, which are edited, translated, and stored differently. These four types are: Content:: - Information (text, images, etc.) meant to be displayed to site visitors. This - type of information tends to be relatively permanent, but can normally be - edited. + Information (text, images, etc.) meant to be displayed to site visitors. This type of information tends to be relatively permanent, but can normally be edited. Configuration:: - Information about your site that is not content, but is also relatively - permanent, and is used to define how your site behaves or is displayed. It is - sometimes also displayed to site visitors, but tends to be smaller pieces of - text (like field labels, the name of your site, etc.) rather than larger - chunks that you'd normally think of as Content. + Information about your site that is not content, but is also relatively permanent, and is used to define how your site behaves or is displayed. It is sometimes also displayed to site visitors, but tends to be smaller pieces of text (like field labels, the name of your site, etc.) rather than larger chunks that you'd normally think of as Content. State:: - Information of a temporary nature about the current state of your - site, such as the time when cron jobs were last run. + Information of a temporary nature about the current state of your site, such as the time when cron jobs were last run. Session:: - Information about individual site visitors' interactions with the site, such - as whether they are logged in and their cookies. This is technically a - subtype of State information, since it is also temporary. + Information about individual site visitors' interactions with the site, such as whether they are logged in and their cookies. This is technically a subtype of State information, since it is also temporary. ==== Related topics @@ -52,7 +42,5 @@ Session:: *Attributions* -Adapted by https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon] from -https://www.drupal.org/node/2120523["Overview of Configuration (vs. other types of information)"], -copyright 2000-2016 by the individual contributors to the -https://www.drupal.org/documentation[Drupal Community Documentation] +Adapted by https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon] from https://www.drupal.org/node/2120523["Overview of Configuration (vs. other types of information)"], +copyright 2000-2016 by the individual contributors to the https://www.drupal.org/documentation[Drupal Community Documentation] diff --git a/source/hu/understanding-distributions.txt b/source/hu/understanding-distributions.txt index 495c858..10b27b8 100644 --- a/source/hu/understanding-distributions.txt +++ b/source/hu/understanding-distributions.txt @@ -19,25 +19,15 @@ Overview of distributions and their different types to set up use-specific websi ==== What are Distributions? -_Distributions_ provide site features and functions for a specific type of site -as a single download containing the core software, contributed modules, themes, -and pre-defined configuration. A distribution makes it possible to set up a -complex, use-specific site in fewer steps than installing and configuring -elements individually. +_Distributions_ provide site features and functions for a specific type of site as a single download containing the core software, contributed modules, themes, and pre-defined configuration. A distribution makes it possible to set up a complex, use-specific site in fewer steps than installing and configuring elements individually. There are two main types of distributions: Full-featured Distributions:: - A full-featured distribution is a project that provides a complete solution - to set up a site for a specialized purpose such as academic, business, - government, nonprofit, publishing, social, etc. For example, you could use an - existing distribution for farmers markets to build your own website, or you - could share your set-up for the farmers market site as a distribution for - others to use. + A full-featured distribution is a project that provides a complete solution to set up a site for a specialized purpose such as academic, business, government, nonprofit, publishing, social, etc. For example, you could use an existing distribution for farmers markets to build your own website, or you could share your set-up for the farmers market site as a distribution for others to use. Other Distributions:: - Distributions can also be quick-start tools that developers and site - builders can use as a starting point. + Distributions can also be quick-start tools that developers and site builders can use as a starting point. ==== Related topics @@ -51,8 +41,6 @@ https://www.drupal.org/project/project_distribution[_Drupal.org_ Drupal Distribu *Attributions* Adapted and edited by https://www.drupal.org/u/diana.lakatos[Diána Lakatos] -and https://www.drupal.org/u/ifrik[Antje Lorch], -from https://www.drupal.org/documentation/build/distributions["Distributions"] -and https://www.drupal.org/project/project_distribution["Download & Extend -- Distributions"] +and https://www.drupal.org/u/ifrik[Antje Lorch], from https://www.drupal.org/documentation/build/distributions["Distributions"] and https://www.drupal.org/project/project_distribution["Download & Extend -- Distributions"] copyright 2000-2016 by the individual contributors to the https://www.drupal.org/documentation[Drupal Community Documentation]. diff --git a/source/hu/understanding-drupal.txt b/source/hu/understanding-drupal.txt index 15e124c..caedcba 100644 --- a/source/hu/understanding-drupal.txt +++ b/source/hu/understanding-drupal.txt @@ -16,33 +16,13 @@ Overview of Drupal and the reasons to choose it as a reliable Content Management ==== What is a Content Management System? -A content management system (CMS) is a software tool that lets users add, -publish, edit, or remove content from a website, using a web browser on a -smartphone, tablet, or desktop computer. Typically, the CMS software is written -in a scripting language, and its scripts run on a computer where a database and -a web server are installed. The content and settings for the website are usually -stored in a database, and for each page request that comes to the web server, -the scripts combine information from the database and _assets_ (JavaScript -files, CSS files, image files, etc. that are part of the CMS or have been -uploaded) to build the pages of the website. - -The combination of the operating system that the CMS runs on, the scripting -language it is written in, the database it stores its information in, and the -web server that runs the scripts to retrieve information and return it to the -site visitor's web browser is known as the _stack_ that the CMS runs on; the -commonly used combination of the Linux operating system, Apache web server, -MySQL database, and PHP scripting language is known as the _LAMP stack_. +A content management system (CMS) is a software tool that lets users add, publish, edit, or remove content from a website, using a web browser on a smartphone, tablet, or desktop computer. Typically, the CMS software is written in a scripting language, and its scripts run on a computer where a database and a web server are installed. The content and settings for the website are usually stored in a database, and for each page request that comes to the web server, the scripts combine information from the database and _assets_ (JavaScript files, CSS files, image files, etc. that are part of the CMS or have been uploaded) to build the pages of the website. + +The combination of the operating system that the CMS runs on, the scripting language it is written in, the database it stores its information in, and the web server that runs the scripts to retrieve information and return it to the site visitor's web browser is known as the _stack_ that the CMS runs on; the commonly used combination of the Linux operating system, Apache web server, MySQL database, and PHP scripting language is known as the _LAMP stack_. ==== What is Drupal? -Drupal is a flexible CMS based on the LAMP stack, with a modular design allowing -features to be added and removed by installing and uninstalling _modules_, and -allowing the entire look and feel of the website to be changed by installing and -uninstalling _themes_. The base Drupal download, known as Drupal Core, contains -the PHP scripts needed to run the basic CMS functionality, several optional -modules and themes, and many JavaScript, CSS, and image assets. Many additional -modules and themes can be downloaded from the https://www.drupal.org[_Drupal.org_] -website. +Drupal is a flexible CMS based on the LAMP stack, with a modular design allowing features to be added and removed by installing and uninstalling _modules_, and allowing the entire look and feel of the website to be changed by installing and uninstalling _themes_. The base Drupal download, known as Drupal Core, contains the PHP scripts needed to run the basic CMS functionality, several optional modules and themes, and many JavaScript, CSS, and image assets. Many additional modules and themes can be downloaded from the https://www.drupal.org[_Drupal.org_] website. Drupal can also run on other technology stacks: @@ -53,43 +33,19 @@ Drupal can also run on other technology stacks: * The database can be PostgreSQL or SQLite instead of MySQL, or a MySQL-compatible replacement such as MariaDB or Percona. -Other operating systems, web servers, and databases can also be made to work; -however, the scripts that the software uses are written in PHP, so that cannot -be changed. +Other operating systems, web servers, and databases can also be made to work; however, the scripts that the software uses are written in PHP, so that cannot be changed. ==== What are the reasons for using Drupal? -When building a website, you have your choice of using one of the many existing -CMS packages and hosted services, developing your own CMS, or building the site -without using a CMS. Here are some of the reasons you might choose to use -Drupal: - -* Building a small, simple site with static HTML pages is not difficult, and you -can get a simple site up very quickly. Setting up a site in a CMS generally -requires more time initially, but brings you the benefits of on-line editing -(easier for less experienced content maintainers), uniformity (harder to -maintain using static HTML for larger sites), and the possibility of more -complex features requiring a database. - -* Some CMS software is special-purpose; for instance, there are packages and -hosted services that you can use to build a blog or a club membership -website. Drupal, in contrast, is a general-purpose CMS. If you are building a -special-purpose site, you might choose to use a special-purpose CMS; however, if -your site falls even slightly outside the intended purpose, you will probably be -better off using a general-purpose CMS rather than trying to adapt a -special-purpose CMS. - -* Building your own CMS-type software can seem attractive. However, using a -general-purpose CMS like Drupal as a starting point is usually a better idea, -because the basic CMS functionality (such as user accounts and content -management) has thousands of developer hours behind it, including many years of -user testing, bug fixing, and security hardening. - -* Some CMS software packages are expensive to purchase a license for. Some are -free or have a free version, but have restrictive licenses that do not allow you -to make modifications and extensions. You might prefer to use a package (like -Drupal) that has a less restrictive software license, and is developed by a -world-wide community. See <> for more on this topic. +When building a website, you have your choice of using one of the many existing CMS packages and hosted services, developing your own CMS, or building the site without using a CMS. Here are some of the reasons you might choose to use Drupal: + +* Building a small, simple site with static HTML pages is not difficult, and you can get a simple site up very quickly. Setting up a site in a CMS generally requires more time initially, but brings you the benefits of on-line editing (easier for less experienced content maintainers), uniformity (harder to maintain using static HTML for larger sites), and the possibility of more complex features requiring a database. + +* Some CMS software is special-purpose; for instance, there are packages and hosted services that you can use to build a blog or a club membership website. Drupal, in contrast, is a general-purpose CMS. If you are building a special-purpose site, you might choose to use a special-purpose CMS; however, if your site falls even slightly outside the intended purpose, you will probably be better off using a general-purpose CMS rather than trying to adapt a special-purpose CMS. + +* Building your own CMS-type software can seem attractive. However, using a general-purpose CMS like Drupal as a starting point is usually a better idea, because the basic CMS functionality (such as user accounts and content management) has thousands of developer hours behind it, including many years of user testing, bug fixing, and security hardening. + +* Some CMS software packages are expensive to purchase a license for. Some are free or have a free version, but have restrictive licenses that do not allow you to make modifications and extensions. You might prefer to use a package (like Drupal) that has a less restrictive software license, and is developed by a world-wide community. See <> for more on this topic. ==== Related topics diff --git a/source/hu/understanding-gpl.txt b/source/hu/understanding-gpl.txt index c404190..338e45f 100644 --- a/source/hu/understanding-gpl.txt +++ b/source/hu/understanding-gpl.txt @@ -17,27 +17,17 @@ Overview of Drupal licensing and the guidelines to be followed by users and cont ==== What is Drupal Licensing? -Drupal and all contributed files hosted on _Drupal.org_ are licensed under the -GNU General Public License (GPL), version 2 or later. That means you are free to -download, reuse, modify, and distribute any files that are part of a project on -_Drupal.org_ under the terms of GPL version 2 or 3. You can also run the core -software in combination with any code with any license that is compatible with -version 2 or 3. +Drupal and all contributed files hosted on _Drupal.org_ are licensed under the GNU General Public License (GPL), version 2 or later. That means you are free to download, reuse, modify, and distribute any files that are part of a project on _Drupal.org_ under the terms of GPL version 2 or 3. You can also run the core software in combination with any code with any license that is compatible with version 2 or 3. Drupal contributors should follow these guidelines: -* All files (PHP, JavaScript, images, Flash, etc.) that are part of a project -on _Drupal.org_ have to be under GPL version 2 or later. +* All files (PHP, JavaScript, images, Flash, etc.) that are part of a project on _Drupal.org_ have to be under GPL version 2 or later. -* All Drupal contributors retain copyright on their code, but agree to release -it under the same license as Drupal. +* All Drupal contributors retain copyright on their code, but agree to release it under the same license as Drupal. -* Drupal modules and themes are a derivative work of Drupal. If you distribute -them, you must do so under the terms of GPL version 2 or later. +* Drupal modules and themes are a derivative work of Drupal. If you distribute them, you must do so under the terms of GPL version 2 or later. -* All content on _Drupal.org_ itself is copyrighted by its original -contributors, and is licensed under the Creative Commons Attribution-ShareAlike -license 2.0. +* All content on _Drupal.org_ itself is copyrighted by its original contributors, and is licensed under the Creative Commons Attribution-ShareAlike license 2.0. * Sample code on _Drupal.org_ is also available under GPL version 2 or later. @@ -63,7 +53,5 @@ license 2.0. *Attributions* Adapted by https://www.drupal.org/u/diana.lakatos[Diána Lakatos] at -http://pronovix.com[Pronovix] from -https://www.drupal.org/about/licensing["Licensing"] -copyright 2000-2016 by the individual contributors to the -https://www.drupal.org/documentation[Drupal Community Documentation]. +http://pronovix.com[Pronovix] from https://www.drupal.org/about/licensing["Licensing"] +copyright 2000-2016 by the individual contributors to the https://www.drupal.org/documentation[Drupal Community Documentation]. diff --git a/source/hu/understanding-modules.txt b/source/hu/understanding-modules.txt index a6bd612..7a2bbbb 100644 --- a/source/hu/understanding-modules.txt +++ b/source/hu/understanding-modules.txt @@ -30,29 +30,20 @@ Overview of modules and the functionality they can be used for. ==== What is a module? -A module is a set of PHP, JavaScript, and/or CSS files that extends site -features and adds functionality. You can turn the features and functionality on -by _installing_ the module, and you can turn it off by _uninstalling_ the -module; before uninstalling, you may need to remove data and configuration -related to the feature or functionality. Each module that is installed adds to -the time needed to generate pages on your site, so it is a good idea to -uninstall modules that are not needed. +A module is a set of PHP, JavaScript, and/or CSS files that extends site features and adds functionality. You can turn the features and functionality on by _installing_ the module, and you can turn it off by _uninstalling_ the module; before uninstalling, you may need to remove data and configuration related to the feature or functionality. Each module that is installed adds to the time needed to generate pages on your site, so it is a good idea to uninstall modules that are not needed. The core download provides modules for functionality such as: * Managing user accounts (the core User module) -* Managing basic content (the core Node module) and fields (the core Field and -Field UI modules; there are also core modules providing field types) +* Managing basic content (the core Node module) and fields (the core Field and Field UI modules; there are also core modules providing field types) * Managing navigation menus (the core Menu UI module) -* Making lists, grids, and blocks from existing content (the core Views and -Views UI modules) +* Making lists, grids, and blocks from existing content (the core Views and Views UI modules) You can download additional _contributed modules_ from the -https://www.drupal.org/project/modules[_Drupal.org_ Module Downloads], or create your own -_custom modules_. +https://www.drupal.org/project/modules[_Drupal.org_ Module Downloads], or create your own _custom modules_. ==== Related topics diff --git a/source/hu/understanding-project.txt b/source/hu/understanding-project.txt index 7b1b943..3ddf6e3 100644 --- a/source/hu/understanding-project.txt +++ b/source/hu/understanding-project.txt @@ -16,35 +16,20 @@ Overview of Free and Open Source Software (FOSS), Drupal project, and Drupal Ass ==== What is Free and Open Source Software? -Free and Open Source Software (FOSS) is software that is developed by a -community of people, released under a non-commercial license, and whose _source -code_ (the program files that make up the software) is freely available. For -more information on the non-commercial license used by Drupal, see -<>. +Free and Open Source Software (FOSS) is software that is developed by a community of people, released under a non-commercial license, and whose _source code_ (the program files that make up the software) is freely available. For more information on the non-commercial license used by Drupal, see <>. ==== What is the Drupal project? -The Drupal project is a FOSS project whose purpose is to develop the core -content management system software, as well as add-on modules, additional -themes, translations, documentation, and special-purpose distributions. The -people who contribute their time and money to the Drupal project come from all -over the world, and are a diverse community that comes together for this common -purpose. +The Drupal project is a FOSS project whose purpose is to develop the core content management system software, as well as add-on modules, additional themes, translations, documentation, and special-purpose distributions. The people who contribute their time and money to the Drupal project come from all over the world, and are a diverse community that comes together for this common purpose. -The community encompasses many smaller groups who perform many different tasks -such as developing a particular piece of Drupal-related software, writing -documentation, maintaining the security of Drupal software, translating Drupal -software into a particular language, using Drupal for some specific purpose, -and coming together to meet in person within a particular geographical area. +The community encompasses many smaller groups who perform many different tasks such as developing a particular piece of Drupal-related software, writing documentation, maintaining the security of Drupal software, translating Drupal software into a particular language, using Drupal for some specific purpose, and coming together to meet in person within a particular geographical area. For more on how you can connect to and communicate with the world-wide community, see <> and <>. ==== What is the Drupal Association? -The https://assoc.drupal.org[Drupal Association] is a non-profit organization -dedicated to supporting the Drupal project and community. Its main functions -are: +The https://assoc.drupal.org[Drupal Association] is a non-profit organization dedicated to supporting the Drupal project and community. Its main functions are: * Putting on large conventions around the world * Maintaining the _Drupal.org_ websites and the servers that they run on diff --git a/source/hu/understanding-themes.txt b/source/hu/understanding-themes.txt index 4c82b39..cc934eb 100644 --- a/source/hu/understanding-themes.txt +++ b/source/hu/understanding-themes.txt @@ -20,25 +20,14 @@ Overview of themes and where to obtain them. ==== What is a Theme? A theme is a set of files that define the visual look and feel of your site. -The core software and modules that run on your site determine which -_content_ (including HTML text and other data stored in the database, uploaded -images, and any other asset files) is displayed on the pages of your site. The -theme determines the HTML markup and CSS styling that wraps the content. +The core software and modules that run on your site determine which _content_ (including HTML text and other data stored in the database, uploaded images, and any other asset files) is displayed on the pages of your site. The theme determines the HTML markup and CSS styling that wraps the content. The core software provides several basic themes with the core distribution. -These themes have largely been designed and built by the community over the last -several years and will all be good choices for building your first sites and -becoming more familiar with how the core software works. - -Drupal is a well-established CMS so the market for 3rd party themes - both free -and paid - is very robust. - -If none of the 3rd party options suit your needs, you'll need to create a custom -theme. A custom theme can be as simple as a single CSS file that adds styling to -the markup provided by the core software. Guidance for creating custom themes -in Drupal 8 can be found in the -https://www.drupal.org/theme-guide/8[_Drupal.org_ community documentation page -"Theming Drupal"]. +These themes have largely been designed and built by the community over the last several years and will all be good choices for building your first sites and becoming more familiar with how the core software works. + +Drupal is a well-established CMS so the market for 3rd party themes - both free and paid - is very robust. + +If none of the 3rd party options suit your needs, you'll need to create a custom theme. A custom theme can be as simple as a single CSS file that adds styling to the markup provided by the core software. Guidance for creating custom themes in Drupal 8 can be found in the https://www.drupal.org/theme-guide/8[_Drupal.org_ community documentation page "Theming Drupal"]. ==== Related topics diff --git a/source/hu/user-admin-account.txt b/source/hu/user-admin-account.txt index c08f484..a401050 100644 --- a/source/hu/user-admin-account.txt +++ b/source/hu/user-admin-account.txt @@ -16,41 +16,21 @@ Overview of the User 1 account, also known as the root account or administrative ==== What is the user 1 account? -During the installation of your site, you created the first user account. Each -user account internally has a numeric user ID, and since the ID of this user is -one, it is commonly referred to as the _user 1_ account. This user account is -special, because independent of what roles it is assigned, someone logged in as -user 1 has permission to do all actions on the site, including viewing and -editing all content, editing any user account, changing site configuration, -installing and uninstalling modules, and running the update script. - -Because of this level of permission, some people refer to this account as the -_root user_, similar to the "root" user account that has full administrative -permissions in Linux and other operating systems. - -It is usually better to make separate accounts for each administrative user, -giving them the _Administrator_ role, rather than having all administrative -users log in using the user 1 account. There are several reasons for this: - -* Some actions and updates on the site are logged, and if everyone uses the same -account, it is difficult to know who did them if you have questions. - -* The _Administrator_ role permissions can be modified to be safer than the -full permissions of the user 1 account, so that people do not inadvertently -change site features that shouldn't be changed. - -* People's responsibilities on a site may change over time. With ordinary user -accounts, this can be mirrored in permissions by assigning or unassigning -roles to their user accounts. If they are all using the user 1 account, -this is more difficult. - -* On some sites, the author of content or comments is displayed or tracked, and -if everyone uses the same account to create content, it is difficult to know -who created the content. - -It is not possible to delete the user 1 account from the administrative user -interface. It would be possible to do with a database query, but it could cause -problems in your site and is not advisable. +During the installation of your site, you created the first user account. Each user account internally has a numeric user ID, and since the ID of this user is one, it is commonly referred to as the _user 1_ account. This user account is special, because independent of what roles it is assigned, someone logged in as user 1 has permission to do all actions on the site, including viewing and editing all content, editing any user account, changing site configuration, installing and uninstalling modules, and running the update script. + +Because of this level of permission, some people refer to this account as the _root user_, similar to the "root" user account that has full administrative permissions in Linux and other operating systems. + +It is usually better to make separate accounts for each administrative user, giving them the _Administrator_ role, rather than having all administrative users log in using the user 1 account. There are several reasons for this: + +* Some actions and updates on the site are logged, and if everyone uses the same account, it is difficult to know who did them if you have questions. + +* The _Administrator_ role permissions can be modified to be safer than the full permissions of the user 1 account, so that people do not inadvertently change site features that shouldn't be changed. + +* People's responsibilities on a site may change over time. With ordinary user accounts, this can be mirrored in permissions by assigning or unassigning roles to their user accounts. If they are all using the user 1 account, this is more difficult. + +* On some sites, the author of content or comments is displayed or tracked, and if everyone uses the same account to create content, it is difficult to know who created the content. + +It is not possible to delete the user 1 account from the administrative user interface. It would be possible to do with a database query, but it could cause problems in your site and is not advisable. //==== Related topics diff --git a/source/hu/user-concept.txt b/source/hu/user-concept.txt index 4c9aab2..0dea36a 100644 --- a/source/hu/user-concept.txt +++ b/source/hu/user-concept.txt @@ -17,42 +17,25 @@ Overview of user accounts, permissions, and roles. ==== What are Users? -Anyone who visits your website is a _user_, including you. There are three -groups of users: +Anyone who visits your website is a _user_, including you. There are three groups of users: * Users who are not logged in, or _anonymous users_ * Users who are logged in, or _authenticated users_ -* The administrative user account that was automatically created when you -installed your site, or User 1. See <>. +* The administrative user account that was automatically created when you installed your site, or User 1. See <>. ==== What are Permissions? -The ability to do actions on your site (including viewing content, editing -content, and changing configuration) is governed by _permissions_. Each -permission has a name (such as _View published content_) and covers one action -or a small subset of actions. A user must be granted a permission in order to do -the corresponding action on the site; permissions are defined by the modules -that provide the actions. +The ability to do actions on your site (including viewing content, editing content, and changing configuration) is governed by _permissions_. Each permission has a name (such as _View published content_) and covers one action or a small subset of actions. A user must be granted a permission in order to do the corresponding action on the site; permissions are defined by the modules that provide the actions. ==== What are Roles? -Rather than assigning individual permissions directly to each user, permissions -are grouped into _roles_. You can define one or more roles on your site, and -then grant permissions to each role. The permissions granted to authenticated -and anonymous users are contained in the _Authenticated user_ and _Anonymous -user_ roles, and depending on the installation profile you used when you -installed your site, there may also be an _Administrator_ role that is -automatically assigned all permissions on your site. +Rather than assigning individual permissions directly to each user, permissions are grouped into _roles_. You can define one or more roles on your site, and then grant permissions to each role. The permissions granted to authenticated and anonymous users are contained in the _Authenticated user_ and _Anonymous user_ roles, and depending on the installation profile you used when you installed your site, there may also be an _Administrator_ role that is automatically assigned all permissions on your site. -Each user account on your site is automatically given the _Authenticated user_ -role, and may optionally be assigned one or more additional roles. When you -assign a role to a user account, the user will have all the permissions of the -role when logged in. +Each user account on your site is automatically given the _Authenticated user_ role, and may optionally be assigned one or more additional roles. When you assign a role to a user account, the user will have all the permissions of the role when logged in. -It is a good practice to make several roles on your site. In the farmers market -site example, you might want the following roles: +It is a good practice to make several roles on your site. In the farmers market site example, you might want the following roles: * A Vendor role that allows vendors to edit their own vendor listing page @@ -60,8 +43,7 @@ site example, you might want the following roles: * A User manager role for managing the vendor accounts -* The _Administrator_ role that was installed with your site, for expert users -to manage the site configuration +* The _Administrator_ role that was installed with your site, for expert users to manage the site configuration ==== Related topics @@ -83,7 +65,5 @@ to manage the site configuration Adapted by https://www.drupal.org/u/mark-lacroix[Mark LaCroix], https://www.drupal.org/u/batigolix[Boris Doesborg], and -https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon] from -https://www.drupal.org/node/1803614["User Roles"], -copyright 2000-2016 by the individual contributors to the -https://www.drupal.org/documentation[Drupal Community Documentation]. +https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon] from https://www.drupal.org/node/1803614["User Roles"], +copyright 2000-2016 by the individual contributors to the https://www.drupal.org/documentation[Drupal Community Documentation]. diff --git a/source/hu/user-content.txt b/source/hu/user-content.txt index d6a5499..0e1e52c 100644 --- a/source/hu/user-content.txt +++ b/source/hu/user-content.txt @@ -10,8 +10,7 @@ How to assign authorship of content items to a user account. ==== Goal -Assign Vendor content items Happy Farm and Sweet Honey to the corresponding -Vendor user accounts, so they can edit their own Vendor profiles on the site. +Assign Vendor content items Happy Farm and Sweet Honey to the corresponding Vendor user accounts, so they can edit their own Vendor profiles on the site. ==== Prerequisite knowledge @@ -19,9 +18,7 @@ Vendor user accounts, so they can edit their own Vendor profiles on the site. ==== Site prerequisites -* The Vendor content type must exist, and your site must have at least two -Vendor content items. See <>, <>, and -<>. +* The Vendor content type must exist, and your site must have at least two Vendor content items. See <>, <>, and <>. * User accounts for at least two vendors must exist. See <>. @@ -29,10 +26,7 @@ Vendor content items. See <>, <>, and . In the _Manage_ administrative menu, navigate to _Content_ (_admin/content_). -. Find Vendor content item Happy Farm in the list. If it is not immediately -visible, you can filter the list by _Published status_, _Type_ (Vendor), _Title_ -or _Language_. Click _Edit_ for the Vendor content item you would like to -assign an author to. +. Find Vendor content item Happy Farm in the list. If it is not immediately visible, you can filter the list by _Published status_, _Type_ (Vendor), _Title_ or _Language_. Click _Edit_ for the Vendor content item you would like to assign an author to. . Locate the information block and click _Authoring information_. + @@ -42,8 +36,7 @@ image:images/user-content.png["Assigning an author to the Vendor content item"] -- . Start typing the Vendor's user name Happy Farm in the _Authored by_ field. -The field lists matching user names. Select the Vendor's user name from the -list. +The field lists matching user names. Select the Vendor's user name from the list. . Click _Save and keep published_. @@ -54,8 +47,7 @@ list. image:images/user-content_updated.png["Vendor content item has been updated"] -- -. Follow these steps again to assign Vendor content item Sweet Honey to the -Vendor user account Sweet Honey. +. Follow these steps again to assign Vendor content item Sweet Honey to the Vendor user account Sweet Honey. // ==== Expand your understanding diff --git a/source/hu/user-new-role.txt b/source/hu/user-new-role.txt index d8afc4d..6044299 100644 --- a/source/hu/user-new-role.txt +++ b/source/hu/user-new-role.txt @@ -13,8 +13,7 @@ How to create a new role. ==== Goal -Create a Vendor role to allow some - but not all - users to perform specific -tasks. +Create a Vendor role to allow some - but not all - users to perform specific tasks. ==== Prerequisite knowledge @@ -24,11 +23,9 @@ tasks. ==== Steps -. In the _Manage_ administrative menu, navigate to _People_ > _Roles_ -(_admin/people/roles_). +. In the _Manage_ administrative menu, navigate to _People_ > _Roles_ (_admin/people/roles_). -. You will find default roles _Anonymous user_, -_Authenticated user_, and _Administrator_ already present. +. You will find default roles _Anonymous user_, _Authenticated user_, and _Administrator_ already present. + -- // Roles page (admin/people/roles). @@ -44,8 +41,7 @@ image:images/user-new-role-roles-page.png["Roles page"] image:images/user-new-role-add-role.png["adding vendor as a role"] -- -. You will see the message "Role Vendor has been added." displayed at the top -of the page. +. You will see the message "Role Vendor has been added." displayed at the top of the page. + -- // Confirmation message after adding new role. @@ -70,6 +66,4 @@ https://www.drupal.org/node/1803614[_Drupal.org_ community documentation page "U Adapted and edited by https://www.drupal.org/u/JackProbst[Jack Probst], https://www.drupal.org/u/batigolix[Boris Doesborg], and https://www.drupal.org/u/eojthebrave[Joe Shindelar] from -https://www.drupal.org/node/1803614["User Roles"], copyright 2000-2016 by the -individual contributors to the https://www.drupal.org/documentation[Drupal -Community Documentation] +https://www.drupal.org/node/1803614["User Roles"], copyright 2000-2016 by the individual contributors to the https://www.drupal.org/documentation[Drupal Community Documentation] diff --git a/source/hu/user-new-user.txt b/source/hu/user-new-user.txt index 44b763a..3c4f9b0 100644 --- a/source/hu/user-new-user.txt +++ b/source/hu/user-new-user.txt @@ -49,8 +49,7 @@ image:images/user-new-user_form.png["Form for creating a new user account",width |================================ -. Click _Create new account_. You will get a notification about the user account -creation. +. Click _Create new account_. You will get a notification about the user account creation. + -- // Confirmation message after adding new user. diff --git a/source/hu/user-permissions.txt b/source/hu/user-permissions.txt index 0f64e09..a218973 100644 --- a/source/hu/user-permissions.txt +++ b/source/hu/user-permissions.txt @@ -12,9 +12,7 @@ How to assign a permission to a role. ==== Goal -Change the permissions for the Vendor role so that users can create, edit, -and delete Recipe and Vendor content, format the content, and contact each -other. +Change the permissions for the Vendor role so that users can create, edit, and delete Recipe and Vendor content, format the content, and contact each other. ==== Prerequisite knowledge @@ -28,15 +26,9 @@ The Vendor role must exist on your site. See <>. ==== Steps -. In the _Manage_ administrative menu, navigate to _People_ > _Roles_ -(_admin/people/roles_). The _Roles_ page appears. +. In the _Manage_ administrative menu, navigate to _People_ > _Roles_ (_admin/people/roles_). The _Roles_ page appears. -. Click _Edit permissions_ in the dropdown for the Vendor -role. The _Edit role_ page appears where you can see all the available -actions for the website such as, for example, _Post comments_ or _Use advanced -search_. The available permissions depend on the modules that are installed in -the site. Note: Some permissions may have security implications. Be cautious -while assigning permissions to roles. +. Click _Edit permissions_ in the dropdown for the Vendor role. The _Edit role_ page appears where you can see all the available actions for the website such as, for example, _Post comments_ or _Use advanced search_. The available permissions depend on the modules that are installed in the site. Note: Some permissions may have security implications. Be cautious while assigning permissions to roles. . Check the boxes for the following permissions, listed by module: + @@ -57,8 +49,7 @@ while assigning permissions to roles. image:images/user-permissions-check-permissions.png["Granting users with the Vendor role the rights to create, delete and edit Recipes",width="100%"] -- -. Click _Save permissions_. You will get a message saying your changes have been -saved. +. Click _Save permissions_. You will get a message saying your changes have been saved. + -- // Confirmation message after updating permissions. @@ -67,8 +58,7 @@ image:images/user-permissions-save-permissions.png["Confirmation message after u ==== Expand your understanding -* Log in as one of the new users you created in <>. Verify -whether you have the correct permissions. +* Log in as one of the new users you created in <>. Verify whether you have the correct permissions. * <> diff --git a/source/hu/user-roles.txt b/source/hu/user-roles.txt index 95a6c4b..9464dd3 100644 --- a/source/hu/user-roles.txt +++ b/source/hu/user-roles.txt @@ -10,8 +10,7 @@ How to change or add roles for a user. ==== Goal -Change or add roles to a given user, either by editing a single-user or by -applying a bulk operation. +Change or add roles to a given user, either by editing a single-user or by applying a bulk operation. ==== Prerequisite knowledge @@ -19,20 +18,15 @@ applying a bulk operation. ==== Site prerequisites -The user account that you want to update, and the role you want it to have, must -already exist. See <>, <>, and -<>. +The user account that you want to update, and the role you want it to have, must already exist. See <>, <>, and <>. ==== Steps ===== Updating the roles using single-user editing method -. In the _Manage_ administrative menu, navigate to _People_ -(_admin/people_). +. In the _Manage_ administrative menu, navigate to _People_ (_admin/people_). -. Locate the user 1 account (named "admin") to assign it the _Administrator_ -role. If it is not immediately visible, use the _Name or email contains_ filter, -or other filters, to narrow down the list. +. Locate the user 1 account (named "admin") to assign it the _Administrator_ role. If it is not immediately visible, use the _Name or email contains_ filter, or other filters, to narrow down the list. . Click _Edit_ to update the user account. + @@ -41,16 +35,14 @@ or other filters, to narrow down the list. image:images/user-roles_people-list.png["People page",width="100%"] -- -. On the _Edit_ page, scroll down to _Roles_ section. Check the _Administrator_ -role for the user account. +. On the _Edit_ page, scroll down to _Roles_ section. Check the _Administrator_ role for the user account. + -- // Roles area on user editing page. image:images/user-roles_person-edit.png["Roles section of user edit page",width="141px"] -- -. Click _Save_ to update the user account. You should be returned to the -_People_ page and see a message saying that the changes have been saved. +. Click _Save_ to update the user account. You should be returned to the _People_ page and see a message saying that the changes have been saved. + -- // Confirmation message after updating user. @@ -59,24 +51,18 @@ image:images/user-roles_message.png["Confirmation message"] ===== Updating the roles using bulk editing method -. If the users Happy Farm and Sweet Honey did not already have the Vendor role, -here is how you would add it. In the _Manage_ administrative menu, navigate to -_People_ (_admin/people_). +. If the users Happy Farm and Sweet Honey did not already have the Vendor role, here is how you would add it. In the _Manage_ administrative menu, navigate to _People_ (_admin/people_). -. Locate Vendor user accounts _Sweet Honey_ and _Happy Farm_ and check them. If -they are not immediately visible, use the _Name or email contains_ filter, or -other filters, to narrow down the list. +. Locate Vendor user accounts _Sweet Honey_ and _Happy Farm_ and check them. If they are not immediately visible, use the _Name or email contains_ filter, or other filters, to narrow down the list. -. Select _Add the Vendor role to the selected users_ from the _With selection_ -select list. +. Select _Add the Vendor role to the selected users_ from the _With selection_ select list. + -- // Bulk editing form on People page (admin/people). image:images/user-roles_bulk.png["People page with bulk operation set up", width="100%"] -- -. Click _Apply_. You should see a message indicating that the desired changes -were made. +. Click _Apply_. You should see a message indicating that the desired changes were made. + -- // Confirmation message after bulk user update. diff --git a/source/hu/views-block.txt b/source/hu/views-block.txt index 8b3e663..bbe8b9e 100644 --- a/source/hu/views-block.txt +++ b/source/hu/views-block.txt @@ -12,9 +12,7 @@ How to add a block display to a view. ==== Goal -Add a block display to the Recipes view to display the most recent recipes -in a sidebar, and change its configuration without changing the existing -Recipes page view. +Add a block display to the Recipes view to display the most recent recipes in a sidebar, and change its configuration without changing the existing Recipes page view. ==== Prerequisite knowledge @@ -24,28 +22,17 @@ Recipes page view. ==== Site prerequisites -* The Recipe content type must exist, it must have a Main image field, and your -site must have a couple of Recipe content items. See <>, -<>, <>, and <>. +* The Recipe content type must exist, it must have a Main image field, and your site must have a couple of Recipe content items. See <>, <>, <>, and <>. -* The _Thumbnail (100x100)_ image style must be defined. This is created on your -site when you install the core Image module (installed with the core Standard -installation profile) but can be recreated if deleted. See -<>. +* The _Thumbnail (100x100)_ image style must be defined. This is created on your site when you install the core Image module (installed with the core Standard installation profile) but can be recreated if deleted. See <>. * The Recipes view must exist. See <> and <>. ==== Steps -. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_ -(_admin/structure/views_). Find the view "Recipes" and click _Edit_ from its -dropdown button. Alternatively, navigate to the Recipes page in the main site -navigation, and click the _Edit view_ contextual link in the main area of the -page. See <> for information about contextual links. +. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_ (_admin/structure/views_). Find the view "Recipes" and click _Edit_ from its dropdown button. Alternatively, navigate to the Recipes page in the main site navigation, and click the _Edit view_ contextual link in the main area of the page. See <> for information about contextual links. -. Create a new block display by clicking _Add_ in the _Displays_ section. Click -_Block_ from the dropdown button. The new display is created, and the focus is -automatically switched to its configuration. +. Create a new block display by clicking _Add_ in the _Displays_ section. Click _Block_ from the dropdown button. The new display is created, and the focus is automatically switched to its configuration. + -- // Add display button on Recipes view edit page, with Block highlighted @@ -53,64 +40,40 @@ automatically switched to its configuration. image:images/views-block_add-block.png["Add block display"] -- -. Change the title of this display by clicking _Block_ next to _Display -name_. The _Page: The name and the description of this display_ pop-up -appears. Change the _Administrative name_ to "Recent recipes". Click _Apply_. +. Change the title of this display by clicking _Block_ next to _Display name_. The _Page: The name and the description of this display_ pop-up appears. Change the _Administrative name_ to "Recent recipes". Click _Apply_. -. Change the title of the view by clicking _Title: Recipes_ in the _Title_ -section. In the pop-up that appears, select _For This block (override)_ from the -_For_ dropdown button. Change the title to "New Recipes" and click _Apply (this -display)_. +. Change the title of the view by clicking _Title: Recipes_ in the _Title_ section. In the pop-up that appears, select _For This block (override)_ from the _For_ dropdown button. Change the title to "New Recipes" and click _Apply (this display)_. + -- // Configuring the block title for this display only. image:images/views-block_title.png["Title only for this block"] -- -. Change the view's style by clicking _Format: Grid_ in the _Format_ section. In -the pop-up that appears, select _For This block (override)_ from the _For_ -dropdown button. Select _Unformatted list_ and Click _Apply (this display)_. You -can further configure the style options in the next pop-up that appears. +. Change the view's style by clicking _Format: Grid_ in the _Format_ section. In the pop-up that appears, select _For This block (override)_ from the _For_ dropdown button. Select _Unformatted list_ and Click _Apply (this display)_. You can further configure the style options in the next pop-up that appears. -. Configure the image field by clicking _Content: Main image_ in the _Fields_ -section. In the pop-up that appears, select _For This block (override)_ from the -_For_ dropdown button. Select _Image style Thumbnail (100x100)_. Click _Apply -(this display)_. +. Configure the image field by clicking _Content: Main image_ in the _Fields_ section. In the pop-up that appears, select _For This block (override)_ from the _For_ dropdown button. Select _Image style Thumbnail (100x100)_. Click _Apply (this display)_. + -- // Configuring the image field for this display only. image:images/views-block_image.png["Image to thumbnail",width="100%"] -- -. Remove ingredients as a filter by clicking _Content: Ingredients (exposed)_ in -the _Filter criteria_ section. In the pop-up that appears, select _For This -block (override)_ from the _For_ dropdown button. Click _Remove_ at the bottom. +. Remove ingredients as a filter by clicking _Content: Ingredients (exposed)_ in the _Filter criteria_ section. In the pop-up that appears, select _For This block (override)_ from the _For_ dropdown button. Click _Remove_ at the bottom. -. Configure how you want the content to be sorted in the view by clicking _Add_ -in the _Sort criteria_ section. In the pop-up that appears, select _For This -block (override)_ from the _For_ dropdown button. Check the field _Authored on_ -(from Content category), and then _Add and configure sort criteria_. +. Configure how you want the content to be sorted in the view by clicking _Add_ in the _Sort criteria_ section. In the pop-up that appears, select _For This block (override)_ from the _For_ dropdown button. Check the field _Authored on_ (from Content category), and then _Add and configure sort criteria_. -. In the appearing configuration pop-up, select _Sort descending_ to have the -most recent recipes appear first. Click _Apply_. +. In the appearing configuration pop-up, select _Sort descending_ to have the most recent recipes appear first. Click _Apply_. -. Specify the number of items to be displayed by clicking _Use pager: Mini_ in -the _Pager_ section. In the pop-up that appears, select _For This block -(override)_ from the _For_ dropdown button. Under _Pager_, select _Display a -specified number of items_. Click _Apply (this display)_. In the _Page: Pager -options_ pop-up, provide "5" as the value for _Items to display_. +. Specify the number of items to be displayed by clicking _Use pager: Mini_ in the _Pager_ section. In the pop-up that appears, select _For This block (override)_ from the _For_ dropdown button. Under _Pager_, select _Display a specified number of items_. Click _Apply (this display)_. In the _Page: Pager options_ pop-up, provide "5" as the value for _Items to display_. -. Click _Save_. You will either see the view editing page again, or the Recipes -page, depending on what you did in step 1. You should also see a message saying -that the view has been saved. +. Click _Save_. You will either see the view editing page again, or the Recipes page, depending on what you did in step 1. You should also see a message saying that the view has been saved. + -- // View saved confirmation message. image:images/views-block_recipes.png["Summary page after configuration",width="100%"] -- -. Place the "Recipes: Recent Recipes" block in the _Sidebar second_ region. See -<>. Navigate to the site's home page to see the block. +. Place the "Recipes: Recent Recipes" block in the _Sidebar second_ region. See <>. Navigate to the site's home page to see the block. + -- // Home page with recipes sidebar visible. diff --git a/source/hu/views-concept.txt b/source/hu/views-concept.txt index 8ee6c05..d8effbd 100644 --- a/source/hu/views-concept.txt +++ b/source/hu/views-concept.txt @@ -14,16 +14,11 @@ Overview of views and the data that can be displayed or output by them. ==== What is a view? -A _view_ is a listing of content on a website. The core Views module handles the -display of views, and the core Views UI module allows you to create and edit -them in the administrative interface. When you define views, you are interested -in taking data from your website and displaying it to the user. +A _view_ is a listing of content on a website. The core Views module handles the display of views, and the core Views UI module allows you to create and edit them in the administrative interface. When you define views, you are interested in taking data from your website and displaying it to the user. ==== What types of data can be displayed using views? -You can create views to output practically any content entity that is stored in -the system. For example, you can create the following lists for the farmers -market site: +You can create views to output practically any content entity that is stored in the system. For example, you can create the following lists for the farmers market site: * Lists of vendors * Lists of recipes diff --git a/source/hu/views-create.txt b/source/hu/views-create.txt index e4cbb42..6b0bf9b 100644 --- a/source/hu/views-create.txt +++ b/source/hu/views-create.txt @@ -14,8 +14,7 @@ How to create a content list view. ==== Goal -Create a page listing vendors that will be automatically updated whenever a -vendor is added, deleted, or updated on the site. +Create a page listing vendors that will be automatically updated whenever a vendor is added, deleted, or updated on the site. ==== Prerequisite knowledge @@ -24,22 +23,15 @@ vendor is added, deleted, or updated on the site. ==== Site prerequisites -* The core Views and Views UI modules must be installed. These are installed for -you when you install with the core Standard installation profile. +* The core Views and Views UI modules must be installed. These are installed for you when you install with the core Standard installation profile. -* The Vendor content type must exist, with URL and Main image fields. Your -site must have a couple of Vendor content items. See <>, -<>, and <>. +* The Vendor content type must exist, with URL and Main image fields. Your site must have a couple of Vendor content items. See <>, <>, and <>. -* The _Medium (220x220)_ image style must be defined. This is created on your -site when you install the core Image module (installed with the core Standard -installation profile) but can be recreated if deleted. See -<>. +* The _Medium (220x220)_ image style must be defined. This is created on your site when you install the core Image module (installed with the core Standard installation profile) but can be recreated if deleted. See <>. ==== Steps -. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_ > _Add -view_ (_admin/structure/views/add_). The _Add view_ wizard appears. +. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_ > _Add view_ (_admin/structure/views/add_). The _Add view_ wizard appears. . Fill in the fields as shown below. + @@ -68,15 +60,13 @@ image:images/views-create-wizard.png["Add new view wizard",width="100%"] . Click _Save and edit_. The view configuration page appears. -. Click _Add_ from the dropdown button in the _Fields_ section. The _Add -fields_ pop-up appears. +. Click _Add_ from the dropdown button in the _Fields_ section. The _Add fields_ pop-up appears. . Enter the word "image" in the search field. . Check Main image in the table. -. Click _Apply_. The _Configure field: Content: Main Image_ -pop-up appears. +. Click _Apply_. The _Configure field: Content: Main Image_ pop-up appears. . Fill in the fields as shown below. + @@ -90,15 +80,13 @@ pop-up appears. . Click _Apply_. The view configuration page appears. -. Click _Add_ from the dropdown button in the _Fields_ section. The _Add -fields_ pop-up appears. +. Click _Add_ from the dropdown button in the _Fields_ section. The _Add fields_ pop-up appears. . Enter the word "body" in the search field. . Select _Body_ in the table. -. Click _Apply_. The _Configure field: Content: Body_ pop-up -appears. +. Click _Apply_. The _Configure field: Content: Body_ pop-up appears. . Fill in the fields as shown below. + @@ -115,13 +103,11 @@ appears. . Click _Content: Title (Title)_ in the _Fields_ list. The _Configure field: Content: Title_ pop-up appears. -. Uncheck _Create a label_. This will remove the label that was created by the -wizard. +. Uncheck _Create a label_. This will remove the label that was created by the wizard. . Click _Apply_. The view configuration page appears. -. Click _Rearrange_ from the dropdown button in the _Fields_ section. The -_Rearrange fields_ pop-up appears. +. Click _Rearrange_ from the dropdown button in the _Fields_ section. The _Rearrange fields_ pop-up appears. . Drag the fields into the right order: Image, Title. Body. @@ -136,8 +122,7 @@ _Rearrange fields_ pop-up appears. image:images/views-create-view.png["Vendors view configuration page", width="100%"] -- -. Navigate to the homepage and click Vendors from the main navigation to see -the result. +. Navigate to the homepage and click Vendors from the main navigation to see the result. + -- // Completed vendors view output. @@ -146,9 +131,7 @@ image:images/views-create-view-output.png["Vendors view output", width="100%"] ==== Expand your understanding -The link to the view in the main navigation will probably not be in the right -place. Change the order of the menu items in the main navigation. See -<>. +The link to the view in the main navigation will probably not be in the right place. Change the order of the menu items in the main navigation. See <>. //==== Related concepts diff --git a/source/hu/views-duplicate.txt b/source/hu/views-duplicate.txt index 9461bed..3efafde 100644 --- a/source/hu/views-duplicate.txt +++ b/source/hu/views-duplicate.txt @@ -11,9 +11,7 @@ How to create a new page by duplicating a view. ==== Goal -Create a page listing recipes by duplicating the existing Vendors view. Modify -the page so that the recipes are displayed in a grid and can by filtered by -ingredients. +Create a page listing recipes by duplicating the existing Vendors view. Modify the page so that the recipes are displayed in a grid and can by filtered by ingredients. ==== Prerequisite knowledge @@ -23,19 +21,13 @@ ingredients. ==== Site prerequisites -* The Vendor and Recipe content types must exist; both must have Main image -fields, and the Recipe content type must have an Ingredients field. Your site -must also have a couple of Recipe content items. See <>, -<>, <>, <>, -and <>. +* The Vendor and Recipe content types must exist; both must have Main image fields, and the Recipe content type must have an Ingredients field. Your site must also have a couple of Recipe content items. See <>, <>, <>, <>, and <>. * The Vendors view must exist. See <>. ==== Steps -. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_ -(_admin/structure/views_). Find the view "Vendors" and click _Duplicate_ in its -dropdown button. +. In the _Manage_ administrative menu, navigate to _Structure_ > _Views_ (_admin/structure/views_). Find the view "Vendors" and click _Duplicate_ in its dropdown button. + -- // Views page (admin/structure/views), with operations dropdown @@ -43,39 +35,24 @@ dropdown button. image:images/views-duplicate_duplicate.png["Duplicate existing view",width="100%"] -- -. Name the duplicate "Recipes" and click _Duplicate_. The view configuration -page appears. +. Name the duplicate "Recipes" and click _Duplicate_. The view configuration page appears. -. Change the title of the view page to "Recipes" by clicking Vendors in the -_Title_ section. The _Page: The title of this view_ pop-up appears. Type in -"Recipes". Click _Apply_. +. Change the title of the view page to "Recipes" by clicking Vendors in the _Title_ section. The _Page: The title of this view_ pop-up appears. Type in "Recipes". Click _Apply_. + -- // View title configuration screen. image:images/views-duplicate_title.png["Change view title",width="100%"] -- -. Change from a table to a grid format by clicking _Table_ in the _Format_ -section. The _Page: How should this view be styled_ pop-up appears. Check _Grid_ -and click _Apply_. The _Page: Style options_ pop-up appears. Retain the default -values and click _Apply_. +. Change from a table to a grid format by clicking _Table_ in the _Format_ section. The _Page: How should this view be styled_ pop-up appears. Check _Grid_ and click _Apply_. The _Page: Style options_ pop-up appears. Retain the default values and click _Apply_. -. Retain only the title and image fields for the Recipes view by clicking -_Content: Body_ in the _Fields_ section. Click _Remove_ in the pop-up that -appears. +. Retain only the title and image fields for the Recipes view by clicking _Content: Body_ in the _Fields_ section. Click _Remove_ in the pop-up that appears. -. Change the content type filter to use the Recipe content type by clicking -_Content: Type (=Vendor)_ in the _Filter criteria_ section. In the _Configure -filter criterion: Content: Type_ pop-up, check Recipe and uncheck Vendor. Click -_Apply_. +. Change the content type filter to use the Recipe content type by clicking _Content: Type (=Vendor)_ in the _Filter criteria_ section. In the _Configure filter criterion: Content: Type_ pop-up, check Recipe and uncheck Vendor. Click _Apply_. -. Add a further filter that is exposed to visitors by clicking _Add_ in the -_Filter criteria_ section. Search for "ingredients" and check "Ingredients -(field_ingredients)". Click _Add and configure filter criteria_. +. Add a further filter that is exposed to visitors by clicking _Add_ in the _Filter criteria_ section. Search for "ingredients" and check "Ingredients (field_ingredients)". Click _Add and configure filter criteria_. -. The appearing pop-up offers extra settings on vocabulary and selection -type. Click _Apply and continue_. The next pop-up allows you to expose this -filter to visitors. Fill in the fields as shown below. +. The appearing pop-up offers extra settings on vocabulary and selection type. Click _Apply and continue_. The next pop-up allows you to expose this filter to visitors. Fill in the fields as shown below. + [width="100%",frame="topbot",options="header"] |================================ @@ -90,27 +67,17 @@ filter to visitors. Fill in the fields as shown below. image:images/views-duplicate_expose.png["Expose filter"] -- -. Change the _Path_ label field to "Recipes" by clicking "/vendors" in the _Page -settings_ section. In the pop-up that appears, enter the path "recipes" and -click _Apply_. +. Change the _Path_ label field to "Recipes" by clicking "/vendors" in the _Page settings_ section. In the pop-up that appears, enter the path "recipes" and click _Apply_. + -Note that when editing a view, you enter paths without the leading "/", unlike -on other administrative pages (such as when providing a path to a content item -page). +Note that when editing a view, you enter paths without the leading "/", unlike on other administrative pages (such as when providing a path to a content item page). -. Change the menu link title by clicking "Normal: Vendors" in the _Page -settings_ section. In the pop-up that appears, change the title to "Recipes" and -click _Apply_. +. Change the menu link title by clicking "Normal: Vendors" in the _Page settings_ section. In the pop-up that appears, change the title to "Recipes" and click _Apply_. -. In order to use Ajax (see <>) to make filtering and paging -faster for users, click _Advanced_ to expand the section for more options. In -the _Other_ section, change _Use Ajax: No_ to "Yes" by clicking _No_ and -checking _Use Ajax_ in the pop-up that appears. Click _Apply_. +. In order to use Ajax (see <>) to make filtering and paging faster for users, click _Advanced_ to expand the section for more options. In the _Other_ section, change _Use Ajax: No_ to "Yes" by clicking _No_ and checking _Use Ajax_ in the pop-up that appears. Click _Apply_. . Click _Save_ to save the view. -. Go back to the home page and click Recipes in the navigation to view the new -Recipes page. +. Go back to the home page and click Recipes in the navigation to view the new Recipes page. + -- // Completed recipes view output. @@ -119,9 +86,7 @@ image:images/views-duplicate_final.png["Recipes view",width="100%"] ==== Expand your understanding -The link to the view in the main navigation will probably not be in the right -place. Change the order of the menu items in the main navigation. See -<>. +The link to the view in the main navigation will probably not be in the right place. Change the order of the menu items in the main navigation. See <>. ==== Related concepts diff --git a/source/hu/views-parts.txt b/source/hu/views-parts.txt index 8f3cc98..1d3947e 100644 --- a/source/hu/views-parts.txt +++ b/source/hu/views-parts.txt @@ -31,13 +31,10 @@ Overview of the administrative parts of a view. ==== What are the parts of a view? -When you are editing a view in the administrative interface, you will see the -following parts (or sections), which allow you to specify what data to output, -in what order, and in what format: +When you are editing a view in the administrative interface, you will see the following parts (or sections), which allow you to specify what data to output, in what order, and in what format: Display:: - Each view can have one or more displays, each of which produces one type of - output. Options for display types include: + Each view can have one or more displays, each of which produces one type of output. Options for display types include: Page;; Makes output at a particular URL, for the main page content at that URL. Block;; @@ -47,40 +44,18 @@ Display:: Attachment;; Makes output that you can attach to another display. Format:: - Depending on the display type, you can choose to output your data in a - table, grid, HTML list, or another format. Some formats also give you a - second choice that lets you output either rendered entities or fields; other - formats do not give you this choice (for example, if you use a table format, - you must always use fields). + Depending on the display type, you can choose to output your data in a table, grid, HTML list, or another format. Some formats also give you a second choice that lets you output either rendered entities or fields; other formats do not give you this choice (for example, if you use a table format, you must always use fields). Fields:: - Depending on the format choice, you may be able to choose which content fields - are output. For example, if you were making a view of recipe content items, in - a block display you might show only the recipe names, while in a full page - display you might also show an image field because you have more space. + Depending on the format choice, you may be able to choose which content fields are output. For example, if you were making a view of recipe content items, in a block display you might show only the recipe names, while in a full page display you might also show an image field because you have more space. Filter criteria:: - Filters limit the data to be output, based on criteria such as whether the - content has been published or not, the type of content, or a field value. - For instance, to make a view of recipe content items, you would need to filter - to the Recipe content type, and to published recipes. Filters can also be - _exposed_, which means that users will have a form where they can choose - their own filter values. You might use this on a Recipe page to let users - filter for recipes with certain ingredients. + Filters limit the data to be output, based on criteria such as whether the content has been published or not, the type of content, or a field value. + For instance, to make a view of recipe content items, you would need to filter to the Recipe content type, and to published recipes. Filters can also be _exposed_, which means that users will have a form where they can choose their own filter values. You might use this on a Recipe page to let users filter for recipes with certain ingredients. Sort criteria:: - Defines the order to present the output, which can be based on any content - field. + Defines the order to present the output, which can be based on any content field. Contextual filters:: - Contextual filters are like regular filters, except that the values come from - the _context_ of the view display, such as the full URL of the page being - displayed, the current date or time, or some other value that can be - detected by the view calculation. + Contextual filters are like regular filters, except that the values come from the _context_ of the view display, such as the full URL of the page being displayed, the current date or time, or some other value that can be detected by the view calculation. Relationships:: - Relationships allow you to expand what is displayed in your view, by relating - the base content being displayed to other content entities. Relationships are - created using fields on the base content that relate it to the other content; - one example is that all regular content items have an author field, which - references the user account of the person who authored the content. Once you - have created a relationship, you can display fields from the referenced - entity in the view. + Relationships allow you to expand what is displayed in your view, by relating the base content being displayed to other content entities. Relationships are created using fields on the base content that relate it to the other content; one example is that all regular content items have an author field, which references the user account of the person who authored the content. Once you have created a relationship, you can display fields from the referenced entity in the view. ==== Related topics