All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
Please read about the changes to BoldMinded add-on licensing.
Ticket: Allow atomless bloqs or include the new Notes field
| Status | Resolved |
| Add-on / Version | Bloqs 4.12.5 |
| Severity | |
| EE Version | 6.3.4 |
Wardour
Jul 08, 2022Hi there,
by default a new bloq includes an atom that cannot be deleted.
I have found in my usage of bloqs for some components they don’t need an editable values. So a signup banner bloq is set in the template file, there is no need for editing.
In the UI, for the bloq I then rename the default text field to “null field” with a description of, field not used.
It would be great not have fields in a bloq for a cleaner look. I have had a client question, why is there a field there if is does nothing!
I can understand that removing the atom would create more problems for the integrity of a bloq, so the alternative I was thinking is, allow the use of the notes field. This will keep the integrity of always having one atom for a bloq, but eliminate a “random” field being seen in the UI.
BoldMinded (Brian)
If I’m understanding correctly, you can create a single atom in a bloq with the short name “__hidden” and it won’t display any atoms in the bloq. Each bloq is required to have a at least 1 atom, but making one __hidden works around that.
Wardour
Awesome thanks. That does hide the field.