Forum Replies Created

Viewing 15 replies - 1 through 15 (of 123 total)
  • Thread Starter DensitySK

    (@densitysk)

    Thank you for clarification. I will check it and get back if anything happens.

    Thread Starter DensitySK

    (@densitysk)

    Where do you see any kind of entry about FLATSOME theme?? I am not and never was using FLATSOME in any of my shops. I am using Shopkeeper theme.

    I have also already checked the theme editor and there is no mention of wc_get_related_products in any of files in function.php or woocommerce folders and subfolders.

    • This reply was modified 10 months, 1 week ago by DensitySK.
    Thread Starter DensitySK

    (@densitysk)

    Hi,

    thank you for checking. Here is the system report

    https://pastebin.com/4XmyrPR1

    Thread Starter DensitySK

    (@densitysk)

    ďakujem za testovaciu verziu. Pozriem si to bližšie.

    Možno k tej fatal error chybe a prečo VAT aj po validácii je nakoniec zákazníkovi vyúčtované môžeme spraviť tak, že Vám nejako pošlem dočasné prístupové údaje na staging stránku, kde som to testoval a budete si to vedieť sami pozrieť. Možno to je aj nejakým konfliktom s iným pluginom, čo používam. Sám to ale neviem ešte vylúčiť. Máte nejaký kontakt, kde by sme si mohli vymeniť prístupové údaje?

    Thread Starter DensitySK

    (@densitysk)

    Zdravím,

    to by bolo super. Hlavne by som chcel vyriešiť, prečo najskôr VAT je odstránené v košíku a následne po potvrdení objednávky zákazníkom mu je stiahnutá plná sume s DPH a dostane aj normálne potvrdenie ako bežný spotrebiteľ. TO je pre mňa najzávažnejší problém. Ponechanie VAT pri dodaní do inej krajiny ako je registrácia IČ DPH by bolo tiež dobré vyriešiť.

    Chápem, že s tým MS_MAX_CONCURRENT_REQ to súvisí skôr s API VIESu. Ja som možno len behom cca 10 minút vytváral cca 10-20 manuálnych objednávok s rôznymi údajmi s VAT a bez VAT a vtedy to možno vyhodnotilo ako veľa requestov na to isté VAT ID.

    Možno ale jedno vylepšenie by som navrhoval, aby Váš VAT plugin mal nejakú DEBUG funkciu aby sa dali lepšie odsledovať chyby, validácie, odpovede z VIES na validáciu a podobne. Lebo aktuálne len Woocommerce zaeviduje fatal error (čo je bežné) ale inak človek nevidí moc do pozadia pluginu, ak sa snaží vyriešiť nejaký problém.

    s pozdravom

    Michal

    Thread Starter DensitySK

    (@densitysk)

    sorry, but is this supposed to be any kind of solution? I do not have a problem to get into backend – see screenshot above which shows that I can get into backend. Just the email functions do not work as they should.

    I would like to be able to preview emails, send test emails or make changes in the backend without critical errors that were caused by the recent woocommerce update.

    Please provide a fix.

    Thread Starter DensitySK

    (@densitysk)

    Here you go

    [27-Feb-2025 15:57:42 UTC] PHP Fatal error:  Uncaught Error: Call to a member function get_tax_status() on false in /xxx/wp-content/plugins/product-bundles-variation-bundles/product-bundles-variation-bundles.php:645
    Stack trace:
    #0 /xxx/wp-includes/class-wp-hook.php(324): WC_PB_Variable_Bundles::variation_get_tax_class('', Object(WC_Product_Variation))
    #1 /xxx/wp-includes/plugin.php(205): WP_Hook->apply_filters('', Array)
    #2 /xxx/wp-content/plugins/woocommerce/includes/class-wc-product-variation.php(309): apply_filters('woocommerce_pro...', '', Object(WC_Product_Variation))
    #3 /xxx/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-order.php(1581): WC_Product_Variation->get_tax_class()
    #4 /xxx/wp-content/plugins/woocommerce/src/Internal/Admin/EmailPreview/EmailPreview.php(309): WC_Abstract_Order->add_product(Object(WC_Product_Variation))
    #5 /xxx/wp-content/plugins/woocommerce/src/Internal/Admin/EmailPreview/EmailPreview.php(162): Automattic\WooCommerce\Internal\Admin\EmailPreview\EmailPreview->get_dummy_order()
    #6 /xxx/wp-content/plugins/woocommerce/src/Internal/Admin/EmailPreview/EmailPreviewRestController.php(242): Automattic\WooCommerce\Internal\Admin\EmailPreview\EmailPreview->set_email_type('WC_Email_Custom...')
    #7 /xxx/wp-content/plugins/woocommerce/src/Internal/Admin/EmailPreview/EmailPreviewRestController.php(144): Automattic\WooCommerce\Internal\Admin\EmailPreview\EmailPreviewRestController->validate_email_type('WC_Email_Custom...')
    #8 /xxx/wp-includes/rest-api/class-wp-rest-request.php(913): Automattic\WooCommerce\Internal\Admin\EmailPreview\EmailPreviewRestController->{closure:Automattic\WooCommerce\Internal\Admin\EmailPreview\EmailPreviewRestController::get_args_for_preview_subject():144}('WC_Email_Custom...', Object(WP_REST_Request), 'type')
    #9 /xxx/wp-includes/rest-api/class-wp-rest-server.php(1114): WP_REST_Request->has_valid_params()
    #10 /xxx/wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch(Object(WP_REST_Request))
    #11 /xxx/wp-includes/rest-api.php(449): WP_REST_Server->serve_request('/wc-admin-email...')
    #12 /xxx/wp-includes/class-wp-hook.php(324): rest_api_loaded(Object(WP))
    #13 /xxx/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
    #14 /xxx/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
    #15 /xxx/web/wp-includes/class-wp.php(418): do_action_ref_array('parse_request', Array)
    #16 /xxx/wp-includes/class-wp.php(813): WP->parse_request('')
    #17 /xxx/wp-includes/functions.php(1336): WP->main('')
    #18 /xxx/wp-blog-header.php(16): wp()
    #19 /xxx/index.php(17): require('/data/f/c/fc2fe...')
    #20 {main}
    thrown in /xxx/wp-content/plugins/product-bundles-variation-bundles/product-bundles-variation-bundles.php on line 645
    Thread Starter DensitySK

    (@densitysk)

    Hi,

    thank you for clarification. I will wait then if this gets added

    Thread Starter DensitySK

    (@densitysk)

    I really start to think that someone is not trying to read the full message

    This has NOTHING to do with the theme and the errors from the DEBUG log are completely unrelated to the issue I have. And by the way after some recent updates even these errors have dissapeared.

    If favicon setting and 404 errors would be happening only when the theme is active, then it is a theme issue.

    But if favicon upload and 404 errors are happenling literally on every theme I install, then it is not a theme issue and all the theme developers have confirmed, that they do not alter favicon settings and are using the wordpress core functions to create appropriate thumbnails.

    As I have stated several times above, this issue persist even when I set a different theme – WORDPRESS is creating a duplicate file for the site icon even though the site icon is in correct PNG, ICO or JPG format and in the correct resolution of 512x512px NO MATTER THE THEME that is currently active.

    The issue is happening on other staging sites that I have where ALL plugins are deactivated and only the default WORDPRESS WOOCOMMERCE STOREFRONT theme is active. So this is clearly a WORDPRESS issue

    Thread Starter DensitySK

    (@densitysk)

    kind reminder

    Thread Starter DensitySK

    (@densitysk)

    thank you. I have installed the RC version and so far it does not show errors.

    Thread Starter DensitySK

    (@densitysk)

    In the meantime I had to deactivate hcaptcha because the fatal errors were getting very frequent

    Thread Starter DensitySK

    (@densitysk)

    HI,

    Here is the screenshot of the SDK version

    https://ibb.co/WDN3rs0

    Thread Starter DensitySK

    (@densitysk)

    HI,

    after further checking it is most likely, that the Post SMTP plugin is creating this issue as it was pointed out by the Query Monitor.

    With theme developer we have deactivated your plugin and all errors disappeared. We have tried to install other SMTP plugins to test an none of the errors showed up.

    Thread Starter DensitySK

    (@densitysk)

    HI,

    thank you for checking. I know that these are just warnings, however sometimes I also see fatal errors caused by stripe in the woocommerce status page in the logs section. This happens usually when non-EU customers try to pay during checkout.

    I have unfortunately purged all caches and old logs, so when it appears again (I assume very shortly) I will send you the copy of the fatal error as well.

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