A few users of my forum report that they can see topic lists in first page. However when they open a topic, they see a blank page.
What could be wrong here?
Users are reporting a blank page when opening topics on mobile devices, though topic lists load fine on the homepage. hosna confirmed the issue doesn’t occur on desktop and is isolated to mobile. Canapin suggested checking browser console errors and testing in safe mode, but hosna noted users can’t easily access console on mobile. Stephen speculated it may relate to older devices or browsers. hosna reported one affected user used a ZTE BLADE V0720 with updated Chrome, yet the issue persisted. dimsuz confirmed similar reports: one Android user resolved the issue by upgrading to Firefox Mobile, while an iOS user with the latest Chrome still saw a blank page — only the header rendered. This iOS user had an outdated iOS version and planned to upgrade. dimsuz noted the issue began after upgrading from Discourse 2.2.x to 2.3.1, and they’ve since upgraded to 2.3.3, pending user feedback. The issue appears tied to mobile browsers, possibly outdated OS or browser versions, and may be related to recent Discourse updates.
Did you encounter the issue yourself too? If you did, you could try in safe mode to see if the issue persists: Using Safe Mode to troubleshoot issues with themes and plugins
If you didn’t, you can ask your users to take a screenshot of the console tab in the browser development tools (on desktop) to see if there is any error.
Also, does it happen on any topic?
Does it happen only on mobile?
No i dont encounter it.
It seems it only happens in mobile. So I dont know how they can lunch console.
It’s usually indicative of an older device/browser.
Can you get some details on the phone model and browser being used?
One of the recent users with this bug had ZTE BLADE V0720. Also, I tell all of them to update chrome and they claim they have updated it. However the problem exists.
Same happens here. I’ve got 2 user reports, both on mobile, one Android, one iOS.
These reports started coming after I’ve upgraded from 2.2.x to 2.3.1. I have just upgraded to 2.3.3, will ask if this helped my user…