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.
This was brought up in #1700140-2: Drupal 6 port, offer to co-maintain.
I believe we will also need to trigger a cache clearing event by adding another hook_update_N() to the .install file.
Comment | File | Size | Author |
---|---|---|---|
#7 | 1707200-menu-item-fixup-7.patch | 2.22 KB | greggles |
| |||
#5 | 1707200-menu-item-fixup.patch | 1.48 KB | greggles |
#3 | login_history-1707200-3.patch | 1.56 KB | star-szr |
#2 | menu_item_bug_1707200.patch | 2.8 KB | a_thakur |
Comments
Comment #1
star-szrThere's only one menu item that uses an underscore, fixing title.
Comment #2
a_thakur CreditAttribution: a_thakur commented#1691412-1:Per-user login history report shows data from all users solves the issue. Please find the attached file.
Comment #3
star-szrThanks @a_thakur. The patch in #2 still leaves the link path in the block as login_history, and I believe users would need to clear their cache after updating the module. I think it would be better to clear the cache via hook_update_N() since users are used to running update.php after updating modules.
The attached patch:
#1691474: Convert files to unix line endings has been applied first.
This came up as well: #1711938: "Last login" block throws errors if there are less than two logins stored for the user
Comment #4
star-szrActually, it would probably be an idea to use the conventional hook_update_N() schema numbering as well, i.e. 7101, 7102, etc.
Comment #5
gregglesHere's a re-roll of #3 with the advice from #4. The hook update now also explicitly clears the menu because some environments don't clear cache on every hook_update (e.g. my environment :) ).
Comment #7
gregglesComment #9
gregglesThis was already fixed for 8.x, so nothing to be ported.