This is a topic for the licensing working group.
More information was asked for 8 years ago and it has not been supplied. Due to lack of interest I am closing this issue.
If you are interested in this idea, open a new issue in the core issue queue and add this issue as a related issue.
Based on #5 I am closing this as won't fix.
If there are still concerns about licensing and core, open an issue in the core issue queue instead of here. This project is deprecated.
The ideas project is deprecated, moving to core.
The ideas project is deprecated, moving this back to core.
@bbrala, moving to 11.x so this isn't is my searches for issues on the wrong branch. And change spelling in the title while I am here.
Changes are made on 11.x first, then backported.
Changes are made on the main development branch 11.x first, then backported.
This also needs the standard issue template restored so that decision and the work can be tracked. Adding tag for that.
Changes are made on the main development branch 11.x first, then backported.
The ideas queue is deprecated, moving this back to core.
If this is a bug, it will be fixed on 11.x first.
@gaelicmichael, was Start and Bartik installed on both the source and destination sites?
OK, changes made and linting passed.
Reword for the deprecation of the ideas project.
The ideas project is deprecated, so I am closing this issue.
The ideas project is being deprecated.
I cannot find a 'Mission and principles' page on d.o. and the current 'Values & Principles' does not include a mission statement. But I think this is now outdated and this type of work is being done in 📌 Drupal Core strategy for 2025-2028 Active .
The page for the mission statement is now a 404. Is this outdated?
The ideas project is being deprecated.
The issue summary refers to the problem in Seven, Bartik, and Umami themes. Since 2 of those are no longer in core and there has been several years of work on Umami, is this still relevant? Are there existing issues in core for remaining problems?
The core ideas project is deprecated, moving to core.
The ideas project is deprecated. Since this is being pursued in core in ✨ [meta] Add database driver for MongoDB to Core as experimental Active , I am closing this issue.
As mentioned this change will not be made in Drupal core and a solution to the problem was offered.
There has been no discussion here supporting this idea for 4 years, so I am closing this issue.
I am closing this as a duplicate of ✨ Add support for encrypted field api field storage in core Active .
The core ideas project is deprecated, moving to core. There is a similar core issue,
If the community approves such a list, what would be the criteria used to do that and where would that criteria as well as the results be documented?
The core ideas project is being deprecated, moving to core.
The ideas project is being deprecated, moving this to core.
I suspect that there are existing issues for adding filters to the pages listed.
The core ideas project is being deprecated and issues moved back to core. However, there is already a core issue for this, ✨ Uploaded files are impossible to replace Needs review where the solution here is mentioned in comment #32 of the issue.
@camerongreen, thanks for the idea.
Yes, doing this when Drupal 8 was released might have been helpful. But that didn't happen and now Drupal 7 is past End of Life, results for modern Drupal should be more prominent. And that is true for my simple tests just now when searching for Drupal tasks. Ans since, there hasn't been discussion here supporting this idea in 2 1/2 years I am closing this issue.
If anyone wants to explore this more, move the issue to the Drupal core issue queue.
Drupal has signed the GAAD pledge and there are issues in other projects for implementation. Therefore closing this issue.
The Coding Standards are being discussed in
📌
GAAD Pledge - Publish Accessibility Coding Standards
Active
The documentation is being done in
📌
Update documentation for GAAD Pledge
Active
This is being implemented in 📌 Add Accessibility Coding Standards Active .
This needs to be converted to the new coding standards issue template. That will including adding proposed text.
The page in IS has the following.
The Drupal Accessibility Team and project governance will follow the latest recommended release of the WCAG guidelines (WCAG 2.2 AA).
So, I think this has been fixed.
@nicxvan, I stand by what I said in #34. The proposed resolution is "Stop using a version number when referring to Drupal in any marketing". But core does not do marketing, so cannot resolve that.
I do agree with catch that there are improvements that can be made in the d.o UI but those are issues for other projects, not core.
Add steps for what to do with a draft change record that is no longer needed.
Yes, just delete it. Otherwise it merely clutters the list of change records and makes them harder to manage.
I have deleted it. Thanks catch.
There has been no discussion here for 12 years, and of course, things have changed a bit in those years. Due to the lack of activity I am going to close this issue.
If there is anything in this issue that still need work, open a new issue and let's start fresh. As always, search for a duplicate issue first.
Thanks.
Closing this based on #8
Sorry folks, but we need to get the change records right on this.
I agree with @berdir in #24 that the change records for this should follow the established pattern used for the plugin conversion from annotation to attributes. Since this issue is implementing the new feature then it should not refer to https://www.drupal.org/node/3499788 → . And if more implementations are planned then we should have a CR for that work, similar to https://www.drupal.org/node/3229001 →
The change record for this issue has not been reviewed.
There has been no review of the change record for this issue.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Removing fixed issues from the IS.
The deprecation in the remaining issue was updated to be removed in Drupal 12.
So, yes, this can be closed.
The deprecation was updated so this code would be removed in Drupal 12.0.
There hasn't been any comment objecting to closing this issue or defining what more work must be done.
Drupal 9 is End of Life.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Restoring template. The issue template is used to track progress and various tasks on an issue.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
OK, setting back to NW.
I didn't mean to set to RTBC.
I see the problem. When I created the issue I didn't include all that lines that are to be remove. I have updated the issue summary. Sorry about that.
There is an existing comment in the test explaining that migrations run through the UI must must as user #1, See https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/migra....
Migrate UI tests were also discussed in 📌 Fix Migrate Drupal UI tests that rely on UID1's super user behavior Closed: won't fix , but this one was missed.
@O'Briat, thanks.
I scanned the new page and I didn't spot anything that requires a change.. Any further improvements can be made by the community on a on-going basis.
It has been 8 months since I made changes to the page and there has been no further discussion. I am going to be bold and set this to RTBC.
I see that the property, "pseudo_destination_path", is used in the example.
uri:
-
plugin: skip_on_empty
method: process
source: image
-
plugin: file_copy
source:
- image
- '@pseudo_destination_path'
file_exists: rename
move: falseThe page in the issue summary is a forum post from 2005 discussing installing Drupal 4. The recommended way to install Drupal on a local server is DDEV, and that is documented at
https://www.drupal.org/docs/getting-started/installing-drupal/install-dr... →
This is task for the Drupal core issue queue. The pages about the releases are managed by the core release managers.
Is has been 2 years since @avpaderno said that this has been fixed. Therefor, closing as fixed.
This is for the Drupal 7 Form API page. Since Drupal 7 is end of life, this is now a "won't fix'.
Based on #20 and that Drupal 7 is past end of life, I am closing this.
The changes read well.
This could still use a screenshot.
@avpaderno, thanks for the extra info. Since you say that 'permissions an administrator can assign effectively change more than in the past', I think this should be a won't fix. It really isn't sustainable to maintain a list like this in the wiki.
I am closing as won't fix.
I took a closer look and this is documented in the note-tip https://www.drupal.org/docs/8/api/database-api/dynamic-queries/introduction-to-dynamic-queries. It has been there since the page was created in 2017. It is also in the Drupal 7 documentation, added in Jan 2013.
If anyone want this is Coding Standards, then an issue should be opened there for discussion.
I think this is fixed.
Is creating those URLs something for the drupal.org customization project?
It has been 9 years and there hasn't been support for adding this extra checking.
Therefor I am closing this issue.
@kim.pepper, thanks for closing this issue.
I am updating the meta data and credit to the time of the commit.
commit d53f3e39d5da63f20a90f3a221da139b7afa7673
Author: Dries Buytaert <dries@buytaert.net>
Date: Tue Jan 26 08:29:25 2010 +0000
- Patch #685074 by pwolanin: some stream wrappers need to be hidden or read-only.
@kim.pepper, thanks for cleaning up issues.
Updating credit and version to the time of the commit.
commit a1ce6bac55287fa815921561d747b5fc2e88fde6
Author: Angie Byron <webchick@24967.no-reply.drupal.org>
Date: Wed Aug 4 06:55:35 2010 +0000
#819816 by aaronbauman, yched, Damien Tournoud, tsi: Fixed Reordering multivalue file and image field uploads is broken.
@kim.pepper, thanks for finding this.
The commit was actually made to Drupal 7. Changing version and adding credit for that work.
Author: Dries Buytaert <dries@buytaert.net>
Date: Sat Jul 10 01:51:02 2010 +0000
- Patch #844676 by chx, asimmonds: stream wrappers stream_seek() return is invalid.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Restored the issue template. The issue template is used to track progress and various tasks on an issue.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Restoring template. The issue template is used to track progress and various tasks on an issue.
There are many issues in the views and views_ui component. Did you search for a duplicate issue before creating this one?
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Restoring template. The issue template is used to track progress and various tasks on an issue.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the
Core change policies →
.
Restoring template. The issue template is used to track progress and various tasks on an issue.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
quietone → created an issue.
quietone → created an issue.