I don’t update as often as I used to, but so far it seems that it doesn’t break. Let me know when that happens.
I follow on Discourse Theme and I don’t see any issue yet.
2 Likes
Same. I’m giving up on all of my Discourse plugins and going to delete them entirely.
I’d change forum software if it was easier, but at least this will mean a bit less work.
The way this project has been managed is a complete disaster.
Will this update affect the MD components?： Improving automatic switching of mobile/desktop modes
https://github.com/discourse/discourse/commit/9aa52af4c9d261be19c538164eafd83463054998
I did a test on the latest version (commit : FEATURE: new tag info heading (#40171) · discourse/discourse@3c95497 · GitHub)
It works, but there’s a Deprecation notice
[THEME 9 'MD Topic List Mobile'] DEPRECATION NOTICE: Accessing site.mobileVieworsite.desktopView during the site initialization can lead to errors and inconsistencies when the browser window is resized. Please move these checks to a component, transformer, or API callback that executes during page rendering. [deprecated since Discourse 3.5.0.beta9-dev] [deprecation id: discourse.static-viewport-initialization] [info: https://meta.discourse.org/t/367810]
I’ll see what I can do, but it doesn’t break at least
4 Likes
Great! Thank you for your work 
There’s a notice on recent versions of Discourse 
:
[Admin Notice] Theme ‘MD Topic List Mobile’ contains code which needs updating. (id:discourse.static-viewport-initialization)
1 Like
I’ll try to look into it, it seems like a lot of work
But I think I can adapt using what @lhc_fl did with this component: Show both OP and last reply on mobile - #23 by Lhc_fl
3 Likes
After battling with it for hours… You can upgrade the component, the depecrated message should be gone (I couldn’t upgrade on the latest version today, but I don’t have the deprecated notice anymore, so the banner should disappear too) and we should be good for a few months, until Discourse changes everything again
The changes should be seamless on your forum but let me know if you have some issue!
The work by @Arkshine on the previous version and @lhc_fl on her component helped me a lot
4 Likes