Search Results for 'block'

Hello,
we are aware of what you are mentioning but the issue remains the cart css is still incomplete as visible here: https://prnt.sc/rt54n8Jn5mfR (add remove buttons are definatelly missing css) so we would like to fix the issues.
Before applying the hotfix i mentioned i check your demos, from what i noticed they are all old and none of them (unless mistaken) has block layout … so none of these css are working.
So:
1) can one of you check the reason why this happened on our website or not?
2) please provide a wordpress demo that used block in the checkout so we can check what css files are used in specific.

Kind regards,
Alexandros S.

Hello, update:
after a lot of search and AI tools assistance we used the following funcntions that loads 2 css files that were not loading before (checkout.css,checkout-rtl.css).
We noticed that there are still some minor css issues but at least page is functional.

So please allow me to ask once more. What are the files that should load in checkout/cart with blocks and if you know what can be the issue that they dont load in our case. We dont consider the issue fixed until the cause is located and extra code is removed.

Kind regards,
Alexandros S.
Please do notify a.sklepas@webpoint.gr
thank you.

/**
* Load ONLY WooCommerce Blocks Checkout CSS on Cart / Checkout / Order Received.
* Files:
* – /wp-content/plugins/woocommerce/assets/client/blocks/checkout.css
* – /wp-content/plugins/woocommerce/assets/client/blocks/checkout-rtl.css
*/
add_action(‘wp_enqueue_scripts’, function () {

if ( is_admin() ) {
return;
}

$is_order_received = function_exists(‘is_order_received_page’)
? is_order_received_page()
: ( function_exists(‘is_wc_endpoint_url’) && is_wc_endpoint_url(‘order-received’) );

if ( ! ( is_cart() || is_checkout() || $is_order_received ) ) {
return;
}

$dir = WP_PLUGIN_DIR . ‘/woocommerce/assets/client/blocks/’;
$url = plugins_url(‘woocommerce/assets/client/blocks/’);

// LTR checkout CSS
$ltr = $dir . ‘checkout.css’;
if ( file_exists( $ltr ) ) {
wp_enqueue_style(
‘kynigesia-wc-blocks-checkout’,
$url . ‘checkout.css’,
array(),
filemtime( $ltr )
);
}

// RTL checkout CSS (only if site language is RTL)
$rtl = $dir . ‘checkout-rtl.css’;
if ( is_rtl() && file_exists( $rtl ) ) {
wp_enqueue_style(
‘kynigesia-wc-blocks-checkout-rtl’,
$url . ‘checkout-rtl.css’,
array( ‘kynigesia-wc-blocks-checkout’ ),
filemtime( $rtl )
);
}

}, 100);

NEWSPAPER – VERSION: 12.7.5
new: External image support for Image info box;
new: Load more option(ajax) to Categories/tags list shortcode;
new: Custom no post message on all Flex blocks;
new: Popular taxonomy option to Popular category shortcode;
new: Category siblings option to hide all the categories when no siblings;

You rock, team. Such a welcome addition, already implemented and working great.

Have a lovely weekend!

• This reply was modified 5 months by c386.
• This reply was modified 5 months by c386.

Can you also please provide the file that loads the css for wc-block-checkout /cart so we can check its loaded properlly?

kind regards.

Hello,
this statement is wrong ->It appears that this situation appears only when the cart is empty and you have something in it the layout is better – https://prnt.sc/4KLP06kqVlos

about:
o what the problem could be is something related to the cache settings, please clear all cache, object cache, purge CDN, and also check when you are logged in if the situation is the same. -> already did that and disabled caching plugin, cdn confirmed disabled (it was already)

In case the situation persists, and this is a WooCommerce bug, I will recommend getting the previous plugin version from here – https://wordpress.org/plugins/woocommerce/advanced/ https://prnt.sc/hRD8Lt4wzp-l and update the plugin only after this is fixed by WooCommerce developers. -> i did enable and tested up to woocommerce.10.4.3.zip and your theme downgraded to 12.7.2.

neither of these actions solved the issue. i noticed that during the update/downgrade when tagdiv is disabled checkout shows ok as woocomerce default as a block.

i also tried to revert to old shortcode (in this way i saw the page looking good) but our payment provider only supports blocks so i changed back to blocks…

Please for your assistance.
I can send credentials for checking…

We have installed
Advanced Editor Tools – Extends and enhances the block editor (Gutenberg) and the classic editor (TinyMCE).
and
Disable Gutenberg Disables Gutenberg Block Editor and restores the Classic Editor and original Edit Post screen. Provides options to enable on specific post types, user roles, and more.

Hi,

Quick update after upgrading Newspaper to v12.7.5.

The issue still reproduces with the Accessibility module enabled (Template Settings → Accessibility (Keyboard + Skip link + Search dialog)), but the behaviour has slightly changed due to the update.

Before 12.7.5, the focus/ARIA conflict typically involved #maincontent. After 12.7.5 (changelog mentions “Accessibility, improved main content wrapper selector”), the browser warning now consistently shows the ancestor being hidden/inert is #td-outer-wrap:

“Blocked aria-hidden on an element because its descendant retained focus…”
Focused element: #td-header-search-button / #td-header-search-button-mob
Ancestor with aria-hidden/inert: div#td-outer-wrap

So the underlying problem remains the same (ARIA hidden/inert applied to a container that still contains the focused search trigger/input), but the update appears to have changed which wrapper is targeted by the Accessibility logic.

We currently mitigate this with a temporary hotfix on our side that prevents aria-hidden/inert from being applied to the wrapper being targeted. After the update, that mitigation had to be adjusted from #maincontent to also cover #td-outer-wrap, which matches the new runtime behaviour.

In short: 12.7.5 changed the target wrapper, but the focus/aria-hidden timing conflict is still present.
Thank you.
Regards.

That’s useful, Calin – didn’t know that Post Settings could be moved. But my width problem is solved, thanks to your plugins suggestion. I had installed Fluent Forms Block – now deleted and all is good!

yeah i tried by deactivating the litespeed plugin. after that everything was working fine. thanks

One more question. can we reduce this space? – https://prnt.sc/0Jj-_E2ioNqI
using flex block 1