Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUGFIX] Fix showing "Scheduled" and "Run-time" columns in backend log #1121

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

cweiske
Copy link
Contributor

@cweiske cweiske commented Jan 29, 2025

In Info > Site Crawler > Crawler log:
As soon as the backend user activated the "Show Result Log" checkbox one time, the columns "Scheduled" and "Run-time" are empty when the checkbox is disabled.

The reason is that the variable's value is not taken into account, only its existence in the user session data.

Description

I have

  • Checked that CGL are followed
  • Checked that the Tests are still working
  • Added description to CHANGELOG.md (github-handle is optional)
  • Added tests for the new code

@tomasnorre
Copy link
Owner

tomasnorre commented Jan 29, 2025

Thanks for the PR.

Would you mind updating the PHPStan baseline, so that it runs green again.
I have just re-triggered the Acceptance Tests, as there should be no reason for them to fail.
Update: I'll update the v11.x branch to use never versions of the deprecated actions, can you please rebase?

Would this also apply for 12.0.x releases?

I sort of had decided to not do anymore bug fixes for the 11.x branch as TYPO3 11 it ELTS now.
But if it requires less work from me, I'll accept it.

In Info > Site Crawler > Crawler log:
As soon as the backend user activated the "Show Result Log" checkbox
one time, the columns "Scheduled" and "Run-time" are empty when
the checkbox is disabled.

The reason is that the variable's value is not taken into account,
only its existence in the user session data.
@cweiske
Copy link
Contributor Author

cweiske commented Jan 30, 2025

  • rebased
  • phpstan fixed

Would this also apply for 12.0.x releases?

No, the backend log view had been rewritten in 2022 with commit 0e7d7e2.

@tomasnorre tomasnorre merged commit 68f96d2 into tomasnorre:v11.x Jan 30, 2025
32 checks passed
@cweiske cweiske deleted the empty-logfields branch January 30, 2025 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants