I didn't consider that could be the issue - good idea. But hopefully there's nothing wrong with self-hosting the CSS, if that's what's causing the problem.Guys, make sure your users are white-listing your site if they're using any kind of browser addon blocker, like uBlock.
Thank you. Now if you guys could just do something about the issue I mentioned in my last post above....Working with uBlock we have the CSS no longer blocked so most of the styling has returned, still waiting to see if they will approve the JS for full functionality once again.
Thank you for your patience on this!
Working with uBlock we have the CSS no longer blocked so most of the styling has returned, still waiting to see if they will approve the JS for full functionality once again.
Thank you for your patience on this!
http://blog.threadloom.com/thread-prefix-support-for-xenforo@threadloom
Any chance you guys plan on adding a prefix search option?
Not sure if you looked yet or not, but I believe it to be a bug. Working with our ENG team to get that corrected.I've got lots of prefixes, but there's no drop-down menu with a prefix field as on the Home Theater site you guys link to, and searching by prefix brings up nothing. I am on your XF 2.0 beta version, though, so maybe that's why...? Or maybe it just isn't working right at the moment. I'll take a look again later today.
Thank you for tackling the uBlock issue!
I had thought maybe this had been resolved at some point, but I was still seeing this regularly on searches. I'm not sure if this is intentional, but I don't like thread responses showing up as separate search results, each one looking at first glance like a separate thread. I've disabled Threadloom until this is no longer the case, or there's an option to disable it. It's confusing for users. (Again, I'm using the beta on XF 2.)Does anyone know a way to NOT display thread replies in the search results? If I search by title I'd rather just have that title returned, not the title and down the page the ten replies people made to the thread, because it looks as if they're all separate results.
Is this happening every search? Or just particular results that aren't plentiful?I had thought maybe this had been resolved at some point, but I was still seeing this regularly on searches. I'm not sure if this is intentional, but I don't like thread responses showing up as separate search results, each one looking at first glance like a separate thread. I've disabled Threadloom until this is no longer the case, or there's an option to disable it. It's confusing for users. (Again, I'm using the beta on XF 2.)
It definitely does seem to happen when there are fewer thread results. If there were dozens of thread results for a search, it would likely be a non-issue. But if there's, let's say, only one thread returned, then that one thread will be shown and then below it all seven or eight (or however many) posts/responses to the thread will also be shown, but the way the results are formatted they all look at first glance like separate threads.Is this happening every search? Or just particular results that aren't plentiful?
If you provide your forum url via conversation, I'm sure we can work together to solve this dilemma
Yes, we support custom tabs for addons like Showcase - I know we discussed this via eMail - but for all others still wondering we do.Does Threadloom support add-ons like Showcase? Our users need the ability to search Showcase items.
Adds support for List Builder and includes an AMP-friendly change. Fixes an issue with expanded cards in search.
New
Changes
- Adds support for List Builder.
Fixes
- Improves compatibility with AMP by not loading JavaScript on AMP pages.
- Fixes an issue with expanded cards in search. There is still a known issue when filtering by certain usernames. This will be addressed in a future release.
I know we sorted this out via the helpdesk ticket, but for all others, if you are running Xenforo 2.0, we have launched the 1.0 full from the beta that we had previously.In the portal I'm only given the option to download 1.0.0, which I'm already running...
View attachment 183539
We use essential cookies to make this site work, and optional cookies to enhance your experience.