the menu hierarchy. For example, if you choose

, the page will appear in the highest level of the navigation. By choosing another menu item as parent, you can create a menu hierarchy of multiple levels. Weight The order in which the page -2 should appear in the menu (lower-weighted menu items will be shown before higher-weighted menu items) 6. Click Save and keep published to save the changes. Click Home or Return to site in the navigation bar to see the result, which could look like the picture below. 58 Manajemen Dasar Halaman Expand your understanding Bagian 5.8, “Changing the Order of Navigation” Additional resources Drupal.org community documentation page "Working with menus" Attributions Adapted by Boris Doesborg from "Working with Menus", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation; edited by Jack Haas. 5.8. Changing the Order of Navigation Goal Reorder the items in a menu. Prerequisite knowledge • Bagian 5.6, “Concept: Menu” • Bagian 5.7, “Adding a Page to the Navigation” Site prerequisites Home and About pages must exist in the main navigation menu. See Bagian 5.7, “Adding a Page to the Navigation”. 59 Manajemen Dasar Halaman Steps 1. In the Manage administrative menu, navigate to Structure > Menus (admin/structure/ menu) where all menus on your site are listed. Click Edit Menu from the Operations dropdown for Main navigation. You can also reach this page using contextual links (refer to Bagian 4.1, “Concept: Administrative Overview”) for the menu. 2. The Edit menu page will display a list of each item in the menu you chose (Main navigation). 3. Use the cross bar handles to reorder the menu items. Drag the Home menu item above the About menu item so that it appears first. 4. Click Save. 5. The home page now displays the main navigation with the Home menu item displayed first. 60 Manajemen Dasar Halaman Expand your understanding Add a menu item called Contact, leading to the /contact page, to your Main navigation menu. The contact page is provided by the core Contact module; you may want to edit its layout and fields (see Bagian 6.9, “Changing Content Entry Forms”). Related concepts Bagian 5.6, “Concept: Menu” Attributions Written by Ann Greazel. 61 Bab 6. Menyiapkan Struktur Konten 6.1. Adding a Content Type Goal Add and configure a new content type Vendor. Prerequisite knowledge Bagian 2.3, “Concept: Content Entities and Fields” Site prerequisites You need to have a plan in place for your content structure. See Bagian 2.5, “Planning your Content Structure”. Steps 1. In the Manage administrative menu, navigate to Structure > Content types (admin/ structure/types). The Content types page appears showing all the available types of content. 2. Click Add content type. The Add content type page appears. Fill in the fields as shown below. Field name Explanation Example value Name Name of the content type Vendor Description Explain the use of the content type Information about a vendor 62 Menyiapkan Struktur Konten 3. In the vertical tab Submission form settings, configure the form that is used for creating and editing content of this type. Fill in the fields as shown below. Field name Explanation Example value Title field label Label of the Title field that is shown when editing or creating content of this type. Vendor name Preview before submitting Option to choose whether Optional you should preview the content before submitting. Explanation or submission guidelines Instructions for creating or (Leave blank) editing content. 4. In the vertical tab Publishing options, decide on default options for new content of this type. Fill in the fields as shown below. Field name Explanation Example value Published Make the content item published by default. Checked Promoted to front page In a default website, this Unchecked setting can be used to show content on the homepage. Sticky at top of lists In a default website, this Unchecked setting can be used to keep content on top of a list. 63 Menyiapkan Struktur Konten Field name Explanation Example value Create new revision Create a new revision each time the vendor is being edited. Checked Changing these settings does not affect the content items that have already been created. 5. In the vertical tab Display settings, decide if the author and publication date will be visible in the content item. Fill in the fields as shown below. Field name Explanation Example value Display author and date information Display the author username and publication date on each vendor page. Unchecked 6. In the vertical tab Menu settings, fill in the fields as shown below. Field name Explanation Example value Available menus Menus that this type of content can be added to. Vendors do not need to appear in menus, so uncheck all menu options. Unchecked 64 Menyiapkan Struktur Konten 7. Click Save and manage fields to save the content type. The Manage fields page appears that allows you to add fields to the content type. See Bagian 6.3, “Adding Basic Fields to a Content Type” 8. Follow the same steps to create a content type for recipes. Example values for the fields in the forms, where they are different from the steps above: Field name Example value Name Recipe Description A recipe submitted by a vendor Submission form settings - Title Recipe name Expand your understanding • Bagian 6.3, “Adding Basic Fields to a Content Type” • Install and configure the contributed Pathauto module so that content items get automatically generated URLs/path aliases. See Bagian 5.1, “Concept: Paths, Aliases, and URLs” for more on URLs within your site, Bagian 11.1, “Finding Modules” for instructions on finding contributed modules, and Bagian 11.3, “Downloading and Installing a Module from Drupal.org” for instructions on downloading and installing contributed modules. 65 Menyiapkan Struktur Konten Attributions Written and edited by Sree Veturi, Boris Doesborg, and Jennifer Hodgdon. 6.2. Deleting a Content Type Goal Delete the unneeded content type Article. Prerequisite knowledge Bagian 4.1, “Concept: Administrative Overview” Site prerequisites The Article content type must exist. It is created on your site when you install with the core Standard installation profile. Steps 1. In the Manage administrative menu, navigate to Structure > Content types (admin/ structure/types). The Content types page appears. 2. Click Delete in the Operations dropdown button for the Article content type. 3. A confirmation page is displayed. Click Delete. 66 Menyiapkan Struktur Konten 4. The Content types page appears with a confirmation message saying that the content type has been deleted: Attributions Written and edited by Sree Veturi and Boris Doesborg. 6.3. Adding Basic Fields to a Content Type Goal Add a link field and an image field to the Vendor content type. Prerequisite knowledge Bagian 2.3, “Concept: Content Entities and Fields” 67 Menyiapkan Struktur Konten Site prerequisites The Vendor content type must exist. See Bagian 6.1, “Adding a Content Type”. Steps Add the fields Vendor URL and Main image to the Vendor content type. 1. In the Manage administrative menu, navigate to Structure > Content types (admin/ structure/types). Then click Manage fields in the dropdown button for the Vendor content type. The Manage fields page appears. 2. Click Add field. The Add field page appears. You can either create a new field for the content type or re-use an existing field. 3. Fill in the fields as shown below. Field name Explanation Value Add a new field Field type Link Label Label that is visible in administration pages Vendor URL A machine name is automatically generated, based on the Label value. Click Edit if you want to override the default name. 4. Click Save and continue. The page Vendor URL appears which lets you set the allowed number of values. Fill in the fields as shown below. Field name Explanation Value Allowed number of values The number of values that can be entered Limited, 1 5. Click Save field settings. The page Vendor URL settings for Basic page appears which allows you to configure the field. Fill in the fields as shown below. 68 Menyiapkan Struktur Konten Field name Explanation Value Label Label that is visible in the content form Vendor URL Help text The instruction that is shown below the field (leave blank) Required field Whether the field is required or not Unchecked Allowed link type The kind of links that can be External links only entered Allow link text Whether a link text can be entered Disabled 6. Click Save settings. The Vendor URL has been added to the content type. Continue creating the Main image field. 7. Click Add field. The Add field page appears. Fill in the fields as shown below. Field name Explanation Value Add a new field Field type Image Label Label that is visible in administration pages Main image 8. Click Save and continue. The page Main image appears. Fill in the fields as shown below. 69 Menyiapkan Struktur Konten Field name Explanation Value Allowed number of values The number of values that can be entered Limited, 1 You can set a default image here. This will be used when you do not provide an image when creating a Vendor content item. 9. Click Save field settings. The page Main image settings for Basic page appears. Fill in the fields as shown below. Field name Explanation Value Label Label that is visible in the content form Main image Help text The instruction that is shown below the field (leave blank) Required field Whether the field is required or not Checked Allowed file extensions The type of images that can png, gif, jpg, jpeg be uploaded File directory The directory where the files will be stored. By providing a file directory value, you ensure that all images uploaded via the Main image field will be located in the same directory. vendors Minimum image resolution The minimum resolution of 600 x 600 the uploaded image Maximum upload size The maximum file size of the uploaded image Enable Alt field Whether an alternative text Checked can be entered Alt field required Whether an alternative text Checked is required 70 5 MB Menyiapkan Struktur Konten 10. Click Save settings. Main image has been added to the content type. 11. Add a Main image field to the Recipe content type, using similar steps. Start by navigating to the Recipe content type’s Manage Fields page in step 1. Then skip to step 7 and follow the remaining steps, but reuse the existing Main image field you created for the Vendor content type rather than creating a new field. In subsequent steps, some of the configuration screens will not be available, because of the field reuse. 12. Create two Vendor content items (see Bagian 5.2, “Creating a Content Item”) called "Happy Farm" and "Sweet Honey". Make sure that they include images and URLs. 71 Menyiapkan Struktur Konten Expand your understanding • Bagian 6.12, “Concept: Image Styles” • Bagian 6.11, “Changing Content Display” • Bagian 6.9, “Changing Content Entry Forms” Additional resources Drupal.org community documentation page "Add a field to a content type" Attributions Written by Sree Veturi and Boris Doesborg. 6.4. Concept: Reference Fields Prerequisite knowledge Bagian 2.3, “Concept: Content Entities and Fields” What is a reference field? A reference field is a field that represents a relationship between an entity and one or more other entities, which may belong to the same or different entity type. The three most commonly-used reference fields are: Content reference A reference to a content item. For example, you might want to connect recipes to the vendors who submitted them. You would set up a content reference field called Submitted by referencing Vendor content items on the Recipe content type. Taxonomy term reference A reference to a taxonomy term. For example, you might want to connect recipes to their ingredients. You would set up a taxonomy term reference field called Ingredients on the Recipe content type. This reference field will point to the vocabulary Ingredients. User reference A reference to a user account. For example, you might want to connect recipes with their chefs. You would set up a user reference field called Chefs on the Recipe content type. 72 Menyiapkan Struktur Konten Related topics Bagian 6.5, “Concept: Taxonomy” Attributions Written and edited by Surendra Mohan, and Jojy Alphonso at Red Crackle. 6.5. Concept: Taxonomy Prerequisite knowledge • Bagian 2.3, “Concept: Content Entities and Fields” • Bagian 6.4, “Concept: Reference Fields” What is Taxonomy? Taxonomy is used to classify website content. One common example of taxonomy is the tags used to classify or categorize posts in a blog website; the farmers market website could use an ingredients taxonomy to classify recipes. Individual taxonomy items are known as terms (the blog tags or recipe ingredients in these examples); and a set of terms is known as a vocabulary (the set of all blog post tags, or the set of all recipe ingredients in these examples). Technically, taxonomy terms are an entity type and the entity subtypes are the vocabularies. Like other entities, taxonomy terms can have fields attached; for instance, you could set up an image field to contain an icon for each term. An individual vocabulary can organize its terms in a hierarchy, or it could be flat. For example, blog tags normally have a flat structure, while a recipe ingredients vocabulary could be hierarchical (for example, tomatoes could be a sub-term of vegetables, and under tomatoes, you could have green and red tomatoes). Taxonomy terms are normally attached as reference fields to other content entities, which is how you can use them to classify content. When you set up a taxonomy reference field, you can let users enter terms in two ways: Free tagging New terms can be created right on the content editing form. Fixed list of terms The list of terms is curated and managed outside the content editing form, and users can only choose from the existing list when editing content. 73 Menyiapkan Struktur Konten Taxonomy reference fields can be added to any entity, such as user accounts, custom blocks, or regular content items. If you use them to classify regular content items, your site will automatically be set up with taxonomy listing pages for each term; each of these pages lists all of the content items that are classified with that term. For example, if you created several recipes that all had carrots as an ingredient, you might see something like this on the Carrots taxonomy listing page: Related topics • Bagian 6.6, “Setting Up a Taxonomy”. • The listing pages are views, which are covered in Bab 9, Membuat Daftar dengan Views. Attributions Adapted and edited by Surendra Mohan, Jennifer Hodgdon, and Jojy Alphonso at Red Crackle from "Organizing content with taxonomies" and "About taxonomies", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 6.6. Setting Up a Taxonomy Goal Create an Ingredients vocabulary and add it to the Recipe content type as a field that can contain an unlimited number of values and that allows adding new terms to the vocabulary. Prerequisite knowledge • Bagian 2.3, “Concept: Content Entities and Fields” • Bagian 6.5, “Concept: Taxonomy” • Bagian 6.3, “Adding Basic Fields to a Content Type” 74 Menyiapkan Struktur Konten Site prerequisites The Recipe content type must exist. See Bagian 6.1, “Adding a Content Type”. Steps 1. In the Manage administrative menu, navigate to Structure > Taxonomy (admin/structure/ taxonomy). You will see the Tags vocabulary that was created with the core Standard installation profile. 2. Click Add vocabulary, and fill in the values below. Field name Explanation Example value Name The name of the vocabulary Ingredients Description A brief note about the vocabulary (Leave blank) 3. Click Save. You will be taken to the Ingredients page, which shows a list of all the terms in this vocabulary. 75 Menyiapkan Struktur Konten 4. Click Add term. Enter "Butter" in the Name field. Click Save. 76 Menyiapkan Struktur Konten 5. You will receive a confirmation about the term you created. Add more terms. For example, "Eggs" and "Milk". 6. In the Manage administrative menu, navigate to Structure > Content Types (admin/ structure/types). Click Manage fields for your Recipe content type. 7. Click Add field, and enter values from the table below. Click Save and continue. Field name Explanation Value Add a new field Select the field type Reference > Taxonomy term Label The title to give the field Ingredients 77 Menyiapkan Struktur Konten 8. On the following configuration screen, enter the values from the table below. Click Save field settings. Field name Explanation Value Type of item to reference The type of entity that is referenced by the field Taxonomy term Allowed number of values The number of values a user can enter Unlimited 9. On the following configuration screen, enter the values from the table below. Click Save settings. Field name Explanation Value Help text Help shown to users creating content Enter ingredients that site visitors might want to search for Reference type > Reference Select the method used to method choose allowed values Default Reference type > Available Vocabularies Select the vocabulary to Ingredients choose allowed values from Reference type > Create referenced entities if they don’t already exist Whether new ingredient terms can be created from the content editing form 78 Checked Menyiapkan Struktur Konten 10. Click Save settings. You will be taken back to the Manage Fields page. A message will be displayed saying that the configuration for Ingredients is complete. Attributions Written and edited by Bob Snodgrass, and Jojy Alphonso at Red Crackle. 6.7. Adding a Reference Field Goal Add a reference field so that recipes can be linked to the vendor that has submitted it. 79 Menyiapkan Struktur Konten Prerequisite knowledge • Bagian 6.3, “Adding Basic Fields to a Content Type” • Bagian 6.4, “Concept: Reference Fields” • Bagian 6.1, “Adding a Content Type” Site prerequisites The Recipe and Vendor content types must exist. See Bagian 6.1, “Adding a Content Type”. Steps 1. In the Manage administrative menu, navigate to Structure > Content types (admin/ structure/types). Then click Manage fields in the dropdown button for the Recipe content type. The Manage fields page appears. 2. Click Add field. The Add field page appears. Fill in the fields as shown below. Click Save and continue. Field name Explanation Value Add a new field Option to specify the field type Reference > Content Label The title you want to give the field Submitted by 3. The page Submitted by appears which lets you set the allowed number of values. Fill in the fields as shown below. Click Save field settings. Field name Explanation Type of item to reference Option to select the type of Content referenced item Allowed number of values Specify the count of values associated with the field 80 Value Limited, 1 Menyiapkan Struktur Konten 4. The page Submitted by settings for Recipe appears which allows you to configure the field. Fill in the fields as shown below. Click Save settings. Field name Explanation Label Title shown for this field on Submitted by the page Help text Brief text aiding the person Choose the vendor that creating content submitted this recipe Required field Whether a value has to be provided or not Checked Reference method Option to select reference method Default Content types Specify the content type Vendor Sort by Sorting field Title Sort direction Sorting order Ascending 81 Value Menyiapkan Struktur Konten 5. The Submitted by field has been added to the content type. Attributions Written and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle. 82 Menyiapkan Struktur Konten 6.8. Concept: Forms and Widgets Prerequisite knowledge Bagian 2.3, “Concept: Content Entities and Fields” What are forms and widgets? The content management system software that your site is running allows administrators to edit content and configure settings online, using various web forms. In particular, content editing forms are used to edit your site’s content, and they are configurable by administrators; settings configuration forms are provided by modules and cannot themselves be configured. The data in your site’s content is stored in one or more fields that are attached to the content type and/or sub-type. When you configure the content editing form for each content subtype, you can: • Select a widget for each field. A widget defines the method used to enter the data for the field. For example, a taxonomy term can be chosen using an autocomplete field, a select list, or a tags-style field that lets editors add new tags automatically. • Configure widget settings. For example, you can choose the size of a plain-text entry field. • Hide one or more fields from the editing form. • Reorder the fields. In principle, you can also have multiple content editing forms available for each content subtype. This feature is rarely used, however; the only exception in common use is for the user profile fields: you can use different forms for user registration and user editing. For example, you might have a limited set of fields shown when users first register on the site, and more fields shown later on when they edit their profiles. Related topics • Bagian 6.9, “Changing Content Entry Forms” • Bagian 6.10, “Concept: View Modes and Formatters” Attributions Written by Jennifer Hodgdon. 6.9. Changing Content Entry Forms Goal Change the Recipe form to use a different widget to enter terms in the Ingredients field. 83 Menyiapkan Struktur Konten Prerequisite knowledge • Bagian 6.1, “Adding a Content Type” • Bagian 6.3, “Adding Basic Fields to a Content Type” • Bagian 6.5, “Concept: Taxonomy” • Bagian 6.8, “Concept: Forms and Widgets” Site prerequisites The Recipe content type must exist, and it must have an Ingredients taxonomy term reference field. See Bagian 6.1, “Adding a Content Type” and Bagian 6.6, “Setting Up a Taxonomy”. Steps 1. In the Manage administrative menu, navigate to Content > Add content > Recipe (node/ add/recipe) to look at the content entry form that is set up by default. Notice how you have to enter ingredients one by one, instead of having a more compact format. 2. In the Manage administrative menu, navigate to Structure > Content types (admin/ structure/types). Then click Manage form display on the dropdown button for the Recipe content type. The Manage form display page appears. 3. For the Ingredients field, select Autocomplete (Tags style) in the Widget column. 84 Menyiapkan Struktur Konten 4. Click Save. 5. In the Manage administrative menu, navigate to Content > Add content > Recipe (node/ add/recipe) to verify the changed behavior of the content form. The Ingredients field is now a single text field that accepts multiple values. 85 Menyiapkan Struktur Konten 6. Create two Recipe content items (see Bagian 5.2, “Creating a Content Item”), such as recipes for "Green Salad" and "Fresh Carrots". Make sure all the fields have values, including images, ingredients, and submitted by (set this to one of the Vendor content items you created in Bagian 6.3, “Adding Basic Fields to a Content Type”). Expand your understanding Change the main site Contact form by navigating in the Manage administrative menu to Structure > Contact forms. For instance, you may want to hide the Send yourself a copy or Language fields. Attributions Written by Boris Doesborg. 6.10. Concept: View Modes and Formatters Prerequisite knowledge Bagian 6.1, “Adding a Content Type” 86 Menyiapkan Struktur Konten What is a View mode? How an entity (such as content, a user or a comment) is displayed, depends on the context in which it is shown. This context is known as a view mode. Examples of view modes are: • a full page of the content with all the field values • a teaser of the content with a thumbnail image and a Read more link • a full user profile with a zoomable portrait photo • a user avatar with username and a link to the profile Every view mode can be configured through the administration pages. To see the configuration options for the view modes of the Recipe content type, navigate in the Manage administrative menu to Structure > Content types (admin/structure/types) and click Manage display from the dropdown button. In each view mode, all fields can be hidden or displayed, and if they are displayed, you can choose and configure the field formatter. What is a field formatter? A field formatter is a setting for displaying the field values. For example, long text fields can be displayed trimmed or full-length, and taxonomy term reference fields can be displayed in plain text or linked to the taxonomy term page. Consult the Manage display page to see the field formatters for the fields of the Recipe content type. Related topics • Bagian 6.1, “Adding a Content Type” • Bagian 6.11, “Changing Content Display” Additional resources Drupal.org community documentation page "View modes" Attributions Adapted by Boris Doesborg from "View modes", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 6.11. Changing Content Display Goal Make the content items more readable, accessible, and visibly attractive by reordering the fields, hiding labels, and tuning the output of the fields. 87 Menyiapkan Struktur Konten Prerequisite knowledge • Bagian 2.3, “Concept: Content Entities and Fields” • Bagian 6.10, “Concept: View Modes and Formatters” Site prerequisites The Vendor content type must exist, it must have Main Image and Vendor URL fields, and your site must have at least one Vendor content item. See Bagian 6.1, “Adding a Content Type”, Bagian 6.3, “Adding Basic Fields to a Content Type”, and Bagian 5.2, “Creating a Content Item”. Steps 1. Find and view a Vendor content item you created in Bagian 6.3, “Adding Basic Fields to a Content Type”. Notice that there are several things that could be done to improve how the page looks: • The Main Image and Vendor URL fields should not have labels. • The order of the fields should be changed so that the image comes first. • The image should be smaller. 2. To fix the first two problems, and update some additional settings, in the Manage administrative menu, navigate to Structure > Content types (admin/structure/types). Then click Manage display in the dropdown button for the Vendor content type. 3. Under the Label column, select Hidden for Main image. Do the same for Vendor URL. 88 Menyiapkan Struktur Konten 4. Click the gear for the Vendor URL field. Clear the Trim link text length setting. Links will no longer have a trim length. Check the Open link in new window checkbox. Now, when the link is clicked, it will open in a new browser window. Click Update. 5. Drag the cross arrows next to the field items to reorder as Main image, Body, Vendor URL, and Links. 89 Menyiapkan Struktur Konten 6. Click Save. 7. Find the Vendor content item from step 1 again, and verify that the updates have been made. 8. Repeat similar steps to manage the display of the Recipe content type fields. Expand your understanding • Make the main image smaller. See Bagian 6.13, “Setting Up an Image Style”. • If you do not see the effect of these changes in your site, you might need to clear the cache. See Bagian 12.2, “Clearing the Cache”. Related concepts Bagian 6.12, “Concept: Image Styles” Additional resources • Drupal.org community documentation page "Specify how fields are displayed" • Drupal.org community documentation page "Rearrange the order of fields" • Drupal.org community documentation page "View modes" Attributions Written by Ann Greazel and Boris Doesborg. 6.12. Concept: Image Styles Prerequisite knowledge Bagian 6.3, “Adding Basic Fields to a Content Type” 90 Menyiapkan Struktur Konten What are image styles? Image styles allow you to upload a single image but display it in several ways; each display variation, or image style, is the result of applying one or more effects to the original image. As an example, you might upload a high-resolution image with a 4:3 aspect ratio, and display it scaled down, square cropped, or black-and-white (or any combination of these effects). The core software provides a way to do this efficiently: 1. Configure an image style with the desired effects on the Image styles page (admin/config/ media/image-styles). 2. The effects will be applied the first time a particular image is requested in that style. 3. The resulting image is saved. 4. The next time that same style is requested, the saved image is retrieved without the need to recalculate the effects. The core software provides several effects that you can use to define styles; others may be provided by contributed modules. Visit the Image styles page via the Manage administrative menu, navigate to Configuration > Media > Image styles (admin/config/media/image-styles) to see the image styles that are defined by default. Related topics • Bagian 6.13, “Setting Up an Image Style” • Bagian 6.14, “Concept: Responsive Image Styles” • Bagian 6.3, “Adding Basic Fields to a Content Type” Additional resources Drupal.org community documentation page "Working with images in Drupal 7 and 8" Attributions Adapted and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle, from "Working with images in Drupal 7 and 8", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation 6.13. Setting Up an Image Style Goal Add an image style and use it to display images on Vendor pages. 91 Menyiapkan Struktur Konten Prerequisite knowledge • Bagian 6.3, “Adding Basic Fields to a Content Type” • Bagian 6.11, “Changing Content Display” • Bagian 6.12, “Concept: Image Styles” Site prerequisites • Vendor and Recipe content types must exist. See Bagian 6.1, “Adding a Content Type”. • Main image fields must exist for both content types. See Bagian 6.3, “Adding Basic Fields to a Content Type”. • Content items must exist for both content types. See Bagian 6.1, “Adding a Content Type”, Bagian 6.3, “Adding Basic Fields to a Content Type”, and Bagian 5.2, “Creating a Content Item”. Steps 1. In the Manage administrative menu, navigate to Configuration > Media > Image styles (admin/config/media/image-styles). 2. Click Add image style. 3. Enter the name Extra medium (300x200) 4. Click Create new style. The page Edit style Extra medium (300x200) appears. 5. In the Effect table, select Scale and crop. Click Add. 6. Fill in the fields as shown below. Field name Value Width 300 Height 200 7. Click Add effect. The image style is saved with the chosen effects. 92 Menyiapkan Struktur Konten 8. In the Manage administrative menu, navigate to Structure > Content types (admin/ structure/types). 9. Click Manage display in the Operations dropdown for the Vendor content type. The Manage display page (admin/structure/types/manage/vendor/display) appears. 10. Ensure that the secondary tab Default is selected. 11. Click the cogwheel next to Main image for the configuration options. 12. Fill in the fields as shown below. Field name Value Image style Extra medium (300x200) Link image to Nothing 93 Menyiapkan Struktur Konten 13. Click Update. 14. Click Save. The new image style will be used while displaying Vendor content. 15. Open a Vendor content item and verify that it now shows up with the scaled-down image. See Bagian 5.3, “Editing a Content Item” for information on how to locate an existing content item. 16. Repeat steps 8-15 for the Recipe content type. Related concepts • Bagian 6.3, “Adding Basic Fields to a Content Type” • Bagian 6.12, “Concept: Image Styles” • Bagian 6.14, “Concept: Responsive Image Styles” Additional resources Drupal.org community documentation page "Working with images in Drupal 7 and 8" Attributions Adapted and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle from "Working with images in Drupal 7 and 8", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 6.14. Concept: Responsive Image Styles Prerequisite knowledge • Bagian 1.3, “Concept: Themes” 94 Menyiapkan Struktur Konten • Bagian 6.11, “Changing Content Display” • Bagian 6.12, “Concept: Image Styles” What are responsive image styles? The core Responsive Image module provides responsive image styles. This allows you to have images in your website that are specifically sized for different screen sizes. This is useful, for example, to make your site load faster on mobile devices because image sizes are optimized for smaller screens. A responsive image style is a mapping between images styles and breakpoints. Breakpoints are the points where a responsive design needs to change in order to respond to different screen sizes. Responsive image styles can only be used if the breakpoints are defined in the theme. When a responsive image style is defined, it can be used in the display settings for Image fields. This allows the site to display responsive images using the HTML5 picture tag. Related topics Bagian 6.3, “Adding Basic Fields to a Content Type” Additional resources • Drupal.org community documentation page "Responsive web design" • Drupal.org community documentation page "Responsive images in Drupal 8" • Drupal.org community documentation page "Working with breakpoints in Drupal 8" Attributions Adapted by Boris Doesborg from Responsive images in Drupal 8, copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 6.15. Concept: Text Formats and Editors What are text formats and filters? Text formats change how HTML tags and other text are processed and displayed on your site. Text formats are composed of a series of filters, each of which transforms text. When users create content, a text format is associated with the content, and the full, original text is stored in the database. The content is then passed through the filters in the text format before it becomes output on the site. The core Filter module provides text format functionality, and the core Standard installation profile sets up Basic HTML, Restricted HTML, and Full HTML text formats. Each text format 95 Menyiapkan Struktur Konten has an associated permission, so that you can allow only trusted users to use permissive text formats. This restricts untrusted users to text formats like Basic HTML, which filters out dangerous HTML tags. What are the editors associated with text formats? Each text format can be associated with an editor, such as a visual WYSIWYG (What You See Is What You Get) HTML editor. The core Text Editor module provides the ability to associate editors with text formats, and to configure the editors (such as adding and removing buttons from their toolbars). The core CKEditor module provides the industry-standard editor known as CKEditor, so that it can be used to edit HTML content on your site. What is cross-site scripting? Cross-site scripting (XSS) is a security vulnerability typically found in websites. In a site that is not well protected, malicious users can enter script into web pages that are viewed by other users (for example, in a comment or in the body of a page). A cross-site scripting vulnerability may be used by attackers to login as another user. It is important to configure the text formats of your website to prevent such abuse. Related topics Bagian 13.3, “Concept: Security and Regular Updates” Additional resources • Drupal.org community documentation page "Filter module: text formats that filter user input" • Wikipedia page "Cross-site scripting" Attributions Written and edited by Boris Doesborg and Jennifer Hodgdon. 6.16. Configuring Text Formats and Editors Goal Add a horizontal rule tag to the Basic HTML text format, and a corresponding button to its editor configuration. Prerequisite knowledge Bagian 6.15, “Concept: Text Formats and Editors” 96 Menyiapkan Struktur Konten Site prerequisites • The core Filter, Editor, and CKEditor modules must be installed. They are installed on your site when you install with the core Standard installation profile. • The Basic HTML text format must exist. This is created on your site when you install with the core Standard installation profile. Steps 1. In the Manage administrative menu, navigate to Configuration > Content authoring > Text formats and editors (admin/config/content/formats). The Text formats and editors page appears. 2. Click Configure for the Basic HTML text format. The Basic HTML page appears. 3. Note that CKEditor is selected in the Text editor field. This allows you to configure the editor’s toolbar. 4. Drag the horizontal rule button from Available buttons to Tools in Active toolbar. You may need to click the Show group names link to see the Tools group name. 5. Note that you can change the Filter processing order. 6. In the field Allowed HTML tags, add

---

to what is already present. 7. Click Save configuration. You will be taken back to the Text formats and editors page. A message will be displayed saying that the text format has been updated. 97 Menyiapkan Struktur Konten Expand your understanding If you do not see the effect of these changes in your site, you might need to clear the cache. See Bagian 12.2, “Clearing the Cache”. Attributions Written by Boris Doesborg. 98 Bab 7. Mengelola Akun Pengguna 7.1. Concept: Users, Roles, and Permissions What are 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 Bagian 7.2, “Concept: The User 1 Account”. 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. 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. 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: • A Vendor role that allows vendors to edit their own vendor listing page • A Content editor role for editing the general farmers market pages • A User manager role for managing the vendor accounts 99 Mengelola Akun Pengguna • The Administrator role that was installed with your site, for expert users to manage the site configuration Related topics • Bagian 7.3, “Creating a Role” • Bagian 7.5, “Assigning Permissions to a Role” • Bagian 7.6, “Changing a User’s Roles” • Bagian 7.4, “Creating a User Account” • Bagian 7.2, “Concept: The User 1 Account” • Bagian 7.7, “Assigning Authors to Content” Additional resources • Drupal.org community documentation page "Users, roles and permissions" • Drupal.org community documentation page "Managing Users" • Drupal.org community documentation page "User Roles" Attributions Adapted by Mark LaCroix, Boris Doesborg, and Jennifer Hodgdon from "User Roles", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 7.2. Concept: The User 1 Account Prerequisite knowledge Bagian 7.1, “Concept: Users, Roles, and Permissions” 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. 100 Mengelola Akun Pengguna 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. Additional resources Drupal.org community documentation page "Accounts and roles" Attributions Written and edited by Mark LaCroix and Jennifer Hodgdon. 7.3. Creating a Role Goal Create a Vendor role to allow some - but not all - users to perform specific tasks. Prerequisite knowledge Bagian 7.1, “Concept: Users, Roles, and Permissions” Steps 1. In the Manage administrative menu, navigate to People > Roles (admin/people/roles). 2. You will find default roles Anonymous user, Authenticated user, and Administrator already present. 101 Mengelola Akun Pengguna 3. Click Add Role to add a custom role. 4. Type Vendor in the Role name field. Click Save. 5. You will see the message "Role Vendor has been added." displayed at the top of the page. Expand your understanding • Bagian 7.5, “Assigning Permissions to a Role” • Bagian 7.6, “Changing a User’s Roles” 102 Mengelola Akun Pengguna Additional resources Drupal.org community documentation page "User Roles" Attributions Adapted and edited by Jack Probst, Boris Doesborg, and Joe Shindelar from "User Roles", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation 7.4. Creating a User Account Goal Create Vendor user accounts for Sweet Honey and Happy Farm vendors. Prerequisite knowledge • Bagian 7.1, “Concept: Users, Roles, and Permissions” • Bagian 7.2, “Concept: The User 1 Account” • Bagian 7.3, “Creating a Role” Site prerequisites The Vendor role must exist on your site. See Bagian 7.3, “Creating a Role”. Steps 1. In the Manage administrative menu, navigate to People (admin/people). 2. Click Add user. 103 Mengelola Akun Pengguna 3. Fill in the form fields. See the table below. Field name Explanation Email address A valid email address for honey@example.com the vendor. All emails from the system will be sent to this address. The email address is not made public. Username A username for the Sweet Honey vendor that they will use to sign in or author content items. Spaces are allowed; punctuation is not allowed except for periods, 104 Example value Mengelola Akun Pengguna Field name Explanation Example value hyphens, apostrophes, and underscores. Password A password the vendor (Make a secure password) will use to sign in to the site. You can see how safe the password is on the Password strength gauge. You also get tips on how to make it safer. Confirm password Type the same password to (Repeat password) avoid any typing mistakes. Status Set the status of the user account. Blocked users will not be able to sign in. Active Roles Set the role of the user account. Vendor Notify user of new account Whether or not to send a notification to the vendor’s email address. Checked Picture Click Browse and select a picture to upload. Pay attention to size restrictions. Photo of the vendor Contact settings Enable or disable the display of a contact form for the account. Checked 4. Click Create new account. You will get a notification about the user account creation. 5. Create a second Vendor account for Happy Farm by following the steps above. Expand your understanding Create a user account for yourself. Attributions Written by Diána Lakatos at Pronovix. 105 Mengelola Akun Pengguna 7.5. Assigning Permissions 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. Prerequisite knowledge • Bagian 7.1, “Concept: Users, Roles, and Permissions” Site prerequisites The Vendor role must exist on your site. See Bagian 7.3, “Creating a Role”. Steps 1. In the Manage administrative menu, navigate to People > Roles (admin/people/roles). The Roles page appears. 2. 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 Administer blocks. 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. 3. Check the boxes for the following permissions, listed by module: Module Permission Contact Use users' personal contact forms Filter Use the Restricted HTML text format Node Recipe: Create new content Node Recipe: Edit own content Node Recipe: Delete own content Node Vendor: Edit own content Quick Edit Access in-place editing 106 Mengelola Akun Pengguna 4. Click Save permissions. You will get a message saying your changes have been saved. Expand your understanding • Log in as one of the new users you created in Bagian 7.4, “Creating a User Account”. Verify whether you have the correct permissions. 107 Mengelola Akun Pengguna • Bagian 7.6, “Changing a User’s Roles” Related concepts Bagian 7.2, “Concept: The User 1 Account” Additional resources Drupal.org community documentation page "Managing Users" Attributions Adapted and edited by Boris Doesborg, Brian Emery, and Jojy Alphonso at Red Crackle, from "User Roles", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 7.6. Changing a User’s Roles Goal Change or add roles to a given user, either by editing a single-user or by applying a bulk operation. Prerequisite knowledge Bagian 7.1, “Concept: Users, Roles, and Permissions” Site prerequisites The user account that you want to update, and the role you want it to have, must already exist. See Bagian 7.4, “Creating a User Account”, Bagian 7.3, “Creating a Role”, and Bagian 7.5, “Assigning Permissions to a Role”. Steps Updating the roles using single-user editing method 1. In the Manage administrative menu, navigate to People (admin/people). 2. 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. 3. Click Edit to update the user account. 108 Mengelola Akun Pengguna 4. On the Edit page, scroll down to Roles section. Check the Administrator role for the user account. 5. 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. Updating the roles using bulk editing method 1. 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). 2. 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. 3. Select Add the Vendor role to the selected users from the Action select list. 109 Mengelola Akun Pengguna 4. Click Apply to selected items. You should see a message indicating that the desired changes were made. Attributions Written by Chris Dart and Jennifer Hodgdon 7.7. Assigning Authors to Content 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. Prerequisite knowledge • Bagian 7.1, “Concept: Users, Roles, and Permissions” Site prerequisites • The Vendor content type must exist, and your site must have at least two Vendor content items. See Bagian 6.1, “Adding a Content Type”, Bagian 6.3, “Adding Basic Fields to a Content Type”, and Bagian 5.2, “Creating a Content Item”. • User accounts for at least two vendors must exist. See Bagian 7.4, “Creating a User Account”. Steps 1. In the Manage administrative menu, navigate to Content (admin/content). 110 Mengelola Akun Pengguna 2. Find Vendor content item Happy Farm in the list. If it is not immediately visible, you can filter the list by Published status, Content type (Vendor), Title, or Language. Click Edit for the Vendor content item you would like to assign an author to. 3. Locate the information block and click Authoring information. 4. 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. 5. Click Save and keep published. 6. You will get a notification that the Vendor content item has been updated. 111 Mengelola Akun Pengguna 7. Follow these steps again to assign Vendor content item Sweet Honey to the Vendor user account Sweet Honey. Attributions Written by Diána Lakatos at Pronovix. 112 Bab 8. Blok 8.1. Concept: Blocks What is a block? Blocks are individual pieces of your site’s web page layout. They are placed inside the regions (see Bagian 2.1, “Concept: Regions in a Theme”) of your theme, and can be created, removed, and rearranged in the Block layout (admin/structure/block) administration page. Examples of blocks include the Who’s online listing, the main navigation menu, and the breadcrumb trail. The main page content is also a block. Some modules make new blocks available for placement on your site. For example, when the core Search module is installed and configured, it provides a block that contains a search form. You may also create and place your own custom blocks. Each block has its own configuration settings, which allow you to select which pages of your site will display the block. It is even possible to place multiple copies of a block, each with its own separate configuration and visibility rules. Related topics • Bagian 2.1, “Concept: Regions in a Theme” • Bagian 8.2, “Creating A Custom Block” • Bagian 8.3, “Placing a Block in a Region” Attributions Adapted by Les Lim from "Working with blocks (content in regions)" copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 8.2. Creating A Custom Block Goal Create a block showing the hours and location of the farmers market. Prerequisite knowledge • Bagian 8.1, “Concept: Blocks” 113 Blok • Bagian 2.1, “Concept: Regions in a Theme” Steps 1. In the Manage administrative menu, navigate to Structure > Block layout > Custom block library (admin/structure/block/block-content). 2. Click Add custom block. The Add custom block page appears. 3. Fill in the fields as shown below. Field name Explanation Block description Name of the block shown to Hours and location block administrators Body Content of the block when it is displayed 114 Example value Open: Sundays, 9 AM to 2 PM, April to September
Location: Parking lot of Trust Bank, 1st & Union, downtown Anytown. Blok 4. Click Save. A message appears indicating the block has been saved. Expand your understanding • Edit the content of your custom block. In the Manage administrative menu, navigate to Structure > Block layout > Custom block library (admin/structure/block/block-content). Find your block in the list and click Edit to make changes. • Place the block you created in the sidebar. See Bagian 8.3, “Placing a Block in a Region” for details. Additional resources Drupal.org community documentation page "Working with blocks (content in regions)" Attributions 115 Blok Adapted by Jacob Redding and Boris Doesborg from Working with blocks (content in regions), copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 8.3. Placing a Block in a Region Goal Place the Opening hours and location block in the website’s sidebar. Prerequisite knowledge Bagian 8.1, “Concept: Blocks” Site prerequisites • The core Bartik theme must be installed and set as default. See Bagian 4.6, “Configuring the Theme”. • The Opening hours and location block must exist. See Bagian 8.2, “Creating A Custom Block”. Steps 1. In the Manage administrative menu, navigate to Structure > Block layout (admin/structure/ block). The Block layout page appears, listing the theme’s regions. 2. Ensure that in the secondary tab the core Bartik theme is selected. Block placement is defined per theme. 3. Locate the region Sidebar second in the list and click Place block next to it. The Place block window appears, listing all the blocks. 4. Locate the block Opening hours and location and click Place block next to it. The Configure block window appears. Fill in the fields as shown below. Field name Value Title Hours and location Display title Checked Region Sidebar second You can also hide or display the block on specific pages. In the case of the Farmer’s market website you do not set any of these configuration options because you want to show the block everywhere. 116 Blok 5. Click Save block. The Block layout page appears. You can drag blocks to change the order in which they will appear. 6. Verify that the Opening hours and location block is listed in the Sidebar second region, and click Save blocks. The block has been placed on the sidebar of all pages that use the core Bartik theme. 117 Blok Expand your understanding • Remove the Powered by Drupal block from the Footer fifth region by setting the region to - None -. • Remove the Tools block from the Sidebar first region by setting the region to - None -. This block is only visible to logged-in users. • Place the User login block in a region. • If you do not see the effect of these changes in your site, you might need to clear the cache. See Bagian 12.2, “Clearing the Cache”. Attributions Written and edited by Boris Doesborg and Jennifer Hodgdon. 118 Bab 9. Membuat Daftar dengan Views 9.1. Concept: Uses of Views Prerequisite knowledge • Bagian 2.4, “Concept: Modular Content” • Bagian 2.3, “Concept: Content Entities and Fields” 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. 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: • Lists of vendors • Lists of recipes • Lists of the most recent content on the site • Lists of users on the site What are the ways data can be output using views? A listing created by a view can be in any of the following forms: • Table with sortable fields • Grid layouts • Teasers or pictures that link to articles • Blocks • JSON output • RSS feeds • Calendars 119 Membuat Daftar dengan Views • On-screen slideshows Related topics • Bagian 9.2, “Concept: The Parts of a View” • Bagian 9.3, “Creating a Content List View” Attributions Written and edited by Michael Lenahan at erdfisch, and Jojy Alphonso at Red Crackle. 9.2. Concept: The Parts of a View Prerequisite knowledge • Bagian 2.3, “Concept: Content Entities and Fields” • Bagian 2.4, “Concept: Modular Content” • Bagian 9.1, “Concept: Uses of Views” • Bagian 5.1, “Concept: Paths, Aliases, and URLs” • Bagian 8.1, “Concept: Blocks” 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: Display 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 Makes output in a block, which can be placed on pages. Feed Makes an RSS or another type of feed. 120 Membuat Daftar dengan Views 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). 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. 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. Sort criteria 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. 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. Related topics Bagian 9.3, “Creating a Content List View” Attributions Written and edited by Surendra Mohan and Jennifer Hodgdon. 121 Membuat Daftar dengan Views 9.3. Creating 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. Prerequisite knowledge • Bagian 9.1, “Concept: Uses of Views” • Bagian 9.2, “Concept: The Parts of a View” 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 Vendor content type must exist, with URL and Main image fields. Your site must have a couple of Vendor content items. See Bagian 6.1, “Adding a Content Type”, Bagian 6.3, “Adding Basic Fields to a Content Type”, and Bagian 5.2, “Creating a Content Item”. • 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 Bagian 6.13, “Setting Up an Image Style”. Steps 1. In the Manage administrative menu, navigate to Structure > Views > Add view (admin/ structure/views/add). The Add view wizard appears. 2. Fill in the fields as shown below. Field name Explanation Example value View name Name of the view that will be visible in the administration pages Vendors Show Type of information listed in the view Content of type Specify content type Vendor sorted by List order Title Create a page Create a page that displays Checked the view Page title Title show above the view Vendors Path Address of the page vendors 122 Membuat Daftar dengan Views Field name Explanation Example value Display format Type of list Table Items to display Number of items visible on 10 the page Use a pager Split up the list in several pages if there are more items Checked Create a menu link Add the view page to the menu Checked Menu Menu in which to add the link Main navigation Link text Label of the link in the menu Vendors 3. Click Save and edit. The view configuration page appears. 4. Click Add from the dropdown button in the Fields section. The Add fields pop-up appears. 5. Enter the word "image" in the search field. 6. Check Main image in the table. 7. Click Apply. The Configure field: Content: Main Image pop-up appears. 8. Fill in the fields as shown below. 123 Membuat Daftar dengan Views Field name Explanation Example value Create a label Add a label before the field Unchecked value Image style The format of the image Medium (220x220) Link image to Add a link to the content item Content 9. Click Apply. The view configuration page appears. 10. Click Add from the dropdown button in the Fields section. The Add fields pop-up appears. 11. Enter the word "body" in the search field. 12. Select Body in the table. 13. Click Apply. The Configure field: Content: Body pop-up appears. 14. Fill in the fields as shown below. Field name Explanation Example value Create a label Add a label before the field Unchecked value Formatter The presentation of the field value Summary or trimmed Trimmed limit: The number of maximum characters shown 120 15. Click Apply. The view configuration page appears. 16. Click Content: Title (Title) in the Fields list. The Configure field: Content: Title pop-up appears. 17. Uncheck Create a label. This will remove the label that was created by the wizard. 18. Click Apply. The view configuration page appears. 19. Click Rearrange from the dropdown button in the Fields section. The Rearrange fields popup appears. 20. Drag the fields into the right order: Image, Title. Body. 21. Click Apply. The view configuration page appears. 22. Optionally, click Update preview for a preview. 23. Click Save. 124 Membuat Daftar dengan Views 24. Navigate to the homepage and click Vendors from the main navigation to see the result. 125 Membuat Daftar dengan Views 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 Bagian 5.8, “Changing the Order of Navigation”. Attributions Written/edited by Boris Doesborg and Jennifer Hodgdon. 9.4. 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. Prerequisite knowledge • Bagian 9.1, “Concept: Uses of Views” • Bagian 9.2, “Concept: The Parts of a View” • Bagian 9.3, “Creating a Content List View” 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 Bagian 6.1, “Adding a Content Type”, Bagian 6.3, “Adding Basic Fields to a Content Type”, Bagian 6.6, “Setting Up a Taxonomy”, Bagian 6.9, “Changing Content Entry Forms”, and Bagian 5.2, “Creating a Content Item”. • The Vendors view must exist. See Bagian 9.3, “Creating a Content List View”. Steps 1. In the Manage administrative menu, navigate to Structure > Views (admin/structure/views). Find the view "Vendors" and click Duplicate in its dropdown button. 126 Membuat Daftar dengan Views 2. Name the duplicate "Recipes" and click Duplicate. The view configuration page appears. 3. 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. 4. 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. 5. 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. 6. 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 popup, check Recipe and uncheck Vendor. Click Apply. 7. 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. 8. 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, and click Apply. 127 Membuat Daftar dengan Views Field name Explanation Example value Expose this filter to visitors, Allow visitors to filter and to allow them to change it search Checked Required Whether a value has to be provided or not Unchecked Label Label shown for this filter on the view page Find recipes using… 9. 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). 10. 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. 11. In order to use Ajax (see Ajax entry in the Glossary) 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. 12. Click Save to save the view. 13. Go back to the home page and click Recipes in the navigation to view the new Recipes page. 128 Membuat Daftar dengan Views 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 Bagian 5.8, “Changing the Order of Navigation”. Related concepts • Bagian 2.5, “Planning your Content Structure” • Ajax entry in the Glossary Attributions Written and edited by Laura Vass at Pronovix, and Jojy Alphonso at Red Crackle. 9.5. Adding 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. 129 Membuat Daftar dengan Views Prerequisite knowledge • Bagian 9.1, “Concept: Uses of Views” • Bagian 9.2, “Concept: The Parts of a View” • Bagian 9.3, “Creating a Content List 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 Bagian 6.1, “Adding a Content Type”, Bagian 6.3, “Adding Basic Fields to a Content Type”, Bagian 6.9, “Changing Content Entry Forms”, and Bagian 5.2, “Creating a Content Item”. • 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 Bagian 6.13, “Setting Up an Image Style”. • The Recipes view must exist. See Bagian 9.3, “Creating a Content List View” and Bagian 9.4, “Duplicating a View”. Steps 1. 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 Bagian 4.1, “Concept: Administrative Overview” for information about contextual links. 2. 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. 3. Change the title of this display by clicking Block next to Display name. The Block: The name and the description of this display pop-up appears. Change the Administrative name to "Recent recipes". Click Apply. 4. Change the title of the view by clicking Title: Recipes in the Title section. In the pop-up that appears, select This block (override) from the For select list. Change the title to "New recipes" and click Apply (this display). 130 Membuat Daftar dengan Views 5. Change the view’s style by clicking Format: Grid in the Format section. In the pop-up that appears, select This block (override) from the For select list. Select Unformatted list and Click Apply (this display). You can further configure the style options in the next pop-up that appears. Then click Apply. 6. Configure the image field by clicking Content: Main image in the Fields section. In the pop-up that appears, select This block (override) from the For select list. Select Image style Thumbnail (100x100). Click Apply (this display). 131 Membuat Daftar dengan Views 7. Remove ingredients as a filter by clicking Content: Ingredients (exposed) in the Filter criteria section. In the pop-up that appears, select This block (override) from the For select list. Click Remove at the bottom. 132 Membuat Daftar dengan Views 8. 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 This block (override) from the For select list. Check the field Authored on (from Content category), and then Add and configure sort criteria. 9. In the appearing configuration pop-up, select Sort descending to have the most recent recipes appear first. Click Apply. 10. Specify the number of items to be displayed by clicking Use pager: Mini in the Pager section. In the pop-up that appears, select This block (override) from the For select list. Under Pager, select Display a specified number of items. Click Apply (this display). In the Block: Pager options pop-up, provide "5" as the value for Items to display. Click Apply. 11. 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. 12. Place the "Recipes: Recent Recipes" block in the Sidebar second region. See Bagian 8.3, “Placing a Block in a Region”. Navigate to the site’s home page to see the block. Attributions Written and edited by Laura Vass at Pronovix, Jennifer Hodgdon, and Jojy Alphonso at Red Crackle. 133 Bab 10. Membuat Situs Anda Multilingual 10.1. Concept: User Interface, Configuration, and Content translation Prerequisite knowledge • Bagian 1.5, “Concept: Types of Data” • Bagian 1.2, “Concept: Modules” • Bagian 2.3, “Concept: Content Entities and Fields” What can be translated on your site? The base language for the software that your site runs (core software, modules, and theme) is English. However, you can create either a site that displays in a different language or a multi-lingual site; if you do so, all relevant text, images, and file attachments should be shown in the appropriate language for each site visitor. You need to have the core Language module installed in order to use a language other than English on the site. There are three types of information that you can translate, each with its own method for translating: User interface text Built-in text present in the core software, modules, and themes. This can be translated from the base English language of the software into the language(s) of your site. Typically, rather than needing to translate this text yourself, you can download translations. You need to have the core Interface Translation module installed in order to translate this text. Configuration text Text whose structure and initial values are defined by the core software, modules, and theme, but that you can edit. Examples include the labels for fields in your content types, header text in views, your site name, and the content of automatic email messages that your site sends out. After creating configuration text in the default language of your site, you can translate it into other languages. You need to have the core Configuration Translation module installed in order to translate this text. Content text and files If your site is multilingual, you can configure the content fields on your site to be translatable. After creating content in one language, you can translate it into other 134 Membuat Situs Anda Multilingual languages. Fields can contain textual information or uploaded files, and for each field on each content type, you can configure it to be translatable or non-translatable. You need to have the core Content Translation module installed in order to translate this text. Related topics • Bagian 10.2, “Adding a Language” • Bagian 10.3, “Configuring Content Translation” • Bagian 10.4, “Translating Content” • Bagian 10.5, “Translating Configuration” Attributions Written by Jennifer Hodgdon. 10.2. Adding a Language Goal Add one or more languages to your site and define which one is used by default. Prerequisite knowledge Bagian 10.1, “Concept: User Interface, Configuration, and Content translation” Steps 1. Install the four core multilingual modules (Language, Interface Translation, Content Translation, and Configuration Translation), by following the steps in Bagian 4.3, “Installing a Module”. 2. In the Manage administrative menu, navigate to Configuration > Regional and language > Languages (admin/config/regional/language). 3. Click Add language. 4. Select Spanish (or your preferred language) from the Language name select list. Click Add language. After waiting for translations to finish downloading, you will be returned to the Languages page, with a confirmation message and the new language shown. 135 Membuat Situs Anda Multilingual 5. Follow the steps in Bagian 8.3, “Placing a Block in a Region” to place the Language switcher block in the Sidebar second region. This will enable site visitors to switch between languages, once the site has been translated. Expand your understanding • Bagian 10.3, “Configuring Content Translation” • Bagian 10.4, “Translating Content” Additional resources Drupal.org page "Resource Guide: Configuring a Multilingual Site" Attributions Written and edited by Leila Tite, Jennifer Hodgdon, and Boris Doesborg. 10.3. Configuring Content Translation Goal Make Custom block, Custom menu link, and Content entity types translatable. Select specific subtypes and set which fields of these can be translated. 136 Membuat Situs Anda Multilingual Prerequisite knowledge • Bagian 2.3, “Concept: Content Entities and Fields” • Bagian 10.1, “Concept: User Interface, Configuration, and Content translation” Site prerequisites The core Content Translation module must be installed, and your site must have at least two languages. See Bagian 10.2, “Adding a Language”. Steps 1. In the Manage administrative menu, navigate to Configuration > Regional and language > Content language and translation (admin/config/regional/content-language). 2. Under Custom language settings, check Content, Custom block and Custom menu link to make these entity types translatable. 3. Configuration options appear for Content, Custom block and Custom menu link. Choose the subtypes you want to translate for each entity type. Check Basic page for Content, Basic block for Custom block and Custom menu link for Custom menu link. 4. Verify the settings for the entity types as shown below: 137 Membuat Situs Anda Multilingual Field name Explanation Example value Default language The default language for the entity subtype Site’s default language (English) Show language selector on Whether or not the Checked create and edit pages language selector should be shown while editing and creating content 5. Choose the fields that should be translatable for Basic page as shown in the table below. If a field is not translation-dependent, leave it unchecked. Enabling translation for fields that are numbers or dates has use for accountability or implementing workflows. Field name Explanation Example value Title The title of the content Checked Authored by The author Unchecked Publishing status Whether the content has been published or not Checked Authored on Date of publishing Unchecked Changed Date of last update Unchecked Promoted to front page Whether the content will be Unchecked included in some content views Sticky at top of lists Whether the content will be displayed first in some content views Unchecked URL alias Nicer URL for the content Checked Body The main content of the page Checked 138 Membuat Situs Anda Multilingual 6. Similarly, check the appropriate boxes for translatable fields belonging to Basic block and Custom menu link. 7. Click Save configuration. Expand your understanding • Bagian 10.5, “Translating Configuration” • Bagian 10.4, “Translating Content” Additional resources • Blog post "Multilingual Drupal 8 tidbits, part 5" • Blog post "Multilingual Drupal 8 tidbits, part 17" Attributions Written and edited by Laura Vass at Pronovix, Jojy Alphonso at Red Crackle, and Jennifer Hodgdon. 139 Membuat Situs Anda Multilingual 10.4. Translating Content Goal Translate the home page to Spanish. Prerequisite knowledge Bagian 10.1, “Concept: User Interface, Configuration, and Content translation” Site prerequisites • The Home content item must exist. See Bagian 5.2, “Creating a Content Item”. • The core Content Translation module must be installed, and your site must have at least two languages. See Bagian 10.2, “Adding a Language”. • The Basic page content type must be configured to be translatable. See Bagian 10.3, “Configuring Content Translation”. Steps 1. In the Manage administrative menu, navigate to Content (admin/content). 2. Locate the home page. You can search for it by entering "Home" in the title field. 3. Select Translate from the dropdown button in the row of the Home content item. The page Translations of Home appears. 4. Click Add in the row Spanish. 5. Note that the user interface has switched to Spanish. To switch it back to English, remove the first instance of es in the browser’s URL. For example, if your URL looks like example.com/es/node/5/translations/add/en/es, remove the es that comes immediately after example.com. 6. Fill in the fields as shown below. You will have to click and expand URL path settings on the right to provide the value for URL alias. Field name Explanation Title Translated title of the page Página principal 140 Value Membuat Situs Anda Multilingual Field name Explanation Value Body Translated body of the page Bienvenido al mercado de la ciudad - ¡el mercado de agricultores de tu barrio! Horario: Domingos de 9:00 a 14:00. Desde Abril a Septiembre Lugar: parking del Banco Trust número 1. En el centro de la ciudad URL path settings > URL alias Translated address of the webpage pagina-principal 7. Click Save and keep published (this translation). 8. Go to your site’s home page to view the newly translated page. Expand your understanding • Follow the steps above to translate more content on your site. • Bagian 10.5, “Translating Configuration” Attributions Written by Boris Doesborg. 10.5. Translating Configuration Goal Translate the labels on the Recipes view page into Spanish. Prerequisite knowledge • Bagian 10.1, “Concept: User Interface, Configuration, and Content translation” • Bagian 9.3, “Creating a Content List View” Site prerequisites • The core Configuration Translation module must be installed, and your site must have at least two languages. See Bagian 10.2, “Adding a Language”. • The Recipes view must exist. See Bagian 9.3, “Creating a Content List View” and Bagian 9.4, “Duplicating a View”. 141 Membuat Situs Anda Multilingual Steps The basic steps for translating any configuration on your site are: 1. Locate the page where the configuration you want to translate is created or edited in the site’s primary language. For example, to translate the site name, you need to find the page where you would edit the site name (see Bagian 4.2, “Editing Basic Site Information”). 2. Find a link, tab, or button on the page that says "Translate" or something similar. Click this link, tab, or button. 3. Find a button that will let you add a translation in the desired language, and click this button. 4. Enter the translation in the form, and save. Most configuration is fairly straightforward and intuitive to edit in this manner. Views configuration is an exception, because the translation editing form is nothing like the view editing form, and it is complex and hierarchical rather than being a simple form with just a few fields. As an example of how to translate a view, here are the steps to translate the labels in the Recipes view to Spanish: 1. In the Manage administrative menu, navigate to Structure > Views (admin/structure/views). 2. Locate the Recipes view and click Translate from the dropdown button. 3. Click Add in the row Spanish. The page Add Spanish translation for Recipes view appears. 4. Find Displays > Master Display settings > Recipes default display Options. Translate the Display title from "Recipes" to "Recetas". 5. Find Displays > Master display settings > Recipes default display options > Exposed form > Reset options. Translate Submit button text (Apply) to "Applicar". The other buttons and labels in this section do not appear on the Recipes page or block, and do not need to be translated. 142 Membuat Situs Anda Multilingual 6. Find Displays > Master display settings > Recipes default display options > Filters > (Empty) taxonomy term ID > Find recipes using… Expose. In the Label field, enter "Encontrar recetas usando…". 7. Click Save translation. 8. Navigate to the Recipes page and switch to Spanish using the Language switcher block. Verify that the labels have been translated. Expand your understanding • Translate the block display title in the Recent recipes display settings section of the Recipes view. • Translate the page title in the Vendors view. • Translate other configuration. Some examples of where to find the translation pages: • To translate the site name, navigate in the Manage administrative menu to Configuration > System > Basic site settings > Translate system information (admin/config/system/siteinformation/translate). • To translate the contact form, navigate in the Manage administrative menu to Structure > Contact forms (admin/structure/contact). Click Translate in the dropdown button in the Website feedback row. • To translate the name of a menu, navigate in the Manage administrative menu to Structure > Menus (admin/structure/menu). Click Translate in the dropdown button for the menu whose name you want to translate. 143 Membuat Situs Anda Multilingual • Menu items within a menu are considered to be content (not configuration); see Bagian 10.3, “Configuring Content Translation” to enable translation. Once translation is enabled, navigate in the Manage administrative menu to Structure > Menus (admin/structure/ menu). Click Edit menu in the dropdown button for the menu whose links you want to translate. Click Translate in the dropdown button for the link you want to translate. • To translate field labels on a content type, navigate in the Manage administrative menu to Structure > Content types (admin/structure/types). Click Manage fields in the dropdown button for the content type whose field labels you want to edit. Click Translate in the dropdown button for the field whose label you want to edit. • Translate content. See Bagian 10.4, “Translating Content”. Attributions Written and edited by Boris Doesborg and Jennifer Hodgdon. 144 Bab 11. Mengembangkan dan Menyesuaikan Situs Anda 11.1. Finding Modules Goal Find and evaluate modules on Drupal.org. Prerequisite knowledge • Bagian 1.1, “Concept: Drupal as a Content Management System” • Bagian 1.2, “Concept: Modules” Steps 1. Go to Drupal.org, and navigate to Download & Extend > Modules (https://www.drupal.org/ project/project_module). 2. Filter your search using the categories on the module search page. Fill in the fields as shown below. Field name Explanation Example value Maintenance status How actively should the module be maintained? Actively maintained Development status What kind of development should the module undergo? Any Module categories The module’s topic area. Administration Core compatibility The version of the core software the module is compatible with. 8.x Status Project status: Sandbox Full projects projects are experimental projects. Full projects have already gone through an approval process, but they can still be in development. Search Modules Search for Admin Toolbar, a Admin Toolbar module that will be covered 145 Mengembangkan dan Menyesuaikan Situs Anda Field name Explanation Example value in detail later. Alternatively, you can also leave the field blank if you are not sure which module to search for. Sort by Order your search results Most installed by criteria like Most installed (popular modules that many sites use) or Last release (date of latest version released). 3. Click Search. Search results will appear. 146 Mengembangkan dan Menyesuaikan Situs Anda 4. To further evaluate a module, click its title in the list of search results to visit its project page. Some aspects to pay attention to when evaluating modules: • Project description: The description of the module on its project page should be clear and useful. You should get an idea of its features and requirements. • Maintenance status: If a module is Actively maintained, you can be sure that there will be security updates, bug fixes and feature improvements provided on a regular basis. However, if the module is unmaintained or abandoned, you shouldn’t use it. 147 Mengembangkan dan Menyesuaikan Situs Anda • Development status: Under active development means you can expect new features to be added to the project, but some aspects (for example, API) may still change. Maintenance fixes only means that the project is considered feature complete. • Reported installs, downloads: You can see how many people have downloaded and how many sites use the module. If it’s only used by a few sites, it might be a unique solution that not many people need, or it might be a warning sign that you shouldn’t use it either. • Maintainers: When was the last commit (the last time someone updated something on the module) or last release (new version)? If the project has few open issues, a long time since commits/releases might be appropriate, but if it has a lot of open issues and there are no commits/releases, that would be a clue that it might be abandoned. • Issues: See if there are any open issues, potential problems with the module. Check the Statistics to see how regularly issues are responded to. • Resources: Check if the module has documentation or a README file, that can help you install, configure, explore, and test it. Expand your understanding Bagian 11.3, “Downloading and Installing a Module from Drupal.org” Attributions Written by Diána Lakatos at Pronovix. 148 Mengembangkan dan Menyesuaikan Situs Anda 11.2. Enabling and Disabling Maintenance Mode Goal Put your site in maintenance mode to allow users with the right permissions to use the site while users without this permission are presented with a message that the site is under maintenance. Prerequisite knowledge Bagian 13.3, “Concept: Security and Regular Updates” Steps Enabling maintenance mode 1. In the Manage administrative menu, navigate to Configuration > Development > Maintenance mode (admin/config/development/maintenance). The Maintenance mode page appears. 2. Fill in the fields as shown below. Field name Explanation Value Put site into maintenance mode Enable the maintenance mode Checked Message to display when in The information that is maintenance mode shown to website visitors when the mode is enabled. Variables such as @site can be used in the message @site is currently under maintenance but should be back shortly. Thank you for your patience. 3. Click Save configuration. 4. Verify that the site is in maintenance mode by accessing it from another browser where you aren’t logged in. If you are not able to verify, try clearing the cache. See Bagian 12.2, “Clearing the Cache”. 149 Mengembangkan dan Menyesuaikan Situs Anda Disabling maintenance mode 1. In the Manage administrative menu, navigate to Configuration > Development > Maintenance mode (admin/config/development/maintenance). The Maintenance mode page appears. 2. Fill in the fields as shown below. Field name Explanation Value Put site into maintenance mode Disable the maintenance mode Unchecked Message to display when in No message required while maintenance mode disabling. You can leave the field blank. 3. Click Save configuration. 4. Verify that the site is no longer in maintenance mode by accessing it from another browser where you aren’t logged in. If you are not able to verify, try clearing the cache. See Bagian 12.2, “Clearing the Cache”. Expand your understanding • Bagian 13.5, “Updating the Core Software” 150 Mengembangkan dan Menyesuaikan Situs Anda • Bagian 13.7, “Updating a Theme” • Bagian 13.6, “Updating a Module” Attributions Written and edited by Boris Doesborg, and Jojy Alphonso at Red Crackle. 11.3. Downloading and Installing a Module from Drupal.org Goal Download and install the contributed Admin Toolbar module, which allows you to easily browse through the administration section of the website. Prerequisite knowledge • Bagian 1.2, “Concept: Modules” • Bagian 11.1, “Finding Modules” • Bagian 3.2, “Concept: Additional Tools” Site prerequisites • If you want to install modules via the website, the core Update Manager module must be installed. See Bagian 4.3, “Installing a Module” for instructions on installing modules. • If you want to use Drush, Drush must be installed. See Bagian 3.2, “Concept: Additional Tools”. Steps You can use the administrative interface or Drush to install a contributed module. If you are installing a custom module rather than a contributed module, if you see a message saying Installing modules and themes requires FTP access to your server, or if the steps below do not work to download and unpack the module files, follow the steps in Bagian 11.6, “Manually Downloading Module or Theme Files”. If you are installing a contributed module with external dependencies that are managed by Composer, follow the steps for downloading in Bagian 11.9, “Using Composer and Git to Download Files”. In either of these cases, then continue here with step 7 in the instructions for the administrative interface below. Using the administrative interface 1. On the Admin toolbar project page on drupal.org (https://www.drupal.org/project/ admin_toolbar), scroll to the Downloads section at the bottom of the page. 151 Mengembangkan dan Menyesuaikan Situs Anda 2. Copy the address of the tar.gz link. Depending on your device and browser, you might do this by right clicking and selecting Copy link address. 3. In the Manage administrative menu, navigate to Extend (admin/modules). The Extend page appears. 4. Click Install new module. The Install new module page appears. 5. In the field Install from a URL, paste the copied download link. This value could look like this: https://ftp.drupal.org/files/projects/admin_toolbar-8.x-1.14.tar.gz 6. Click Install to upload and unpack the new module on the server. The files are being downloaded to the modules directory. 7. Click Enable newly added modules to return to the Extend page. If you used the manual uploading procedure, start with this step, and reach the Extend page by using the Manage administrative menu and navigating to Extend (admin/modules). 8. Locate and check Admin toolbar. 9. Click Install to turn on the new module. 152 Mengembangkan dan Menyesuaikan Situs Anda Using Drush 1. Find the project name for the module you want to install, which is the last segment of the module’s project page URL. For example, if the project URL is https://www.drupal.org/ project/admin_toolbar, the project name is "admin_toolbar". 2. Run the following Drush commands, giving the project name (for example, admin_toolbar) as a parameter: drush dl admin_toolbar drush en admin_toolbar 3. Follow the instructions on the screen. Expand your understanding • Verify that the contributed Admin Toolbar module is working by browsing through the menu in the administration section. • Install and configure the contributed Pathauto module so that content pages in your site get nice URLs by default. See Bagian 5.1, “Concept: Paths, Aliases, and URLs” for more on URLs. • If you do not see the effect of these changes in your site, you might need to clear the cache. See Bagian 12.2, “Clearing the Cache”. Additional resources • Drupal.org community documentation page "Contributed modules" • "Download and Extend" page on Drupal.org • Admin Toolbar module on Drupal.org Attributions Written and edited by Boris Doesborg and Jennifer Hodgdon. 11.4. Finding Themes Goal Find and evaluate themes on Drupal.org. Prerequisite knowledge • Bagian 1.1, “Concept: Drupal as a Content Management System” • Bagian 1.3, “Concept: Themes” 153 Mengembangkan dan Menyesuaikan Situs Anda Steps 1. Go to https://www.drupal.org, and navigate to Download & Extend > Themes (https:// www.drupal.org/project/project_theme). 2. Filter your search using the categories on the theme search page. For example, you might use these filters: Field name Explanation Maintenance status How actively is the theme Actively maintained maintained? If a theme is actively maintained, you can expect bug fixes and improvements on a regular basis. Development status What kind of development is the theme undergoing? If you select Under active development, you can expect new features to be added, and some aspects may still change. If you select Maintenance fixes only, it means that the theme is considered complete. Any Core compatibility The Drupal version the theme is compatible with. 8.x Status Sandbox projects are experimental projects. Full projects have already gone through an approval process, but they can still be in development. Full projects Search Themes Search by search term in the theme’s description. - Sort by Order your search results Most installed by criteria like Most installed (popular themes that many sites use) or Last release (date of latest version released). 154 Example value Mengembangkan dan Menyesuaikan Situs Anda 3. Click Search. Search results will appear. 155 Mengembangkan dan Menyesuaikan Situs Anda 4. To further evaluate a theme, click its title in the list of search results to visit its project page. Some aspects to pay attention to while evaluating themes: • Introduction: The description of the theme on its project page should be clear and useful. A screenshot of the theme helps your evaluation as well. • Downloads: The theme should be available for your version of the core software. Pay attention to the color-coding: Themes marked green are recommended to be used on 156 Mengembangkan dan Menyesuaikan Situs Anda live sites, the ones marked yellow should be carefully evaluated before use, and the ones marked red are only recommended for testing. • Project Information: Check the theme’s maintenance and development status, and how frequently it’s downloaded and installed. • Issues: See if there are any open issues or potential problems with the theme. • Resources: Check if the theme has documentation. Expand your understanding • Bagian 11.5, “Downloading and Installing a Theme from Drupal.org” Attributions Written by Diána Lakatos. 11.5. Downloading and Installing a Theme from Drupal.org Goal Download and install a theme from Drupal.org. Prerequisite knowledge • Bagian 11.4, “Finding Themes” • Bagian 3.2, “Concept: Additional Tools” Site prerequisites If you want to install via the website, the core Update Manager module must be installed. See Bagian 4.3, “Installing a Module” for instructions on installing modules. If you want to use Drush, Drush must be installed. See Bagian 3.2, “Concept: Additional Tools”. Steps You can use the administrative interface or Drush to install a contributed theme. If you are installing a custom theme rather than a contributed theme, if you see a message saying Installing modules and themes requires FTP access to your server, or if the steps below do not work to download and unpack the theme files, follow the steps in Bagian 11.6, “Manually Downloading Module or Theme Files”. If you are installing a contributed theme with external dependencies that are managed by Composer, follow the steps for downloading in Bagian 157 Mengembangkan dan Menyesuaikan Situs Anda 11.9, “Using Composer and Git to Download Files”. In either of these cases, then continue here with step 7 in the instructions for the administrative interface below. Using the administrative interface 1. On the theme’s project page on drupal.org (for example, https://www.drupal.org/project/ mayo), scroll to the Downloads section at the bottom of the page. 2. Right-click tar.gz to copy the address. 3. In the Manage administrative menu, navigate to Appearance (admin/appearance). The Appearance page appears. 4. Click Install new theme. The Install new theme page appears. 5. In the field Install from a URL, paste the copied download link. This value could look like https://ftp.drupal.org/files/projects/mayo-8.x-1.3.tar.gz. 158 Mengembangkan dan Menyesuaikan Situs Anda 6. Click Install to upload and unpack the new theme on the server. The files are being downloaded to the themes directory. 7. Click Install newly added themes to return to the Appearance page. If you used the manual uploading procedure, start with this step, and reach the Appearance page by using the Manage administrative menu and navigating to Appearance (admin/appearance). 8. Locate the new theme under Uninstalled themes and click Install and set as default to use it. All non-administrative pages on the site will now use this new theme. Using Drush 1. Find the project name for the theme you want to install, which is the last segment of the theme’s project page URL. For example, if the project URL is https://www.drupal.org/ project/mayo, the project name is mayo. 2. Run the following Drush commands, giving the project name (for example, mayo) as a parameter: drush dl mayo drush en mayo drush config-set system.theme default mayo 3. Follow the instructions on the screen. Expand your understanding • In the Manage administrative menu, navigate to Appearance (admin/appearance) and uninstall any themes that you are not using. • Bagian 11.1, “Finding Modules” 159 Mengembangkan dan Menyesuaikan Situs Anda • Bagian 11.3, “Downloading and Installing a Module from Drupal.org” • If you do not see the effect of these changes in your site, you might need to clear the cache. See Bagian 12.2, “Clearing the Cache”. Attributions Written and edited by Joe Shindelar at Drupalize.Me, and Boris Doesborgh. 11.6. Manually Downloading Module or Theme Files Goal Manually download module or theme files and upload them to your site, if the website or Drush methods for installing or updating a module or theme do not work, or if you are placing a custom-written module or theme. Prerequisite knowledge • Bagian 1.2, “Concept: Modules” • Bagian 11.1, “Finding Modules” • Bagian 1.3, “Concept: Themes” • Bagian 11.4, “Finding Themes” Site prerequisites You need to be facing any of the following to perform the manual download described in this topic: • File permission issues • FTP permission issues • You created a custom module/theme or received its files from someone • You could not successfully complete the instructions in Bagian 11.3, “Downloading and Installing a Module from Drupal.org”, Bagian 11.5, “Downloading and Installing a Theme from Drupal.org”, Bagian 13.6, “Updating a Module”, or Bagian 13.7, “Updating a Theme” Skip this topic if none of the above applies to you. Steps If you are installing a module or theme from Drupal.org, follow the downloading instructions, and then the uploading/unpacking instructions. If you created the module or theme, skip the 160 Mengembangkan dan Menyesuaikan Situs Anda downloading step. Instead, create an archive file (that you know how to extract on the server) and proceed with the steps in uploading/unpacking, using whatever method is appropriate for the way you initially created the archive file. Downloading the files 1. Open the module or theme project page on drupal.org; for example, the Admin toolbar page (https://www.drupal.org/project/admin_toolbar). 2. Scroll to the Downloads section near the bottom of the page. 3. Click tar.gz to download the file to your computer. Uploading the files to your site and unpacking them 1. If you are adding a new module or theme, create subdirectories in your top-level modules and themes directories (if they don’t already exist). Typically, people make a contrib subdirectory for contributed modules and themes that are downloaded from Drupal.org, and a custom subdirectory for modules and themes that they created. Your modules directory might look like this: 2. If you are replacing an existing module or theme with an updated version, put the site into maintenance mode. See Bagian 11.2, “Enabling and Disabling Maintenance Mode”. 3. If you are replacing an existing module or theme with an updated version, find and delete all the existing files and directories for the existing module or theme. Modules are normally located in directories under the top-level modules directory, and themes are normally located in directories under the top-level themes directory. 4. Upload the .tar.gz file (or whatever archive you created) to your site. Place it in either the same location from which you deleted the directory (if replacing an existing module or theme) or the appropriate subdirectory of modules or themes (if adding a new module or theme). 5. Extract the files from the .tar.gz archive (or whatever archive you created), making a subdirectory in the same location as the archive file. If you do not have terminal access, 161 Mengembangkan dan Menyesuaikan Situs Anda or your hosting server is not running Linux, your hosting control panel’s file manager should provide a way to extract the files. If you have terminal access to your hosting server (running Linux) and you are using a tar.gz file, you can use a command like: tar -xzf admin_toolbar-8.x-1.17.tar.gz 6. Delete the compressed file from the server, unless your unpacking method already deleted it. 7. Refer to Bagian 11.3, “Downloading and Installing a Module from Drupal.org”, Bagian 11.5, “Downloading and Installing a Theme from Drupal.org”, Bagian 13.6, “Updating a Module”, or Bagian 13.7, “Updating a Theme” to complete the installation or update of the module or theme. Start at the step after the automatic download has been completed. Expand your understanding • If you work with multiple environments (for example, a local development site and a production site) you will have to repeat the steps on each environment, or re-clone the environment. See Bagian 11.8, “Making a Development Site”. • If you added a new theme, navigate in the Manage administrative menu to Appearance (admin/appearance) and uninstall the old theme. Additional resources • Drupal.org community documentation page "Updating modules" • Drupal.org community documentation page "Installing contributed modules (Drupal 8)" • Drupal.org community documentation page "Installing themes" Attributions Written and edited by Boris Doesborg, Jennifer Hodgdon, and Marc Isaacson. 11.7. Concept: Development Sites What are Development Sites? Development Sites are different copies of the same site used for developing, updating, and testing a site without risking the integrity of the live site. An example deployment workflow for site building will usually include the sites mentioned below: Local environment The development process starts with developers working on new features, bug fixes, theming, and configuration in their local environment. 162 Mengembangkan dan Menyesuaikan Situs Anda Development site Developers push the changes they’ve been working on to the development site. For a team of more than one developer, version control is usually used. Git is a version control system that tracks your files for any changes. You can then commit those changes to a repository. Using Git allows team members to work on the same site without overriding each other’s work. It also makes it possible to easily roll back to previous stages of the development. Staging site The staging site can be used for testing, or presenting the changes to the client for approval. QA (Quality Assurance) and UAT (User Acceptance Testing) are most often carried out on the staging site. It is recommended to have live content on both the development and staging sites, so that you can test how the new features will work with the existing content. Production site The live site on the web available to visitors. It contains new features that have been proven safe to go live. Based on the project’s size, scope, requirements, or stakeholders, stages from the above workflow can be removed, or additional stages can be added. For example, a testing site before staging can be added to separate testing and user acceptance processes. Related topics • Bagian 11.8, “Making a Development Site” • Bagian 2.6, “Concept: Editorial Workflow” Additional resources Drupal.org community documentation page "Introduction to Git" Attributions Written and edited by Diána Lakatos, and Jojy Alphonso at Red Crackle. 11.8. Making a Development Site Goal Make a copy of a site that you can use to develop new features and test updates on. 163 Mengembangkan dan Menyesuaikan Situs Anda Prerequisite knowledge Bagian 11.7, “Concept: Development Sites” Site prerequisites • You have a live, developed site that you would like to make a copy of for development purposes. • If you want to use Drush for some of the steps in this task, Drush must be installed. See Bagian 3.2, “Concept: Additional Tools”. Steps 1. Follow the steps in Bagian 3.3, “Preparing to Install”, so that you have hosting set up for your development site, you know where the web root is for your development site, and you have an empty database and database user for your development site to use. 2. Make a database dump file from your live site’s database. Try one of the following methods: • If you are using MySQL as your database, and your live site’s server has phpMyAdmin installed (it is available from many hosting control panels), use the Export tab in phpMyAdmin to export in SQL format. Using gzip compression on the output file is suggested, to reduce the file size. • If you are using MySQL and have access to the command line, use this command (substituting in your site’s database name, user name, and password): mysqldump -u USERNAME -p'PASSWORD' DATABASENAME > BACKUPFILE.sql • If you prefer to use Drush, use this command: drush sql-dump > BACKUPFILE.sql • Use the contributed Backup and Migrate module from within your live site. See Bagian 11.3, “Downloading and Installing a Module from Drupal.org” for instructions on installing contributed modules. You now have a database dump stored in the file BACKUPFILE.sql. For security reasons, avoid storing this file on your hosting server anywhere under the Drupal site root. This will prevent others from getting a copy of your database. 3. Copy all of the files from the web root of your live site to the web root of your development site. 4. Edit the sites/default/settings.php file under your development site’s top-level directory in a plain-text editor. Find the lines near the end that contain the database name, database username, and database password, and update them to the information about the development site database you set up. The lines look something like this (before editing): $databases['default']['default'] = array ( 'database' => 'live_site_database_name', 164 Mengembangkan dan Menyesuaikan Situs Anda 'username' => 'live_site_database_username', 'password' => 'live_site_database_password', 5. Check whether your settings.php file has the following setting; if yes, then you will need to edit this to point to your development site URL instead of your production site URL: $settings['trusted_host_patterns'] 6. Import the database dump file you created, into the development site’s database. Try one of the following methods: • If you are using MySQL as your database, and your live site’s server has PHPMyAdmin installed (it is available from many hosting control panels), use the Import tab in PHPMyAdmin. You may find that you have to restart the import a few times, if your database was large. • If you are using MySQL and have access to the command line, use this command (substituting in your site’s database name, user name, and password; if you made a gzip-compressed backup file, you will also need to uncompress it first): mysql -u USERNAME -pPASSWORD DATABASE_NAME < BACKUPFILE.sql • If you prefer to use Drush, use this command: drush sql-query --file=BACKUPFILE.sql 7. If your development and live sites need to have different configuration, then you have to use configuration overrides in the settings.php file. The $config variable will help you maintain override values separately from the standard configuration data. For instance, you might want the site name to be "Anytown Farmers Market" on the production site, but "Development Site for Anytown Farmers Market" on the development site. To do that, you could have the production value in the site configuration (in the database), and on the development site, in the settings.php file, you would need to have: $config['system.site']['name'] = "Development Site for Anytown Farmers Market"; Expand your understanding • Verify that the development site is working correctly. • Log in to the development site as an administrator, and clear the cache. See Bagian 12.2, “Clearing the Cache”. • Bagian 11.10, “Deploying New Site Features” Additional resources • Drupal.org community documentation page "Backing up a site" • Drupal.org community documentation page "Create a Test Site" Attributions Written and edited by Jennifer Hodgdon, Joe Shindelar at Drupalize.Me, and Jojy Alphonso at Red Crackle. 165 Mengembangkan dan Menyesuaikan Situs Anda 11.9. Using Composer and Git to Download Files Goal Use Composer and/or Git to download files and dependencies in the core software, or in add-on modules and themes. Prerequisite knowledge • Bagian 3.2, “Concept: Additional Tools” • Bagian 11.7, “Concept: Development Sites” Site prerequisites If you want to use Git or Composer, they must be installed either on a local development server or your live site. See Bagian 3.2, “Concept: Additional Tools”. Steps If you are unable to install the Git or Composer tools on your live server, after following the steps in any of the sections below on your local server, you will need to transfer any updated or added files to your live server. The recommended procedure is to make an archive or zip file of the new and changed files, transfer the archive to your live server, and extract it there. If you are using Composer, make sure to check for updates and additions to the following files, in the root of your installation: • vendor directory • autoload.php • composer.json • composer.lock Using Git to download a project Follow these steps if you want to download the development version of the core software, or of a contributed module or theme, from the project’s Git version control repository: 1. In a command-line window, change to one level above the directory where you want the files to reside. For the core software, this would be your web root. For an add-on module, this would be the modules directory, or a sub-directory like contrib under the modules directory. 2. Locate the page for the project that you want to download on Drupal.org; for example, https://www.drupal.org/project/drupal for the core software, or https://www.drupal.org/ project/admin_toolbar for the contributed Admin Toolbar module. 166 Mengembangkan dan Menyesuaikan Situs Anda 3. Click the Version control link near the top of the page, which opens up a page giving Git commands for this project. 4. Copy the git clone command under Setting up repository for the first time, and paste it into your command line. For example, it might be: git clone --branch 8.2.x https://git.drupal.org/project/drupal.git 5. This will create a directory named with the short name of the project (drupal in this example), and download the required files into that directory. If necessary, rename the directory. 6. If you downloaded the drupal project (the core software), follow the instructions below to download its external dependencies. 7. Later on, you can change to the created directory and run the command git pull to update the files to the latest version from the Git repository for the project. Using Composer to download external core dependencies Follow these steps if you downloaded the core software files using Git, which does not include the external dependencies: 1. Change to the core software’s root directory. 2. Run the command composer install at the command line. The external dependencies will be downloaded. Using Composer to download the core software Follow these steps if you have not yet downloaded or installed the core software, and you want to use Composer to download both the core software and its external dependencies: 1. At the command line, change to one level above the directory where you want the software to reside. 2. Enter this command, where my_site_name is the directory you want to create: composer create-project drupal/drupal my_site_name Using Composer to download a module or theme Follow these steps if you have already downloaded the core software, and you want to use Composer to add a contributed module or theme (usually because it has external dependencies that need to be downloaded with Composer): 1. If you have not already done so, tell Composer about the download location for contributed modules and themes, by entering this command from the root of your site installation: composer config repositories.drupal composer https://packages.drupal.org/8 2. If you have not already done so, you can optionally override the default location where Composer will put downloaded modules and themes. For example, typically you would want contributed modules to go in a contrib subdirectory of the top-level modules directory, instead of the default location of modules. To make this change, edit the 167 Mengembangkan dan Menyesuaikan Situs Anda composer.json file at the root level in your site installation. Find the line that says "extra": {, and add these lines following that line: "installer-paths": { "modules/contrib/{$name}": ["type:drupal-module"], "modules/custom/{$name}": ["type:drupal-custom-module"], "profiles/contrib/{$name}": ["type:drupal-profile"], "themes/contrib/{$name}": ["type:drupal-theme"], "themes/custom/{$name}": ["type:drupal-custom-theme"], "libraries/{$name}": ["type:drupal-library"], "drush/{$name}": ["type:drupal-drush"] }, 3. Each time you want to add a contributed module or theme, determine the project’s short name. This is the last part of the URL of the project page; for example, the Geofield module, at https://www.drupal.org/project/geofield, has short name geofield. 4. To download the contributed module or theme, along with its external dependencies, enter the following command at the root of your site (substituting the short name of the module or theme for geofield): composer require drupal/geofield Using Composer to update a project’s files Follow these steps to update the files for the core software or a contributed module or theme, after having already started to manage dependencies with Composer: 1. Determine the short name of the project you want to update. For the core software, it is drupal. For contributed modules and themes, it is the last part of the URL of the project page; for example, the Geofield module, at https://www.drupal.org/project/geofield, has short name geofield. 2. Determine how to enter the version number you want to update to. For example, for version 8.x-1.7 of a contributed module, you would enter just the 1.7, and for the core software version 8.3.1, you would enter 3.1. 3. Enter the following command at the root of your site (substituting the short name of the module or theme for geofield and the correct version number): composer require drupal/geofield:1.7 Additional resources Drupal.org community documentation page "Using Composer with Drupal" Attributions Adapted by Jennifer Hodgdon from "Using Composer with Drupal", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 168 Mengembangkan dan Menyesuaikan Situs Anda 11.10. Deploying New Site Features Goal Copy a view that you have created in a local development site to the production site. Prerequisite knowledge • Bagian 11.8, “Making a Development Site” • Bagian 11.11, “Synchronizing Configuration Versions” • Bagian 11.7, “Concept: Development Sites” Site prerequisites • The core Configuration Manager module must be installed in both the development and production sites. See Bagian 4.3, “Installing a Module” for instructions on installing core modules. • The Vendor content type must exist in both the development and production sites, with the same fields. See Bagian 6.1, “Adding a Content Type”. • The Vendors view must exist in the development site but not the production site. See Bagian 9.3, “Creating a Content List View”. Steps 1. Open the local development site. 2. In the Manage administrative menu, navigate to Configuration > Development > Configuration synchronization > Export > Single item (admin/config/development/ configuration/single/export). The Single export page appears. 3. Select View from the Configuration type list. 4. Select Vendors from the Configuration name list. The configuration appears in the textarea. 5. Copy the configuration from the textarea. 169 Mengembangkan dan Menyesuaikan Situs Anda 6. Open the production site. 7. In the Manage administrative menu, navigate to Configuration > Development > Configuration synchronizationImport > Single item (admin/config/development/ configuration). The Import page appears. 8. Select View from the Configuration type list. 9. Paste the configuration in the textarea. 10. Click Import. The confirmation page appears. 11. Click Confirm. 12. Verify that the view was imported by navigating in the Manage administrative menu to Structure > Views. 170 Mengembangkan dan Menyesuaikan Situs Anda Expand your understanding The steps in this topic show how to export and import a single configuration item. However, often if you develop functionality on a development website and want to transfer it to your production site, you will need to transfer multiple configuration items. For instance, if you developed a new content type with fields, you would need to transfer several configuration items for each field, one for the content type itself, and possibly multiple view mode and form mode items, and they would have to be transferred in the right order. Getting this right can be both tedious and difficult. As an alternative, you can export and import the complete configuration of the site. For this, you would need a local development site that is a clone of the production site (see Bagian 11.8, “Making a Development Site”), and then you can follow the steps in Bagian 11.11, “Synchronizing Configuration Versions” to synchronize configuration between development and production sites. Another alternative is to use the contributed Features module, which allows exporting and importing bundled functionality (for example, all the configuration for a photo gallery). Finally, if you do not see the effect of these changes in your site, you might need to clear the cache. See Bagian 12.2, “Clearing the Cache”. Related concepts • Bagian 11.7, “Concept: Development Sites” • Bagian 2.6, “Concept: Editorial Workflow” Attributions Written by Boris Doesborg. 11.11. Synchronizing Configuration Versions Goal Synchronize the configuration between a development and live site. Prerequisite knowledge • Bagian 1.5, “Concept: Types of Data” • Bagian 3.3, “Preparing to Install” • Bagian 11.7, “Concept: Development Sites” • Bagian 11.8, “Making a Development Site” 171 Mengembangkan dan Menyesuaikan Situs Anda Site prerequisites • You must have a development copy of your production site. See Bagian 11.8, “Making a Development Site”. • The core Configuration Manager module must be installed on both the development and production sites. See Bagian 4.3, “Installing a Module” for instructions on how to install core modules. • You must have changed configuration on either the production or development site (the source site), and want to synchronize the changes to the other site (the destination site). As an example, you can develop a new content type, fields, and views on your development site, and when it is all working correctly, deploy the changes to the live site. • All configuration that should not be synchronized between the source and destination sites must be stored in configuration overrides in the settings.php file rather than in the database. See Bagian 11.8, “Making a Development Site”. Steps 1. In the source site, in the Manage administrative menu, navigate to Configuration > Development > Configuration synchronization > Export (admin/config/development/ configuration/full/export). 2. Click Export. Your site will generate an archive of the full site configuration. Save the file on your local computer. 3. In the destination site, in the Manage administrative menu, navigate to Configuration > Development > Configuration synchronization > Import (admin/config/development/ configuration/full/import). 4. Browse to find the downloaded configuration archive, and click Upload. Your configuration archive will be uploaded to the destination site, and you will be redirected to the configuration Synchronize page (admin/config/development/configuration) with a message saying your files were uploaded. 5. Verify that the differences shown on the page are what you expect. You may see configuration items that have been added, deleted, or changed; for changed items, you can click View differences to see what the changes are. 6. When you are satisfied, click Import all to import the configuration changes. Expand your understanding • If the changes you have made involve only one configuration item (such as one view), you can use the single configuration export/import feature to deploy the change between sites. See Bagian 11.10, “Deploying New Site Features”. • After the step where you export the full configuration from the source site, you might also want to unpack the archive and commit it to a version control system, such as Git, to track changes in your site configuration. See Bagian 3.2, “Concept: Additional Tools”. Attributions 172 Mengembangkan dan Menyesuaikan Situs Anda Written by Jennifer Hodgdon. 173 Bab 12. Mencegah dan Memperbaiki Masalah 12.1. Concept: Cache Prerequisite knowledge Bagian 1.1, “Concept: Drupal as a Content Management System” What is the page cache? The software that runs your site, on each page request, must perform calculations and retrieve data from the database, in order to compose the page that is sent to the web browser or other application that is accessing the site. These calculations take time, which can mean that your page load time is longer than would be desirable. There are several ways that page load time can be sped up, including installing software on the server. The system includes the core Internal Page Cache and Dynamic Page Cache modules, which do not require any additional server software; they use a database cache mechanism to speed up your site. The way these modules work is that during page calculations, intermediate results and the final page output are stored in a special database area (known as the cache). Then the next time a compatible request is made, intermediate or final results, as appropriate, can be retrieved and used rather than redoing the entire calculation. In addition, when content or data that affects a particular calculation is updated, the affected cached data is removed from the cache, forcing that part of the calculation to be redone the next time it is needed. These caching modules normally work reasonably well, and offer at least some speed-up for most sites. However, sometimes the page cache can have problems, such as: • Corrupted data in the cache, leading to garbled or incorrect page output • Old data remaining in the cache too long, leading to outdated page output • Insufficient caching, leading to slow page loads What other data is cached? Independent of whether the two page cache modules are installed on your site, the software that your site runs will still cache the output of many internal calculations. The core systems that cache data include: • The theme system caches information in the database cache about which template files are used to render various types of data. If you are developing a new theme and add a new template file, you’ll need to clear this cache to have your theme file recognized. 174 Mencegah dan Memperbaiki Masalah • CSS and JavaScript files can optionally be optimized and compressed (depending on your site settings). If so, the compressed versions are stored in the file system so that they don’t have to be re-optimized too often. If you are developing a module or theme, you may need to either turn off or clear this file cache to have changes to CSS or JavaScript files be recognized. • The system locates certain low-level PHP functions and classes, such as hook implementations and plugin classes, from your installed modules and stores information about which module has which functionality. If you are developing a new module or adding features to an existing module, you may need to clear this cache to have your new features be recognized. Related topics If you have problems with your site, the first thing to try to fix it is usually to clear the cache. See Bagian 12.2, “Clearing the Cache” for more information. Additional resources Learn about additional caching and performance optimization methods in the Drupal.org community documentation page "Caching to improve performance". Attributions Written by Jennifer Hodgdon. 12.2. Clearing the Cache Goal Clear or rebuild your site’s internal caches to ensure they are up-to-date with the most recent data, using the user interface or Drush. Prerequisite knowledge • Bagian 12.1, “Concept: Cache” • Bagian 3.2, “Concept: Additional Tools” Site prerequisites If you want to use Drush to clear the cache, Drush must be installed. See Bagian 3.2, “Concept: Additional Tools”. 175 Mencegah dan Memperbaiki Masalah Steps You can use the administrative interface or Drush to clear the cache. Using the administrative interface 1. In the Manage administrative menu, navigate to Configuration > Development > Performance (admin/config/development/performance). 2. Click Clear all caches. 3. A message saying the cache has been cleared appears at the top of the page. Using Drush You can use one of two commands: • Use the command drush cache-rebuild to clear and rebuild all cached data for a site. After running this command, you will see the output message "Cache rebuild complete." • Use the command drush cc to see a list of individual caches and then choose the specific cache you would like to clear. Running this command should produce output like the following: > drush cc Enter a number to choose which cache to clear. [0] : Cancel [1] : drush [2] : theme-registry [3] : menu [4] : css-js [5] : block [6] : module-list [7] : theme-list [8] : render [9] : views Choose a cache to clear by entering the number associated with that cache. Press "Enter" to continue. Additional resources Drupal.org community documentation page "Clearing or rebuilding Drupal’s cache" Attributions Adapted and edited by Joe Shindelar and Jack Haas from "Clearing or rebuilding Drupal’s cache", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 176 Mencegah dan Memperbaiki Masalah 12.3. Concept: Data Backups Prerequisite knowledge • Bagian 1.1, “Concept: Drupal as a Content Management System” • Bagian 3.3, “Preparing to Install” What is a site backup? If something happens to the computer (or computers) that your site and its database are running on, or if you lose access to this computer, you could lose some or all of your site’s data. You could also lose data if your site is hacked, or if someone with administrative privileges on your site deletes or alters data mistakenly from the administrative interface. In order to prevent scenarios like this from being permanent, expensive data losses, it is important to make regular backups of your site’s data, and to store them in a location that is separate from the computer where your site is running. The frequency with which you should make data backups, and how many backups you should keep, depends on how frequently your site is changing. If you have a very large amount of content on your site that is being added to or updated many times per day, you would want to make more frequent backups than you would for a site that changes rarely. Also consider that some time could pass between when a data problem occurs and when you notice that it is a problem, so storing a sequence of backups (so that you can go back to the last known good data and retrieve that), rather than overwriting a single backup repeatedly, is a good practice. Another consideration is that whatever format you store your backups in, it is a good idea to verify that you can actually retrieve lost data from your backups. You might want to test several possible data loss scenarios, and make sure that your data can be restored to the site in all cases. In order to make a complete backup of your site, you will need to make copies of the following: • The data in the sites directory, including the sites/default/settings.php file. • The data in your site’s database. A few tables can be truncated, such as those storing the temporary data cache and user login session information, but it is always safe to back up the entire database. • Uploaded files, such as images and other attachments. The location of these files is configurable; the standard location is the sites/default/files directory under your site root. In the Manage administrative menu, navigate to Configuration > Media > File system (admin/ config/media/file-system) to check the file upload locations; to change them, you’ll need to edit your settings.php file. • Modules, themes and any other software files you have customized. You can find customized modules and themes in the modules and themes directories respectively. Some 177 Mencegah dan Memperbaiki Masalah people prefer to back up all software files, including core files and contributed modules and themes (which you could recover by downloading them again from the source), rather than trying to pick out specific files that definitely need to be backed up. You can perform a test to confirm whether your backup has been done right by making a development copy of the site (see Bagian 11.8, “Making a Development Site”). Related topics • Bagian 13.5, “Updating the Core Software” • Bagian 11.8, “Making a Development Site” • Bagian 12.1, “Concept: Cache” Additional resources • Drupal.org community documentation page "Backing up a site" • The contributed Backup and Migrate module, which can be used to set up automatic backups of the database and uploaded files. Attributions Written by Jennifer Hodgdon. 12.4. Concept: Log What is a Log? Your site captures system events in a log to be reviewed by an authorized individual at a later time. The log is a list of recorded events containing usage data, performance data, errors, warnings, and operational information. It is vital to check the log on a regular basis as it is often the only way to tell what is going on. You can find your site’s recent log messages in the Manage administrative menu by navigating to Reports > Recent log messages (admin/reports/dblog). 178 Mencegah dan Memperbaiki Masalah Attributions Adapted by Diána Lakatos from "Reports" copyright 2000-2017 by the individual contributors to the Drupal Community Documentation 12.5. Concept: Status Report What is a Status Report? The status report is a short overview of your site’s parameters as well as any problems detected with your installation. It may be useful to copy and paste this information into support requests filed on Drupal.org’s support forums and project issue queues or when asking for help on other channels. You can find the status report in the Manage administrative menu by navigating to Reports > Status report (admin/reports/status). 179 Mencegah dan Memperbaiki Masalah Related topics Bagian 14.2, “Getting Support” Attributions Adapted by Diána Lakatos from "Reports" copyright 2000-2017 by the individual contributors to the Drupal Community Documentation 180 Bab 13. Keamanan dan Pemeliharaan 13.1. Concept: Cron What are cron tasks? To ensure that your site and its modules continue to function well, a group of administrative operations should be run periodically. These operations are called cron tasks. Examples of cron tasks are: checking for module and theme updates, indexing content for search, or cleaning up temporary files. What is the relationship between the site’s cron tasks and Unix cron? Linux/Unix-based operating systems have a cron scheduler that can be used to run periodic tasks. You can use the server’s cron scheduler to schedule runs of the site’s cron tasks. Alternatively, you can use the core Automated Cron module to run tasks. You can check the site’s cron tasks' status in the status report. Related topics • Bagian 13.2, “Configuring Cron Maintenance Tasks” • Bagian 12.5, “Concept: Status Report” Additional resources Drupal.org community documentation page "Setting up cron" Attributions Written and edited by Diána Lakatos at Pronovix, Dave Hansen-Lange at Advomatic, and Boris Doesborg. 13.2. Configuring Cron Maintenance Tasks Goal Check whether cron maintenance tasks are run regularly, and if not, either install the core Automated Cron module or run cron maintenance tasks from outside the website. 181 Keamanan dan Pemeliharaan Prerequisite knowledge Bagian 13.1, “Concept: Cron” Steps 1. Review the Status report (see Bagian 12.5, “Concept: Status Report”) to see when cron maintenance tasks were last run. If you installed the website using the core Standard installation profile (or similar), then cron maintenance tasks might already be running via the core Automated Cron module. By default, these tasks are run about every three hours. 2. Choose whether to run cron maintenance tasks using the core Automated Cron module, or by other means. The core Automated Cron module might not be suitable for some websites because: • Each time someone accesses a page on the site, the module checks how long it has been since cron maintenance tasks have last run, and then runs them if necessary. If no one visits the website for a long time, cron maintenance tasks will not be run. • Cron maintenance tasks are run after the page has been generated. This means there is less time for the tasks to be run before various server timeouts are reached (for example, PHP execution timeout). If this happens, the logs (see Bagian 12.4, “Concept: Log”) will show error messages that cron is unable to complete. • There is a small scalability cost associated with the core Automated Cron module. This is because one of the web server’s processes is occupied (and can’t serve other web pages) until the cron maintenance tasks are complete. 3. If you want to use the core Automated Cron module, first make sure it is installed (it is installed with the core Standard install profile; see Bagian 4.3, “Installing a Module” if it is not installed). Next, configure the module to control how frequently cron maintenance tasks are run. In the Manage administrative menu, navigate to Configuration > System > Cron (admin/ config/system/cron). Choose the desired interval in the Cron settings section, and click Save configuration. 182 Keamanan dan Pemeliharaan 4. If you want to run cron maintenance tasks from outside the website, uninstall the core Automated Cron module (see Bagian 4.4, “Uninstalling Unused Modules”). Next, find the cron URL. This URL is shown in the Status report (see Bagian 12.5, “Concept: Status Report”), and in the Cron administration page (see previous step). The URL looks like this: http:// www.example.com/cron/0MgWtfB33FYbbQ5UAC3L0LL3RC0PT3RNUBZILLA0Nf1Re Whenever this URL is visited, cron maintenance tasks will run. Set up one of the following schedulers to access this URL regularly: • The Cron daemon (Linux, OS X, Solaris, BSD) • Scheduled Tasks (Windows) • A cron SASS provider (software as a service) • A cron manager provided by your web hosting provider (see the documentation provided by your provider) Related concepts Bagian 13.3, “Concept: Security and Regular Updates” Additional resources • Drush page "Running Drupal cron tasks from Drush" • Drupal.org community documentation page "Setting up cron" Attributions Written and edited by Dave Hansen-Lange at Advomatic, Boris Doesborg, and Jennifer Hodgdon. 183 Keamanan dan Pemeliharaan 13.3. Concept: Security and Regular Updates Prerequisite knowledge • Bagian 1.1, “Concept: Drupal as a Content Management System” • Bagian 1.2, “Concept: Modules” • Bagian 1.3, “Concept: Themes” • Bagian 1.6, “Concept: The Drupal Project” What are security updates? Any software occasionally has bugs, and sometimes these bugs have security implications. When security bugs are fixed in the core software, modules, or themes that your site uses, they are released in a security update. You will need to apply security updates in order to keep your site secure. See Bagian 13.4, “Keeping Track of Updates” to learn how to be notified of security updates by email, and Bagian 13.5, “Updating the Core Software”, Bagian 13.6, “Updating a Module”, and Bagian 13.7, “Updating a Theme” to learn how to make updates. What is the security team? The Drupal open-source project has a team of volunteers who track security-related bugs and release security updates. They also help other developers fix bugs, and maintain information for users on how to keep their websites secure. You can learn more about the security team and their practices and processes at the Drupal.org Security Team page. How are security bugs reported? It is important that security problems be kept confidential until they are fixed, so that sites are less likely to be compromised before they can be secured. If you find a potential security problem in any of the software you downloaded from the Drupal.org website, follow the procedures on the Drupal.org Security Team page to report it. What are regular (non-security) updates? The core software, modules, and themes also periodically have regular updates to add new features and fix bugs. These updates are less critical than security updates. As a general best practice, updates should be applied as long as they do not cause problems with your site. Testing on a development copy of your site is always a good idea before applying updates on a live site. This is because some updates may include changes that are not compatible with the modules or themes on your site, or that will break a particular functionality on your site. Related topics • Bagian 13.4, “Keeping Track of Updates” • Bagian 13.5, “Updating the Core Software” • Bagian 13.6, “Updating a Module” 184 Keamanan dan Pemeliharaan • Bagian 13.7, “Updating a Theme” • Bagian 11.8, “Making a Development Site” Additional resources • Drupal.org community documentation page "Securing your site" • "Security advisories" on Drupal.org • Drupal.org Security team Attributions Written and edited by Boris Doesborg and Jennifer Hodgdon. 13.4. Keeping Track of Updates Goal Keep your site safe and up-to-date by keeping up with the latest security updates. Prerequisite knowledge Bagian 13.3, “Concept: Security and Regular Updates” Steps There are a few different ways to receive notifications of security releases: • In the Manage administrative menu, navigate to Reports > Available updates > Settings. Enter the email addresses to be notified when updates are available. You can also specify whether you want daily or weekly updates. Click Save configuration. • Subscribe to the security announcements email list. To subscribe, log in to Drupal.org, go to your user profile page and subscribe to the security newsletter on the Edit > My newsletters tab. • Follow @drupalsecurity on Twitter. • Subscribe to RSS feeds for core security updates, contributed project updates and public service announcements. Related concepts • Bagian 13.3, “Concept: Security and Regular Updates” • Bagian 13.5, “Updating the Core Software” • Bagian 13.6, “Updating a Module” • Bagian 13.7, “Updating a Theme” 185 Keamanan dan Pemeliharaan Additional resources • "Security advisories" on Drupal.org • Drupal.org Security Team • @drupalsecurity on Twitter Attributions Written by Sarah German at Advomatic. 13.5. Updating the Core Software Goal Update the core software, either through the administrative interface or by using Drush. Site prerequisites • If you want to use Drush, Drush must be installed. See Bagian 3.2, “Concept: Additional Tools”. • If your site is live, you should test this process in a development environment before running it on your production site. See Bagian 11.8, “Making a Development Site”. Steps 1. Make a complete backup of your site. Refer to Bagian 12.3, “Concept: Data Backups”. 2. Open settings.php (/sites/default/settings.php) in any plain text editor. Find the line with the $settings[update_free_access] variable. By default, it is set to "FALSE" due to security reasons. Change the setting to "TRUE": $settings['update_free_access'] = TRUE; 3. Disable any caching technique (memcache, varnish, and so on) your application might be using. 4. Put your site in maintenance mode. See Bagian 11.2, “Enabling and Disabling Maintenance Mode”. 5. If you are using Composer to manage dependencies, or using Git, skip the next six steps, and instead see Bagian 11.9, “Using Composer and Git to Download Files” for instructions on downloading updated files. Continue with the update.php step. 6. Download the tar.gz or zip file archive for the latest version of Drupal 8.x core from Drupal.org Drupal Core Downloads. See Bagian 3.3, “Preparing to Install” for more details on how to find the latest version. 7. Upload the archive file to your web hosting server. 186 Keamanan dan Pemeliharaan 8. Extract the archive file to a temporary directory on your server (should be outside the directory where the site is hosted). Your hosting control panel’s file manager should provide a way to extract the files. Or, if you have terminal access to your hosting server (running Linux), you can use a command like: tar -xzf drupal-8.3.2.tar.gz 9. You can also use Drush to download the archive and extract it in one step, by navigating to the temporary directory on the server and entering this command: drush dl drupal 10. In your site hosting directory, delete the core and vendor directories, and all files that are not in a subdirectory, including .htaccess, composer.json, and autoload.php. Don’t delete custom and customized files because you may end up losing the custom functionality stored in them. 11. Copy the core and vendor directories and the non-custom/non-customized files that you deleted in the preceding step from the temporary directory to your site directory. 12. Run the update.php script using either of the following: • Visit http://www.example.com/update.php in your browser (where www.example.com is your site’s URL). Click Continue in the first screen to run the updates and successfully complete the script. • Run the following Drush command: drush updb 13. If you get any error or warning, re-run the update.php script again till all the updates have been completed successfully. 14. Open settings.php (/sites/default/settings.php) in a text editor. Find the line with the $settings[update_free_access] variable and update it to "FALSE": $settings['update_free_access'] = FALSE; 15. Click Administration pages to return to the administration section of your site. 16. Take your site out of maintenance mode. See Bagian 11.2, “Enabling and Disabling Maintenance Mode”. 17. Clear the cache. See Bagian 12.2, “Clearing the Cache”. 18. Re-enable any caching technique you disabled at Step 3. 19. You should have the updated version running. You can verify the current version of your software by checking the Status report (see Bagian 12.5, “Concept: Status Report”). Expand your understanding • Bagian 3.2, “Concept: Additional Tools” • Bagian 11.8, “Making a Development Site” • Bagian 12.3, “Concept: Data Backups” Related concepts Bagian 12.5, “Concept: Status Report” 187 Keamanan dan Pemeliharaan Additional resources • "Drupal Core Downloads" page on Drupal.org • "Registry Rebuild" page on Drupal.org • The file /core/UPDATE.txt within your installation. Attributions Written and edited by Surendra Mohan, Boris Doesborgh, and Jojy Alphonso at Red Crackle. 13.6. Updating a Module Goal Update a contributed module and run the Database updates script. Prerequisite knowledge • Bagian 13.3, “Concept: Security and Regular Updates” • Bagian 13.1, “Concept: Cron” Site prerequisites • A contributed module has been installed and there is an update available for it. See Bagian 11.3, “Downloading and Installing a Module from Drupal.org” and Bagian 13.4, “Keeping Track of Updates”. • If your site is live, you should test this process in a development environment before running it on your production site. See Bagian 11.8, “Making a Development Site”. • You have created a full-site backup. See Bagian 12.3, “Concept: Data Backups”. • If you want to use the user interface, the core Update Manager module must be installed. See Bagian 4.3, “Installing a Module” for instructions on installing core modules. • If you want to use Drush, Drush must be installed. See Bagian 3.2, “Concept: Additional Tools”. Steps Before you start, check for module-specific update instructions. This is typically necessary while updating modules that involve the usage of third-party libraries. Read and understand all module-specific requirements before proceeding with the updates. To find instructions, check the module’s project page Read Documentation link. To view further instructions, download the tar.gz or .zip file from the project page to your local computer. Unzip the file and look for README.txt, INSTALL.txt, and UPGRADE.txt that come 188 Keamanan dan Pemeliharaan with the module’s installation file. Also, review the release notes on the project page by clicking the version number you’re downloading. You can use the administrative interface or Drush to update a contributed module. If you are updating a custom module rather than a contributed module, if you see a message saying Installing modules and themes requires FTP access to your server, or if the steps below do not work to obtain the new module files, follow the steps in Bagian 11.6, “Manually Downloading Module or Theme Files”. You can then continue here with step 6 in the instructions for the administrative interface below. Using the administrative interface 1. Put your site in maintenance mode. See Bagian 11.2, “Enabling and Disabling Maintenance Mode”. 2. In the Manage administrative menu, navigate to Reports > Available updates > Update (admin/reports/updates/update). 3. Find and check the module in the list. Click Download these updates for the module. 189 Keamanan dan Pemeliharaan 4. Click Continue. 5. Click Run database updates. If you obtained the new module files manually, start with this step, and reach the database updates page by typing the URL example.com/update.php in your browser. 6. Click Continue and apply all updates. The database update scripts will be executed. 7. Click Administration pages to return to the administration section of your site. 8. Take your site out of maintenance mode. See Bagian 11.2, “Enabling and Disabling Maintenance Mode”. 9. Clear the cache (refer to Bagian 12.2, “Clearing the Cache”). Using Drush 1. Find the project name for the module you wish to update. It is the last segment of the module’s project page URL. For example, if the project URL is https://www.drupal.org/ project/admin_toolbar, the project name is "admin_toolbar". 2. Run the following Drush command, giving the project name (for example, admin_toolbar) as a parameter (if you have more than one module to update, add the additional module project names to the end of the command, separated by spaces): drush up admin_toolbar 3. Follow the instructions on the screen. Expand your understanding • Review the site log (refer to Bagian 12.4, “Concept: Log”) once the updates are complete to check for errors. • Bagian 13.7, “Updating a Theme” Additional resources Drupal.org community documentation page "Updating modules" Attributions Adapted by Boris Doesborgh, and Sarah German at Advomatic, from "Updating modules", copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. 13.7. Updating a Theme Goal Update a contributed theme on your site and run the Database Updates script. 190 Keamanan dan Pemeliharaan Prerequisite knowledge • Bagian 13.3, “Concept: Security and Regular Updates” • Bagian 13.1, “Concept: Cron” Site prerequisites • A contributed theme has been installed and there is an update available for it. See Bagian 11.5, “Downloading and Installing a Theme from Drupal.org” and Bagian 13.4, “Keeping Track of Updates”. • If your site is live, you should test this process in a development environment before running it on your production site. See Bagian 11.8, “Making a Development Site”. • You have created a full site backup. See Bagian 12.3, “Concept: Data Backups”. • If you want to use the user interface, the core Update Manager module must be installed. See Bagian 4.3, “Installing a Module” for instructions on installing core modules. • If you want to use Drush, Drush must be installed. See Bagian 3.2, “Concept: Additional Tools”. Steps You can use the administrative interface or Drush to update a contributed theme. If you are updating a custom theme rather than a contributed theme, if you see a message saying Installing modules and themes requires FTP access to your server, or if the steps below do not work to obtain the new theme files, follow the steps in Bagian 11.6, “Manually Downloading Module or Theme Files”, and then continue with step 6 in the instructions for administrative interface below. Using the administrative interface 1. Put your site in maintenance mode. See Bagian 11.2, “Enabling and Disabling Maintenance Mode”. 2. In the Manage administrative menu, navigate to Reports > Available updates > Update (admin/reports/updates/update). 3. Find and check the theme in the list. Click Download these updates for the theme. 191 Keamanan dan Pemeliharaan 4. Click Continue. 5. Click Run database updates. If you obtained the new theme files manually, start with this step, and reach the database updates page by typing the URL example.com/update.php in your browser. 6. Click Continue to run the updates. The database update scripts will be executed. 7. Click Administration pages to return to the administration section of your site. 8. Take your site out of maintenance mode. See Bagian 11.2, “Enabling and Disabling Maintenance Mode”. 9. Clear the Drupal cache (refer to Bagian 12.2, “Clearing the Cache”). Using Drush 1. Find the project name for the theme you wish to update, which is the last segment of the theme’s project page URL. For example, if the project URL is https://www.drupal.org/ project/mayo, the project name is "mayo". 2. Run the following Drush command, giving the project name (for example, mayo) as a parameter: drush up mayo 3. Follow the instructions on the screen. Expand your understanding • Review the site log, see Bagian 12.4, “Concept: Log”, once the updates are complete to check for errors. 192 Keamanan dan Pemeliharaan • Bagian 13.6, “Updating a Module” Attributions Written by Boris Doesborg. 193 Bab 14. Pemikiran Akhir 14.1. Connecting with the Community Prerequisite knowledge Bagian 1.6, “Concept: The Drupal Project” How can you connect with the community? The Drupal project has a world-wide community of developers and users. One of the best ways to improve your knowledge of the platform is to connect with others that are using it, and get involved in the open-source community. There are many ways that you can get started: Attend an event There are both regional and international Drupal events held around the world. See the "DrupalCon" page on Drupal.org to find international events, and the "Event Calendar" on groups.drupal.org or drupical.com to find regional events. Join a local group There are Drupal user groups all around the world. Many of them have regular meetings, which you can attend to learn more about Drupal and connect to other Drupal users. Find local user groups on groups.drupal.org. Participate in a topical or language group There are also interest groups for a wide range of topics, which have on-line discussion forums. Find topical groups on groups.drupal.org. Many languages have their own websites too; you can find them on the "Language-specific communities" page on Drupal.org. Chat online The Drupal project uses IRC for on-line chatting. There are regional, topical, and generalpurpose chat groups available. Find out more on the "IRC" page on Drupal.org. Report a problem See below. Contribute You can contribute your time and expertise to the community in many ways, such as: 194 Pemikiran Akhir • Developing modules or themes. See the "Contribute to Development" page on Drupal.org, or improving them (using the issue queues for existing projects). • Translating the user interface. See localize.drupal.org. • Writing documentation. See "Contribute to Documentation" on Drupal.org. • Answer Support questions. See Bagian 14.2, “Getting Support”. How can you report a problem or suggest a feature? Each project within the community (such as the Drupal Core project for the base software, and projects for each contributed theme and module) uses issues to keep track of software bugs and plans for new features. You can participate by creating a bug report when you find a problem, creating a feature request, or commenting on existing issues. Search before creating an issue, to make sure that the problem or feature has not already been reported or requested. See the Drupal.org page "Use the issue queue" and the Drupal.org page "Reporting a problem" for more information. If you find a problem that you believe is related to security, such as a cross-site scripting vulnerability, do not report it in the standard issue queue. Instead, report it to the security team. See the Drupal.org page "How to report a security issue" for details. Related topics Bagian 14.2, “Getting Support” Additional resources • "Code of Conduct" on Drupal.org • "Event Calendar" on groups.drupal.org or drupical.com • "Where is the Drupal Community?" page on Drupal.org • groups.drupal.org • "IRC" page on Drupal.org • "Ways to get involved" page on Drupal.org • Drupal.org page "Why get involved?" • Drupal.org page "Contributor tasks" • Drupal.org page "Use the issue queue" • Drupal.org page "Reporting a problem" • Drupal.org page "How to report a security issue" Attributions Written by Jennifer Hodgdon, and Joe Shindelar at Drupalize.Me. 195 Pemikiran Akhir 14.2. Getting Support Prerequisite knowledge • Bagian 1.6, “Concept: The Drupal Project” • Bagian 14.1, “Connecting with the Community” 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 Bagian 14.1, “Connecting with the Community”). 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 Bagian 14.1, “Connecting with the Community” 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.org Forums • "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 "Drupal Marketplace" on Drupal.org. Related topics • Bagian 14.3, “Learning More” • Bagian 14.1, “Connecting with the Community” Additional resources • "Support" page on Drupal.org • "Drupal Marketplace" on Drupal.org 196 Pemikiran Akhir • The Drupal.org Forums • "Drupal Answers" on StackExchange Attributions Written by Jennifer Hodgdon. 14.3. Learning More Prerequisite knowledge • Bagian 1.6, “Concept: The Drupal Project” • Bagian 14.1, “Connecting with the Community” Where can you go to learn more? The following resources should prove useful to you, as you continue to advance your skills: "Drupal Community Documentation" section on Drupal.org Wiki-like documentation contributed by the Drupal community, ranging from basic to advanced, about all aspects of Drupal (site building and administration, theming, development, and contributed modules). api.drupal.org Reference documentation for programmers about the Drupal API. "Drupal Planet" page on Drupal.org An aggregation of blog posts about Drupal from around the web, posted by blogging members of the Drupal community who have applied for inclusion. Topics range from programming to site building to Drupal news. Groups, events, and meetups See Bagian 14.1, “Connecting with the Community” for more about topical, regional, and language groups, as well as local, regional, and international events. "Training Marketplace" page on Drupal.org The Marketplace lists paid training providers. For free training, check whether events include training sessions; there are also free or very low-cost training events listed on the "Global Training Days" page on Drupal.org. Support sites See Bagian 14.2, “Getting Support” to locate support forums; searching them can be useful for learning about specific topics. 197 Pemikiran Akhir Attributions Written by Jennifer Hodgdon, and Joe Shindelar at Drupalize.Me. 198 Glosarium Ajax A web technology used to exchange data with a server to dynamically update parts of a web page (for example, forms) without needing entire page reloads. Alias A user-friendly name to replace the internal path that the system assigns to a URL on the site. For example, you might assign an alias of /about to the About page on your site, to replace the internal path /node/5. This would give the page a URL of http://example.com/ about instead of http://example.com/node/5. See Bagian 5.1, “Concept: Paths, Aliases, and URLs” for more information. Anonymous A person (user) interacting with the site who is not logged in. See Bagian 7.1, “Concept: Users, Roles, and Permissions” for more information. Block A chunk of content (text, images, links, etc.) that can be displayed on a page of a site. Blocks are displayed in regions. See Bagian 8.1, “Concept: Blocks” for more information. Breakpoint Breakpoints are used to separate the height or width of browser screens, printers, and other media output types into steps. A responsive site adjusts its presentation at these breakpoints. See Bagian 6.14, “Concept: Responsive Image Styles” for more information. Bundle Synonym for Entity subtype. Cache The site’s internal cache stores the output of time-consuming calculations, such as computing output for an HTML page request, and then retrieves them instead of recalculating the next time they are needed. External caching systems can also be used on the web server to speed up a site’s response. See Bagian 12.1, “Concept: Cache” for more information on the internal cache. CMS Acronym for Content Management System. Configuration Information about your site that is not content, and is meant to be more permanent than state information, such as the name of your site, the content types and views you have defined, etc. See Bagian 1.5, “Concept: Types of Data” for more information. 199 Glosarium Content Information meant to be displayed on your site, such as text, images, downloads, etc. See also Configuration and State. See Bagian 1.5, “Concept: Types of Data” for more information. Content item An item of content that is typically meant to be displayed as the main content of a page on your site. This is an entity type. See Bagian 2.3, “Concept: Content Entities and Fields” for more information. Content Management System (CMS) A collection of tools designed to allow the creation, modification, organization, search, retrieval and removal of information on a website. See Bagian 1.1, “Concept: Drupal as a Content Management System” for more information. Content type An entity subtype for the content itementity type. Each content type is used for some particular purpose on the site, and each has its own fields. For example, a site for a farmers market might have a content type for simple pages, and another for a vendor listing page. See Bagian 2.3, “Concept: Content Entities and Fields” for more information. Contextual link A link to an administrative page for editing or configuring a feature of the site, shown in the context where that feature is displayed. Example: a link to configure a menu that is shown when you hover your mouse over the menu. See Bagian 4.1, “Concept: Administrative Overview” for more information. Contributed Modules, themes, and distributions that are not part of the Drupal core download, and that can be downloaded separately from the Drupal.org website. Cron On some operating systems, cron is a command scheduler application that executes commands or scripts periodically. Your site defines periodic tasks, also known as cron tasks, that need to be triggered either by an operating system cron scheduler, or internally. See Bagian 13.1, “Concept: Cron” for more information. Distribution A single download that provides a shortcut for setting up a specific type of site, such as a website for a club or for e-commerce. A distribution contains Drupal core, along with contributedmodules and/or themes; many distributions also pre-configure the site or even create sample content upon installation. See Bagian 1.4, “Concept: Distributions” for more information. Drupal core The files, themes, profiles, and modules included with the standard project software download. See Bagian 1.1, “Concept: Drupal as a Content Management System” for more information. Entity An item of either content or configuration data, although in common usage, the term often refers to content entities. Examples include content items, custom blocks, taxonomy 200 Glosarium terms, and definitions of content types; the first three are content entities, and the last is a configuration entity. See also Entity type, Entity subtype, and Field. See Bagian 2.3, “Concept: Content Entities and Fields” for more information. Entity subtype Within a contententity type, a grouping of entities that share the same fields. For example, within the content item entity type, a farmers market site might have subtypes (known as content types) for static pages and vendor pages, each with its own group of fields. You may also see the term bundle used (especially in programmer documentation) as a synonym of entity subtype. See Bagian 2.3, “Concept: Content Entities and Fields” for more information. Entity type The overall type of an entity; in common usage, it is only applied to a content entity. Examples include content types, taxonomy terms, and custom blocks. See Bagian 2.3, “Concept: Content Entities and Fields” for more information. Field Data of a certain type that is attached to a contententity. For instance, on a farmers market site’s vendor content type, you might have fields for an image, the vendor description, and a taxonomy term. See Bagian 2.3, “Concept: Content Entities and Fields” for more information. Field bundle Synonym for Entity subtype. Field formatter Configuration that defines how the data in a field is displayed. For example, a text field could be displayed with a prefix and/or suffix, and it could have its HTML tags stripped out or limited. See also View mode and Field widget. See Bagian 6.10, “Concept: View Modes and Formatters” for more information. Field widget Configuration that defines how someone can enter or edit data for a field on a data entry form. For example, a text field could use a single-line or multi-line entry box, and there could be a setting for the size of the box. See also Field formatter. See Bagian 6.8, “Concept: Forms and Widgets” for more information. Formatter See Field formatter. FOSS Acronym for Free and Open Source Software, meaning software that is developed by a community of people and released under a non-commercial license. See also GPL. See Bagian 1.6, “Concept: The Drupal Project” for more information. GPL Acronym for the GNU General Public License, a non-commercial software license. All software downloaded from the Drupal.org website is licensed under the "GNU General Public License, version 2". See also FOSS. See Bagian 1.7, “Concept: Drupal Licensing” for more information. 201 Glosarium Image style A set of processing steps that transform a base image into a new image; typical processing includes scaling and cropping. See Bagian 6.12, “Concept: Image Styles” for more information. LAMP Acronym for Linux, Apache, MySQL, and PHP: the software on the web server that the scripts commonly run on (although it can use other operating systems, web servers, and databases). See Bagian 3.1, “Concept: Server Requirements” for more information. Log A list of recorded events on the site, such as usage data, performance data, errors, warnings, and operational information. See Bagian 12.4, “Concept: Log” for more information. Menu A set of links used for navigation on a site, which may be arranged in a hierarchy. See Bagian 5.6, “Concept: Menu” for more information. Module Software (usually PHP, JavaScript, and/or CSS) that extends site features and adds functionality. The Drupal project distinguishes between core and contributed modules. See Bagian 1.2, “Concept: Modules” for more information. Path The unique, last part of the internal URL that the system assigns to a page on the site, which can be a visitor-facing page or an administrative page. For example, the internal URL for the About page on your site might be http://example.com/node/5, and in this case, the path is node/5. See also Alias. See Bagian 5.1, “Concept: Paths, Aliases, and URLs” for more information. Permission The ability to perform some action on the site, such as editing a particular type of content, or viewing user profiles. See also Role. See Bagian 7.1, “Concept: Users, Roles, and Permissions” for more information. Reference field A field that represents a relationship between an entity and one or more other entities, which may be the same entity type or a different type. For example, on a farmers market site, a recipe content item might have a reference field to the vendor (also a content item) that posted the recipe. Taxonomy term fields are also reference fields. See Bagian 6.4, “Concept: Reference Fields” for more information. Region A defined area of a page where content can be placed, such as the header, footer, main content area, left sidebar, etc. Regions are defined by themes, and the content displayed in each region is contained in blocks. See Bagian 2.1, “Concept: Regions in a Theme” for more information. 202 Glosarium Responsive A site or theme is said to be responsive if it adjusts its presentation in response to the size of the browser screen, printer, or other media output type. See also Breakpoint. See Bagian 6.14, “Concept: Responsive Image Styles” for more information. Revision A record of the past or present state of a contententity, as it is edited over time. See Bagian 2.6, “Concept: Editorial Workflow” for more information. Role A named set of permissions that can be applied to a user account. See Bagian 7.1, “Concept: Users, Roles, and Permissions” for more information. Security update An update that fixes a security-related bug, such as a hacking vulnerability. See Bagian 13.3, “Concept: Security and Regular Updates” for more information. State Information of a temporary nature about the current state of your site, such as the time when cron was last run, etc. See also Content and Configuration. See Bagian 1.5, “Concept: Types of Data” for more information. Taxonomy The process of classifying content. See Bagian 6.5, “Concept: Taxonomy” for more information. Taxonomy term A term used to classify content, such as a tag or a category. See also Vocabulary. See Bagian 6.5, “Concept: Taxonomy” for more information. Text format Configuration that defines the processing that happens to user-entered text before it is shown in the browser. This might include stripping or limiting HTML tags, or turning URLs into links. See Bagian 6.15, “Concept: Text Formats and Editors” for more information. Theme Software and asset files (images, CSS, PHP code, and/or templates) that determine the style and layout of the site. The Drupal project distinguishes between core and contributed themes. See Bagian 1.3, “Concept: Themes” for more information. UI Acronym for User Interface. Update A newer version of your site’s software, either Drupal core or a module or theme. See also Security update. See Bagian 13.3, “Concept: Security and Regular Updates” for more information. User A person interacting with the site, either logged-in or anonymous. See Bagian 7.1, “Concept: Users, Roles, and Permissions” for more information. 203 Glosarium User interface The text, styles, and images that are visible on a site, separated logically into the user interface for site visitors and the administrative user interface. User one (User 1) The initial user account that is created when you install the site (whose ID number is 1). It automatically has all permissions, even if it is not assigned an administrative role. See Bagian 7.2, “Concept: The User 1 Account” for more information. View A formatted listing of data; typically, the data comes from contententities. For example, on a farmers market site, you might create a content item for each vendor. You could then make view that generates a listing page that shows a thumbnail image and short description of each vendor, linking to the full-page content item. Using the same data, you could also make a view that generates a new vendors block, which would show information from the most recently added vendors. See Bagian 2.4, “Concept: Modular Content” for more information. View mode A set of field formatterconfiguration for all of the fields of a contententity, some of which may be hidden. Each entity subtype can have one or more view modes defined; for example, content types typically have Full and Teaser view modes, where the Teaser view mode displays fewer or trimmed-down fields. See Bagian 6.10, “Concept: View Modes and Formatters” for more information. Vocabulary A group of taxonomy terms to choose from when classifying content in a particular way, such as the list of all of the vendor categories on a farmers market site. Technically, vocabularies are the entity subtype for the taxonomy term entity type. See Bagian 6.5, “Concept: Taxonomy” for more information. Widget See Field widget. Wizard A web form that allows you to fill in a few values, and creates something with sensible defaults based on the values you chose. For example, there are wizards for creating views of different types. See Bagian 9.3, “Creating a Content List View” for more information. WYSIWYG Acronym for What You See is What You Get, meaning a method for editing content where what you see on the editing screen closely resembles the final product. See Bagian 6.16, “Configuring Text Formats and Editors” for more information. 204 Indeks A Account setting configuring, 41 Admin Toolbar module downloading, 151 installing, 151 Administration overview, 32 Administrative interface using to update the core software, 186 Administrative menu overview, 32, 55 Administrative user account overview, 99 Ajax definition, 199 Alias definition, 199 overview, 48 Anonymous definition, 199 Anonymous user overview, 99 Apache web server version requirements, 20 Appearance menu entry administrative menu, 32 Attributions for this document, 215 Authenticated user overview, 99 Author assigning, 110 Automated Cron module configuring, 181 overview, 181 B Backup overview, 177 Bartik theme configuring, 43 regions in, 10 Basic page creating, 49 Block creating, 113 creating from a view, 129 definition, 199 entity type, 13 overview, 113 placing in a region, 116 Breadcrumb region overview, 10 Breakpoint definition, 199 overview, 95 Bug reporting, 184, 194 Bundle definition, 199 C Cache clearing, 175 definition, 199 overview, 174 rebuilding, 175 Chatting online, 194, 196 CKEditor module configuring, 96 CKEditor text editor default assignment to text format, 96 CMS (Content Management System) definition, 199 overview, 1 Coder tool overview, 21 Color scheme configuring, 43 Comment entity type overview, 13 Comment module entity type, 13 Community connecting with, 194 Composer tool overview, 21 using to download modules, 166 using to download the core software, 166 using to download themes, 166 Composite page creating with modular content, 15 Configuration as a type of data, 6 205 Indeks copying, 169 definition, 199 deploying, 169 synchronizing between development and live site, 171 translating, 134, 141 Configuration Manager module using to synchronize the configuration between a development and live site, 171 Configuration menu entry administrative menu, 32 Configuration Translation module installing, 135 overview, 134 Configuring content translation, 136 home page, 54 site, 35 text format, 96 Contact form entity type overview, 13 Contact module entity type, 13 Content adding to menu while editing, 57 as a type of data, 6 assigning author, 110 backing up, 177 definition, 199 displaying, 87 editing, 51, 53 editing entry form, 83 entity type, 13 finding, 51 modular, 15 translating, 134, 140 translation, 136 Content attributions for this document, 215 Content display changing, 87 managing, 87 Content editing form overview, 83 Content entity type overview, 13 Content item creating, 49 definition, 200 Content list view creating, 122 Content Management System (CMS) definition, 199, 200 overview, 1 Content menu entry administrative menu, 32 Content reference field adding, 79 overview, 72 Content region overview, 10 Content structure planning, 16 Content Translation module installing, 135 overview, 134 Content type adding, 62 adding field to, 67 definition, 200 deleting, 66 Contextual filters part of view overview, 120 Contextual link definition, 200 overview, 32 Contributed definition, 200 Contributed module definition, 200 downloading, 151, 160, 166 evaluating, 145 finding, 145 installing, 151 overview, 3 updating, 188 Contributed theme definition, 200 downloading, 157, 160, 166 enabling, 157 evaluating, 153 finding, 153 installing, 157 updating, 190 Contributing to the project, 194 Copyright for this document, vi, 215 Core module overview, 3 206 Indeks Core software installation requirements, 20 installing, 26 updating, 186 Core theme overview, 4 Country setting configuring, 35 Cron command scheduler definition, 200 Cron task configuring, 181 definition, 200 overview, 181 Cross-site scripting (XSS) preventing, 95 Custom block creating, 113 entity type, 13 Custom block module entity type, 13 Custom menu overview, 55 Custom theme enabling, 157 installing, 157 overview, 4 D Data type configuration, 6 content, 6 overview, 6 session, 6 state, 6 Database backing up, 177 configuring during the installation process, 26 installation requirements, 20 Deployment workflow overview, 162 Devel tool overview, 21 Development site making, 163 overview, 162 synchronizing with live site, 171 Disk space installation requirements, 20 Display part of view overview, 120 Distribution definition, 200 full-featured, 5 overview, 5 quick-start, 5 Documentation about Drupal, 197 about the Drupal API, 197 available on drupal.org, 197 contributed by the Drupal Community, 197 Drupal Planet blog posts, 197 for programmers, 197 Downloading core software, 23, 166 module, 151, 166 module or theme files manually, 160 theme, 157, 166 Drupal Association overview, 7 Drupal Console tool overview, 21 Drupal content management system overview, 1 server requirements, 1 Drupal core definition, 200 installing, 26 overview, 1 preparing install, 23 Drupal licensing overview, 8 Drupal project connecting with, 194 overview, 7 Drupal training resources for, 197 Drupal user group finding, 194 Drupal.org website downloading and installing module from, 151 downloading and installing theme from, 157 downloading modules and themes from, 1 finding and evaluating modules on, 145 207 Indeks finding and evaluating themes on, 153 Drush tool overview, 21 using to download and install module, 151 using to download and install theme, 157 using to install the core software, 23 using to uninstall module, 39 using to update module, 188 using to update the core software, 186 using to update theme, 190 Dynamic Page Cache module overview, 174 E Editing content, 51, 53 Editor configuring, 96 Editor module configuring, 96 Editorial Workflow overview, 19 Effect image, 91, 91 Email address configuring, 35 Enabling module, 151 theme, 157 Entity definition, 200 overview, 13 Entity reference field adding, 79 Entity subtype definition, 201 overview, 13 Entity type definition, 201 overview, 13 Entity view mode overview, 87 Error log report, 178 Error page configuring, 35 Event Drupal, 194 Extend menu entry administrative menu, 32 F Farmers market usage scenario for this document, xi Feature copying, 169 deploying, 169 Featured regions overview, 10 Field adding to content type, 67 content reference, 72 definition, 201 for adding references, 79 overview, 13, 83 reference, 72 taxonomy term reference, 72 user reference, 72 Field bundle definition, 201 Field formatter definition, 201 overview, 87 Field module overview, 3 Field UI module overview, 3 Field widget definition, 201 Fields part of view overview, 120 File backing up, 177 File module entity type, 13 Filter criteria part of view overview, 120 Filter module configuring, 96 Firebug tool overview, 21 First day of week configuring, 35 Footer menu overview, 55 Footer regions overview, 10 Form overview, 83 208 Indeks Form entity type overview, 13 Format part of view overview, 120 Formatter definition, 201 overview, 87 Forum user support, 196 FOSS (Free and Open Source Software) definition, 201 overview, 7 Free and Open Source Software (FOSS) definition, 201 overview, 7 Front page configuring, 35, 54 Full editor, 53 Full-featured distribution overview, 5 Functionality extending, 151 G overview, 10 Home page configuring, 54 creating, 49 HTML5 picture tag and responsive images, 95 I Git tool overview, 21 Glossary, 199 GNU General Public License definition, 201 overview, 8 GPL (General Public License or GNU General Public License) definition, 201 overview, 8 Group finding, 194 Guiding scenario for this document (farmers market), xi H Header region overview, 10 Help menu entry administrative menu, 32 Help region overview, 10 Hiawatha web server version requirements, 20 Highlighted region Image resizing, 91 Image effect overview, 91 Image field adding, 67 Image module creating a view, 122 Image style creating, 91 definition, 201 overview, 91 responsive, 95 In-place editor, 53 Installation process, 26 Installation profile, 26 Installation requirements database, 20 disk space, 20 overview, 20 PHP programming language, 20 web server, 20 Installer tool running, 26 Installing core software, 20, 23 development site, 162 module, 151 staging site, 162 theme, 157 Interest group finding, 194 Interface Translation module installing, 135 overview, 134 Internal Page Cache module overview, 174 Internet Relay Chat (IRC) using to chat online, 194, 196 IRC (Internet Relay Chat) using to chat online, 194, 196 209 Indeks L Label translating, 141 LAMP (Linux Apache MySQL PHP) definition, 202 Language adding, 135 Language module installing, 135 overview, 134 Layout planning, 11 Learning resource link to, 197 Legal overview, 8 Licensing overview, 8 Linux Apache MySQL PHP (LAMP) definition, 202 Listing content using Views module to, 122 Live site synchronizing with development site, 171 Locale setting configuring, 35 Log definition, 202 overview, 178 Logo image configuring, 43 M Maintenance mode disabling, 149 enabling, 149 overview, 149 Manage administrative menu overview, 32 Manually downloading module or theme files overview, 160 Menu adding a link to page, 57 administrative, 55 custom, 55 definition, 202 footer, 55 main, 55 overview, 55 user account, 55 Menu items reordering, 59 Menu region overview, 10 Menu UI module overview, 3 Metadata creating, 74 Microsoft IIS web server version requirements, 20 Modular content overview, 15 Module Admin Toolbar, 151 CKEditor, 96 Comment, 13 Configuration Manager, 171 Configuration Translation, 134, 135 Contact, 13 Content Translation, 134, 135 contributed, 3, 151 core, 3 custom, 151 Custom Block, 13 definition, 202 downloading, 151, 160, 166 Dynamic Page Cache, 174 Editor, 96 enabling, 37, 151 evaluating, 145 Field, 3 Field UI, 3 File, 13 Filter, 96 finding, 145 Image, 122 installing, 37, 151 Interface Translation, 134, 135 Internal Page Cache, 174 Language, 134, 135 Menu UI, 3 Node, 3, 13 overview, 3 Taxonomy, 13 uninstalling unused, 39 Update Manager, 151, 157 210 Indeks updating, 188 User, 3, 13 Views, 3, 122, 126, 129 Views UI, 3 Multilingual modules enabling, 135 installing, 135 MySQL database version requirements, 20 N Navigation changing the order of menu items, 59 linking menu to page, 57 Nginx web server version requirements, 20 Node module entity type, 13 overview, 3 P Page adding to menu while editing, 57 composite, 15 Page cache overview, 174 Path definition, 202 overview, 48 People menu entry administrative menu, 32 Performance improving, 39 log report, 178 status report, 179 Permission changing, 106 changing role, 108 definition, 202 denying, 106 granting, 106 overview, 99 PHP programming language version requirements, 20 PHP version status report, 179 Planning site layout, 11 PostgreSQL database version requirements, 20 Primary menu region overview, 10 Profile installation, 26 Published flag overview, 19 Q Quick editor, 53 Quick-start distribution overview, 5 R Reference field adding, 79 content, 72 definition, 202 overview, 72 taxonomy term, 72 user, 72 Region breadcrumb, 10 content, 10 definition, 202 featured, 10 footer, 10 header, 10 help, 10 highlighted, 10 menu, 10 overview, 10 placing a block in, 116 primary menu, 10 secondary menu, 10 sidebar, 10 Regional setting configuring, 35 Relationships part of view overview, 120 Report Recent log messages, 178 Reports menu entry administrative menu, 32 Resource documentation and training, 197 Responsive definition, 202 Responsive image style 211 Indeks overview, 95 Revision definition, 203 overview, 19 Role administrator, 101 anonymous user, 101 authenticated user, 101 changing, 108 changing permission, 106 creating, 101 definition, 203 overview, 99 S Scenario for this document (farmers market) overview, xi Secondary menu region overview, 10 Security assigning permission, 106 cross-site scripting, 95 managing user accounts, 41 overview, 184 status report, 179 text format, 95 user account settings, 41 user one account, 100 Security announcement subscribing to by email, 185 subscribing to on Twitter, 185 Security bug reporting, 184 Security team overview, 184 Security update applying, 188, 190 definition, 203 keeping track of, 185 Server information status report, 179 Session as a type of data, 6 Sidebar regions overview, 10 Site email address configuring, 35 Site information status report, 179 Site layout planning, 11 Site name configuring, 35 Site plan content structure, 16 Site slogan configuring, 35 Site tagline configuring, 35 Slogan configuring, 35 Software dependencies managing, 166 Software version status report, 179 Sort criteria part of view overview, 120 SQLight database version requirements, 20 Staging site making, 163 overview, 162 State as a type of data, 6 definition, 203 Status report overview, 179 Structure menu entry administrative menu, 32 Style image, 91, 91 Support finding, 196 T Tagline configuring, 35 Taxonomy creating, 74 definition, 203 overview, 73 Taxonomy module entity type, 13 Taxonomy term definition, 203 overview, 13 Taxonomy term reference field adding, 79 212 Indeks overview, 72 Term (taxonomy) fixed list, 73 free tagging, 73 overview, 73 Term list creating, 74 Terminology (Glossary), 199 Text format configuring, 96 definition, 203 overview, 95 Theme configuring, 43 contributed, 157 core, 4 custom, 4, 157 definition, 203 downloading, 157, 160, 166 enabling, 157 evaluating, 153 finding, 153 installing, 157 overview, 4 regions in, 10 third-party, 4 updating, 190 Third-party theme overview, 4 Time zone setting configuring, 35 Tool Coder, 21 Composer, 21 Devel, 21 drupal Console, 21 Drush, 21 Firebug, 21 Git, 21 Toolbar overview, 32 Training Global Training Days, 197 resource, 197 Training Marketplace, 197 Translating configuration, 141 content, 140 label, 141 overview, 134 view, 141 Troubleshooting log report, 178 status report, 179 U UI (User Interface) definition, 203 Uniform Resource Locator (URL) overview, 48 Uninstalling unused modules, 39 Unpublished flag overview, 19 Update definition, 203 keeping track of, 185 overview, 184 status report, 179 Update Manager module overview, 185 using to install module, 151 using to install theme, 157 Update status status report, 179 URL (Uniform Resource Locator) overview, 48 URL alias overview, 48 URL field adding, 67 Usage scenario for this document (farmers market), xi User administrative, 100 configuring account setting, 41 creating account, 103 definition, 203 overview, 99 root, 100 user one, 100 User account menu overview, 55 User group finding, 194 User interface translating, 134 User Interface (UI) 213 Indeks definition, 203 User module entity type, 13 overview, 3 User one definition, 204 User profile entity type overview, 13 User reference field adding, 79 overview, 72 User role changing, 108 creating, 101 overview, 99 User-entered content filtering, 95 W V X View adding block display to, 129 and modular content, 15 contextual filters part, 120 creating, 122 definition, 204 display part, 120 duplicating, 126 fields part, 120 filter criteria part, 120 format part, 120 overview, 119 parts of, 120 relationships part, 120 sort criteria part, 120 translating, 141 View mode definition, 204 overview, 87 Views module adding to a view, 129 creating a view, 122 duplicating a view, 126 overview, 3, 15, 119 Views UI module overview, 3 Vocabulary creating, 74 definition, 204 overview, 13, 73 Web installer running, 26 using to install the core software, 23 Web server installation requirements, 20 What You See Is What You Get (WYSIWYG) configuring editor, 96 definition, 204 Widget definition, 201, 204 overview, 83 Wizard definition, 204 WYSIWYG (What You See Is What You Get) configuring editor, 96 definition, 204 XSS (Cross-site scripting) preventing, 95 214 Lampiran A. Lampiran A.1. Guide-Wide Attributions This guide was written by contributors to the Drupal open-source project, and is licensed under the CC BY-SA 2.0 license. See Bagian i.1, “Hak Cipta” for more information. Details about the contributors for guide-wide tasks are below. For individual topics, the attributions for writing, editing, and/or translating are at the end of each topic. Project coordination of original (English, Drupal 8) text Writing of the initial version of this guide was coordinated by the following people: • Amber Matz - Volunteer coordination and project management • Jennifer Hodgdon - Content oversight • Joe Shindelar - Content oversight • Antje Lorch - Content oversight Writing, editing, and testing of original text The following people contributed to guide-wide writing: • The glossary was written and adapted by Jennifer Hodgdon, with parts from "Glossary", "Overview of Configuration (vs. other types of information)", and "Working with breakpoints in Drupal 8", each copyright 2000-2017 by the individual contributors to the Drupal Community Documentation. • The index was improved and curated by Anna van Raaphorst. • Topic summaries were written by Jojy Alphonso at Red Crackle. Guide-wide editing was done by the following people: • Amber Matz at Drupalize.Me • Anna van Raaphorst • Antje Lorch • Balu Ertl • Boris Doesborg • Charles Leverington • chirag shah • Grant Dunham 215 Lampiran • Jennifer Hodgdon • Joe Shindelar at Drupalize.Me • Jojy Alphonso at Red Crackle — who copy edited the vast majority of the User Guide • Kamal Kant Pansari at Intelliswift • Michael Lenahan at erdfisch • Swarad Mokal at Blisstering Solutions The content was tested by: • Zach Carter • A workshop organized by the "Spokane Drupal User Group" on groups.drupal.org, with students from the Web Development Certificate program at Spokane Community College Images Most of the images in the guide are screen captures from the Drupal software, generated by software written by Jennifer Hodgdon. The word Drupal, the Druplicon logo (which appears as part of several images throughout the guide), and the Drupal wordmark logo (which is part of the cover image), are registered trademarks of Dries Buytaert). The cover image is a CC BY-SA 2.0 licensed illustration by Amanda Luker at Advomatic. The Anytown Farmers Market logo, which appears as part of several images throughout the guide, is a CC BY-SA 2.0 licensed illustration by Justin Harrell at Drupalize.Me. The honey bee image, which appears as part of several images throughout the guide, is a public domain image by John Severns at the English Wikipedia project via Wikimedia Commons. The farm image, which appears as part of several images throughout the guide, is a public domain image by Xianmin Chang via Wikimedia Commons. The salad image, which appears as part of several images throughout the guide, is a public domain image by Yinan Chen via Wikimedia Commons. The carrot image, which appears as part of several images throughout the guide, is public domain image K11611-1 by Stephen Ausmus at the Agricultural Research Service of the United States Department of Agriculture via Wikimedia Commons. Translation into Bahasa Indonesia The Bahasa Indonesia translation of this guide was coordinated by: • Suryanto Rachmat • Pratomo Ardianto 216