Get WPFTS Pro today with 25% discount!

Categories

  • Announcements regarding our community

    1 Topics
    1 Posts
    EpsilonAdminE
    A new version of WPFTS with a fundamentally new search algorithm is out now! Some time ago, we have accumulated quite a lot of feedback from users who very much asked to add an improvement in search - to significantly increase the search speed on a large number of documents and add the ability to search for a phrase. This became somewhat of a challenge for us since it seemed almost impossible to implement a full-fledged indexed search using the small power of PHP and MySQL. New Search Algorithm But, as a result, we managed to get closer to the goal. To achieve this, the search algorithm had to be completely redone. Yes, it's still TF-IDF, but with significant additions to the logic and relevance calculation. In particular, we have added a "phrase bonus", which allows those documents in which similar phrases were encountered to be displayed in higher places. Note that phrases, in this case, can be not only EXACT matches but also partial matches of words, as well as nearby words (not only close ones). For example, for the search phrase "infinite space", the relevance will be increased in those documents where the phrases "infinite distant space" and even "space seems to be infinite" are found. The word order in the phrase is currently ignored. An option that includes strict word order in the phrase will appear in the next updates. Deep searching is faster Also, the speed for "deep search" has been significantly increased. So, for example, by default the query "cat" will only find words like "catty", "catalog", that is, those whose beginning exactly coincides with the search word. When you enable "deep search", the words "subcategory", "procatering", "mystification" and the like will also be found, that is, words in which the "cat" occurs in the middle or at the end. Previously, a "deep" search literally put the algorithm into a stupor and the search could take 10, 20, or even more seconds. Now, with our new algorithm, deep search has become much faster, and even on a large number of documents can take only 2-3 times longer than a regular "non-deep" search. No character limit anymore Thanks to the new algorithm, it becomes possible to get rid of the 3 character limit on the length of the request. Previously, this limitation was necessary because searching for one or two characters set in motion almost the entire search index, as a result of which the query could run for a very long time and even lead to a script crash. Now it has become possible to remove the limitation on the number of characters since requests of one or two characters only receive a limited number of matches and do not significantly slow down or crash the script. Faster with the Word Index We have introduced one more small index - word index. It allows you to increase the search speed significantly for a large number of documents, since it partially relieves the load on MySQL, eliminating the need to perform concatenation operations on huge tables. MyISAM support was dropped We have dropped support for the MyISAM table type and removed the corresponding option and all associated algorithms from the code. Tables of this type all too often lead to "locking" and despite the fact that they sometimes give a 10-20% bonus to search speed, people decided to abandon MyISAM in favor of the more modern type as InnoDB. Faster re-indexing Indexing and re-indexing of documents have also been significantly accelerated, although the new "word index" slightly increases the re-indexing time. We are still working on improving this part of the plugin. Work on improving the plugin is very active, only about 40% of all planned improvements for this year have been implemented. Therefore, your feedback and understanding that bugs may occur are very important to us. If you notice an error or inaccuracy, please report it immediately on the plugin support forum. Let me remind you that I have a Patreon page. If you want to support the development of this awesome plugin, I would be very grateful. Thank you for using WPFTS!
  • 24 Topics
    71 Posts
    EpsilonAdminE
    Hi @inkedraskal Great, thank you. We going to release this version officially in some days. Thanks!
  • Noticed a bug or an issue? The solution is (probably) here!

    50 Topics
    246 Posts
    EpsilonAdminE
    Hi @alihs Thank you for this message. Could you please tell me what is php_deprecated error is? Any screenshot or error message? Thanks!
  • 37 Topics
    92 Posts
    V
    We recently implemented a licensed version of WPFTS, and it's working great. I did find a code snippet to change the results per page from the default 5, to 10 per page, and that works. (Using the Code Snippets plugin to add this.) Here's the issue I'm hoping someone can help with. I've searched the forums, and can't find an answer that quite matches. We use a membership plugin, Restrict Content Pro, to limit certain content to active members. When I do a search, get excerpts, then click on the link in the excerpt, I get a 'forbidden' error, even if I'm logged in. Even as an admin. I assume this is because the pdf in question is behind the RCP member firewall. What I'd like to do is get a bit of code I can implement using the Code Snippets plugin that would recognize the logged in active member, and allow clicking on the link in the excerpt to open the pdf in question. I found some related code, but it is basically designed to block access, and I'm trying to do the opposite. If it helps, I pulled this from RCP developer docs: rcp_membership_get_status Parameters: $status (string) – The member’s current status. $membership_id (int) – ID of the membership being checked. $membership (RCP_Membership) – Membership object. The membership status we want is 'active'. Thanks for any help you can provide.
  • Blog posts from individual members

    0 Topics
    0 Posts
    No new posts.
  • A place to talk about whatever you want

    14 Topics
    42 Posts
    EpsilonAdminE
    Hi @marcellosalass Actually WPFTS could be not that great for you in case you have millions of records (e.g. posts). The whole Wordpress could be not good for you either, because to handle such amount of data you will need to use specific optimization and caching algorithms and even clustering. I would like to propose you to use full-text solutions based on Apache Solr or Elastic Search - those tools are implemented in Java and work way faster than PHP+MySQL solution provided by WPFTS and they are especially good for big data. Alternatively you can wait until we release a new WPFTS version (in 1-2 months) that can use self-hosted Elastic Search engine to keep full-text index and uses WPFTS data collecting algorithms. Thank you for the question.

Be the first to read the news!

We are always improving our products, adding new functions and fixes. Subscribe now to be the first to get the updates and stay informed about our sales! We are not spammy. Seriously.

Join Us Now!

We are a professional IT-team. Many of us have been working in a Web IT field for more than 10 years. Our advanced experience of software development has been employed in the creation of the WordPress FullText Search plugin. All solutions implemented into the plugin have been used for 5 or more years in over 60 different web-projects.

We are looking forward to your comments, requests and suggestions in relation to the current plugin and future updates.

ewm-logo-450

The forum powered by NodeBB | Contributors