Please fix this bug!

[StrangeTech]

Hi @Louis,

I wasn’t sure whether you are just referring to UI related bugs or all Cwicly bugs, so I’ve made 2 lists.

Cwicly UI Bugs:

1. display: grid added unnecessarily to lg breakpoint

Display: grid is automatically added to Query Template block class for lg breakpoint when using mobile first breakpoints

Description: Display grid appears to be added to the block class by default on the lg breakpoint. I assume this was an optimisation put in place to enable proper grid display by default. I am typing this from memory as we encountered this a few times when adding a new Query block with a Query Template. We haven’t created a minimal test case and haven’t attempted to repeat this since 1.4.1 was released, so there is a chance it may already have been fixed. With mobile-first breakpoints when ma…

2. Inherited values not displayed in relative styles

Base breakpoint value not showing in other breakpoints in relative style

Description: Usually the base breakpoint value gets shown in gray: [grafik] [grafik] But in a relative style it isn’t. The value is empty: [grafik] [grafik] Environment info WordPress version: 6.4.3 Cwicly Plugin version: 1.4.0.3

3. Clicking on quick code rules not revealing styles in inspector

@Marius

Clicking the CSS property in the code editor doesn’t send me to the corresponding GUI area anymore

Functional bugs:

1. Blocks expanding unnecessarily

InnerBlocks selection and display issues

@Louis, This is also still happening.

2. Mini cart not syncing:

Mini Cart does not sync when WooCommerce AJAX buttons are used to add and remove products

Description: We have added a mini cart using the Cwicly tutorial video. The only minor difference is we are displaying it in a Nav Dropdown rather than a Modal. When we add or remove products using WooCommerce’s AJAX buttons (outside of the mini cart) the cart items and count do not update asynchronously, only on refresh of the page. The reason I am adding this as a bug rather than a feature request is because in some places in the documentation it is implied that this should work. Step-by-s…

3. Filter defaults not working:

Query Order By with Meta Key is not using fallback by default with frontend rendering

Description: When using filters to sort a query, we are specifying fallback’s for the default behaviour when no filter has been selected. These are not applying and the default sort is being used. Step-by-step reproduction instructions: Open the Post Editor/Site Editor Create a Posts Query Add filters including a field for the meta key (e.g. “orderby”) and a field for the sort direction (e.g. “direction”) Specify the fallback’s for each of these Note they are not applied by default when no …

Filter block → include + default

hello, Heroes, i want to report a issue about filter block which i met today, i have three filter block [20231223151119] filter type is select with taxonomy options and a “default” placeholder [111] filter: user input form search text [20231223151532] filter: reset button when i click reset button, the query list are working very well. the only small issue is : the select options can not get back to “default”.

To give credit where it is due, so many bugs have been fixed recently, the actual list remaining is relatively small already!