The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- Status changed to Needs review
almost 2 years ago 8:27am 7 February 2023 - Status changed to Needs work
almost 2 years ago 5:25pm 28 February 2023 - 🇺🇸United States smustgrave
Points in #33 were not addressed.
Not ready for review yet.
- Status changed to Needs review
almost 2 years ago 5:00am 1 March 2023 - Status changed to Needs work
almost 2 years ago 2:33pm 1 March 2023 - 🇺🇸United States smustgrave
Now the strings are going over 80 characters per line.
- Assigned to adeshsharma
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 4:26am 3 March 2023 - 🇮🇳India adeshsharma Bhopal
Fixed docs' lines having characters above 80 in a single line.
- Status changed to RTBC
almost 2 years ago 4:08pm 3 March 2023 The last submitted patch, 55: 2905848-55.patch, failed testing. View results →
- Status changed to Needs review
over 1 year ago 7:10am 3 August 2023 - last update
over 1 year ago 29,946 pass - 🇮🇳India urvashi_vora Madhya Pradesh, India
Hi,
I tested the patch of #55 in d11, it works fine, applies cleanly. Since, the issue has changed to 11.x, providing the patch for 11.x.
- last update
over 1 year ago 29,953 pass - Status changed to Needs work
over 1 year ago 12:24am 5 August 2023 - 🇺🇸United States smustgrave
Hiding #60. Thank you but #55 applied cleanly to 11.x so #60 is just a re-upload from what I can tell, since there was no interdiff.
Can run the 11.x tests by clicking the "Add test/retest" link. Queued #55 for 11.x tests.
But #57 I believe is correct in that IS should be updated about what is being accomplished. Me marking RTBC in #56 was incorrect on my part.
- 🇧🇪Belgium mr.baileys 🇧🇪 (Ghent)
-
+++ b/core/assets/scaffold/files/default.services.yml @@ -160,15 +160,33 @@ parameters: + # Setting exposedHeaders: ['*'] will result in a Access-Control-Expose-Headers: + # * response header. See
This line should wrap at 80 characters. This will also fix the fact that header name and value are currently split over 2 lines.
-
+++ b/core/assets/scaffold/files/default.services.yml @@ -160,15 +160,33 @@ parameters: + # Setting Access-Control-Max-Age header value to '0' or false will omit this from the response. + # However, setting it to '-1' will explicitly disable caching. For example, 600 to
Line wrapping should be fixed.
It might make sense to merge 🐛 Improve documentation for cors configuration. Needs work and this issue, since that issue is about adding and documenting the new
allowedOriginsPatterns
-option tocors.config
indefault.services.yml
. -
- Status changed to Needs review
about 1 year ago 2:52pm 14 November 2023 - Status changed to Needs work
about 1 year ago 3:07pm 14 November 2023 The Needs Review Queue Bot → tested this issue.
While you are making the above changes, we recommend that you convert this patch to a merge request → . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)
- Merge request !5410Issue #2905848: Improve documentation for cors configuration. → (Closed) created by sourabhjain
- First commit to issue fork.
- Status changed to Needs review
about 1 year ago 2:39pm 15 November 2023 - Status changed to Needs work
about 1 year ago 3:15pm 15 November 2023 The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- 🇧🇪Belgium BramDriesen Belgium 🇧🇪
This still needs a rebase which was not addressed in the creation of the MR.
Remember to hide all patch files when switching to a MR.
- 🇮🇳India sourabhjain
Hi @xjm @smustgrave
I intentionally deferred work on these issues. All the updates were made on November 14, 2023, and I've been addressing them sequentially in the Drupal issue queue without initially considering the tags assigned to each. I acknowledge this oversight and apologize for any confusion. Moving forward, I will ensure to prioritize and address issues based on their respective tags. - First commit to issue fork.
- Status changed to Needs review
5 months ago 9:08am 18 August 2024 - Status changed to RTBC
5 months ago 12:57pm 22 August 2024 - 🇺🇸United States smustgrave
Went ahead and updated issue summary.
Update text definitely reads like a net improvement.
- Status changed to Fixed
5 months ago 8:01pm 22 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.