Definitely following. Being able to add a rich visual experience, without losing the ‘to business’ functionality of a Discourse forum will greatly improve our user engagement.
Adding a tag to a post to set it to blog mode seems like a logical and simple way to go.
hi I met some problems, that our blog categaory is not blog-116 but blog/116, so I cannot apply this theme to my forum.
How should i set this set problem?
and this my forum link:https://www.agora.io/cn/community/forum/c/blog/116
We have a much better way of defining categories now in theme settings. I’ll get the setting updated at some point. Unfortunately, switching to the new method will disable the component until the setting is re-adjusted. I will make sure to warn everyone here when that change is coming.
That is strange. I just checked my test site and the component is working fine using the slug name. I wonder if it has to do with your subfolder setup. I haven’t ever tested the component in that environment.
Do you see any errors in your browser’s javascript console when you try to visit a topic in the category? You would want to check after setting the blog category theme setting to blog. And are you certain you have added the component to your main theme?
Hey! It has not, but I will bump it up in my priorities. I’ll make sure it gets added in the next couple weeks. I may even have a little time tomorrow next week
EDIT: I have tags working now on my local computer, but have found a few unrelated things I’d like to address before pushing the changes. Thanks for your patience
I just pushed a commit that adds Tag support and improves a few styling related things Please let me know if you notice any issues after updating the component.
Small note - tags you use for blog posts must be visible to all users (not hidden through tag groups). You can alway hide the tag with CSS if absolutely necessary.
On updating on the hosted instance with the default theme the following errors are popping up:
Error: Undefined variable: "$blog-tag". on line 80 of mobile.scss >> $values: $blog_tag; -----------^
Error: Undefined variable: "$blog-tag". on line 77 of desktop.scss >> $values: $blog_tag; ---------^
Doesn’t seem to have broken previous functionality though
Edit add: This went away after I added a tag, now the blog post styling is working but the image is not appearing, I earlier thought this was an issue with private tag groups, but doesn’t seem to be the case.
This is an odd bug in core we’ve been meaning to look into. For some reason there seems to an issue where it’s expecting a - instead of an _ in the variable name. The workaround at the moment is to make an adjustment to the theme settings as you figured out.
Thanks for reporting this! There was a flaw in the logic that was preventing the tags from being fully evaluated. It should be fixed if you update again.
I spotted a bug where, if I use either the category or tag based system,
If within a <div align="center"></div> tag there are uploaded images (not hotlinks, hotlinks work) then they are rendered in the preview but not after posting, sometimes they appear for a couple of seconds after posting but disappear soon after
It looks like this Theme Component isn’t being updated much these days, and the to-do list seems to perhaps include my problem (DiscoToC), but I thought I’d mention it anyway in the hopes it will inspire some updates here.
It appears that Blog Post Styling and DiscoTOC are fundamentally incompatible, at least with the site width I have. The ToC overlaps the text and I haven’t found a clear way to address this with CSS alone (though I am far from a CSS expert!).
I tried using the Default theme and removing my CSS customizations and it still happens. But as soon as I disable Blog Post Styling, it is resolved and the ToC appears in the right place. I would really love to be able to use both together though.
I have disabled DiscoToC for now, but you can see my site (with customized theme) here if that is helpful:
If it is helpful for me to re-enable DiscoToC so you can see this happening live, let me know.