Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter sinusiks

    (@sinusiks)

    I understand that it is difficult to detect a bug if there is no rule for when it happens and we also do not know how to reproduce the error every time.

    as far as we have observed, two lines are inserted in the [prefix]woocommerce_order_items table as “line_item” for normal (correct) orders, but only one for a problematic order. It is interesting that if I go by order_item_id to look at the data for this bundle in the [prefix]woocommerce_order_itemmeta table:

    • for the correct order, this bundle meta data has _woosb_ids = 74392/665572d4f0821/4
    • for the incorrectly entered order, the meta data is _woosb_ids = 74392/4

    where 74392 is the ID of the bundled product, 4 is the quantity but when the order is inserted correctly it also includes 665572d4f0821

    as I browse the code, I see that woosb_ids are generated when adding to the cart, so I suspect that this happens already when adding to the cart – the store does not add all products from the bundle to the customer’s cart, but only the basic bundle

    Thread Starter sinusiks

    (@sinusiks)

    Great solution, thank you! This fixed CSS / JS from loading from another domain. After we changed the domains configuration (they are now configured as alias instead of child domains in cyberpanel) it also fixed our problems of cache not clearing up so it seems all problems are resolved.

    Thread Starter sinusiks

    (@sinusiks)

    No it’s not a cpanel, it is openlitespeed server on cyberpanel on Ubuntu VPS. One domain is “primary” while others are added as add-on domains (child domains). But your question prompted me to check the configuration a bit more so I tried to define other domains as alias domains instead of child domains. That way there is only one vhost that has multiple domains defined in listener mappings.
    I will monitor if this helps as now I also see that the cache is only being built for the primary domain in /usr/local/lsws/cachedata – before it was separated for all 3 domains (separate subfolders)

    This still doesn’t fix the issue that combined JS/CSS files are still served from primary domain but I guess it may fix cache clearing problems.

Viewing 3 replies - 1 through 3 (of 3 total)