The International Splash Awards are back — happening at DrupalCon Vienna on 14 October 2025! Submit your project(s) by 16 June 2025 and join others from around the world to celebrate the very best of what Drupal can do.This issue is for reporting the results of testing the User Guide.
What to post here
Several of the User Guide project coordinators are planning to host testing sessions, where testers will go through the guide and see if it all works and makes sense. In this issue, the coordinators of testing sessions should post:
- Any problems the participants encountered (see guidelines below), or places you noticed them having difficulty or asking questions. We'll make the identified problems into individual "Fix this topic" issues afterwards.
- A list of who participated in testing, including their Drupal.org user names. The ideal format for listing each tester would be one of the following:
https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon] https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon] of https://example.com[Example Company] Joe Smith(The second format would be for someone whose testing time was sponsored by a company. The third is for someone without a Drupal.org user account.)
Testing Guidelines and Instructions
Have testers start at the beginning of the guide, and go through the topics in order, with a test site available (you could use simplytest.me, for instance, for temporary hosting). They should read through each topic, and follow the steps in Task topics as they go. Note that in some cases, they will also need to do the Follow-on tasks, if they are listed as Site Prerequisites in a later topic, so they may find they need to backtrack now and then.
Have the testers look for the following (you might post this list somewhere or hand out copies):
- Do the concept topics make sense?
- Is terminology defined the first time it is used?
- Are concepts introduced in Concept topics (not in Task topics)?
- Are the steps in Task topics clear, and do they work if you follow the steps exactly as written?
- Are the instructions in the steps presented in both text (with tables for filling out forms) and images (screen shots)?
- Does the user interface text mentioned in the steps match what you see in the actual user interface?
- Does the navigation get you to the desired page, and is the final URL specified in the navigation text correct?
- Are the knowledge and site prerequisites listed for each topic adequate?
Comments
Comment #2
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]Chapter 1 Feedback:
ID: understanding-drupal
First section: term "browser" mentioned twice. First time it refers to site admin, second I think refers more to end user, but it isn't clear who is running the browser in the second case. Perhaps change "send it to the browser" to "send it to the end user's browser".
ID: understanding-themes
Bad sentence: There is a user guide page that explains how to find --themes-- on Drupal.org.
ID: understanding-project
Term "non-commercial license" introduced here before explained in detail in next topic. Is it possible to have FOSS software that has a commercial (but still open source) license?
Form a diverse comminity, or 'from' a diverse community? Probably 'form' is ok, but it kind of jumped out at me
as I read it.
ID: understanding-gpl
"git repository" term introduced with no explanation. Also, what if you download via a tarball instead of using git?
Link at bottom points to gpl v2, but not v3, even though v3 is mentioned in the topic. Difference between 2 and 3 is not explained.
Lower down it says "GPL version 2 or later". Why not "or later" instead of "3" in the top section?
Comment #3
jhodgdonNote to Joe/etc.: Zach is my partner and is testing the guide for us. ;)
Comment #4
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]After reading the first chapter, it isn't clear why I need Drupal. What factors (technical or otherwise) would go into my decision to use Drupal versus some other software to build my website? If that type of info is not in scope for the guide, at least a link to find it would be helpful.
Comment #5
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]Chapter 2 feedback:
ID: planning-chapter
Terms introduced but not explained: site branding, navigation aids, formated text, images, and like items
site branding and navigation aids might need explanation. text and images may be obvious.
ID: planning-layout
Two Theme concepts are knowledge prerequisites for this topic, but the word "Theme" isn't found anywhere in the topic. How do I relate my layout to the theme? Do I need to be choosing my theme at this point in the process?
ID: planning-data-types
Are the entity types, sub-types, and fields defined by the site builder, or are they built in to and provided by the Drupal software?
ID: planning-structure
Step 2 -- Knowledge of Node module needed when planning content entity type. How would I have known this as I execute step 2? I'm supposed to choose content entity types for all my pieces of content, but I don't have a full list of what types exist. There is a small example list in ID: planning-data-types, but where is the full list?
Step 5 -- filtering option term introduced but not defined.
Step 7 -- taxonomy term introduced but not defined. Or is the definition after the semicolon?
ID: planning-workflow
Revisions term is introduced but not explained. Is it a module?
Comment #6
jhodgdonNotes from the Spokane testing session yesterday:
Generally: It was not clear which things in Follow-on tasks were required steps, which were optional steps, and which were "if you're excited about this topic and want to read ahead" steps. We need to make this clearer. Maybe the ones that are required (in the sense of "if you don't do this, you'll be missing site prerequisites for later tasks") could be added to Steps instead, something like "Follow these steps again to make a Recipe content type". And then maybe the section should also be renamed "Related tasks" instead of "Follow-on", because people were clicking links and jumping around when maybe they didn't really want/need to.
Generally: The attendees had trouble switching between the User Guide and their site on laptops (this is not really something we can resolve). And they wanted demos. Maybe we should consider a companion video series?
Generally: formatting note: we are using H4 headers in some of the topics, such as ID: install-prepare (3.2). These are not well differentiated from DT elements in DL lists in the Bluecheese theme; on my test site, they're not well differentiated from regular paragraph text. This made a few of the topics a bit difficult to parse. We might want to think about better CSS for this. It is more differentiated in the PDF -- the headers are much bigger there -- it may waste space but at least it is clear. Although the PDF uses a stupid table-like format for the DL lists in that topic... should see if we can fix that to be more like HTML.
Installation chapter - Most of the people at our session used simplytest.me and skipped the whole Installation chapter, but we had a few brave souls who had MAMP or XAMPP and tried to follow this. Some gave up and downloaded a plugin that would automatically install Drupal for them... some difficulties here:
- ID: install-prepare (3.2)
-- The sub-headings were confusing. You're not installing yet, you're preparing to install. So maybe change these to "Planning to install with..." or something like this?
-- In the web installer section, item 2 "Get a full-acces database user" needed to be clearer. Maybe make steps 1 and 2 there be something like "Create a database, along with a database user account with full access".
-- Step 6 says "Create the files sites/default/settings.php and sites/default/services.yml and make sure these are writeable." but this is not explained. I'm also not sure it is still necessary to do? The user on MAMP was able to install without first creating these files.
-- Step 7 says to run the installer... which is not really part of preparing to install.
-- Another thing that is missing is to create or locate the web document root for the hosting option you've chosen, and figure out what the URL is for it. This may seem obvious, but it wasn't to some of the readers, especially if they were using MAMP or XAMPP. Maybe there should be a step like "Set up hosting, and verify that the URL is working and that you have access to the web document root by putting up a simple Hello World HTML file" or something like that?
- ID: install-run (3.3)
-- It doesn't say at the top under which circumstances you need to run the installer at all. (you wouldn't if you use Drush, for instance).
-- At the top of steps, it says "The first time you visit your site". This was very confusing. We instead need a step 1 that says "Visit the URL of your site" or something like that.
ID: config-uninstall (4.3) - One tester said the steps should have been clearer about what exactly to uninstall. They are vague.
ID: config-theme (4.5) - One tester wanted guidance on what size an uploaded logo should be.
ID: language-add (5.2) - Prerequisite is listed as language-concept (5.3) which is the following topic. Out of order.
ID: content-create (6.2) - This is missing a step (or maybe a line in the fields/values table) to create the URL alias of "home". It is in the screenshot but not in the steps. Also the follow-on task should say to give it the URL of "about". Also the screenshot needs a width=100% added I think -- it seems to be too wide.
ID: structure-content-display (7.11) - In step 3 it says "Select the gear for the Link field.". This is confusing because there is a "Links" pseudo-field in the list; the one you're actually looking for here is the Vendor URL field, so it should say that instead of "Link field".
ID: structure-image-responsive (7.14) - says: 'Drupal’s "Responsive Image" module provides responsive image styles.'. Should say this is a core module. Reader/tester tried to look on Drupal.org for this module.
ID: structure-text-format-config (7.16) - Navigation says /Configuration/ > /Text
formats and editors/. Should be Configuration > Content authoring > Text formats and editors
ID: block-create-custom (9.2) - Instructions do not match current UI. The Add custom block button is on the Custom Blocks Library and not on the Block Layout page. And when you save a custom block, you do not get the block configuration form. Needs to be updated.
Comment #7
jhodgdonSuggested attribution for testing (so far):
I'll start making some of the notes submitted so far into issues in the next few days...
Comment #8
jhodgdonOne more comments from discussions with Zach and with workshop participants:
In the preface, under conventions of the guide, we talk about navigation. It's too early in the guide -- the new user doesn't have Drupal installed yet. So we need to:
- Make a comment about that you can't see it until you've installed Drupal
- In the admin overview topic, link back to this or repeat the description, because by then they have Drupal installed.
Comment #9
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 3 feedback:
ID: install-requirements
Are the following two sentences redundant and/or in the wrong order?
What are the requirements for running Drupal?
To install and run Drupal your web server must meet certain minimum requirements.
ID: install-prepare
Why would I choose to use drush versus the other methods? drush seems like an advanced method that perhaps shouldn't be included here.
How do I get the point of being able to run "drush" ?
Steps are not detailed enough.
1-2. Perhaps a suggestion for the database name and user? Link to "Create A Database" Additional Resource, which is linked in the next topic but should probably be in this topic.
3. Where do I download it from (link?)? git? tarball? Which version should I choose? I had to use google to find it.
4. Which files? unzip? Good and reliable way to unpack it?
5. Make sites/default writeable. Directories or files? Do I need a chmod command? (note: I skipped this and it worked fine)
6. What is meant by creating these files? Just touch empty files? (note: I skipped this and it worked fine)
ID: install-run
Screenshot shows drupal9 as the database name. Should it be 8 to match the table above?
4. Create a database was done in the last topic.
Comment #10
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]Chapter 4 feedback:
ID: config-basic
Configuring the basic site information
Step 1: Received red alert text/link at top of configuration page:
"One or more problems were detected with your Drupal installation. Check the status report for more information."
Could be alarming to new users. What should they do? Go on, or address the issues right away?
Possibly checking the status report should be a step in the installation section.
Step 3: This isn't a required step. Should it be marked optional somehow? Or maybe just keep it simple and push it to a more
advanced topic somewhere.
Configuring the default Regional settings
Step 3. Optional or required step? Is the timezone only used by logged in users or does it affect the public web pages?
ID: config-uninstall
Having drush installed is a requirement for this topic, however so far the user guide has no topic with the steps to get it done. The referenced topic is Concept only and it links to an external site which sends me down a rathole and takes me away from the guide. It should be taken out or at least marked as advanced/optional somehow. I skipped the drush part and only tested the UI steps.
Step 2: How can I choose which modules can be safely uninstalled without breaking my site? I suggest choosing a few that are safe to uninstall for the Farmer's market example, and list the reasons why they can be disabled.
ID: config-user
Step 3: Informational, not really a step.
Step 4: The screenshot and text should show suggested customization for the Farmer's market example.
Comment #11
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]Chapter 5 feedback:
ID: language-content
Step 4: Took a while to figure out I needed to check the box left of "Basic page" in order for the list of translatable fields to pop up. Perhaps a red arrow pointing to that checkbox would help.
Comment #12
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]General comment about drush. If it is important for new users to be able to use drush, then the guide should go through the step by step process of installing it. If the installation process for drush is too difficult to document, then that indicates that it shouldn't be a requirement for new users here. It interrupts the learning flow to have too much extra content that is not needed. If it is optional everywhere, it should be clearly labelled as optional and never listed as a prerequisite.
My suggestion would be to take out all the references to drush in the early parts of the guide. Instead, create an advanced topic about drush later in the guide that lists the benefits of it and some examples of how and why you'd use it.
Comment #13
eojthebraveOh man @zachcarter, this feedback so far is super valuable. Thank you!
Comment #14
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]Chapter 6 feedback:
ID: content-chapter
The Path core module was on by default, so it seems unnecessary to mention it here.
ID: content-create
The table in step 3 is formatted in such a way, on my screen, that I thought the "Welcome to City Market" content was part of Summary rather than Body. I think because the table cells are centered vertically so the Value is way above the Field name.
The screen shot shows the "home" URL alias filled in, but the step 3 text doesn't mention it. When I entered "home" as shown in the screenshot I got an error because the leading slash was missing.
Suggestion: Could an "add to navigation menu" step be added here so that we can find our new pages more easily? This would make the ID:content-in-place-edit topic simpler.
ID: content-edit
The screenshot in step 2 shows two pieces of Vendor content which we haven't created yet in the Farmers Market scenario. It is missing the Home page which we recently created and later steps imply is the piece of content we are going to edit. Ideally the screenshot should have a red arrow pointing to the Edit button for the Home page.
There is a missing step in which you actually change the opening hours text in the body.
ID: content-in-place-edit
See related suggestion for ID:content-create to have content already available in the navigation menu.
Step 2: Should include specific instructions for finding the About page we created in earlier topics in the Farmers Market scenario.
ID: menu-home
Step 3 screen shot shows the new home page with a Contact link at the bottom, presumably something we haven't done yet
in the Farmer's market scenario.
ID: menu-link-from-content
Step 3:
Why did I choose -3 for Weight?
Screenshot refers to different page than text/table above it (About versus History).
Step 4:
Screenshot doesn't match step 3 text or screenshot.
ID: menu-reorder
Site Prerequisites: Home and About menu items must be linked from the content. "At least two" is vague.
Step 1: Tell the reader to choose the Main navigation menu specifically.
Comment #15
zachcarter CreditAttribution: zachcarter as a volunteer commentedhttps://www.drupal.org/u/zachcarter[Zach Carter]General comment about the scenario. There is frequently a disconnect between generic information and information specific to the Farmers Market scenario. I think it is important for the task topics that have specific steps and screenshots in them all relate to the scenario with very specific instructions. Phrases like "Find the menu you wish to edit" are not as helpful as something like "Choose the Main navigation menu and click Edit Menu". Screenshot data should always match the text and tables in the steps, and I like the red arrows pointing to the relevant fields in the screenshots, which means I miss them when they aren't there.
Comment #16
jhodgdonUpdated testing guidelines in summary.
Comment #17
jhodgdontypo
Comment #18
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 7 Feedback:
ID: structure-content-type
Step 6: Confusing step. One entry in the table refers to many entries on the screen.
ID: structure-fields
Step 5: Table is missing info about field translation.
Step 8: Missing info about upload destination.
ID: structure-taxonomy-setup
Recipe content type has not been created in a previous step. It was an optional followon task, but now it is being treated as a required prerequisite.
Step 2: Missing table with values and fields.
Step 3: Missing clear instruction to click Save button
Step 4: After creating Butter, Eggs and Milk, there wasn't a clear step for getting back to the screen listing all the
terms I just created.
Step 7: Click Save field Settings button.
Step 8: Instructions need to be clearer.
ID: structure-adding-reference
Step 4: Sort by "Vendor name" or "Title" rather than "Name"?
ID: structure-form-editing
Step 4: Cannot verify changed behavior if I haven't seen the previous behavior first. I've not created any Recipe content at this point, though perhaps it was an optional followup task.
ID: structure-content-display
Site prerequisite problem. I haven't created any content in the Vendor type. The referenced section has the steps for creating a Basic Page.
Where can I get the Happy Farm image?
Step 3: "Link" field is vague as there is a Links field above.
Comment #19
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 8 Feedback:
ID: user-new-user
Step 4: Wish I somehow had the picture ready to go at this point. Had to break the flow of learning to go find a picture.
Contact Settings was missing from my "add user" screen.
No clear instruction to click the Create new Account button.
I got "Created a new user account for freshvegetables. No email has been sent."
The example had "instructions has been emailed to freshvegetables"
We will need more than one user in later steps. Should include more instructions for all the users here.
ID: user-permissions
Step 3: "Use users' personal contact forms" missing from my site.
It would be nice to have a step to login as the user and go try the different tasks that we gave permission for.
ID: user-roles
Step 2: Should reference a specific user created in a previous task.
Step 4: Should reference a specific role previously created.
Bulk editing should refer to previously created users.
ID: user-content
Step 2: Should refer to specific content created earlier
Comment #20
jhodgdonNote: The reason you didn't have the personal contact form stuff is that you had uninstalled the core Contact module when you were playing around with the site earlier. :)
Comment #21
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 9 feedback:
ID: block-create-custom
Missing step 1.5: Navigate to Custom Block Library tab.
Step 2: No +Add custom block button on my screen without stop 1.5 above.
Step 3:
tag ended up displayed on the main site page.
Step 5: No obvious way to get to this screen. Cache settings missing.
ID: block-place
Step 5: Do I need to drag and reorder the blocks? It reminds me to clock Save Blocks but the next step tells me to do
it anyway.
Step 6: User login block missing. Vender login is there instead, per the above instructions.
Comment #22
zachcarter CreditAttribution: zachcarter as a volunteer commentedGeneral feedback. Many of the topics are missing a "Go and observe the results of what you did" step. It helps reinforce the learning if we get a chance to do this.
Comment #23
jhodgdonIssue status: I have created child issues for (I think/hope) all of the problems identified in testing by both Zach and the Spokane group, up to this point in the comments. Which is to say, up through chapter 9, and through comment #23. The Spokane group didn't get past this point in the guide. I think Zach will be continuing on in the next week or two.
Comment #24
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 10 Feedback:
ID: views-create
Step 2: Missing "of type" choice from table, which meant all content is part of our view instead of just vendors. I didn't see this problem until navigation to see the results in step 24, and Jennifer had to help me figure out what went wrong.
Step 6: "Main Image" not "Image". No associated screenshot for this step. Recommend a "click checkbox" instruction instead of "select".
Comment #25
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 10 More Feedback:
ID: views-duplicate
Step 4: Format was Table and not Format: Unformatted. Style options popup appears but is not mentioned in the guide.
Step 8: Missing table of values to enter. Had to use screenshot to find what to do.
Step 9: Missing step to click Apply.
General Note. At this point the instructions start dropping in detail without warning. It is a bit jarring when the user is accustomed to following the more specific instructions.
Step 10: "Roll out the Advanced sections" is a confusing way to say it. How about something like "Click Advanced so that Advanced options appear"
Step 11: "Clicking on Save of the Displays panel" was tricky to parse. I figured out what to do but perhaps it should be reworded.
ID: views-block
Step 1: Alternative navigation suggestion not necessary here.
Step 2: It should say Click +Add not plain Add without the + sign.
Comment #26
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 11 feedback:
ID: language-content-translate
Step 5: Instructions too vague. Had to ask Jennifer for help. 'es' is in the url twice.
Step 6: Missing clear instruction to expand URL Path Settings. Also, pagina-principal should have a leading slash or you will get the following error: "The alias needs to start with a slash."
Missing steps to click "Save and keep published" and instruction on how to view the resulting newly translated home page.
General Note. Chapter 5 is a prereq for this chapter, and IMO it comes way too early in the guide. I suggest moving it to right before this chapter and/or combining the two.
ID: language-config-translate
Step 6: Should be taxonomy term ID > Find recipes using... , instead of plain > Ingredients (based on previous steps)
Missing step to view results. Follow-on task says "switch to Spanish" but I don't know how.
Comment #27
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter 12 feedback:
ID: extend-module-find
Step 2: I entered a literal '-' under the Search Modules field and got no results. Suggest using (leave blank) instea
d of hyphen.
Finding modules....
Step 2: Same problem as above with literal '-'
Needs some kind of statement that the search results are dynamic and what to do with the results.
General comments:
I suggest picking a module that is well maintained and use it as an example, prefereably one that would fit into the Farmer's Market scenario somehow.
How would you compare/contrast the two search pages? Why would I use one over the other?
ID: extend-maintenance
Missing step to try using the site and see the maintenance message as a website user. For some reason this took a while on my site, perhaps the page was cached by my browser.
The followup step to disable mainenance mode should not be optional. Should be part of the main list of steps. It wa
s actually tricky for me to do it by clicking the "Go online" link because I kept not unchecking the "Put site into maintenance mode" box, thinking all I needed to do was Save configuration.
ID: extend-module-install
Site Prerequisites. It is awkward to refer to a chapter about Multilingual configuration in order to learn how to install any generic module.
'drush' instructions ignored. See my previous general comment about drush.
ID: extend-manual-install
Is there an example scenario when the non-manual method wouldn't work?
The scenario in this topic is unlikely for a new user going through this guide. Perhaps the Goal should say something like "skip to the next topic unless you fall into this category"
ID: extend-deploy
The instructions here assume I have created a separate development site, but I had no previous instruction for doing it. Unable to test until UNWRITTEN topic is created.
~
Comment #28
jhodgdonIssues have been created for testing notes to this point (comment #27)...
Comment #29
jhodgdonNote that the chapter numbers have changed because of #2717583: Combine the Language topics into one chapter -- chapter 4 was removed; its topics are now in what is chapter 10 (multilingual). All chapters that were formerly numbered 5 or higher are now numbered one less. The chapter names are the same though (except 10), and probably this will not be too confusing if you read the comments above... hopefully. ;)
Comment #30
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter "Security and Maintenance" Feedback:
ID: security-update-core
drush steps ignored.
Step 1: code backups, what exactly does that entail for drupal? data backups, refers to a future topic. Why not introduce that topic first?
Step 6: This is too vague for a new user like me: "Delete the core directory, and all the independent files, including .htaccess, composer.json,autoload.php, and so on". I wouldn't feel comfortable knowing which files I could delete.
Should there be a step to backup these files as well, in concert with the data backup? The "vendor" directory is missing from the list.
Step 7: copy/paste is not what I normally do when manipulating files on the command line. The "vendor" directory is missing here.
Step 9: Missing instruction to click "Continue" button through all the steps.
Step 10: If all went well, Click "Administration pages" to get back into the site. Click "Clear all caches"
ID: security-update-module
Site prerequisite "Ensure that cron maintenance...." refers to a future topic. Suggest reordering that.
Before you start.... Is there a good way to read the *.txt files for the module without first downloading and unpacking
the tarball for the module?
Step 3: After finding the module in the list, need clear instruction to click checkbox next to it.
ID: security-update-theme
Step 2: Reports is top-level, not under Configuration.
Step 7: Click "Administration Pages" when done.
ID: security-cron-concept
I suggest putting some information in here about how the drupal cron is different from the linux/unix cron daemon.
Comment #31
zachcarter CreditAttribution: zachcarter as a volunteer commentedChapter "Preventing and Fixing Problems" Feedback:
ID: prevent-backups
This is a concept topic only. It could be helpful to have a task-based topic with the steps for backing up and restoring.
What about backing up the settings.php file?
What would be the location of the custom modules, themes, etc. that might need to be backed up?
How would one go about safely testing a restore process for drupal?
ID: prevent-log
Instructions for navigating to the Recent log message report do not conform exactly to the standards.
ID: prevent-status
Instructions for navigating to the Status report do not conform exactly to the standards.
Comment #32
zachcarter CreditAttribution: zachcarter as a volunteer commentedGeneral Feedback.
It was a pleasure reading through the guide and learning about drupal. The formatting standards and structure of the guide made it easy to navigate. The topics were mostly easy to digest and should be simple to find and review later on when needed. And I can tell it will only improve with additional revision, editing and testing. Good job folks!
Comment #33
jhodgdonOK! I have made issues for the remaining testing comments. Hopefully once all the child issues of this one are fixed, we'll have a much better guide. THANKS Zach, and the participants in the Spokane workshop, for testing!
Note: There are a couple of child issues that are not part of the User Guide project, so rather than mark this issue Fixed, I am going to leave it open for now. But I think if we have more rounds of testing, it would probably be better to start new issues for the testing notes.
Comment #34
jhodgdonWhoops, I forgot to leave it Active after that. ;)
Comment #35
zachcarter CreditAttribution: zachcarter as a volunteer commentedID: install-dev-making
Step 2: I suggest directly pointing out that your sql dump is now stored in the BACKUPFILE.sql file. The mysqldump (and drush) command should be in some special block like
Step 4: Also needed to tweak 'trusted_host_patterns'
Step 5: See previous comments on Step 2. The + sign in front of drush looks out of place.
Probably should be careful not to write and store the mysql dump file in the webroot where it could possibly be accessed by a malicious user.
Comment #36
jhodgdonGreat! First pass of testing is now complete. I've created an issue for #35, so all issues have been created too.
Comment #37
jhodgdonI think we can mark this one as Fixed. If we do another round of testing, we should probably open up a new issue. If so... the testing guidelines are now in the Guidelines book, on this page (scroll down to section 3.2.3):
https://userguide_new-drupal.dev.devdrupal.org/guidelines/phase-checklis...