Closed webdeck closed 1 month ago
missed this one; ill have a look at it later
could you try .4 ?
Still seeing the same thing after updating to .4
did you clear the cache after updating? (update.sh script)
Yes, I do that every upgrade. Did it again and still have the issue. Here is the output from the upgrade:
Get latest information from git
remote: Enumerating objects: 10, done.
remote: Counting objects: 100% (10/10), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 10 (delta 7), reused 10 (delta 7), pack-reused 0 (from 0)
Unpacking objects: 100% (10/10), 889 bytes | 296.00 KiB/s, done.
From https://github.com/antedebaas/DMARC-SMTPTLS-Reports
f406626..2b808b3 main -> origin/main
* [new tag] v1.21.4 -> v1.21.4
Checkout to latest tag
Previous HEAD position was f406626 add defaults
HEAD is now at 2b808b3 fix reset link
From https://github.com/antedebaas/DMARC-SMTPTLS-Reports
* tag v1.21.4 -> FETCH_HEAD
Already up to date.
Install composer dependencies
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
Generating autoload files
95 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Run composer recipes at any time to see the status of your Symfony recipes.
Executing script cache:clear [OK]
Executing script assets:install public [OK]
clear cache
// Clearing the cache for the prod environment with debug false
[OK] Cache for the "prod" environment (debug=false) was successfully cleared.
run migrations
[OK] Already at the latest version
("DoctrineMigrations\Version20241013152649")
run upgrade script
done
install assets
Installing assets as hard copies.
[OK] No assets were provided by any bundle.
warmup cache
// Warming up the cache for the prod environment with debug false
[OK] Cache for the "prod" environment (debug=false) was successfully warmed.
ill need to dive into this
can you provide an (anonymized) report for investigation?
Oh, now I see that if I go to the SMTP-TLS reports page, the Disabled tag is gone. However, it still displays on the list on the Home page.
Oh good. I will update the homepage later but then I know what to do
.6 fixes the homepage
Describe the bug Every SMTP-TLS report from Microsoft shows a red "Disabled" tag on the main page, but the details don't show anything as Disabled.
Are you using the Docker image?
Database used
Webserver used (when not using docker)
Database version used 15.8
Steps to Reproduce Please provide -detailed- steps to reproduce the problem:
Expected behavior Either show what is disabled, or do not show Disabled tag
Screenshots