Repository navigation
Nibble 0.24.0
Change what a site already holds, safely. A content migration can replace a shipped value where editors haven't
changed it, and this release fixes the deploy of a site whose form emails a site setting.
It adds no database migrations.
What's new
- A content migration can change a value editors may have kept.
set_valuereplaces a stored value on every
record and locale where it still equalsfrom, or the keys of grid and replicator rows that matchwhere. A value
an editor has changed since, in the record or its draft, is left alone, a second run changes nothing, andtois
checked against the field's own validation before anything runs.
What's fixed
- A site whose form emails a global's address builds again.
bin/rails nibble:buildchecked anotifyrecipient
such as{global.site.contact_email}by asking the database for the global's columns, and an image build has no
database, sobin/kamal deploystopped with "Could not find table 'global_sets'". The check reads the schema alone
now, and checks the global against the schema being checked rather than the running site's. - Events keep being delivered after a change is rolled back. A change that published an event and was then rolled
back, such as a preview, left its server thread believing a delivery was already on the way, so that thread
queued none for its later changes; their webhooks, search updates and cache purges waited for another thread's
delivery or a restart. A rollback clears that mark now. - A favicon can be an
.icofile. Site settings' Favicon field offers.ico, but the asset library refused to
upload one, so a package setting an.icofavicon imported without it..icofiles upload now, and are served as
they are.