PayPal pay later setting are not saved

  • Resolved joe16

    (@joe16)


    4 months, 3 weeks ago

    Hi,

    With LiteSpeed Cache enabled: when I try to update check/uncheck PayPal Pay Later settings, then save, the changes are not taken into account. But When I disable the cache, everything work as expected.

    I had a similar issue with Stripe (check this thread) and I had to disable the “Cache REST API” option (based on your suggestion) to make things work. Now, even with this option kept disabled, it looks that it does not work for PayPal Pay Later settings.

    Is there any other option that I have to disable?

    Looking forward to your reply.

    My best regards,

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support qtwrk

    (@qtwrk)

    4 months, 3 weeks ago

    only thing I can only of might be the object cache , have you enabled that ? if so , please try disable it and see how it goes

    Thread Starter joe16

    (@joe16)

    4 months, 3 weeks ago

    Hi @qtwrk,

    Thank you for your quick reply.

    You are right, when I disable the Object cache (tab [6] Object), even with the pages cache enabled (tab [1] Cache), the pay later setting are saved correctly.

    1. Please note that the Object cache is toggled on, but not technically set up (neither Memcached not
      Redis extensions are enabled). Please check the screenshot. How this is supposed to enable the
      Object cache and prevent the pay later settings to be updated?
    2. Also, how come the Object cache is enabled at the back office level and not only at the front
      office level?
    3. How to be able to update settings in the back office while keeping the Object cache enabled?

    Looking forward to your reply.

    My best regards,

      Plugin Support qtwrk

      (@qtwrk)

      4 months, 2 weeks ago

      without further investigation on your site , be honest I am not sure.

      object cache is same for frontenad and backend though.

      but if you don’t have redis/memcached enabled, it is meaningless to keep it enabled, specially if it causes you trouble.

      • This reply was modified 4 months, 2 weeks ago by qtwrk.
      Thread Starter joe16

      (@joe16)

      4 months, 2 weeks ago

      @qtwrk thank you for your reply.

      “object cache is same for frontenad and backend though.”

      => I’m planning to set up object caching. Will this cause me trouble while editing posts and updating posts on the back office?

      Plugin Support qtwrk

      (@qtwrk)

      4 months, 2 weeks ago

      for wordpress’s default post , page , and woocommerce product , these post type works fine , I know for sure , but I can not guarantee for other custom type post though.

      Thread Starter joe16

      (@joe16)

      4 months, 2 weeks ago

      OK, thank you for the answers.

      I would suggest excluding the back office from the object cache, if this is possible.

      • This reply was modified 4 months, 2 weeks ago by joe16.
      Plugin Support qtwrk

      (@qtwrk)

      4 months, 2 weeks ago

      there is an option cache wp-admin , can try that

      Thread Starter joe16

      (@joe16)

      4 months, 2 weeks ago

      I tried it. “Cache WP-Admin” toggled off, and I kept “Store Transients” toggled on.

      It does not work all the time (I tested many times, only seen the change applied 2 times). I don’t know on what it depends on.

      Plugin Support qtwrk

      (@qtwrk)

      4 months, 2 weeks ago

      it also depends on how plugin implements/supports the wordpress’s object cache

      our plugin was merely provide a bridge between wordpress and redis/memcached , wordpress itself has object api for themes/plugins to use

      Thread Starter joe16

      (@joe16)

      4 months, 2 weeks ago

      Thank you for your reply.

      I will ask the PayPal plugin support regarding the object cache implementation.

    Viewing 10 replies - 1 through 10 (of 10 total)
    • You must be logged in to reply to this topic.