Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter emrl

    (@emrl)

    @lovingbro We have Bugsnag installed, and it is reporting the error. It happens for any Store API endpoint, not just the one above.

    POST /wp-json/wc/store/v1/cart/add-item
    POST /wp-json/wc/store/v1/checkout
    DELETE /wp-json/wc/store/v1/cart/items

    Here is the full stack trace:

    Error · Call to undefined method Automattic\WooCommerce\StoreApi\SessionHandler::get_session_data()
    /wp-content/plugins/woocommerce/includes/class-wc-cart-session.php:689 WC_Cart_Session::remove_shipping_for_package_from_session

    private function remove_shipping_for_package_from_session() {
    $wc_session = WC()->session;

    foreach ( array_keys( $wc_session->get_session_data() ) as $key ) {
    if ( 0 === strpos( $key, 'shipping_for_package_' ) ) {
    $wc_session->set( $key, null );
    }

    /wp-content/plugins/woocommerce/includes/class-wc-cart-session.php:426 WC_Cart_Session::set_session
    /wp-content/plugins/woocommerce/includes/class-wc-cart.php:1459 WC_Cart::calculate_totals
    /wp-content/plugins/woocommerce/includes/class-wc-cart-session.php:290 WC_Cart_Session::get_cart_from_session
    /wp-content/plugins/woocommerce/includes/class-wc-cart.php:627 WC_Cart::get_cart
    /wp-content/plugins/woocommerce/src/StoreApi/Utilities/CartController.php:39 Automattic\WooCommerce\StoreApi\Utilities\CartController::load_cart
    /wp-content/plugins/woocommerce/src/StoreApi/Routes/V1/AbstractCartRoute.php:180 Automattic\WooCommerce\StoreApi\Routes\V1\AbstractCartRoute::load_cart_session
    /wp-content/plugins/woocommerce/src/StoreApi/Routes/V1/Checkout.php:147 Automattic\WooCommerce\StoreApi\Routes\V1\Checkout::get_response
    /wp-includes/rest-api/class-wp-rest-server.php:1292 WP_REST_Server::respond_to_request
    /wp-includes/rest-api/class-wp-rest-server.php:1125 WP_REST_Server::dispatch
    /wp-includes/rest-api/class-wp-rest-server.php:439 WP_REST_Server::serve_request
    /wp-includes/rest-api.php:459 rest_api_loaded
    /wp-includes/class-wp-hook.php:324 WP_Hook::apply_filters
    /wp-includes/class-wp-hook.php:348 WP_Hook::do_action
    /wp-includes/plugin.php:565 do_action_ref_array
    /wp-includes/class-wp.php:418 WP::parse_request
    /wp-includes/class-wp.php:818 WP::main
    /wp-includes/functions.php:1342 wp
    /wp-blog-header.php:16 require
    /index.php:4 [main]

    This error was not happening in 10.2.2, only 10.3.0

    Thread Starter emrl

    (@emrl)

    @maartenbelmans thank you, that was very quick. This does help with our current use case, but having $field->id as part of the filter name is very limiting, as you would need to write code to apply this to every single field since the ID is unique. So if you have 10 extra fields, you’d need to have 10 filters. So it becomes difficult to add classes for all types of inputs, or only text inputs, etc. Thus why I mentioned leaving out the $field->id in the filter name, and just passing the entire $field object as the second parameter to the filter, so then you can do anything conditionally in the callback based on the all properties of $field.

    Thank you.

    Thread Starter emrl

    (@emrl)

    Also noticed that the PHP keyword/type mixed is used in the code, and this is only available in PHP 8.0 and later, but the plugin states it is compatible with 7.4.

    The “96” is visible in some email clients it seems, as it is part of the RSVP email HTML for “PixelsPerInch” setting:

    <noscript>
    <xml>
    <o:OfficeDocumentSettings>
    <o:PixelsPerInch>96</o:PixelsPerInch>
    </o:OfficeDocumentSettings>
    </xml>
    </noscript>

    This may be part of a compatibility issue with the https://ww.wp.xz.cn/plugins/email-templates/ plugin, as it wraps the Ticket/RSVP email within it’s template, so there are multiple DOCTYPE and body elements in the email which seems to cause rendering issues in some email clients.

    • This reply was modified 1 year, 2 months ago by emrl.
    Thread Starter emrl

    (@emrl)

    @iconithemes thank you, but I’m suggesting that this filter be in core so that a theme developer can hook into any submenu, even if a plugin does not provide one.

    We are also noticing that we cannot print in Chrome. The print preview pops up and then immediately closes, or says “Print preview failed”. Version 3.0.3

    Same issue here. All of our site’s calendars broken after the update.

    We do have WordPress in a subfolder, and I noticed that all the asset paths were trying to load site.com/wordpress/wp-content/plugins... instead of what they did before, and the correct path: site.com/wp-content/plugins

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