Conversation
📊 Performance Test ResultsComparing f73e587 vs trunk site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
ivan-ottinger
left a comment
There was a problem hiding this comment.
This is a nice shortcut! It works well when the debug.log file exists:
CleanShot.2026-02-24.at.10.35.18.mp4
But if it is missing, the link is not clickable:
CleanShot.2026-02-24.at.10.38.33.mp4
Maybe we could consider disabling it in that case.
|
@bcotrim, it works well for me on Mac. I was wondering what would be the best UX - e.g., if we should add "Debug log path" field below, with |
ivan-ottinger
left a comment
There was a problem hiding this comment.
Thank you for the updates, Bernardo.
I can confirm the link is not displayed anymore when the debug.log does not exist. 👍🏼
There's still a slight edge case: When the user is already on the Settings tab, the link won't appear/disappear if the debug.log is added/removed from the file system, but I think that is acceptable.
I considered it, but it would require a file watcher. To me it seems the added complexity doesn't pay considering it should be an edge case. |
|
@wojtekn I agree that looks better! Please let me know if this is good or if you prefer the previous version.
|
Thanks for trying that. On second thought, the file name will be the same in most cases, and your first approach was consistent with certificate nudge. What do you think? |
I think the file location being always the same is a good point, it doesn't make much sense to have it here. |

Related issues
Proposed Changes
showItemInFolderto reveal thewp-content/debug.logfile in the system file managerTesting Instructions
debug.logselectedPre-merge Checklist