If I go to reports Upgrade Status it puts on on Recent Log messages page, similarly with Upgrade Log. How to I get to run the report? I also tried /admin/reports/upgrade_status (mentioned on the project page) and this goes to a page not found page.
| Comment | File | Size | Author |
|---|---|---|---|
| #17 | 3081161-17.patch | 3.91 KB | robindh |
| #16 | 3081161-16.patch | 2.91 KB | robindh |
| #3 | Screenshot 2019-09-13 at 16.44.12.png | 164.73 KB | gábor hojtsy |
Comments
Comment #2
yktdan commentedREADME says
Administer >> Reports >> Available updates >> Upgrade status and check the status of your installed modules.
There is no Upgrade status tab there.
Comment #3
gábor hojtsyDoes this show up?
Comment #4
gábor hojtsyBTW thanks for noticing the path issue on the project page, I fixed it there. It is /admin/reports/upgrade
Comment #5
yktdan commentedI do get Upgrade status in the report menu and hovering over it says it goes to /admin/reports/upgrade but in fact I wind up on the Recent log messages page.
Comment #6
gábor hojtsyBut it is the same URL /admin/reports/upgrade? or you get redirected? That sounds odd either way.
Comment #7
yktdan commentedIt acts like it is being redirected. This is an empty site getting ready to do a migrate from D7 to D8. There is nothing in the alias table that would redirect. All installed with composer.
Comment #8
yktdan commentedI installed the D7 version on the live site and it works as expected. I did have to run cron to see results. So I forced a cron run on the d8 version and it ran almost instantly, like it didn't really have to do anything. I suspect there is a fair amount of work to actually generate the report data. So perhaps the redirect happens if there is no data to report.
Comment #9
gábor hojtsyNo there is no redirect to the recent logs at all ever in the module. Can you try this in an absolutely empty site just this module? It should show a list of modules. The data is not collected on cron but rather on the module's own UI, so running cron should not make it any worse or better.
Comment #10
super_romeo commentedSame thing. CR and cron not helped.
Request:
Response:
Comment #11
gábor hojtsyOk this is very interesting. At least we have two people reporting the same thing :) can you try on a fresh site? I suspect there may be some contrib module, eg. admin menu enhancer that tries to "fix a wrong URL" so you can get stuff done faster. But it caches too much somewhere.
Comment #12
super_romeo commentedMaybe this issue is related: Silently set 'version'=NULL if .git-repository does not exists
Comment #13
quietone commentedI just ran into this. I installed a empty db I made on Sept 26 (has migrate_run installed), then `drush updb`, then install upgrade_status with composer. No errors. Navigate to /admin/reports/upgrade and instead get /admin/reports/dblog.
The curious thing is that I tried this a few days ago on the same dev site with what should have been the same empty database. And then I was able view the Upgrade Status page. `drush cr` does not help.
Notice: Undefined index: version in git_deploy_system_info_alter() (line 103 of modules/contrib/git_deploy/git_deploy.module).
So I reinstalled, using drush, standard profile, and got this error when installing upgrade status.
And navigating to admin/reports/upgrade still takes me to the admin/reports/dblog
The contrib modules on the site in all cases, are git_deploy, migrate_run, upgrade_status. And on the last test migrate_run was not installed.
Comment #14
xaviemirmonHi 👋🏻 I am also facing this issue. I think super_romeo Might be on to something here. My site is is nested within the repo. So possibly git_deploy isn’t finding what it needs.
Comment #15
singularoHad this issue as well, disabling admin toolbar and drupal upgrade didn't help, ended up just changing the word 'upgrade' to 'cupgrade' in upgrade_status.routing.yml as a quick fix and that worked, so it looks like something else is grabbing the 'upgrade' path, but searching through my installed contrib, only upgrade_status had '/upgrade' in it at all, so a bit stumped, really.
Comment #16
robindh commentedThe migrate_drupal_ui module actually uses the /admin/reports/upgrade path.
The migrate_drupal_ui.log route points to
MigrateController::showLog, which sets some session parameters and performs a redirect to the dblog.overview route.I've created a patch that changes all route suffixes from /upgrade to /upgrade-status to avoid conflicts.
Comment #17
robindh commentedFix test after change in https://git.drupalcode.org/project/drupal/commit/9293166c2713df8a0d582e5...
Comment #18
super_romeo commentedThanks. #17 works.
Comment #19
gábor hojtsyHa, great find! We even advise people to use the two modules alongside when testing upgrades to ensure the new code written is still Drupal 9 compatible.
Comment #20
gábor hojtsyGiving all of you credits because all of you tried to fix this and provided your steps :)
Comment #22
gábor hojtsyAnd landed. Thanks all! I'll try to make a release as soon as I can.
Comment #23
webchickWow! Great find, @robindh! :)