Strange. I updated to 3 nested layers of categories but now i find that the Categories List component ignores any categories which have three layers within them. I get no errors in console
Update: I’ve worked it out. On our forum the component didn’t like category slugs left blank, so using the default set up which just uses sequential numbers. If one category or sub was using the default slug none of its brothers and sisters would show up either… well most of them wouldn’t. Occasionally one does and i can’t see why.
I’ve noticed this plugin doesn’t play nice on desktop with the popular Kanban boards plugin. That can be overcome by allowing users to close the plugin with a click. I guess expected functionality, if you want them to work together, would be that it recognises the other element and begins in closed mode. Allowing the user to open it if needed.
We are currently working on a modified version which would achieve that in a slightly different way. So it won’t be a direct solution to this bug for those who want their functionality to stay the same.
Hey @Drew-ART, check out the layouts interoperability topic on the Pavilion forum. This topic addresses the interoperability of the layouts plugin with other plugins/themes. There is a suggested fix mentioned for the layouts plugin to work with Discourse Kanban by adding some CSS.
I have a very odd output with the use of both custom layout plugin and the location plugin.
I have the layout plugin set up in a way that shows a topic location map on the right side of the topic list for a couple of the categories. it used to display like this.
Thanks for identifying this issue in a very detailed manner. The information your provided will be very helpful in fixing this problem. I created a bug report for this issue, and hopefully we can resolve this issue very soon. Sorry for the inconvenience! I will post an update here once this issue is resolved.
FYI this issue started when I upgraded the discourse software around a month ago. I upgraded to 2.8.0.beta6 (f38fd1a5a7) yesterday and the issue persists.