Recent Activities
This page shows what are we working on.
-
head
-
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
-
Add footer top content block and styles for newsletter integration (WIP) 128131
-
Footer bottom. 8d58ea
-
Add footer content block and styles for enhanced footer layout 4d6b1b
-
Header. Hide menu on medium screens. Update search look on monile. e0146d
-
Installer. Add navigation slideout menu a89fd5
-
-
head
-
Merge pull request #112 from breezefront/fix/104-image-budget-ranking
fix(content-builder): spend the image budget on pictures before icons (#104) c31f2a -
Merge pull request #109 from breezefront/fix/103-unrequested-row-background
fix(content-builder): fill a row's background only where the design has one (#103) ef8aeb -
feat(content-builder): name the widgets that could have covered an unplaced band (#107)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 61ea5b -
fix(content-builder): spend the image budget on pictures before icons (#104)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> fe3fd9 -
fix(content-builder): fill a row's background only where the design has one (#103)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 466958 -
test(content-builder): cover both doors into the editor's chat panel (#111)
The bug was invisible to the unit tests because both halves of it are about
wiring: which URL the editor was reached by, and what BCB hands the mixin
afterwards. Follows field-actions-layout.spec.js, added for the same class of
regression in #96 — a control that is present, absent or misplaced depending
on how the page was reached.
Four assertions: the chat button is there from the admin-menu door (the one
that carries no page_id) and still there from the CMS-page door, the panel
opens when the button is clicked, and it is torn down while no page is
selected.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 0cf836 -
fix(content-builder): show the chat panel when the editor opens without page_id (#111)
Swissup_BreezeContentBuilder's menu entry opens the editor as
breeze_editor/editor/index/activate_panel/content-builder, which carries no
page_id. AiChatConfig::canShow() required one, so the block emitted nothing,
chat-config-store stayed null, and bcb-chat-mixin.js injected no button —
silently, which is why the logs were clean. Picking a page from the toolbar
afterwards could not recover it. Opening the editor from the CMS page form,
which does pass page_id, worked; that is the difference behind "I don't see
the chat interface anymore".
The page is the client's to know: bcb-chat-panel.js already takes its pageId
from the mount, which BCB resolves and re-supplies on every switchPage(). So
canShow() drops the clause and getConfigJson() stops publishing a second,
staler copy of the id.
The mixin now checks the pageId it is handed, which fixes a second bug from
the same gap: BCB drives _startContentBuilder(0) on a store switch and when a
BLB product or category page takes the editor over, and the panel used to
remount against page 0 and post entityId 0.
Also log both failure branches of Controller\Adminhtml\Page\Build. Everything
that endpoint refused reached the browser and nowhere else, so the "not valid
JSON: Syntax error" from #91 left no trace to go back to. Refusals log at
error naming the page; an unexpected throwable logs at critical with the
exception in the context so the trace is written too.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> e29ad5
-
-
1.6.0
-
chore(release): 1.6.0
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> aa4f21
-
-
head
-
3.3.3
-
1.0.24
-
1.0.23
-
Update composer.json 91a0bc
-
-
head
-
Improve price styles when both inc. and ex. prices are shown a30673
-
-
3.3.3
-
1.2.2
-
1.2.1
-
Version 1.2.1 4d0611
-
Added Additional HTML prop for Banner component to store animations 7941f0
-
Hover zoom only image/background, keep text content static 27547f
-
Declare the modules BCB actually needs a4923d
-
Fixed composer.json 975c9b
-
Added magento/module-ui dependency
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> 154d8a -
fix(composer): declare the modules BCB actually needs (breezefront/breeze-content-builder#1)
The metapackage does not need `swissup/module-core` — it arrives
transitively through this module, exactly as in breezefront/breeze-ai#1.
What the metapackage cannot fix is a module that under-declares its own
dependencies, which is what breaks an install on a store that does not
happen to ship every Magento module. Seven of the modules whose classes
this one injects or instantiates were missing from `require`:
- magento/module-catalog — `Block/Adminhtml/Product/Widget/Chooser`
extends `Magento\Catalog\Block\Adminhtml\Product\Widget\Chooser`, and
`FeaturedProductRenderer` injects `ProductRepositoryInterface`,
`Helper\Image` and `Helper\Output`.
- magento/module-widget — `Widget\Helper\Conditions`
(`ProductGridRenderer`), `Widget\Model\Widget` and
`Widget\Model\Widget\Config` (`AdminToolbarPlugin`).
- magento/module-swatches — `FeaturedProductRenderer` promotes
`Swatches\ViewModel\Product\Renderer\Configurable` as a constructor
property, so DI compilation needs it present.
- magento/module-catalog-inventory — `FallbackProductProvider` injects
`CatalogInventory\Helper\Stock`.
- magento/module-variable — `AdminToolbarPlugin` injects
`Variable\Model\Variable\Config`.
- magento/module-customer — `BcbContentRenderer` reads
`Customer\Model\Context::CONTEXT_GROUP` for its cache key.
- magento/module-configurable-product — `FeaturedProductRenderer` reads
`Configurable::TYPE_CODE` with no guard.
- magento/module-newsletter — `NewsletterRenderer` creates
`Newsletter\Block\Subscribe` with no guard; nothing catches the failure.
- magento/module-theme — already sequenced in `etc/module.xml`; it was
the only entry there absent from `require`.
Also tightened:
- `php: "^8.1"` added. Promoted `readonly` properties are used throughout
(`BcbContentRenderer`, every controller, the renderers), so 8.1 is the
real floor. Matches `swissup/module-breeze` and
`swissup/module-breeze-theme-editor`.
- `magento/framework: "*"` → `"^103.0"`. `"*"` guarded nothing; 103.0 is
the 2.4 line, and it is what `swissup/module-breeze-theme-editor` —
already required here — asks for.
Left as is, on purpose:
- `swissup/module-core: "^1.13.1"` — already the tightest constraint in
the family (`module-breeze` and `module-breeze-theme-editor` ask for
`^1.12.27`) and 1.13.1 exists, so it resolves. Not widened.
- `magento/module-review` and `swissup/module-marketplace` are soft:
`FeaturedProductRenderer` guards the review block with `class_exists()`
and `Installer/Command/BcbCmsPage` only names
`Swissup\Marketplace\Installer\Request` in a docblock. Moved to
`suggest` rather than `require`.
- `swissup/module-breeze` stays out. The only coupling is
`view/frontend/layout/breeze_default.xml`, a handle Magento loads only
when Breeze is installed; `cms_page_view.xml` carries the rendering on
any theme.
- `magento/module-page-builder` and `magento/module-ui` appear in
comments only.
- The remaining `magento/module-*: "*"` constraints are untouched — no
version floor is known to be wrong, and inventing one would be a
narrower claim than the code supports.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 2dca6d -
Merge pull request #36 from breezefront/fix/widget-description-for-ai
docs(components): stop telling the AI a known widget directive is invented 45a7e6 -
docs(components): stop telling the AI a known widget directive is invented
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 3d1aa4
-
-
1.12.0
-
Version 1.12.0 346881
-
Typo fix 50a7b6
-
Cleanup CSS ea255a
-
Fix grid styles 4d48e9
-
Stop running composer from the backend (#17)
Running composer through the web server is not reliable, so the backend no
longer dispatches composer operations. Install, Update, Remove, Enable and
Disable now open a modal with the command to copy and run in a terminal, both
for a single row and for a massaction. Run Installer stays a real backend
operation - the one-click installer does not use composer.
Enable and Disable had no console equivalent, so marketplace:package:enable and
marketplace:package:disable were added (aliases marketplace:enable and
marketplace:disable).
Channel configuration and Tasks History are removed from the backend as well.
Channels are managed with the marketplace:channel:* and marketplace:auth:*
commands. With the settings form gone, ChannelsSave was the last job producer,
so the whole queue is removed: JobDispatcher, QueueDispatcher, Validator, the
Job entity, the activity widget, the queue crons and the job table.
The SettingsDataProvider modifiers are kept as empty stubs so that the channel
modules registering them in the pool keep compiling.
BREAKING: the swissup_marketplace_job table is dropped on setup:upgrade, and
HandlerInterface::validateBeforeDispatch() is removed - it had no callers left.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> cccd99 -
Ignore the packages with an invalid name
The channel metadata is not validated, and the package name ends up in
the command we suggest to copy and run. A name containing ;, $() or a
whitespace turns that command into something else.
Filtered where the channel data is read, so that such a package never
reaches the grid, the suggested command, or the installer request. The
pattern is the one composer validates the names with, so nothing that
composer is able to install is dropped.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 956e42 -
Improve package disable/enable operations cc8491
-
Address review comments
- Massaction: require the row to expose the action before offering a
command. Local.php marks every downloaded package as enabled and only
overrides it for the modules, so a downloaded theme passed the shared
disable check even though Links.php never adds Enable/Disable to a
non-module row - marketplace:disable would then write a derived, bogus
module name to config.php.
- Copy button: writeText() is asynchronous and rejects when the clipboard
is blocked. Copy now returns a deferred, falls back to execCommand on
rejection, and the Copied label is shown only once a copy succeeded.
- README grammar.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> f2fdaf -
Stop running composer from the backend
Running composer through the web server was never reliable, so the backend no
longer dispatches composer operations. Install, Update, Remove, Enable and
Disable now open a modal with the command to copy and run in a terminal, both
for a single row and for a massaction. Run Installer stays a real backend
operation - the one-click installer does not use composer.
Enable and Disable had no console equivalent, so marketplace:package:enable and
marketplace:package:disable were added (aliases marketplace:enable and
marketplace:disable).
Channel configuration and Tasks History are removed from the backend as well.
Channels are managed with the marketplace:channel:* and marketplace:auth:*
commands. With the settings form gone, ChannelsSave was the last job producer,
so the whole queue is removed: JobDispatcher, QueueDispatcher, Validator, the
Job entity, the activity widget, the queue crons and the job table.
The SettingsDataProvider modifiers are kept as empty stubs so that the channel
modules registering them in the pool keep compiling.
BREAKING: the swissup_marketplace_job table is dropped on setup:upgrade, and
HandlerInterface::validateBeforeDispatch() is removed - it had no callers left.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> d70a96 -
Forward command output strings to terminal c17318
-
Allow using dry-run option 2d329d
-
Reuse composer_cache from user's directory if possible 9cc10a
-
Command shortcuts 2cfa4c
-
-
1.11.0
-
head
-
1.0.3
-
head
-
docs: document supported DB versions and the MariaDB 10.11 gap (#26)
Magento 2.4.8's SqlVersionProvider accepts only MySQL 5.7/8.0/8.4 and
MariaDB 10.2-10.6/11.4, so a hosting-side upgrade from MariaDB 10.6 to
10.11 aborts setup:upgrade with "Current version of RDBMS is not
supported" while the storefront keeps running. That reaches us as an
extension-compatibility report, because this module is popular exactly
on hostings with older, hosting-managed stacks.
Add a F.A.Q. entry with the accepted version list, state that the module
imposes no database requirement of its own, and warn against patching
di.xml as a workaround (getMariaDbSuffixKey() has no branch for those
releases and falls back to its 10.6 profile, so declarative schema emits
DDL against the wrong engine profile).
Co-authored-by: Claude Opus 5 <noreply@anthropic.com> 52f8c3 -
docs: document supported DB versions and the MariaDB 10.11 gap
Magento 2.4.8's SqlVersionProvider accepts only MySQL 5.7/8.0/8.4 and
MariaDB 10.2-10.6/11.4, so a hosting-side upgrade from MariaDB 10.6 to
10.11 aborts setup:upgrade with "Current version of RDBMS is not
supported" while the storefront keeps running. That reaches us as an
extension-compatibility report, because this module is popular exactly
on hostings with older, hosting-managed stacks.
Add a F.A.Q. entry with the accepted version list, state that the module
imposes no database requirement of its own, and warn against patching
di.xml as a workaround (getMariaDbSuffixKey() has no branch for those
releases and falls back to its 10.6 profile, so declarative schema emits
DDL against the wrong engine profile).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 32e9ef
-