Both tests were done from a test location in California while our servers are located in Germany, we are using HTTPS and babyforum.de is about 2.8 times bigger than Baby Bargains (which does not use HTTPS) - shouldn't your product be a lot faster than our search?
Both tests were done from a test location in California while our servers are located in Germany, we are using HTTPS and babyforum.de is about 2.8 times bigger than Baby Bargains (which does not use HTTPS) - shouldn't your product be a lot faster than our search?
Hi @Andreas - Threadloom will load faster than vB search on most forums, but I'm guessing that you're running on a pretty fast server. The nice thing is that Threadloom is easy to install and you can demo before going live. We've added a side-by-side preview mode that allows you to run a search in Threadloom and your legacy search simultaneously and watch the results load next to each other. You can see what it looks like on Baby Bargains.
Beyond speed, Threadloom has a bunch of other benefits like scaling to your search traffic (no spinning up additional servers when your traffic spikes), reducing your server traffic + associated costs, and spellcheck - ex: search for Maxi Cozi on Baby Bargains suggests Maxi Cosi but returns 0 results with standard search. And we're adding more...
Hope you'll give us a try. We like working with users, so let us know if you're interested and we'll be happy to talk through any questions you have.
Not to shame the developer or anything but there is currently a security issue with this plugin which allows any visitor to access any piece of content (thread, post, etc) stored in their database - the plugin does not currently honor vBulletin 4.x's permissions.
Wait for the threadloom team to address the vulnerability via a patch, in the mean time disable the plugin via the vBulletin admin control panel completely, and bring the /threadloom/ directory in your forum root directory into an inaccessible state. The threadloom team noted they will be disabling the search service on their end to cause an automatic fail-over to standard vBulletin search which in theory should prevent the vulnerability from being leveraged globally, however as of the time of this post that has not yet been activated.
The threadloom team has been in contact with me and are working swiftly to resolve the issue, just wanted to make sure other forum admins who aren't necessarily keeping an eye on their system have the latest information.
As a side note, the time that I have spent using the threadloom plugin I've seen a pretty well performing search engine, and the developers are extremely friendly and active and it really does seem like a great product to replace the aging vBulletin search core, if anyone had any thoughts about any of that. I'll be re-enabling the product on my own forum once the issue has been addressed.
Update: Developer confirms patch has been published and thus the issue resolved.
@xyd: Just wanted to thank you for reporting this issue and offer a brief summary for other admins. The issue affected vBulletin sites that had private forums that were viewable and searchable, but whose thread content were not viewable. Prior to Friday?s fix, it was possible for threads from those forums to show up in Threadloom search snippets. As soon as we confirmed the bug, we updated the Threadloom backend to stop sending search results to vBulletin customers, in order to trigger an automatic failover to standard search. We released an updated plug-in (v2.0.8) a few hours later. We've notified affected customers; all new sign-ups will receive the latest version of Threadloom. Protecting privacy is very important to us and we will work hard to prevent this from happening again.
Threadloom Search (vB4) Details »»
About Developer
Visit Web Site
DB Changes 
No support by the author.
04-24-2017, 03:15 PM
