Support » Plugin: Better Search » Worst plugin ever

  • meem

    (@rayyaninst)


    Searches yielded no results. Had to deactivate and activate again to make it work. After one day, same, searches started yielding no results, then had to deactivate activate again. Avoid, poor plugin.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Ajay

    (@ajay)

    In a bad review for Relevanssi you mentioned you’re using WP Engine as your host?

    WP Engine doesn’t allow FULLTEXT index being created on our DB and will automatically delete this. As a result, you’ll never get this to work.

    It will work on hosts other than WP Engine or Godaddy which give you freedom to do what you want!

    Hey Ajay!

    You are correct about WP Engine not allowing FULLTEXT indexing by default. But I wanted to provide some additional information.

    MySQL 5.5 now uses InnoDB as a default table engine.

    However, WP Engine does offer an upgrade for free if asked to a server that uses MySQL 5.6 which allows InnoDB to FULLTEXT index. The only thing to remember about the upgrade is that you need to compatible with PHP 5.5. That should get the plugin to work. (theory)

    SPM and Ajay, keep that in mind if you see this issue pop up again. 🙂

    Thanks!
    Eric

    Plugin Author Ajay

    (@ajay)

    Eric,

    Thanks for the comments. From mySQL 5.6 onwards, even InnoDB will support FULLTEXT. But, it’s a while before that happens across servers. But, it’s good to hear WP Engine will upgrade you to it. However, would they support FULLTEXT indices?

    Either ways, I don’t think SPM is really going to come back to this review and change it.

    Hey Ajay,

    It’s not the issue with WP Engine supporting FullText, its that InnoDB is reported to have greater performance gains so WP Engine forces tables to use it which then removes FullText indexing from MySQL 5.4 and 5.5.

    If the table is InnoDB and on MySQL 5.6, then FullText index should work just fine. 🙂

    The user just needs to request to be on a PHP 5.5/MySQL 5.6 environment.

    If the review doesn’t change, I’m sorry about that but now you understand the system at WP Engine and can use it in future responses!

    Please feel free to ask me any more questions on this thread about WP Engine’s system.

    Thanks!
    Eric

    Plugin Author Ajay

    (@ajay)

    Eric,

    Thank you and that is indeed good to know about WP Engine. It holds true for my other plugin as well. Contextual Related Posts which also uses the fulltext index.

    However, unfortunately, it still finds its way there 🙁

    Disallowed Plugins

    I’ll talk to the WP Engine plugin team to see if we can re-evaluate the plugin.

    Thanks!
    Eric

    Plugin Author Ajay

    (@ajay)

    Eric, that sounds great 🙂

    meem

    (@rayyaninst)

    I am willing to try this again and if it works, I don’t mind changing my review.

    meem

    (@rayyaninst)

    btw I’m meem now (formerly spm)

    Plugin Author Ajay

    (@ajay)

    Hi meem, I don’t think WP Engine will budge on this one. I had another user who faced a similar issue with another plugin of mine and I suggested the above i.e. getting the mySQL 5.6 and the response was that they don’t have servers with this.

    I really want to get you to change the review, but given their stance, unfortunately there isn’t much I can do because they automatically delete the FULLTEXT indices from I understand.

    You can try using the latest version of the plugin that will fall back on producing search results even if the FULLTEXT results fail. However, you won’t get any relevancy matching.

    Personally, I believe they are doing a good job to try and keep customers sites fast. But, I don’t believe that you should be restricted on what you can run on your site in terms of plugins. However, I am likely a minority on this one.

    Hey Ajay and meem,

    Me again! WP Engine has MySQL 5.6 servers. You may need to request to be put on a PHP 5.5 server.

    Good news is that WP Engine is actively updating their farm to PHP 5.5/MySQL 5.6. This means that the request might not be needed in due time.

    Thanks!
    Eric

    Plugin Author Ajay

    (@ajay)

    Hi Eric, thanks again for the update. This is what another user received as a response for this. Hence, my above response.
    https://wordpress.org/support/topic/the-best-related-posts-plugin-3?replies=6

    meem, My suggestion would be to speak to WP Engine support based on what Eric mentioned above and ask them to upgrade you to InnoDB and mySQL 5.6 so you can use the FULLTEXT indices and hopefully the plugin.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Worst plugin ever’ is closed to new replies.