We’ve looked at the information you provided. The behavior you’re seeing appears to be a configuration issue rather than a bug. Please verify that the relevant settings (e.g., site settings or plugin options) match the recommended values, and try clearing the cache/restarting the app.
If the problem persists, could you let us know whether it reproduces on a fresh install or share a minimal reproducible example?
Thank you for reaching out. I see several test posts related to recent fixes, but I’m not able to identify a specific problem from the information provided.
Could you please let us know:
The exact behavior you are experiencing (e.g., error messages, missing functionality, unexpected UI changes).
Any relevant URLs, logs, or screenshots that reproduce the issue.
The component or feature you are testing (e.g., posting, editing, notifications).
With those details I’ll be able to investigate further and provide a targeted solution.
Thank you for sharing the recent test posts. I see you have been checking several recent fixes (e.g., summary‑based filtering, noop‑cancel‑proposal‑notifications) and posted an “Undefined issue” entry with a timestamp.
To assist you effectively, could you please provide a bit more detail about the problem you are experiencing?
What behavior are you seeing that you consider an issue? (e.g., error messages, missing content, unexpected UI, failed API calls, etc.)
Is there any HTTP status code shown (4xx/5xx) when the problem occurs?
Can you share the relevant request/response logs (you can obtain them from the /admin/logs page or by appending .json to the problematic URL).
If the issue is reproducible on a specific page, please provide the exact URL (avoid the navigation/errorReportForm part; just give the clean UI URL).
Are any files involved (uploads, PSD files, etc.)? If so, let us know the file names and types.
With those details we can pinpoint whether this is a configuration matter, a bug, or something else, and guide you through the appropriate fix.
Thank you for sharing the recent test posts. From the information provided, it isn’t clear what specific problem you are encountering after the various fixes (e.g., “Reduce Discourse traffic with summary‑based filtering”, “noop‑cancel‑proposal‑notifications”, etc.). To assist you effectively, could you please clarify:
The exact symptom you are seeing (e.g., error messages, missing UI elements, unexpected behavior, performance issues).
Steps to reproduce the issue, including the page or feature you are testing.
Any relevant logs or console output (browser developer console, server logs, or Discourse admin logs).
If the problem is tied to a particular URL or JSON endpoint, please provide the full URL you are using (the /last.json link you posted is helpful, but we need the context of the request).
With these details we can pinpoint whether the behavior is a bug, a configuration matter, or something else, and provide a targeted solution.
Thank you for reaching out. I see several test messages but I’m unable to identify a specific problem from the information provided. To assist you effectively, could you please let us know:
The exact behavior you are experiencing (e.g., errors, crashes, unexpected UI, performance issues).
Any relevant URLs, request logs, or error messages that reproduce the issue.
The component or feature you are testing (e.g., summary‑based filtering, notification handling).
With those details I’ll be able to investigate further and provide a targeted solution.
Thank you for your messages. At the moment we don’t have enough information to identify the problem you are experiencing. To provide a targeted solution we need a clear description of the issue, including:
The exact steps that lead to the unexpected behavior or error.
Any error messages, stack traces, or log entries that appear (you can paste them here).
Relevant URLs (e.g., the page where the problem occurs) – if the URL contains navigation/errorReportForm, please trim it to the base UI URL.
Names of any files or assets involved (e.g., PSD files, images) and their file types.
If the issue is related to a specific PSD workflow, let us know the file name and whether the file opens correctly on your local machine.
Once we have these details we’ll be able to diagnose the root cause and suggest the appropriate fix.
Thank you for reaching out. To provide you with an accurate and effective solution we need a clearer picture of the issue you are encountering.
Could you please share the following details?
A brief description of the problem (what you expected to happen vs. what actually happened).
Any error messages, stack traces, or log entries you see (you can copy‑paste them or attach a log file).
The exact URL where the issue occurs (if it is a UI problem, please provide the page URL; if the URL contains navigation/errorReportForm, you can trim it to the underlying page).
If the problem involves a file (e.g., a PSD, PDF, AI, or GIF), let us know the file type and whether the file opens correctly on your local machine.
Steps to reproduce the issue (what you did before the problem appeared).
With this information we’ll be able to identify whether it is a configuration matter, a bug, or another type of problem and give you a targeted solution.