• Resolved Me

    (@marknl1981)


    Hi!

    Just like other users I do not get any answer of you anymore. I spend lots and lots of time in finding the memory issue and you are not reacting anymore by email.

    But i post this for other users…

    The plug-in is not compatible with woocommerce sequential order numbers

    When using that plug-in after a while the order id numbers and the real post id numbers in your plug-in got different numbers. That is a logical thing because the sequential orders numbers plug-in corrects order id numbers to be administrative correct and follow up the others. This is required in some countries or environments.

    So different post id and different order numbers set by the sequential plug-in, are a problem.

    The plugin can not handle if allot orders have different post id vs order numbers and that is why you get a memory error. Your plug-in is based on post id numbers and expects the order numbers to be the same.

    When I set in the database the whole order table to 1 order id with the same post is number the problem is solved.

    The problem stays solved when woocommerce sequential order numbers is disabled. In that case the order numbers and the order id numbers on the license page are always the same and this is what your plug-in expects.

    It is a conflict. So your plug-in does not need to read the order id, but it needs to read the post number id as a foundation, and post the order number next to it as an extra.l as a variable de by woocommerce or seq order numbers.

    Or you should change the plug-in to read the woocommerce order number (can be also set by seq orders) and not the post id that woocommerce creates with orders.

    If any questions you can post them here.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Me

    (@marknl1981)

    Little extra note: disabling sequential order numbers afterwards does not help anymore. You should fix the numbers in the database yourself (the order numbers must match the woocommerce post id numbers) and not use seq order numbers anymore after or need to wait for a fix from the author.

    Hello @marknl1981

    Thank you very much for this, I am looking into this as we speak!

    @marknl1981

    I found the problem and I will be fixing it today. There will be an update this evening which will take care of this one thing. Followed by this fix there will be a major plugin update (version 2.3.0) with tons of new features coming. I just need some more time to test everything and make sure it works.

    Thank you for your patience.

    Thread Starter Me

    (@marknl1981)

    Great news!

    Thread Starter Me

    (@marknl1981)

    Supplied the update and mem problem is fixed. Can you please help me now with the database as promised ? So the store is up again.

    Thread Starter Me

    (@marknl1981)

    Hi you promised to send a script yesterday… never got it.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Your solution for the mem problem’ is closed to new replies.