Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter sectorx

    (@sectorx)

    Skvele, dakujem velmi pekne, funguje to presne ako som chcel. Bola to super rychlost, klobuk dole 🙂
    Este mozno jedna poznamka. Ten pridany stvrty parameter ste nazvali $item, ale asi je to trocha matuce. Osobne by som to radsej nazval $order_item aby sa to neplietlo a bolo na prvy pohlad zrejme o co ide. Prvy parameter je $item_data, stvrty $item. Chcelo by to lepsie odlisit.

    Thread Starter sectorx

    (@sectorx)

    Zdravim, mal som tam 1.50.0
    Uz to funguje, dakujem velmi pekne.

    Thread Starter sectorx

    (@sectorx)

    Dakujem, skusam to na sandboxe ale z nejakeho dovodu mi to nefunguje. Zistil som ze ta action sa mi nespusta vobec:

    function my_sf_after_invoice_create( $response, $order, $type )
    {
    error_log( 'SF HOOK TRIGGERED' );

    error_log( print_r( $response, true ) );
    }
    add_action( 'sf_after_invoice_create', 'my_sf_after_invoice_create', 10, 3 );

    Debug.log mam prazdny. Debugging mam zapnuty.

    Fakturu mi objednavka normlane vytvori. Kde moze byt problem?

    Thread Starter sectorx

    (@sectorx)

    I originally reported problem that no payment methods were displayed at checkout. This was caused by WC PayPal Payments plugin settings in Style tab. I did not have any payment option enabled for Classic checkout. It is in my opinion a bit stupid name/place of the setting. I supposed it’s some design feature only and I turned everything off. But despite this setting PayPal payment methods (paypal and credit card) were displayed on non-subscription products anyway. When I turned it on then I experienced problem described in previous reply.

    Thread Starter sectorx

    (@sectorx)

    Hi,

    my PayPal account was checked by PayPal support. I have reference transactions enabled and also for my app I have Vaulting and Subscriptions options enabled. No problem here. I’m using classic checkout.

    I tried other free subscription plugins and whey show both paypal (ppcp-gateway) and credit card (ppcp-credit-card-gateway) payment methods.

    I looked at this more closely and found that your plugin is filtering out credit card payment method.

    Problem is in “includes\gateways\woocommerce-paypal-payments\module\src\class-ywsbs-wc-paypal-disabled-sources.php” in function “disabled_sources()”.

    This function is disabling payment gateways other than “paypal” when no YITH subscription exists in the system. And this is the case after you do clean install. When I modify this function to always return false, credit card is present on checkout of subscription product.

    How to replicate this problem:

    • deploy new WP installation
    • install WC, switch to classic cart and classic checkout
    • install WC PayPal Payments plugin and activate sandbox, in Settings -> Style allow payment option for Classic checkout page
    • install yith woocommerce subscription plugin
    • create subscription product and go to checkout page – you will see only PayPal option, no credit card
    sectorx

    (@sectorx)

    I have same issue. When I add subscription product to cart on checkout page I see no payment methods. When I press “SIGNUP NOW” I get error message “There was an error processing your order. Please check for any charges in your payment method and review your order history before placing the order again.”

    I’m using WooCommerce PayPal Payments plugin. On non-subscription products payment methods are normally displayed.

    This issue is marked as resolved but there is not comment how to fix this.

    Thread Starter sectorx

    (@sectorx)

    Hello,

    thank you very much for help. I tried plugin version you posted but it did not help.

    I was however tried to solve it this way: I reverted back to original plugin and went through connect wizard. After it ended again in “Complete Your Payment Setup” screen I configured API credentials manually. This way I was able to get it working.

    Have a nice day and thanks again for quick responses.

    Thread Starter sectorx

    (@sectorx)

    Hello,

    thanks for quick reply.

    When I try to connect paypal account, I press “Connect to Paypal” button, successfully login to paypal account, I get “You’re all set!” screen. But then when I return to woocommerce setup is not finished and I get again “Complete Your Payment Setup” screen.

    I notice http api call errors in PLUGIN, not in paypal dashboard. Detail below. I suspect this is causing setup not to finish properly

    Plugin: woocommerce-paypal-payments
    POST
    https://api.woocommerce.com/integrations/ppc/v1/billing-agreements/agreement-tokens
    404 Not Found

    DNS Resolution Time: 0.0011
    Connection Time: 0.1159
    Transfer Start Time (TTFB): 0.4236
    Response Content Type: application/json; charset=utf-8
    IP Address: 192.0.96.246
    
    WooCommerce\P\A\E\BillingAgreementsEndpoint->request()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-api-client/src/Endpoint/RequestTrait.php:40
    WooCommerce\P\A\E\BillingAgreementsEndpoint->create_token()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-api-client/src/Endpoint/BillingAgreementsEndpoint.php:70
    WooCommerce\P\A\E\BillingAgreementsEndpoint->reference_transaction_enabled()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-api-client/src/Endpoint/BillingAgreementsEndpoint.php:94
    WooCommerce\P\W\WCGatewayModule::WooCommerce\P\W\{closure}()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php:319
    WooCommerce\P\V\I\M\C\ReadOnlyContainer->get()
    wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php:58
    WooCommerce\P\W\WCGatewayModule::WooCommerce\P\W\{closure}()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php:394
    WooCommerce\P\V\I\M\C\ReadOnlyContainer->get()
    wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php:58
    WooCommerce\P\W\WCGatewayModule::WooCommerce\P\W\{closure}()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php:232
    WooCommerce\P\V\I\M\C\ReadOnlyContainer->get()
    wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php:58
    WooCommerce\P\W\WCGatewayModule::WooCommerce\P\W\{closure}()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/services.php:88
    WooCommerce\P\V\I\M\C\ReadOnlyContainer->get()
    wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php:58
    WooCommerce\P\B\BlocksModule::WooCommerce\P\B\{closure}()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-blocks/services.php:26
    WooCommerce\P\V\I\M\C\ReadOnlyContainer->get()
    wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php:58
    WooCommerce\P\B\BlocksModule->WooCommerce\P\B\{closure}()
    wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-blocks/src/BlocksModule.php:53
    do_action('woocommerce_blocks_payment_method_type_registration')
    wp-includes/plugin.php:517
    Automattic\W\B\I\IntegrationRegistry->initialize()
    wp-content/plugins/woocommerce/src/Blocks/Integrations/IntegrationRegistry.php:50
    do_action('init')
    wp-includes/plugin.php:517
    Thread Starter sectorx

    (@sectorx)

    Hello,

    thank you very much for quick fix! It is working OK now.

    Thread Starter sectorx

    (@sectorx)

    Dobry den,

    chcel by som vas teda poprosit do buducna pridat do API tuto moznost. Je to prakticka funkcionalita a malo by ju vase API poskytovat, aby ju tretie strany mohli vyuzit vo svojich custom backendoch a nemuseli si to programovat. Navyse to uz aj mate urobene vo vasom superfaktura backende ako som pisal vyssie. Verim ze pridat to do API nebude az taky problem.

    Vdaka

    Thread Starter sectorx

    (@sectorx)

    Dobry den,

    skvele, dakujem velmi pekne, konecne to uz nebude otravovat 🙂

    Dobry den,

    tie meta sa skladaju velmi rozne, niektore s cenou, niektore bez, poradie ako kedy. Riesit to cez nejake sialene regularne vyrazy, to nie je cesta.

    Prosim dorobte filter na ten separator meta fieldov ako sa sklada ten retazec predtym ako to ide do superFA. Zide sa to ucite nielen nam. Lepsie ako si pracne programovat to skladanie. Predstavujeme si to nejako takto:

    function my_meta_separator($separator)
    {
       $separator = "\n";
       return $separator;
    }
    add_filter('sf_order_item_meta_separator', 'my_meta_separator', 10, 3);
    • This reply was modified 2 years, 10 months ago by sectorx.
    • This reply was modified 2 years, 10 months ago by sectorx.
    Thread Starter sectorx

    (@sectorx)

    Dobry den,

    videl som to v superFA zdrojovom kode ze to vola payment_complete() a zvysok robi woocommerce.

    Po dlhsom skumani a debugovani som prisiel na to, ze ta funkcia je napisana spravne, ale problem je v priorite. Ked som tam mal 10 alebo nizsiu, tak to nefungovalo spravne. Ked som tam dal 99 tak to zacalo fungovat bez problemov. Prepisoval to zrejme nejaky iny filter.

    Kazdopadne dakujem za reply.

    Thread Starter sectorx

    (@sectorx)

    Vdaka za rychlu odpoved. Skusil som to ale toto nie je to co potrebujem.

    Ten filter umoznuje uplne modifikovat description ale toto nie je ziaduce.

    Vypisal som si tu $item_data a vyzera to tam takto nejako:

    Array
    (
    [name] => Test produkt
    [quantity] => 1
    [sku] =>
    [unit] => ks
    [unit_price] => 49
    [tax] => 0
    [description] => moj_custom_datum: 1.1.2000, themehigh_custom_preferred_language: 2, themehigh_custom_darcekovy_obal: 1
    Popis produktu
    )

    K produktu user zadava pri nakupe datum, takze nejde len o to zmenit nejako ten popis na nieco ine staticke. Keby som tam mal len 1 custom field tak by sa to nejako dalo vyparsovat. Chcelo by to ale nejake systematickejsie riesenie.

    Navyse tam mam este pouzity plugin na custom product options
    https://www.themehigh.com/product/woocommerce-extra-product-options/ a ten tam pridava tiez nejake custom order item meta tymto sposobom a vo FA sa zobrazuju ako metakey nefiltrovane, rovnako ako ten ‘moj_custom_datum’.

    Idealne by bolo ako sa kreuje ta [description] urobit, aby to slo este cez ten filter woocommerce_order_item_display_meta_key a nahradzalo to tie metakey filtrovanymi hodnotami.

    Ten plugin od Themehigh pozeram ma filter na tie metakey/values takto nastaveny:
    add_filter( ‘woocommerce_order_item_get_formatted_meta_data’, array($this, ‘filter_order_item_get_formatted_meta_data’), 10, 2);

    Myslite ze by sa to dalo nejako urobit aby superFA brala do uvahy tieto filtre?

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