Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.To convert to the new format now that hook_settings has been removed, and take advantage of the ability to have several settings pages.
Also convert the parameters URL to the new 4.8 (5.0) format.
Upstream: #173 / 2006-08-31 12:34:06 +0200
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 2822263-12.patch | 66.75 KB | fgm |
| #11 | 2822263-11.patch | 61.09 KB | fgm |
| #10 | 2822263-10.patch | 46.75 KB | fgm |
| #9 | 2822263-9.patch | 31.6 KB | fgm |
| #8 | 2822263-8.patch | 31.92 KB | fgm |
Issue fork g2-2822263
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare
Comments
Comment #2
fgmComment #3
fgmComment #4
fgmComment #5
fgmAlso g2_admin_settings_submit and g2_admin_settings_validate : those three functions belong in
Drupal\g2\Form\SettingsFormComment #6
fgmFirst step: the main route, now with an auto-completion feature filtering out some unusable routes.
Comment #7
fgmConverted the "main" settings.
Comment #8
fgmConverted the formatting/tooltips and remote/client settings. More cleanup.
Comment #9
fgmRerolled on 8.x-1.0-alpha1.
Comment #10
fgmConverted the API settings, also fixed the majority of the XML-RPC functions.
Comment #11
fgmConverted the homonyms settings, removed duplicating "entries" config, unneeded remote.local config, more cleanup.
Comment #12
fgmCompleted conversion.
Comment #14
fgmMerged to current dev HEAD.
Comment #16
fgm@Harshita mehna : this issue is fixed. Do not spend time on a fork. There are other live issues if you want to work on them :-)
Comment #17
volkswagenchick@Harshita mehna
I see you have opened a merge request on an issue that is already closed. This creates unnecessary noise for the maintainers and anyone following an issue.
The amount of issues you have posted in the last few days leads other contributors to think you may be attempting to gamify the Drupal attribution system.
When you open a merge request or post a file it ticks the credit box for attribution and creates more work for maintainers when they close the issues. Please refrain from opening a merge request unless you are working on code.
I am going to go through some of the issues you are working on and give you individual examples on issue queue etiquette and how you can better improve your contributor experience working within the community.
Here is a list of resources to help you on your contribution journey, thanks!
Issue Queue Etiquette
Contributor tasks
Adding tags to issues and using tags
~AmyJune, Core Mentor and CWG Community Health team member