Forum Replies Created

Viewing 15 replies - 1 through 15 (of 92 total)
  • That could be yes, the last update from this plugin was a signifant time ago. If a lower version works for you, you can have it working like this.
    I don’t know if there are any advantages from using a newer version from Redis (besides maybe security issues that got patched, if any).

    I’m working on something else based on Typesense.
    https://typesense.org/
    I think there is a plugin for WordPress/WooCommerce already (paid) that puts Typesense in place. Perhaps this might be a solid alternative for you too?

    redis and redisearch are not the same thing.

    redisearch is a plugin/extension for Redis that adds search functionality on top of your redis instance. It’s also not “inside” redis by default. If you want to take advantage of redisearch, you first need to install the extension by creating a customized Docker image that includes/installs the extension or you need to install manually after deploying the base image.

    • This reply was modified 3 years, 4 months ago by codeagency.
    Thread Starter codeagency

    (@7grafix)

    @niklasinpsyde

    Sorry for my late reply.
    The error can definetely be reproduced, but the error message is coming from the debug.log
    I’m seeing this error message appearing in many client websites.
    They were not happening before plugin version 7.0.4
    The client sites are running PHP 7.4 to 8.1, they all have this problem after updating Mollie plugin.

    I didn’t understand at first where it was coming from, but as @studiobrabo is mentioning it comes from a cancel process (mostlikely automatic cancel from WooCommerce after pending payment status) but the timeframe is different, depending on what cancel time is configured in settings.

    Confirmed, problem is fixed by manually upgrading the plugin.

    @alexmigf

    This feature seems to be broken after the recent update.
    We are running the premium plugin and after the new preview feature is introduced the invoice and packing slip layout is broken.

    Thumbnail feature is added, custom field is added but nothing shows.
    Even when I select other simple default fields like weight etc…

    I also ready sent an email to support@ to report this issue too.

    Thanks!

    Forum: Plugins
    In reply to: [RediSearch] Unix Socket

    @foadyousefi

    This update has broken connectivity for TCP.
    Plugin was working fine, after installing 0.3.3 I can no longer connect over TCP.
    Tried both from server settings window as also from wp-config.php params.

    Changing back to 0.3.2 and everything works again.

    A phpfpm configuration should look something in these lines (by default):

    pm = dynamic
    pm.max_children = 16
    pm.start_servers = 8
    pm.min_spare_servers = 2
    pm.max_spare_servers = 8

    You can use calculators like the one below to tweak it better according to your server resources.
    https://spot13.com/pmcalculator/
    https://chrismoore.ca/2018/10/finding-the-correct-pm-max-children-settings-for-php-fpm/

    Sounds like an incorrect configuration of your VPS.
    A “normal” hosting setup will never allow unlimited or such huge number of php workers.
    Typically it’s limited to just a few dozen of workers to be spawning and also kill them if they timeout.
    Seems like your hosting configuration is set to go beyong a reasonable limit and that is causing the culprit as your server allows it to go run forever.

    @gijo

    I can confirm I have this very exact same problem on several websites.
    Anything related to cart page is not working such as adding, updating, deleting, the cart page does not reflect until you manually hit F5 on the cart page then it suddenly updates.

    I already triple check all settings. I have added exclusion words.
    By default your plugin already adds /cart but still it does not work.
    I also have some pages in other names in my language and added /winkelmand but still this does not work.
    And it is 100% coming from your plugin because when I disable it, everything works back to normal.

    Since I can replicate this exact bug over and over on multiple websites, this is no coincidence.
    Either there is a bug in the way how your plugin handles interactions with the cart or that wordlist is ignored for cart page.

    If you want to troubleshoot more indepth, let me know how I can contact you and happy to help you improve this.

    Thanks

    Fabio

    @daigo75

    Same problem here 🙁

    When I enter VAT number from the requester WITHOUT countrycode, it returns fail.
    if I add countrycode BE, it fails too
    if I try a second time, it returns failed for BEBExxxxxxx

    Your plugin duplicates the countrycode

    The plugin was working fine for 3+ years on most of my client websites, and now since ~3 or 4 weeks I think it’s problems all over the place with VAT validation.
    Agree, if the VIES service fails, it’s not your plugin fault. I notice they have big issues since some time.

    But still, I think some items might be plugin related.
    When I see that simply saving the options page already fails and the plugin is acting weird with double country codes…. I wonder if that problem is related to any of the validations in the checkout.
    Perhaps it fails VAT number not because of the customer his VAT ID but due to the requester VAT? Since saving the options already returns this error, I can only assume it also runs into same problem during a checkout.

    Is there an option to disable VIES validation in the checkout? But not hide the field or anything. I still want customers to be able to enter the VAT ID so merchant can validate it manually at some point but still remove the VAT from the order total.
    If the customer his VAT was already validated 6 months ago, I don’t see the point why it needs to be validated for every single order, every day, over and over.
    Because now, we only get angry, frustrated clients because they loose turnover due to VAT validation problems.
    And the plugin is not flexible to allow us to disable the validation service while keeping the fields in place.

    Any thoughts Diego on how to get this back working stable or at least have a workaround option from the plugin settings so my clients can enable/disable some thing themselves fast when service issues with VIES?
    Working with code changes and snippets is not possible at those moments, my clients must be able to tick a box themselves immediately if they notice issues with VIES.

    Thanks.

    @joelrsadler @obenland

    To disable the email with login details is very easy with no need for additional plugins.
    It’s default hook and it’s pluggable, so you need to override it with a filter like so:

    add_filter( 'wp_new_user_notification_email', '__return_false');

    That’s all you need to add to your child theme functions.php, and solves the problem.
    I’m using this same function on a few projects myself, and I can confirm this works totally fine.

    Thread Starter codeagency

    (@7grafix)

    @joe-bloggs

    check out this plugin, they have it working.
    https://ww.wp.xz.cn/plugins/dynamicconditions/

    Thread Starter codeagency

    (@7grafix)

    @mashalshaikh no I havent any solution.
    I have removed the plugin since the author is not responding to issues.
    It’s been 4 months since I opened this thread… says enough.
    Shame….

    Thread Starter codeagency

    (@7grafix)

    For anybody else:

    The issue comes from Docker image.
    The redisearch Docker image comes with NO default redis.conf
    You have to create that one first. After that, everything started working immediately

    I tried a regular Redis service before, and that one comes with a default configuration file, hence the reason why the Redis Cache plugin from Till Kruss works “out of the box”.

    So either you upgrade the redis service container with the redisearch mod OR you deploy Redisearch Docker image and use a default config from redis.

    After doing this change, the plugin succesfully can connect to Redisearch.
    Still working out some bugs with CSS and wp_search but the indexing is working properly with the container image.

    @marinblu

    I had same problem. The issue comes from Docker image.
    The redisearch Docker image comes with NO default redis.conf

    You have to create that one first. After that, everything started working immediately

Viewing 15 replies - 1 through 15 (of 92 total)