Recent Activities

Version 1.2.4 08992e

Update readme 2c4823

Deprecate module, drop dependency on removed core Module model

Swissup\Core\Model\Module and its table are gone. Replaced it with a
local dummy that stores and validates nothing, so the license screens
keep working instead of fataling. Activation now points at
bin/magento swissup:channel:enable.

Marked the package abandoned in favour of swissup/module-core.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 15adcd

Move class from core to the consumer code eb76e7

chore(release): 1.2.3

Ships the bcb:fieldRowReady extension point (a9234aa) and its corrected
contract docs (#46), neither of which is in any released tag — 1.2.2
predates both. breeze-ai 1.8.6 subscribes to that event for its
per-field AI button, so on every released BCB the button is dead.

Patch release: comments and an event emit, no API break, and breeze-ai
declares no composer constraint on this package. 18c02c

Merge pull request #48 from breezefront/docs/46-field-row-caveats

docs(property-panel): clarify bcb:fieldRowReady scope and caveats (#46) f12bb4

docs(property-panel): clarify bcb:fieldRowReady scope and caveats (#46)

The header comment read as a blanket claim ("a field row" fires the
event) when only rows built by _renderSingleProp actually emit it. The
editable Label row and grouped props (e.g. spacing) are built inline in
_renderForm and emit nothing, and a prop with type="hidden" or a
contextOnly miss returns before a row exists at all.

Also document that $row is not in the visible panel when the event fires
(_renderForm appends the form last, and a section's rows sit in a still
detached <details>), so subscribers must not read layout; that $row may
already be hidden by an unmatched depends clause; and that renderer is
the shared module for prop.type, to be read and never mutated.

Comments only — no behaviour change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> c77b7c

docs(property-panel): clarify bcb:fieldRowReady scope and caveats (#46)

Code review found the header comment read as a blanket claim ("a field
row" fires the event) when only ordinary ungrouped props built by
_renderSingleProp actually emit it — the label row and grouped props
(e.g. spacing) don't. Also note $row isn't attached to the live panel
yet at fire time (no layout reads), and that renderer is a shared
singleton per prop.type that subscribers must not mutate.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> a68c9f

Emit bcb:fieldRowReady extension point for field rows a9234a

feat(property-panel): emit bcb:fieldRowReady extension point for field rows (#46)

After a field row is built, appended to the form, and bound on change,
property-panel.js now fires 'bcb:fieldRowReady' on $(document) with
{ prop, component, $row, $field, renderer }. A third-party module can
subscribe and append a control to $row without patching this file or
reaching into the DOM, and without touching $field's value collection
or change binding.

Also documents the field-renderer contract (render/getValue) as public
in the file header, since the extension point relies on it.

No new AMD registry and no wrapper around $field — the two walls
described in the issue stay as they are; this only adds the missing
hook point. d841c3

feat(FeaturedProduct): introduce less variables 9d348a

refactor(FeaturedProductRenderer): replace image URL and alt text with pre-rendered HTML 623392

Fixed FAQ items readability on light theme, closes #44 091320

Fixed avoid using self-closing tag with non-void html element 9a3123

Added hide on pages checkbox list prop type ccf9e8

Updated dependent fields logic 278125

feat(accordion): enable product attribute as body source for FAQ items b26684

feat(accordion): add support for per-item icons in FAQ items b7607f

Correct page cleanup when BCB is closed a40061

Merge pull request #38 from breezefront/feat/108-newsletter-and-missing-components

feat(components): inline newsletter layout (#108) 57dafb

fix(components): newsletter heading follows an inherited text colour (#108)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> c56d7d

fix(a11y): real heading elements and decorative icons (#41)

Newsletter rendered its section heading as <div class="...__heading h2">:
invisible to assistive technology and absent from the document outline,
even though it is the heading of a page band. It now emits a real h1-h6
element chosen by a new heading_type prop (default h2), matching what
text_block already does. Same fix for the featured_product name, which
was also a styled div.

Breeze styles the tag and the class off a single selector list -
`h2, .h2 { ... }` in theme-frontend-breeze-blank/web/css/base/
_typography.less - so under a Breeze theme, dropping the class for the
tag is visually neutral. Under a non-Breeze theme .h2 is not styled at
all, so those headings were rendering as plain body text and now pick up
the theme's own h2 size: a fix rather than a regression, but not a no-op.
Either way it changes the markup of existing pages, which is why this is
split out of #38.

text_block borrowed the heading text for its icon alt and wrapped inline
SVG in a plain div, so a screen reader announced the heading twice, or
three times when the SVG carried its own <title>. The icon is decorative
in every design that uses it: alt="" on the image branch, aria-hidden on
the SVG wrapper. A case that needs a real name should get an explicit
icon_alt prop rather than reusing the heading.

The admin H1 guard only fired on banner's headline_type, so raising a
text_block - and now a newsletter - to H1 skipped the warning. It now
watches heading_type too; _countH1 already counted both.

Also corrects the selector these three comments cite: the rule is
`h1, .h1` in the Breeze theme, not `:where(h1), .h1` in the module.

product_grid was checked and already emits a real h2. Accordion item
titles remain divs wrapping an <a> trigger; the heading+button pattern
there is a larger change and stays open.

Refs #41 53edaa

fix(components): collage layout for flat-colour CTA, decorative icon a11y (#108)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 6e2743

feat(components): inline newsletter layout (#108)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 85ed20

Changes for header/footer page: publish spinner, layout picker with images 25b2ae

Version 1.2.2 214d13

Fixed ignored text color when heading used in content c92d33

Version 1.6.10 5b55b3

Merge pull request #110 from swissup/fix/issue-109-aggregation-bucket-size

fix(category filter): request all term buckets from the search engine (#109) 0c2c7c

fix(category filter): resize only the category aggregation (#109)

Lifting the bucket limit for every faceted field at once lets the buckets
of all the high cardinality attributes add up beyond the cluster's
search.max_buckets - 10000 on Elasticsearch 7.0-7.10 - and the engine
answers that with too_many_buckets_exception, so the whole listing errors
out instead of one facet losing its tail.

Resize the fields named in the new fieldNames argument, which holds just
category_ids by default. An empty list restores the previous behavior of
resizing every term aggregation.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 8a902c

test: use the DataProvider attribute, not the annotation (#109)

PHPUnit 12 no longer reads data providers from annotations, which is what
the rest of Test/Unit was migrated away from in #107.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 552c4e

fix(category filter): request all term buckets from the search engine (#109)

Magento hardcodes the Elasticsearch/OpenSearch terms aggregation size to
500, so the engine returns only the 500 most popular values of a faceted
field and silently drops the rest. On a catalog whose result set spans
more categories than that, the category filter loses the child categories
with the lowest product counts, while the header menu keeps showing them.

The existing fallback to Category::getProductCount() cannot cover for it:
addCountToCategories() runs against a search collection whose SQL select
only carries the ids of the current page, so the count comes back as 0 and
the option is skipped altogether.

Raise the term bucket size with a plugin on the aggregation query builder.
The size is a DI argument, so it can be tuned per project.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 233e61

Version 1.6.9 47aee3

Version 1.36.0 c893e0

Version 1.9.0 910446

Version 1.9.0 1ed62b

Fixed missing background on Classic header layout on Eir theme aad26a

Fixed preview issue after previous commit ea8cea

Updating page selector links when store view switched 0d3d12

Added page visibility control and installer support for header/footer content 796f48

Fixed not working theme editor colors for overlay header 2660ce

Do not show overlay header toggles for native layout b000f5

WIP. Header layouts: added overlay mode support 8122c9

Correct page cleanup when BLB is closed 45b825

Improved header/footer preview 07c294

Header/Footer management with Header Layouts 7a0a82

Version 1.2.0 24fff8

Added Contact Us page support d64e46

Config option for upcoming TaxVAT switcher in theme header 7f31bd

Fixed wrong color id in theme editor settings 402ff7

Added width 100% for the contact form 4a1acf

Replaced PB footer top content with BCB version f1006d

Removed unused overlay header config bf9be6

Added Overlay Header settings to Theme Editor c859d3

Fixed layout shift when js is placed between price and swatches 7c4cc4

Move price styles to enterprise-blank 54a350

Version 3.3.3 cf6e70

Up requirements 5539c0

Version 1.1.1 36b6cd

feat: integrate easybanner b0c2ab

fix: hide slider pagination by default 53cede

fix: configure ProLabels selectors 266541

feat: improve recently viewed layouts 246589

feat: use responsive images with srcset in product list item and gallery 63f861

feat: make breadcrumbs horizontally scrollable ab4c14

style: Improve footer links #12 f97617

fix: improve accessibility & mobile logos #9 6a8485

Version 1.1.0 adaf76

Improve spacing for text and headings #7 4d669d

fix: accessibility improve #54 793c44

Improve spacing for text and headings #7 3f5bc1

style: adjust EasyTabs layout and borders for expanded state e5db6c

style: implement container-based layout for more flexible product sliders cde87a

feat: implement brands block a37b3b

feat: implement contact map CMS block 5221b0

style: home page 933872

style: implement advanced product card hover effect and fix slider shadow clipping ca693c

style: use div wrappers instead of li for product carousel f17016

fix: correct mobile menu 18eb40

Version 1.0.4 b799fb

fix: fix exit intent trigger compatibility with Firefox ec09ae