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.
Ported to Drupal 7. I don't know much about coding with Drupal 7, but it works. I attached a patch.
Here is the github repo too: https://github.com/markwk/profiler_builder7
Comment | File | Size | Author |
---|---|---|---|
port-d7-profiler-builder.patch | 5.54 KB | markwk |
Comments
Comment #1
gmclelland CreditAttribution: gmclelland commentedThe patch applied with errors using "git apply", but the module worked for me on D7.
@btopro - Maybe you should make a D7 dev release.
Maybe we should add a D7 "Configure" link that will allow people to jump to admin/config/development/profiler_builder after they enabled the module. This "Configure" link is listed right next to the module name and "Permissions" link in /admin/modules.
May even be good to set a message after the module is enabled. Something like "Profiler Builder has been enabled. Go to admin/config/development/profiler_builder to start building your installation profile."
@markwk - Thanks for porting. Huge time saver.
Comment #2
btopro CreditAttribution: btopro commentedWould either of you like to be put on as co-maintainers? I wouldn't feel right publishing a port of the module on drupal.psu.edu since I didn't write it. As it stands I'm not publishing on drupal.org for a few weeks / months depending on when I get into detailed branch management and elms starts rolling out places. I'd happily add both of you on as I more so like to just get these things going and then let them run from there.
Comment #3
gmclelland CreditAttribution: gmclelland commentedSorry, I've never maintained any d.o. projects.
Comment #4
btopro CreditAttribution: btopro commentednever a bad time to start ;)
Comment #5
markwk CreditAttribution: markwk commentedI'd co-maintain if you want. I don't really know much about Drupal 7 dev yet, so this would be a simple module for me to play around with.
Comment #6
markwk CreditAttribution: markwk commented@btopro: why don't just make a simple 6.x-1.x branch with the current code, then add me as maintainer? I'll push my 7.x-1.x port and release alpha-1 for both branches.
@gmclelland: I'll look at adding that "configure" link in the modules area. I haven't done anything in D7 besides what this currently is, but I don't think this is a major addition.
Comment #7
btopro CreditAttribution: btopro commentedadded as a comaintainer mark. I'll get to branching and what not at some point, too much to do in preparation for release
Comment #8
markwk CreditAttribution: markwk commentedOk. I'll add the code for the D7 branch on d.o. you can do what you want with your branch when you have more time ;)
Comment #9
markwk CreditAttribution: markwk commentedOr do you want me to create both branches and attribute the D6 commit to you?
Comment #10
btopro CreditAttribution: btopro commentedUmm... just create the branch if you could but add no code to it, that way people can submit issues associated to that version. Still planning to do some clean up before elms comes out the door for the next version.
Comment #11
markwk CreditAttribution: markwk commentedOk. I did a dev alpha release for the 7.x branch port I did. I also added empty git repo for 6.x-1.x, but doesn't seem to show up in issue queue...
Comment #12
markwk CreditAttribution: markwk commented