►
From YouTube: Backdrop Weekly - June 30, 2022
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).
B
Hello,
it's
june
30th
2022,
and
this
is
the
weekly
backdrop
developer
meeting.
We
get
together
every
week
to
talk
about
problems
and
priorities
that
the
backdrop
developers
are
facing,
with
pretty
heavy
emphasis
on
core.
So
we'll
do
some
introductions
before
we
get
started.
My
name
is
nate
lampton,
quick
sketch
on
the
internet,
calling
from
oakland
california
we'll
go
to
robert
and
then
tim.
C
My
name
is
tim
erickson,
I'm
st
paul
tim
on
the
internet,
and
I
am
here
today
from
deerwood
minnesota.
B
C
B
Hi,
I'm
alejandro
rg
piano
online
from
denver
colorado
all
right
thanks
folks,
let's
see
to
get
started,
we
like
to
do
a
little
community
and
contribute
contributions,
update
jen
updates
from
the
kintrip
side.
A
Sure
so
this
week
we
have
a
new
theme
and
several
new
modules.
Olaf
made
us
a
new
theme
named
b21,
which
is
based
off
of
the
wordpress
2021
theme.
So
if
you
want
your
backed
website
to
look
like
that,
you've
got
a
new
option,
just
fantastic.
A
B
Excellent
all
right,
let's
see
we
have
a
forum
post
from
forum.backdropcms.org.
B
Under
the
events
section,
we
have
a
weekly
post
for
this
meeting
to
solicit
topics
that
people
would
like
to
have
discussed
during
these
meetings.
Two
items
were
raised
for
this
week.
One
was
from
alejandro
about
5482,
the
layout
relationship
contexts
aren't
getting
set
properly
and
this
particularly
affects
getting
the
author
from
the
node
and
54
82.
We've
had
three
different
pull
requests.
Now
we
think
we've
settled
on
one,
so
it's
marked
rdbc
thanks
alejandro
for
that,
and
we
think
that
we're
going
to
move
it
in
we're.
B
We
were
discussing
this
a
little
bit
before
the
recording
started
and
between
alejandra
and
myself.
We
kind
of
agree
that
technically,
like
the
way
contexts,
work
isn't
the
best,
but
the
pull
request
fixes
the
urgent
problem
that
we're
we're
currently
facing
and
we'd
like
to
possibly
do
a
separate
like
clean
up
re-architecture
to
like
make
the
get
context
method
like
less.
B
More
consistent,
I'm
not
sure
what
it's
going
to
be
less
of,
but
it
needs
to
be
more
consistent
because
right
now
it
does
something
different
based
on
different
properties
and
that's
really
not
great
the
way
that
it
returns
different
things
based
on
different
situations,
yeah,
so
we're
hoping
that
that
will
go
in
that
will
that
you
know
may
prompt
us
or
or
hurry
our
like
delivery
of
the
next
bug
fix
release,
because
it
is
a
pretty
major
problem,
good
enough
at
least
that's
the
important
enough
that
it
could
speed
the
bug,
fix,
release
and
get
123.1
out
there.
B
Let's
see,
okay,
so
that
one's
coming
along
great,
it's
good
to
have
finally
have
some
progress
on
that.
I'm
sorry,
we've
made
lots
of
progress
on
that.
It's
good
to
finally
come
to
a
resolution
on
that.
42.85
is
an
issue.
Let's
see,
there's
there's
a
hang
on
before
we
get
to
42.85.
B
I
can't
actually
find
it
there's
there's
a
pull
request
is
out
there.
That's
marked
rtbc
already
that,
if
you've
been
using
self
updates
on
in
in
backdrop
core,
we
moved
around
some
of
the
modules
that
are
used
in
tests
and
what
ended
up
happening
is
that
some
people,
after
self
upgrading
they
found
that
these
modules
self
ex
they
still
exist
in
their
previous
location
and
in
the
new
location,
and
thanks
to
our
now
our
new
status
report.
B
That
now
tells
you,
if
you
have
the
same
module
multiple
places
and
throws
a
warning
they're
like
oh
I've
got
two
copies
of
the
same
module,
even
though
it's
a
test
module
and
it
doesn't
really
matter
and
what
has
been
happening.
Apparently,
when
you
self-update
dribble
core,
doesn't
fully
replace
the
core
directory,
it
merges
the
core,
it
merges
the
updates.
So
if
files
get
moved
or
renamed,
you
end
up
with
two
copies
of
the
same
file,
sometimes
after
doing
self
updates.
B
So
we
have
one
pull
request
that
removes
those
the
duplicate
modules
that
are
still
in
the
old
location.
That
is
just
done
through
an
update
hook,
and
then
we
have
this
issue.
4285,
which
permanently
prevents
that
from
happening
going
forward.
B
The
point
of
concern
here
is
indigozella
filed
the
issue,
and
I
filed
the
pull
request
and
we're
looking
for
more
testing.
I
think
and
more
commentary
on
the
approach,
because,
because
what
it
does,
is
it
checks
to
see
that
the
the
director
is
writable
and
then
it
deletes
the
entire
directory
and
then
puts
the
new
directory
in
place,
and
while
that
seems
mostly
okay
for
contrib
modules,
you
know
it
deletes
the
the
old
contrib
module
and
puts
the
new
control
module
in
place.
B
What
you
would
expect
for
it
for
an
update
for
core.
It
means
that
the
php
code
that
is
currently
actively
executing
in
memory
is
deleting
itself
and
then
replacing
it
with
something
else
which
understandably,
can
causes
some
concern
that
if
something
were
to
go
wrong,
then
clearly
the
the
site
wouldn't
be
able
to
recover
from
that,
because
the
code
would
that
is
currently
running.
The
page
itself
wouldn't
be
there
anymore,
which
I
agree
is
really
scary,
but
it's
also
the
way
that
it
works.
B
So
yeah
there
is
that
so
we're
looking
for
additional
feedback
there.
I
think
that
in
fact,
the
self
updates
for
core
had
worked
that
way
for
a
certain
period
of
time,
until
some
other
change
happened,
and
then
we
didn't
notice
that
it
had
this
behavior
of
leaving
stray
files
behind.
So
it
is
the
original
intention
of
the
upgrader
to
to
work
this
way,
but
due
to
a
typo,
basically,
we
stopped
deleting
the
directory
and
started
merging
them
instead.
B
B
Report:
okay:
okay,
let's
see
because
I'd
like
someone
else
to
talk
for
a
minute,
I'm
gonna
go
to
issue
4569,
which
is
hiding
the
title
on
comments
as
an
option
which
tim
is
the
advocate
for
and
tim,
could
you
give
us
an
update
of
of
where
that's
sitting
right
now.
C
Sure
so,
up
until
at
the
last
week's
meeting,
we
had
two
pull
requests,
one
that
hid
the
comment
title
with
css
and
one
that
did
it
primarily
through
the
comment
template
file,
and
we
decided,
I
think,
at
the
last
meeting,
to
go
with
the
changing
the
template,
and
so
I
closed
the
the
css
pull
request.
C
I
made
some
additional
changes
to
the
the
other
pr
I've
gotten
a
lot
of
very
helpful,
constructive
feedback
from
peter
b.w,
panda
and
linda
gazelle,
in
particular
amongst
other
people.
I
think
doc
belmont
chimed
in
at
some
point
too,
and
I
made
lots
of
silly
syntactical
errors
that
other
people
have
caught
and
pointed
out
to
me.
Thank
you
and
I
appreciate
everyone's
patience.
C
There
is
something
that
might
still
be
open
for
a
little
bit
of
discussion,
as
I
did
put
because
I
feel
pretty
uncomfortable
just
having
this
not
work
on
some
sites
without
any
clue.
So
I'm
looking
for
some
gentle
way
to
give
people
a
clue
if
it
doesn't
work,
that's
going
to
help
them
solve
this
problem,
and
I
right
now
just
have
some
text
saying
something
to
the
effect
of
you
know
that
this
feature
may
be
dependent
upon
your
contrib
theme
or
something
like
that
which
people
have
pointed
out.
C
Well,
that's
true
of
a
lot
of
things,
but
in
other
cases
we
don't
know
that
this
is
likely
to
cause
problems.
In
this
case,
we
do
I'm
open
to
other
wording,
I'm
open
to
other
ideas
I
just
want.
I
want
for
the
end
user
to
not
be
left
clueless
if
this,
if
they
click
a
box
and
nothing
happens
like
I-
want
them
to
have
some
way
of
sort
of
figuring
out
what's
going
on,
because
I
don't
think
it's
obvious
at
all.
C
I,
as
a
user
would
not
necessarily
assume
this
was
related
to
my
contributing
anyways.
So
that's
one
big
thing.
The
other
thing
that
I
was
reminded
of
today
that
we
forgot
about
was
the
the
the
steps
to
take
for,
because
this
is
there
is
a
contrib
module.
C
So
we
need
to
incorporate
the
you
know
the
check
to
see
if
the
contrib
module
is
already
active
on
the
site
and
if
I'm
understanding
this
correctly,
if,
if
a
user's
already
using
the
contrib
module,
we
would
disable
that
make
sure
that
the
settings
from
the
contrib
module
match
what
what
we're
setting
up
in
the
new
site
and
that
would
be
part
of
the
update
hook.
C
So
that
hasn't
been
addressed
yet,
and
it's
probably
the
primary
thing,
although
the
one
last
thing
would
be
tess
this,
it
seems
pretty
clear
that
this
is
gonna
require
some
new
tests
and
I
probably
am
not
equipped
right
now
to
do
those
myself.
So
I
either
need
a
volunteer
to
either
do
the
tests
or,
if
somebody
wanted
to
schedule
some
time
with
me
and
do
some
team
coding.
C
B
All
right,
thanks
tim,
all
right
yeah.
I
think
you
covered
everything
that
that
I
was
seeing
in
that
issue
as
well.
Great.
A
I
have
one
other
update
for
that
issue
and
tim
if
you're
listening.
I
left
a
note
on
the
issue
with
some
code
samples,
but
the
issue
introduces
an
svg
without
a
ping
fallback,
and
we
haven't
done
that
anywhere
else
in
core
before
now.
So
I
put
in
a
little
code
sample
of
how
we
had
the
ping
fall
back
for
other
svgs
and
course,
so
we
can.
B
Interesting
yeah,
that's
great!
You
know
I.
I
should
dig
up
this
issue
thinking
about
browser
compatibility
things
if
we
haven't
yet
we
should
probably
go
and
find
our
internet
explorer
compatibility
issue
and
totally
absolutely
remove
our
internet
explorer
compatibility
stuff
because,
like
it
is
dead,
dead,
dead,
dead
now
so
no
need,
for.
I
think
we
still
have
the
html5
shim,
for
example,
that
is,
for
internet
explorer.
Eight.
I
think
and
yeah
that
all
that
needs
to
just
go
away
at
this
point.
B
I
know
it's
like
this
is
the
sort
of
thing
with
our
backwoods
compatibility,
we're
finding
that
we're
taking
it
to
such
extremes,
we're
like
outlasting
every
other
software
project
out
there
and
yeah,
I
think
yeah.
Sometimes
it
gets
a
little
a
little
bit
much
anyway.
A
C
A
A
We
haven't
done.
We
haven't
ever
introduced
an
svg
in
core
without
a
ping
fallback
before
now
right,
so
I
think
for
what
getting
this
issue
in
without
any
blockers,
it
would
probably
get
to
introduce
it,
but
then
we
should
also
revisit
our
drop
ie
support
issue,
and
when
that
moves
forward,
we
can
drop
support
every
through
through
all
of
core.
So
that
way
we
don't
have
any
inconsistencies.
B
Yeah,
well,
I'm
not
totally
sure
that
ie
is
the
reason
why
we
have
ping
fallbacks
for
svgs,
I'm
not
sure
where
that
browser
cutoff
is
but
yeah,
obviously
just
hey,
also
related
to
front-end
stuff
like
this
is
also
something
so
sorry.
C
I'm
gonna
bounce
yeah,
so
I
I
could
mention
that
it
occurred
to
me
that
we
were
introducing
a
new
icon
and
originally
the
icon
is
only
necessary
for
arctic
theme,
and
I
I
at
one
point
in
this
module
history.
I
put
the
icon
in
the
core,
the
contrib
or
the
comment,
module
thinking
that
maybe
other
themes
would
want
to
use
it.
C
That's
started
to
open
up
a
new
discussion
which
I
decided
I
we
maybe
didn't
want
to
get
into,
so
I
just
put
the
the
icon
into
basis
where
it's
needed,
but
I
I
wouldn't
mind
feedback
like.
If
we're
adding
an
icon
to
core,
would
it
be
good
to
put
it
somewhere
where
it
can
be
used
by
other
things,
or
in
this
case,
is
it
appropriate
to
keep
it
just
where
it's
needed
in
places.
B
It's
a
a
crazy
idea.
I'm
not
sure
that
that
you
like
it,
so
we
literally
aren't
only
adding
the
image
in
bartik.
Is
that
what
you're
saying
basis
oh
and
basis?
Oh
okay,
yeah?
Well,
that
that's
a
little
bit
different,
but
does
a
that's
a
weird
suggestion?
B
B
A
A
I
think
that
using
an
image
is
probably
best
for
consistency,
but
yeah,
I
think,
especially
if
we're
putting
an
invasives
and
basis
might
be
around
for
a
while.
We
should
have
to
fall
back
in
there
for
now
and
then
later
we
can
go
and
do
some
cleanup
and
remove
it
when
we
decide
to
do
that
everywhere,
and
I
think
that
messages
css
was
also
overridden
basis
in
the
same
way,
and
that's
where
I
got
the
example
from
where
we
have
the
other
svgs.
B
B
Okay,
let's
see.
B
B
Okay,
great,
that
is
just
a
pull
request
that
needs
to
review
yeah.
I
won't
go
into
it
more
than
that.
Let's
see
one
more
thing
from
you:
jen
field
group
functionality
issue
647.
Do
we
have
any
updates
on
that
issue?
I.
A
B
Okay,
let's
see
tim's
asking
in
the
chat,
did
I
miss
a
volunteer
to
help
with
the
tests
on
the
common
title
issue
or
a
volunteer
to
help?
Teach
me?
No,
there
wasn't
any
there.
Wasn't
any
volunteers
active
but
I'll
put
it
out
there
any
any
volunteers
for
helping
with
the
comment.
Titles.
C
B
Okay,
thanks
jen
all
right
and
then
lastly,
in
123,
we've
got
the
entity
reference
module
issue
1301,
the
herb
dual
is
the
advocate
for
hasn't,
had
any
activity
in
several
weeks
now,
which
is
unfortunate
because
it's
it's
it's
right
there,
and
so
I
posted
a
comment
today.
Just
saying
hey
like
could
we
try,
like?
Are
people
open
to
the
idea
that
we
could
merge
in
what
we
have
right
now?
B
The
pull
request,
literally
as
it
exists
right
now,
and
then
cherry
pick
in
the
three
additional
commits
that
are
in
the
contrib
module.
That
way,
herb
doesn't
have
to
go
through
the
work
of
doing
the
the
acrobats
acrobatics
necessary
to
like
maintain
the
entire
git
history
and
then
make
a
pull
request
out
of
that.
So
if
that
helps
to
move
things
along
and
seems
fine
to
people,
then
that
would
be
wonderful,
but
yeah,
also
just
generally
like
more
overall
review
of
the
entire
project
wouldn't
hurt.
B
B
I
do
kind
of
feel
like
it's
that
kind
of
moment.
You
know
where
this
is
a
massive
amount
of
new
code,
but
yeah
that
attitude,
I
don't
think
is-
is
actually
horrible
either,
because
this
is
ten
thousand
lines
of
code
that
have
been
used
in
contrib
and
is
one
of
our
most
popular
contrib
modules.
So
it's
already
out
there
it's
already
being
used
and
actually
the
less.
We
change
the
less
risk
we're
incurring
here.
B
So
so
I'm
in
favor
of
of
moving
things
in,
as
as
we
have
them
now
anyway,
so
that
issue
yeah
could
use
some
use
some
feedback,
but
I'm
also
just
waiting
to
see
if
what
herb
thinks
about
the
idea
of
just
moving
things
in,
as
is,
and
that's
it
for
the
123
status
report
yeah,
I
guess
that's
it
for
today.
Do
you
guys
have
anything
else?
You'd
want
to
bring
up
or
discuss.
C
Well,
I'd
be
remiss
if
I
didn't
bring
a
backdrop
live
at
the
very
minimum
and
up
just
a
reminder
to
everybody
that
we
we
really
just
got
down
to
pushing
registrations
and
outreach
pretty
hard
this
week
the
registration
is
open.
The.
C
Yeah
the
schedule
is
up
and
we
have
like
10
or
15
topics
already
on
there.
We
are
looking
for
more
nate.
Can
I
put
you
on
the
spot?
Do
we
just
want
to
do
the
same
thing
with
the
core
update,
or
did
you
have
any
any
reason
you
want
to
change
the
schedule
or
the
the
way
that
works,
or
do
you
want
to
think
about
that
and
get
back
to
me.
B
Yeah
I'll
think
about
it.
I
think
I
had
something
else
possibly
to
cover
instead,
but
I
don't
know-
maybe
maybe
that
would
just
be
a
separate
session
as
well
so
yeah,
I
guess
core
update,
is
probably
inevitable
that
I'll
that'll
do
that.
One.
C
So
for
now
it
I
just
I
went
ahead
and
put
it
on
the
schedule
in
the
same
spot,
just
to
help
seed
the
skin
that
the
schedule
the
schedule's
getting
full
enough,
though,
that
if
you
prefer,
I
could
take
it
off
until
you
make
a
decision
either
way
anyways.
So
there
there's
that
anybody
else
has
a
topic
or
ideas
or
stats
or
sessions
they
want
to
do.
C
Please
let
us
know,
please
help
promote
it.
We
really
need
people
to
get
the
word
out.
This
is
our
our
big
opportunity,
every
four
months
to
really
engage
with
the
community
and
talk
about
new
things.
C
A
B
All
right:
well,
let's
wrap
it
up
for
today,
thanks
everybody
for
being
present
and
thanks
for
all
of
the
work,
as
always
yeah,
it's
exciting.
Moving
these
things
forward.
The
entity,
references,
huge
thing,
that'll
be
very
exciting
if
that
that
goes
in
it'll
be
a
headline
feature
for
123
for
sure.
So.
C
You
know
what
I
had
another
thought
before
about
backprop
live,
but
we
we
had
talked
at
one
point
about
having
a
fee,
a
discussion
about
planning
for
the
next
release.
I
think
that
maybe
that
has
been
less
urgent
just
because
we
have.
We
have
kind
of
a
big
agenda
already
so
yeah.
B
C
And,
to
some
extent
it
sort
of
happened
naturally,
so
that
doesn't
bother
me,
but
I
thought
I
would
bring
that
up
now,
because
you
know
there
that
might
be
something
to
think
about.
In
terms
of
backdrop
life
is
that
maybe,
instead
of
trying
to
do
anything
during
our
weekly
meetings
that
we
think
about,
if
there
is
some
planning
we
want
to
do,
how
can
we
incorporate
that
into
the
background
live
schedule?
So
we
don't.
I
don't
need
an
answer
on
that
right
now,
but.
B
Yeah,
that's
a
great
idea,
yeah,
it's
possible
that
a
couple
of
these
things.
Hopefully
you
know
like
comment,
titles
and
there's
one
that
we
have,
that
we
didn't
talk
about
the
custom,
validation
messages
and
there's
actually
another
one.
That's
already
rtbc.
B
I
can't
I
can't
remember
quite
what
it
is.
It's
a
it's
a
alter
hook
of
some
kind,
that
is
an
api
expansion
that
robert
worked
on.
A
B
What
I'm
getting
at
is
that
there's
a
bunch
of
issues
that
are
nearing
completion
right
now
for
123
that,
even
if
those
were
to
be
completed
like
yeah
123
is
gonna
look
great,
but
we're
like
halfway
through
the
cycle-
and
so
it's
like
what's
about
to
happen-
is
that
I
hope
those
issues
all
wrap
up
and
then
we're
not
going
to
have
any
other
123
open
tickets.
Wouldn't
that
be
neat
so
so
yeah.
We
definitely
have
the
opportunity
here
to
like
pursue
some
additional
items
for
for
this
release:
okay,
yeah.
C
Okay,
well
think
about
how
you
want
to
handle
that,
and
if
you
just
want
to
do
that
in
the
core
development
update
or
for
something
else,
okay
yeah,
we
did.
I
think
we
just
implemented
the
survey
at
the
last
about
the
time
of
the
last
factor
up
live
on
the
forum,
and
so
I
think
we
were
just
starting
to
get
feedback
or
had
gotten
some
feedback
already
we
got
more
after
backdrop.
C
Live
it's
been
pretty
just
so
everybody
knows
it's
been
pretty
static
for
the
last
month,
like
almost
no
change
in
that
survey,
maybe
one
or
two
new
people
participated,
but
every
once
in
a
while,
I
post
sort
of
the
top
ten
issues
in
that
survey
in
zulu,
but
yeah
just
to
throw
that
out.
There
is
a
data
point
and
if
there's
anything,
we
want
to
do
with
that
before
backdrop
live
now's
the
time
to
think
about
it.
B
Okay,
all
right!
Well,
let's
wrap
up
for
today,
thanks
again
to
everybody
and
we'll
see
everybody
next
week.
Thank
you.
Bye.