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.
I've renamed and cleaned up the ad_example
submodule as discussed in comment #2 of 7.x re-implementation (7.x-3.x?).
You can view the changes I've made in my ad_ad_ui sandbox.
The bulk of the changes are for renaming the submodule and its pieces to ad_ui
. To make it easier to review, I split the changes up among various commits: renaming the module, renaming the content type, renaming the view modes and layouts, renaming the permissions, renaming the views, and then some other commits that fixed minor issues I ran into.
There are still two things lacking that I didn't have time to address:
- The displays in the Ad Display view need to be updated manually after installation so that their Ad size filters point to the correct vocabulary and terms. This really should be an automatic process.
- There's still very little documentation on how to use the modules. It might be useful to at least show that calling
drush ad-ui-install
will install the example content. Being able to play around with the example content should get most people to a point where they can easily figure out things on their own.
Comments
Comment #2
tbaumgard CreditAttribution: tbaumgard commentedComment #3
Jeremy CreditAttribution: Jeremy at Tag1 Consulting commentedPlease submit a patch, and I'll take a look.
Comment #4
tbaumgard CreditAttribution: tbaumgard commentedHere are the individual patches and a single aggregate patch that I created from the commits in my sandbox via
git format-patch ...
.Comment #6
Jeremy CreditAttribution: Jeremy at Tag1 Consulting commentedThanks for your work on this! All patches have been applied.
Regarding #1 in your TODO, as this is a -beta release I don't think it's critical we automate the upgrade path. It would be good to document how this is done manually.
Regarding #2 in your TODO, agreed, more documentation would be super useful.
For future patches, please review:
The Drupal community does not use
git format-patch
andgit apply
.Comment #7
Jeremy CreditAttribution: Jeremy at Tag1 Consulting commentedComment #8
tbaumgard CreditAttribution: tbaumgard commentedFor what it's worth, I was trying to follow this guide as opposed to the typical patch workflow because it was such a complex changeset, but thanks for the heads-up and for merging the changes.
Anyway, the first TODO item I mentioned isn't related to upgrades and will happen with a brand-new install. If I remember correctly, and it's been awhile since I've looked into it, I think there are some IDs hard-coded that don't map to the expected vocabulary or taxonomy term IDs unless you're lucky enough to have a setup close to that of the original author. I ended up leaving it go because I wasn't sure what the proper way to handle them was at the time, and I didn't have exactly have a ton of time to investigate it. In any case, I completely agree with you that it's not critical because it's example content anyway.