►
From YouTube: Backdrop Weekly - Sept 10th 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I've
removed
everything
from
today's
agenda,
except
for
the
issues
we're
working
on
for
117,
and
we
have
a
handful
of
issues
in
the
116
3
milestone
that
we
may
or
may
not
talk
about
today.
Most
of
them
are
bug
fixes.
Some
of
them
are
usability
improvements.
It
would
be
nice,
we
got
them
in,
but
if
they
could
also
go
in
117
one
before
we
get
started,
let's
go
around
and
do
a
quick
round
of
introductions
tim.
Would
you
like
to
go?
First.
B
Making
sure
I'm
not
muted
hi,
I'm
kim
erickson
of
st
paul
tim
up
in
deerwood
minnesota.
Hopefully
the
roofers
are
almost
done,
so
I
don't
make
too
much
noise.
My
focus
the
last
week
and
for
the
coming
week
is
going
to
be
backdrop
live
so
I
may
duck
out
of
this
meeting,
but
I
wanted
to
check
in
see
how
everybody
is
and
answer
any
questions.
If
you're
watching
this
on
youtube,
please
go
register
for
backdrop,
live
right
now
backdrop
dash
live.bankruptcms.org,
see
you
there.
That's
all
gregory
you're
next.
C
Hi,
I'm
greg
I'm
joining
from
greece
as
usual
johnny
next
week
to
see
how
I
can
help
with
things,
and
especially
this
week,
with
the
upcoming
release
on
the
50.
nate.
D
Thanks
gregory,
I'm
nate
lampton
in
oakland,
california,
where
it
is
currently
smoky
and
occluded
and.
D
My
phone
is
ringing
and
yeah
117
is
coming
out
in
five
days,
so
I'm
excited
to
talk
about
the
things
that
we've
got
love
to
do
there
to
you,
jen.
A
D
Oh
sure,
okay,
so
justin
christopherson
was
here
before
the
meeting
started
or
before
the
recording
started,
saying
that
he
did
some
server
maintenance
last
night
on
backdrop
cms.org
and
he
updated
the
backdrop
cms.org
issue
220
to
switch
over
backdrops
certificates,
ssl
certificates
to
let's
encrypt.
So
that's
really
excellent.
We
really
appreciate
the
effort
you
put
in
there
justin
to
make
it
so
that
we
no
longer
have
to
keep
paying
for
wild
card
ssl
certificates
every
year
to
maintain
all
of
the
backdrop
domains.
So
that's
super
cool
thanks,
justin.
D
Shall
I
just
go
right
into
the
progress
report?
Okay,
so,
as
mentioned,
this
is
last
minute.
Before
117
comes
out,
it
comes
out
in
five
days.
Let's
see
that's
september
15th
that
looks
like
it's
tuesday
next
week
and
we
are
in
feature
freeze.
D
So
we're
not
adding
new
features
at
this
point,
but
we
are
trying
to
work
out
bugs
with
some
of
the
new
features
that
have
been
added,
with
one
caveat
to
that
that
I'll
mention
at
the
end
of
the
list,
so
the
biggest
bug
that
we
have
is
we
have
a
pretty
serious
regression
with
the
existing
sites
that
upgrade
if
they
have
created
custom
layouts,
there's
a
problem
that
the
new
ability
for
custom
context
sometimes
causes
some
fatal
errors
when
trying
to
load
the
layout
configuration
files,
and
so
this
issue
is
covered
in
4604
as
the
title
php
fatal,
unsupported,
operand
types
error
and
we
have
a
pretty
good
idea
of
what
is
causing
this.
D
There
are
pull
requests
that
are
up
the
latest
one
needs
review
and
testing.
That
seems
to
get
the
problem
sorted
in
all
known
places.
There
might
be
a
duplicate
of
this
one
herb
dual
opened
separately:
issue,
49
58
from
its
description.
It
sounds
like
it's
a
different
error
that
comes
back
to
the
same
root
cause
so
both
of
those
issues
there's
several
people
that
have
reported
this
issue
and
we're
working
on
getting
it
sorted
as
soon
as
possible.
A
I
get
a
fatal
error
that
crashes,
the
update
process
in
the
middle
and
then
some
like
in
one
instance,
my
database
got
kind
of
confused
as
to
like
what
updates
needed
to
be
run
and
which
one
which
ones
didn't
some
people
have
had
no
problem
whatsoever,
and
so
I
think
it
might
also
be
dependent
on
what
php
version
you're
running,
how
serious
the
errors
you
get
like
whether
it's
fatal
some
people
have
said.
A
If
they're
able
to
get
through
the
updates,
they
see
the
errors,
they
can
clear
the
caches
and
then
it's
fine
again,
but
I
haven't
been
able
to
get
through
the
updates
on
any
of
my
sites
where
I've
run
into
the
problem
it
just
explodes.
I
am
running
php
7.3
on
the
my
local
site,
which
is
where
I'm
trying
to
do
the
updates.
So
I'm
thinking
about
flipping
that
php
version
around
and
seeing
if
it
is
different
in
a
different
version
of
php
but
yeah.
It's
been
interesting
that
everyone
is
encountering
it
in
different
ways.
C
Yeah,
I
I
saw
it
on
7.2
on
my
local
and
on
whatever
is
being
used.
I
think
5.3
of
0.4
or
not
yes,.
A
I
have
a
five
five
site
that
I
think
it
one
of
them.
I
ran
the
updates
locally
and
it
worked,
and
then
I
went
to
run
them
on
production
and
it
crashed,
and
that
was
the
la
most
recent
change
I
made
with
at
the
end
of
the
the
last
check-in
to
get
contests,
and
I
thought
that
was
really
interesting,
because
I
didn't
think
that
was
necessary
because
I
was
running
fine
on
7-3,
but
then
it
didn't
run
fine
on
five
five
on
the
production
server
in
beta,
so
yeah
it's.
A
D
Great
so
that
issue
4604
is
the
highest
priority
ticket
that
we
have
fatal
errors
crashing
people's
websites
is
pretty
bad.
So,
however,
if
this
is
a
new
install,
it
doesn't
seem
like
new
sites
are
affected
by
it,
and
also
you
know.
This
is
one
of
the
reasons
why
we
have
preview
releases.
Is
that
it's
an
opportunity
for
us
to
fix
these
kind
of
errors
before
the
official
release?
So
we've
got
a
couple
more
days
several
more
days
to
figure
this
little
issue
out
and
we'll
get
that
merged
in
there.
D
Probably
there
will
not
be
another
preview
release.
So,
for
the
time
being,
you
can
use
the
preview
release
in
in
testing
environments,
but
for
sure,
like
you,
shouldn't,
be
using
the
preview
release
in
production
in
the
first
place
anyway.
So,
but
still,
all
testers
of
the
preview
release
are
highly
appreciated
and
we've
had
lots
of
helpful
feedback.
D
A
D
Right
yeah,
the
the
way
that
we're
storing
that
config
right
is
is
changed
and
it
looks
like
the
update
hook
did
not
update
existing
sites
correctly
in
all
cases,
so
46.
A
If
you
use
that,
if
you
were
on
116,
where
you
had
the
setting
it's
able
to
pull
the
previous
setting
and
update
it,
but
if
you're
on
115,
where
you
never
have
the
setting
it
inserts
the
machine
name
instead
of
a
date
format
and
the
machine
name
actually
does
work
as
a
date
format.
So
you
get
this
like
really
long
date.
Format
with
like
everything.
A
Yeah
so
I
looked
in
my
log
and
was
like
what
is
this
and
then
I
was
like
oh
wait.
This
is,
I
know
what
this
is
and
I
looked
at
it
and
I'm
like
that's
so
weird
that
it
still
works
as
a
date
format
but
yeah.
So
I
think
we
just
need
a
default
like
if
there's
no
value
then
set
and
we'll
use
whatever
the
date.
This
format
used
before
that
as
a
starting
point.
D
Yep
so
some
fixes
necessary
in
that
update
hook,
but
fortunately
that
one
doesn't
really
cause
any
substantial
problems.
And
if
you
wanted
to,
you
can
just
change
the
setting,
save
it
and
then
the
problem
is
remedied.
D
See
this
last
one
text
update
for
block
admin
info.
D
This
is
actually
okay.
This
is
this,
isn't
actually
bug.
This
is,
and
we
have
it
twice
in
the
agenda.
D
Okay,
so
we
also
have
a
couple
of
follow-ups
for
new
features
that
are
just
like
cleanup
items,
one
of
which
is
that
we
added
a
new
feature
that
makes
it
so
that,
when
you
place
a
block,
you
can
now
give
each
block,
regardless
of
what
type
of
block
it
is.
A
administrative
label
and
description.
D
To,
I
wouldn't
say
to
be
more
consistent,
but
to
be
more
descriptive
of
what
it
is
that
those
things
are
doing
so
that
issue
4600
is
one
of
these
ones,
where
we're
just
going
back
and
forth
discussing
what
strings
are
best
and
most
intuitive
for
that
interface.
D
I
pointed
out
in
that
issue
most
recently
that
views
has
something
similar,
but
fuse's
interface
is
really
pretty
terrible.
We
might
spin
out
of
this,
like
whatever
we
choose
here.
We
probably
also
want
to
update
views
to
do
something
similar,
because
the
vs
ui
has
kind
of
the
same
problem
and
has
worse
text
than
the
layout
ui
has
right
now.
C
D
C
Yes,
so
the
the
page
looks
nice
now,
but
it's
when
you
enable
the
auto
check
updates
for
disabled
things
and
projects.
C
It
has
separate
sections
for
the
disabled
modules,
things
and
layouts
and
like
there's
too
many
sections
there,
I
thought
that
maybe
we
could
consolidate
those
and
if
it's
disabled,
maybe
we
have
them
grayed
out,
similarly
to
what
we
do
with
disabled
views
or
what
have
you
and
then
other
people
chanting
to
say
that
they
find
it
strange
that
they
come
to
a
page
that
says
available
dates,
and
yet
they
see
every
single
project
that
is
installed
in
its
update
status.
C
So
maybe
that
will
evolve
into
renaming
that
page
because
it's
under
reports
to
update
status
and
then
there's
this
other
issue
that
we
have.
I
can't
remember
that
the
issue
number
where
we
want
to
merge
all
the
updates,
the
available
updates
pages
under
modules,
layouts
and
projects,
and
maybe
that
should
be
called
available
updates,
but
yeah
we're
still.
We
still
that
issue
still
has
the
needs
more
feedback
labels,
so
that
people
can
find.
D
C
Yes,
so
one
of
the
things
that
I
think
it's
also
in
juplaid
for
now
is
that
you
can
filter
this
page
by
security
updates
only
available
updates
for
all,
and
maybe
that,
if
we
added
a
filter,
the
as
others
said
as
well,
the
filter
by
name
is
a
bit
too
much
but
having
a
way
to
filter
by
security
updates.
That's
that
could
be
useful,
and
maybe
that
could
then
sort
of
like
satisfied
or
opinions
on
what
this
page
would
do.
D
D
So
I
I
put
one
more
issue
in
the
117
list,
which
is
not
strictly
a
bug
fix
for
a
new
feature,
and
it
is
my
sequel
8
support
that
is
issue
4238,
and
this
is
a
cross
port
from
something
that
was
happening.
The
drupal
7
queue
it's
still
not
in
triple
7
yet,
but
it's
an
adaptation
we
did
get
all
of
the
tests
working.
So
it
seems,
as
though
backdrop
with
these
changes
passes
everything
exactly
the
same
as
before,
and
it
should
now
fully
support
my
sequel
8
as
well.
D
But
if
you
specifically
installed
in
my
sql
package,
it
is
also
now
my
sql,
eight
and
so
not
working
on
the
current
versions
of
all
of
these
operating
systems
is
kind
of
a
bad
look,
and
this
does
change
the
way
the
database
engine
works
because
it
starts
quoting
a
bunch
of
fields
that
it
it
could
have
some
minor
repercussions
that
make
me
a
little
bit
uneasy,
putting
into
a
bug
fix
release,
and
I
don't
think
I'd
want
to
wait.
D
An
additional
four
months
before
backdrop
became
compatible
with
the
current
versions
of
all
of
these
operating
systems.
Yeah.
I
agree.
So
it's
a
little
bit
of
a
conundrum
here,
I
I
might
be
tempted
to
say
okay.
Well,
maybe
we
do
put
it
into
a
bug
fix
release
anyway,
because
we
don't
want
to
rush
it
out,
even
though
it
might
might
have
some
minor
api
implications,
because
the
benefits
are
so
great
compared
to
the
potential
costs.
D
But
in
any
case
that
issue
only
just
got
its
tests
passing
yesterday,
so
yeah.
We
need
need
feedback
and
reviewing
on
it
and
if
it
proceeds
quickly
and
we
can
get
into
117,
then
great
and
if
it's
not,
then
we
might
want
to
start
considering
if
we
can
get
into
117
one.
C
D
The
most
likely
outcome,
because
all
tests
are
passing
and
and
core
is
pretty
extensively
covered
in
its
in
its
test
coverage.
I
doubt
you're
going
to
see
anything
on
a
new
install
most
likely.
The
places
where
you
would
run
into
some
problem
is:
is
it
when
you're
running
a
site
that
has
a
lot
of
contributed
modules?
D
I
think
ones
that
have
some
that
this
starts
getting
really
specific,
but
ones
that
alter
queries
so
ones
that
specifically
are
running
some
sort
of
node
access.
Module
are
the
ones
that
are
most
likely
to
be
affected,
because
if
you're
modifying
the
sql
query
now
the
sql
queries
are
slightly
different
because
they
have
backticks
around
all
the
tables
that
could
potentially
cause
an
issue
it.
D
It
really
shouldn't,
because
if
you're
modifying
queries
with
a
query,
alter
you're
using
dbt
and
g
and
it
doesn't
matter
how
things
are
quoted
because
that's
after
you
do
all
your
your
modifications,
so
it's
not
strictly
making
an
api
change
in
any
of
the
apis.
We
have
exposed,
however,
you're
doing
something
hacky
at
like
a
raw
sql
layer.
Doing
some
reg
access
on
rig
on
your
sql
queries.
Then
it
could
cause
a
problem.
There.
C
Yeah,
I
I
think
that
I
would
like
us.
We
already
had
members
of
the
community
complaining
about
the
lack
of
support
for
my
simple
age
and
also
because,
after
it's
minor
release,
we
have
this
goal
to
have
a
second
bug
fix
release.
If
there's
anything
critical
within
two
weeks,
if
anything
surfaces,
we
can
do
it
as
part
of
that
or
revert
if
it's
that
bad.
So
I
think
yes,
the
other
thing
is
released.
D
Yeah
well,
anyway,
thoughts
and
feedback
are
right
are
appreciated.
It's
issue,
4238
seems
to
be
working,
but
yeah.
We
need
some
some
more
widespread
testing.
D
Okay.
Well,
that's
the
117q.
There
are
a
lot
of
items
that
are
in
the
116
3
list
as
well.
That's
we're
continuing
to
accrue
lots
of
things
there.
D
D
D
Those
are
our
real
serious
priorities
and
then
these
1163
items,
any
of
them
that
we
get
done
is,
is
great
and
there's
lots
of
them
that
are
in
the
needs
review
state.
So
we
might
get.
You
know
half
a
dozen
of
these
or
more
done
in
the
next
couple
of
days
and
that
will
be
in
the
163
release
as
well
as,
of
course,
in
the
117
final
release.
A
Tim
made
an
announcement
in
the
previous
video
or
maybe
the
beginning
of
this
one
to
go
sign
up
for
backdrop
live
and
just
in
case
you
were
watching
the
weren't
watching
the
live
stream
then,
but
are
now
we
do
have
our
first
online
global
event,
september,
18th
and
19th.
Please
register
there.
We
are
having
a
recommended
donation
as
a
registration
fee,
but
if
you
can't
afford
it,
you
can
either
put
in
a
dollar
or
a
cent
or
you
can
contact
us
via
the
contact
form.
A
B
Just
I'll
just
add
to
that
we're
also
looking
for
hosts
for
for
topics,
so
this
is
everybody
has
the
opportunity
to
suggest
a
topic
and
a
host
of
discussion.
So
let
us
know
about
that
too.