• Resolved Georgia Morrison

    (@gmorrison)


    Warning: require_once(/mysite/wp-content/plugins/ajax-search-for-woocommerce/fs/lib/includes/supplements/fs-essential-functions-2.2.1.php): failed to open stream: No such file or directory in /mysite/wp-content/plugins/ajax-search-for-woocommerce/fs/lib/includes/fs-essential-functions.php on line 39

    Fatal error: require_once(): Failed opening required ‘/mysite/wp-content/plugins/ajax-search-for-woocommerce/fs/lib/includes/supplements/fs-essential-functions-2.2.1.php’ (include_path=’.:’) in /mysite/wp-content/plugins/ajax-search-for-woocommerce/fs/lib/includes/fs-essential-functions.php on line 39

Viewing 9 replies - 1 through 9 (of 9 total)
  • same problem error on our site, I have disabled the plugin and will rollback to the previous version tomorrow.

    Plugin Author Damian Góra

    (@damian-gora)

    Hi @gmorrison and @udoh

    Apologies for that. For some reason, TortoiseSVN we use to add new versions to WordPress plugin repository got stuck with an error, and not all files were sent. It shouldn’t happen, but it happened.

    I revert the stable tag to the latest stable version v1.21.0 and put off the next release until next Monday. We have to check why some files weren’t sent.

    Solution on how to rollback the plugin:

    Go to the wp-content/plugins folder and rename the plugins folder to something else like ajax-search-for-woocommerce-off. Then the error will disappear.

    Next, log in to WP Admin and go to Plugins. Remove FiboSearch - AJAX Search for WooCommerce plugin and install it again.

    Best
    Damian

    Thanks for the the fast repsonse and well explained solution. I look forward to the update.

    Hey @damian-gora I still have not updated to the new version, should I wait until next monday or the end of next week? This update didn’t fix any security vulnerabilities right?

    Plugin Author Damian Góra

    (@damian-gora)

    Hi @blclda,

    You can update FiboSearch to the latest stable version v1.22.3 without any hesitation right now. The issue mentioned in this topic occurred only for a short time frame (30 minutes) last Saturday. This issue does not affect 99.9% of users.

    Consequently, we changed our procedures of publications on wp.org and now such problems will not occur. We had a timeout during publication via SVN, and despite an error message, a new version was released with missing files. Now we learned how to create tags from trunk to avoid such as scenario.

    The last version didn’t fix any security issues. The most important change is adding a fantastic feature User History Search and I recommend checking it because it’s another must-have feature for most online stores.

    Best
    Damian

    Thank you very much.

    Thanks for the update and the details.

    Hey @damian-gora just to finish, I saw the new searh history feature and liked it a lot, when does it come out of beta?

    Plugin Author Damian Góra

    (@damian-gora)

    Hi @blclda,

    I’d be happy to answer that question, but it’s not relevant to the following topic. Just create a new topic.

    Best
    Damian

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘“Fatal error” = no weekend updates, k?’ is closed to new replies.