Recent Activities

This page shows what are we working on.

breezefront / theme-frontend-breeze-enterprise-eir

10 hours ago success
  • head
    • Product page. Related products block. 7ed6de

    • Product page. Implement review popup for full review text display and enhance accessibility. d38885

    • Product page. Add toggle for "Write Your Own Review" form and adjust styles for review list 9973d8

    • Product page. Revies list is done. Revie form next. 5bf007

    • Theme Editor: added Listing, Animations, and Advanced sections a4451d

    • Theme Editor: added Colors section 390891

    • Product page. Reviews in progress... e13b99

    • Theme Editor: added Layout, Typography, Overlay Header, Border Radius, Color and Font Palettes ff5e62

    • Productpage. Review in progress... 7059e9

    • Productpage. Review in progress. 669824

    • BCB featured product component. 0651cf

    • Add styles for featured product details, SKU, and price row in BCB d65f2d

    • BCB accordion styles at product info main. 1a262b

    • Installer. Add accordion for products. 466a5b

    • Add padding to swatch options in product add form for improved layout f10f77

    • Product main info ... in progress bf5c3f

    • Enhance product quantity input with increment/decrement buttons and update styles for better usability 72192e

    • Update product page medium image dimensions to 590x590 012c72

    • Fix minicart styles: set empty counter opacity to 0 79fcd1

    • Increased h2 bottom margin dff6ea

    • Product page action buttons. d008f0

    • Updated footer content links and section titles for improved clarity and user experience 241039

    • BCB homepage: fixed wrong image name b1a4f4

    • Rating stars styles in product listing f17a0f

    • BCB homepage: updated full width banner and sections spacings 2076c7

    • Fixed sort order of product details inside grid listing 9ad360

    • BCB homepage: updated Videos and full width banner sections 072733

    • Product page title font-size. d0987c

    • Footer. Minor fix for ring reval animation. Restore missing divider in footer. (#3) 54cdc4

    • Footer ring reveal animation added (#3) 4a8be8

    • BCB homepage: added animated badges to top banners grid 197e37

    • BCB homepage: added rotation animation for Full Width Banner 1420f9

    • BCB homepage: top banner updated a53bd5

    • Update favicon color 5ea666

    • Update favicon 18d8dc

    • Slightly update footer background. 5fcbfc

    • Footer content update. Add contact block (#3) dea42e

    • Fixed missing minicart overlay on first open (#2) 54feaa

    • BCB homepage: updated Browse categories block dbfa89

    • Breadcrumbs 196469

    • Done with search (#2) d8e0f3

    • Enhance minisearch functionality with slideout behavior and styling adjustments without Ajaxsearch (#2) 8c4a9d

    • Minisearch styles when ajaxsearch disabled... in progress (#2) 259fac

    • Remove unused styles from viewcart action and update empty subtitle styles in minicart (#2) dba7a5

    • Minicart complete (#2) 56efd2

    • Search on desktop (#2) 9c587e

    • BCB homepage: added videos section 7ee864

    • Minicart inprogress (only buttons to adjust)... (#2) c1be91

    • Minicart update in progress.... c3d18b

    • Minicart update in progress... (#2) 55e7b9

    • INstaller. Create dummy CMS block header_panel_info to allow user add custom content (#2) f70d58

    • Adjust minicart counter (#2) 03e843

    • BCB homepage: Added brand logos section b905f1

    • BCB homepage: Added testimonials section 2ab2cf

    • Update newsletter styles: adjust input border and add consent positioning (#2) 02d37d

    • Header. Update search behaviou and look of the result dropown. 993432

    • BCB homepage: Added FAQ a0bfde

    • Add focused search styles. d80f88

    • BCB homepage: added new sections 875068

    • BCB homepage: added ECI and full-width banner d40cfa

    • Top navigation added. 8fa9a3

    • Remove color from menu links dec081

    • Clone currency and store switchers in header slideout menu for improved functionality de36e3

    • Enhance header and newsletter styles for improved layout and responsiveness in header slideout menu. b63dd0

    • Installer. Update header slideout menu styles. 825795

    • Update footer top content HTML to enhance newsletter section styling.
      Don't set font familiy for header in Page Builder ba0b81

    • BCB homepage WIP b228af

    • Basic navpro slideout styles 75ac0e

    • Refactor header slideout menu and newsletter styles for improved layout and consistency 3b42ff

    • Header slideout menu... d4f174

    • Listing styles for the list mode and old price update. cbff61

    • Update README.md to clarify usage of `with-bottom-divider` CSS class and provide detailed instructions 1b9ea5

    • Pagination and make with-bottom-divider general. 37ea17

    • Added list banner 5 config; updated installer, moved it to json a43985

    • Add new layout configuration and remove easybanner references; update footer content and styles 87165b

    • Refactor easybanner configuration and installer for product listing banners 8b1d0d

    • Installer. Listing grid banner added. 914c01

    • Add swatches variables and layout styles d59581

    • Update positioning for filter title and content in layered navigation 8cbd21

    • Add image dimensions for product listings and related widgets in view.xml 6985cd

    • layout and styles for category view, product toolbar, shop by button 08fd27

    • Add layered navigation styles and update imports 944ff1

    • Keep working on prodcut listing and category page. 411088

    • Keep working on product listing toolbar. ebcfac

    • Working on product listing and toolbar look. 1ab39d

    • Add Cooper* font 132906

    • Add listing item styles and variables e725b5

    • Product lisnting in progress - grey bg and border radius. 4e7c35

    • Add new variable files for colors, typography, header, footer, icons, navigation, popover, minisearch, and gradient ba122c

    • Refactor footer and newsletter styles for improved consistency and responsiveness d831e4

    • Footer top newsletter - some updates. 452ca5

breezefront / module-breeze-ai

17 hours ago success
  • 1.8.7
    • chore(release): 1.8.7 307e08

    • docs(composer): name the Content Builder version the field AI button needs (#159) (#160)

      * docs(composer): name the Content Builder version the field AI button needs (#159)

      The per-field AI Generate button attaches to bcb:fieldRowReady, which
      Content Builder only started firing in 1.2.3. Below that the button is
      silently absent, and composer said nothing about Content Builder at all.

      suggest rather than require or conflict: Content Builder is optional and
      an update should not be blocked over one button.

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

      * docs(composer): name every Content Builder-gated feature, not just two (#159)

      Build Landing Page and Build from screenshot are the features that cannot
      run without Content Builder at all; the first version of this entry listed
      only the chat panel and the field button.

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

      ---------

      Co-authored-by: Claude Opus 5 <noreply@anthropic.com> c0a7a8

    • docs(composer): name every Content Builder-gated feature, not just two (#159)

      Build Landing Page and Build from screenshot are the features that cannot
      run without Content Builder at all; the first version of this entry listed
      only the chat panel and the field button.

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

    • docs(composer): name the Content Builder version the field AI button needs (#159)

      The per-field AI Generate button attaches to bcb:fieldRowReady, which
      Content Builder only started firing in 1.2.3. Below that the button is
      silently absent, and composer said nothing about Content Builder at all.

      suggest rather than require or conflict: Content Builder is optional and
      an update should not be blocked over one button.

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

  • 1.8.6
    • chore(release): 1.8.6

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

    • feat(content-builder): per-field AI generate button (#142) (#158)

      * feat(content-builder): per-field AI generate button (#142)

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

      * fix(content-builder): field-button CSS scope, isAjax, sibling context (#142)

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

      ---------

      Co-authored-by: Claude Opus 5 <noreply@anthropic.com> 662162

    • fix(content-builder): field-button CSS scope, isAjax, sibling context (#142)

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

    • feat(content-builder): per-field AI generate button (#142)

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

    • Merge pull request #157 from breezefront/fix/156-icon-crop-accuracy

      fix(content-builder): icon crop accuracy is the model's aim, not our arithmetic (#156) 81a57b

    • docs(content-builder): squaredUp() isn't the #156 icon-crop fix — model aim is

      Investigated before changing anything: the model's boxes for the reference's icon strip were already in the wrong place (bunched, sometimes identical across distinct icons), not a good box distorted by our grid math. See PR for evidence. df3739

swissup / module-core

17 hours ago success
  • head
    • Fixed failing ci.swissuplabs tests cc0b30

    • Use psr/log dependency f375c1

    • Update deps 975f93

    • WIP dc009f

    • Keep installer classes in Installer folder 2db105

    • Ready for psr/log 9e58a3

    • Use constructor property promotion in installer classes

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

    • Require and then install in one shot 8d3822

    • Installer command c09401

    • Copy Marketplace Installer engine 42c579

    • WIP d6d017

    • Allow passing package names to swissup:package:update

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

    • WIP 9ffeb4

    • Repo => Channel to match old command 1e3a63

    • Use `swissup.extra` params as primary source 69fcf1

    • Update command descriptions 48a007

    • Remove useless comment e857e3

    • Array offset cannot be null e4017c

    • Add swissup:update command

      - Update swissup/* packages only; -w also updates their 3rd party dependencies
      - Move ensureRepositoryEnabled into PackageAbstractCommand to share with update
      - Drop disabled modules check: setup:upgrade runs with --safe-mode=1 anyway

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

    • WIP 434bf2

    • WIP a8a711

    • Remove unused code 599915

    • Installer => ModuleManager 0f7da5

    • Drop outdated code (Magento < 2.3.3) e5542c

    • Remove outdated code 7c5b9a

    • Open links in new tab 81a541

    • "How to update" added to the grid 4fdc59

    • Add latest version to the grid 21367b

    • Move outdated modules to the top of the grid be87e7

    • Add outdated badge to the Swissup menu aae4b5

  • 1.13.1
    • Version 1.13.1 5b7b24

    • Fixed invisible update instructions when Mollie Payments is installed 72aab6

swissup / module-firecheckout-integrations

18 hours ago success

breezefront / module-breeze-content-builder

19 hours ago success
  • 1.2.3
    • 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

  • 1.2.2
    • Version 1.2.2 214d13

    • Fixed ignored text color when heading used in content c92d33

swissup / module-ajaxlayerednavigation

1 day ago success
  • 1.6.10
    • 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

  • 1.6.9
    • Version 1.6.9 47aee3

    • Merge pull request #108 from swissup/fix/issue-107-phpunit12-test-migration

      Migrate Test/Unit off removed PHPUnit APIs (PHPUnit 12 / PHP 8.5) e5c066

    • Migrate Test/Unit off removed PHPUnit APIs for PHPUnit 12 / PHP 8.5

      The CI runner targets PHP 8.5, whose only compatible PHPUnit is 12.x/13.x.
      Test/Unit used several APIs removed in PHPUnit 10-12, so the suite could not
      run there. Migrate them and refresh stale mocks that drifted from the code:

      - setMethods() (removed v10) -> onlyMethods(); RequestInterface builder
      replaced with createMock(Request\Http) since the stubbed methods
      (isAjax, getFullActionName) are not on the interface.
      - $this->at() (removed v10) -> plain willReturn() stub on getBlock.
      - ->will($this->returnValue()) (removed v12) -> willReturn().
      - Data provider methods made static and switched from the @dataProvider
      doc-comment (ignored under PHPUnit 12) to the #[DataProvider] attribute.
      - AbstractFilterTest: Price::initRange() now reads the product collection
      via Layer::getCurrentCategory(), not Layer::getProductCollection(); the
      setUp mock is rewired accordingly.
      - ViewTest/IndexTest: gate isAjaxlayerednavigationRequest() now checks
      Http::isAjax() and getParam('aln', false); stubs updated to match.

      Verified: PHPUnit 10.5 (PHP 8.3) 34/34 green. Under PHPUnit 12.5 the module
      tests run and pass; the ObjectManager helper's protected getMockBuilder()
      call is a magento/framework 103.0.8-p1 limitation, fixed in later releases.

      Refs swissup/module-ajaxlayerednavigation#107

      Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> b5904f

swissup / firecheckout

1 day ago success

swissup / module-firecheckout

1 day ago success
  • 1.36.0
    • Version 1.36.0 c6b511

    • Fix readonly env: deploy jsbuild during static content deployment f29be0

    • Fix "Maximum call stack size exceeded" in jsbuild

      mage/requirejs/static.js patches the global require.load and parks the
      previous function on require._load. That patch is not idempotent, and its
      modules are reachable two ways on a FireCheckout page: as the plain
      <script> we inject after require.js, and via the bundles entry below.
      requirejs keeps `defined` per context, so with a second context on the
      page (e.g. "$" next to "_") the jsbuild factory runs twice: require._load
      then holds the first wrapper, whose own fallback is itself, and
      require.load recurses forever. Symptoms are the RangeError plus
      "Load timeout for modules: mage/requirejs/text".

      Pin require._load to the real loader before static.js can install the
      wrapper, so any number of jsbuild evaluations stay harmless.

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

    • Replace curl-powered deployment with Asset\Publisher
      This commit should improve speed of jsbuild in development mode a13472

    • Replace curl-powered deployment with Asset\Publisher
      This commit should improve speed of jsbuild in development mode 46c4d4

swissup / delivery-date

1 day ago success

swissup / module-delivery-date

1 day ago success