Currently core provides no way of overridding the page generated by the function tracker_page() in tracker.pages.inc. So if a user wants to say override the number of pages shown in the pager (which I am), there isn't an easy way to do this.

I'm attaching a patch to the first post that will add the following code to the end of the tracker_page() function:

  $page['#account'] = $account;
  drupal_alter('tracker_page', $page);
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Jaypan’s picture

dawehner’s picture

There is a different issues which tries to convert this page to a view. Would this solve your feature request as well?

Jaypan’s picture

Probably not, as Views uses a views pager. So if this issue is not going to move forward because of that, then lets change it to D7, which won't be converted to a view.

Jaypan’s picture

Status: Active » Needs review
dawehner’s picture

Probably not, as Views uses a views pager.

I don't get this point. Can't you change pretty much anything with it?

Jaypan’s picture

Yes, but this patch is based on the existing method of building the tracker page.

Jaypan’s picture

Sorry, I just realized I've been mixing up two related issues I'm posting in.

Ignore my comments about the pager, that is my overall goal, but not related to this current issue. This current issue is to allow overriding of the tracker page, something that cannot be done. If the tracker page is switched to a view, then the function tracker_page() would be removed, because the page would be created in views, and the method of overriding it would be completely different. That's why this thread should be changed to D7, as Views will not be used to create the tracker page in D7.

dawehner’s picture

Well, in Drupal7 you can use hook_page_alter directlly.

Jaypan’s picture

Yes and no. First, hook_page_alter() is way too broad. It gets called on every page load, implementing it to make changes on a single page on the system, and adding a check to see if it's the tracker page on every page load adds unnecessary overhead.

Second, the tracker page doesn't embed the pager in any sub element of the array, so there is no way to specifically alter only the pager on the tracker page.

And from a precedent perspective, Drupal offers hook_form_FORM_ID_alter() as well as hook_form_alter(), and hook_block_view_MODULE_DELTA_alter() as well as hook_block_view_alter(), allowing for hooks that target specific forms and blocks, as well as the blocks overall. This alteration would allow for altering just the tracker page, or altering all pages (hook_page_alter()).

marvil07’s picture

Component: extension system » tracker.module
Related issues: +#1941830: Convert tracker listings to a view

Linking related ticket about converting it to a view, if that gets in I think it's safe to close this or move it to D7 only.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Needs review » Closed (duplicate)

Closing as duplicate of https://www.drupal.org/project/drupal/issues/1941830 which I'm trying to put effort in as we speak.

Feel free to reopen for D7 if you wish though.